where is my disk space

classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

Long Wind-2

for reason i don't know, i see your reply just an hour ago, sorry for delay!

i'm not sure if power key is key on keyboard or button on PC case
i'm afraid the bug not only use all disk, but also take cpu resource, it slow system
i'm not energetic enough to debug it
i have other choice, i have buster, jessie, stretch on another disk that seems ok

i hope info below help

tail -100 /mnt/dos/home/zhou/.local/share/xorg/Xorg.0.log.old
[ 726.014] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.014] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.014] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.014] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.014] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.014] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.014] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.014] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.015] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.016] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.016] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.016] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.016] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.016] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.016] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.018] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.018] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.018] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.018] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.018] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.018] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.018] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.018] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.018] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.018] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.019] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.019] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.019] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.019] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.019] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.019] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.020] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.020] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.020] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.020] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.020] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.020] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.020] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.020] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.020] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.020] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.020] (**) Option "fd" "31"
[ 726.021] (EE) libinput bug: Key 116 is down 75 times.
[ 726.021] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 726.021] (EE) libinput bug: Releasing key 116 failed.
[ 726.023] (**) Option "fd" "26"
[ 726.033] (**) Option "fd" "28"
[ 726.034] (**) Option "fd" "30"
[ 726.132] (II) UnloadModule: "libinput"
[ 726.132] (II) systemd-logind: not releasing fd for 13:69, still in use
[ 726.132] (II) UnloadModule: "libinput"
[ 726.132] (II) systemd-logind: not releasing fd for 13:65, still in use
[ 726.132] (II) UnloadModule: "libinput"
[ 726.132] (II) systemd-logind: not releasing fd for 13:67, still in use
[ 726.132] (II) UnloadModule: "libinput"
[ 726.132] (II) systemd-logind: releasing fd for 13:73
[ 726.364] (II) UnloadModule: "libinput"
[ 726.364] (II) systemd-logind: releasing fd for 13:69
[ 726.364] (EE) systemd-logind: failed to release device: Connection was disconnected before a reply was received
[ 726.364] (II) UnloadModule: "libinput"
[ 726.364] (II) systemd-logind: releasing fd for 13:68
[ 726.364] (EE) systemd-logind: failed to release device: Connection is closed
[ 726.364] (II) UnloadModule: "libinput"
[ 726.364] (II) systemd-logind: releasing fd for 13:65
[ 726.364] (EE) systemd-logind: failed to release device: Connection is closed
[ 726.365] (II) UnloadModule: "libinput"
[ 726.365] (II) systemd-logind: releasing fd for 13:64
[ 726.365] (EE) systemd-logind: failed to release device: Connection is closed
[ 726.365] (II) UnloadModule: "libinput"
[ 726.365] (II) systemd-logind: releasing fd for 13:67
[ 726.365] (EE) systemd-logind: failed to release device: Connection is closed
[ 726.365] (II) UnloadModule: "libinput"
[ 726.365] (II) systemd-logind: releasing fd for 13:66
[ 726.365] (EE) systemd-logind: failed to release device: Connection is closed
[ 726.365] (II) UnloadModule: "libinput"
[ 726.365] (II) systemd-logind: releasing fd for 13:70
[ 726.365] (EE) systemd-logind: failed to release device: Connection is closed
[ 726.365] (II) UnloadModule: "libinput"
[ 726.365] (II) systemd-logind: releasing fd for 13:71
[ 726.365] (EE) systemd-logind: failed to release device: Connection is closed
[ 726.373] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[ 726.373] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[ 726.373] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[ 726.373] (EE) systemd-logind: ReleaseControl failed: Connection is closed
[ 726.373] (II) Server terminated successfully (0). Closing log file.



On Tuesday, August 6, 2019, 8:04:32 AM GMT+8, David Wright <[hidden email]> wrote:


On Mon 05 Aug 2019 at 16:33:29 (-0000), Curt wrote:

> On 2019-08-05, davidson <[hidden email]> wrote:
> >
> > To me it looks like the log below is telling you that your power key
> > was either being held down or stuck in that position.
> >
> > That is all.
>
> Whatever libinput is trying to say is apparently repeated to the point
> where I would consider the repetition itself to be a form of bug,
> whether the power key is going haywire or not (which Long doesn't
> mention as a vector of particular concern).

#define KEY_POWER        116        /* SC System Power Down */

doesn't give me much of a clue as to what sort of power key this is,
but from the company is keeps I'd guess it might be for powering
down a Sound Card. We know the OP watches TV through a sound card,
and has wished to shut it up when the computer is switched off.
Perhaps it's something to do with that.

As for key repetition: the OP has communicated here on this topic
before. Could the problem be self-inflicted: it wouldn't necessarily
be noticed if only Xorg.0.log grew, because restarting X would clean
the directory of all but two generations. However, that third file,
Xorg.1.log, is not going to get cleaned until a second simultaneous
X server has been run twice. The lack of any Xorg.1.log.old suggests
that this is not the OP's habit.


> So if the power key goose is wild (or "fixing" the incriminated key is
> impractical for one reason or another), how do we get libinput to shut
> its redundant trap?


That depends. If you can't restart X because of what's running, one
method might be to chattr +i, though that leaves a large file in
place which might mean moving things around to make room.

If the problem keeps recurring, but you don't want to have to fix it
in haste, then you could try linking ~/.local/share/xorg to a small
spare partition that you can allow to fill up. If you're running
Xserver as root, you can set -logfile there instead.

You might try experimenting with -logverbose which defaults to 3.
No idea what range of values might be allowed or suitable.

Cheers,
David.


Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

David Wright-3
On Mon 12 Aug 2019 at 07:59:03 (+0000), Long Wind wrote:
>  
> for reason i don't know, i see your reply just an hour ago, sorry for delay!
>
> i'm not sure if power key is key on keyboard or button on PC case

If the one on the PC case got stuck, I would expect the machine to
power down. So look for a key on the keyboard. As I said, I can only
guess that it powers down the Sound Card, perhaps to save energy.

> i'm afraid the bug not only use all disk, but also take cpu resource, it slow system
> i'm not energetic enough to debug it
> i have other choice, i have buster, jessie, stretch on another disk that seems ok
>
> i hope info below help

It confirms what you posted before. Swapping keyboards may be helpful
in diagnosing the cause. It might be the only solution too. Otherwise,
I can only reiterate my suggestions for masking the symptoms.

> tail -100 /mnt/dos/home/zhou/.local/share/xorg/Xorg.0.log.old
> [ 726.014] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[…]
> [ 726.020] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 726.020] (**) Option "fd" "31"
> [ 726.021] (EE) libinput bug: Key 116 is down 75 times.
> [ 726.021] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 726.021] (EE) libinput bug: Releasing key 116 failed.

116 agrees with KEY_POWER in the source file.

Cheers,
David.

Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

Long Wind-2

i don't think swapping keyboard will help
i use buster/jessie with same keyboard, it's OK
as log shows, problem is with software, not with my hardware
easy solution for me is install buster over it.

many of list mail go to spam folder of yahoo mail
that may explain why i can't read mail on time
On Monday, August 12, 2019, 10:42:02 PM GMT+8, David Wright <[hidden email]> wrote:


On Mon 12 Aug 2019 at 07:59:03 (+0000), Long Wind wrote:

> for reason i don't know, i see your reply just an hour ago, sorry for delay!
>
> i'm not sure if power key is key on keyboard or button on PC case

If the one on the PC case got stuck, I would expect the machine to
power down. So look for a key on the keyboard. As I said, I can only
guess that it powers down the Sound Card, perhaps to save energy.

> i'm afraid the bug not only use all disk, but also take cpu resource, it slow system
> i'm not energetic enough to debug it
> i have other choice, i have buster, jessie, stretch on another disk that seems ok
>
> i hope info below help

It confirms what you posted before. Swapping keyboards may be helpful
in diagnosing the cause. It might be the only solution too. Otherwise,
I can only reiterate my suggestions for masking the symptoms.

> tail -100 /mnt/dos/home/zhou/.local/share/xorg/Xorg.0.log.old
> [ 726.014] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[…]
> [ 726.020] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 726.020] (**) Option "fd" "31"
> [ 726.021] (EE) libinput bug: Key 116 is down 75 times.
> [ 726.021] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 726.021] (EE) libinput bug: Releasing key 116 failed.

116 agrees with KEY_POWER in the source file.


Cheers,
David.

12