Re: Just had to reset/reboot again, total loss of keyboard & mouse
On Saturday 18 May 2019 12:52:40 am Felix Miata wrote:
> Gene Heskett composed on 2019-05-17 23:16 (UTC-0400):
> > The first thing I saw as it rebooted was some msgs about hid-common
> > This was before recovering the journal on the boot drive.
> >
> > So I at least has a clue where the crash is occurring, hid-common.
> >
> > What else can I do to nail this down good enough for a bug report?
> > sudo grep -R hid-common /var/log/*
> > doesn't give a clue.
>
> On what, Stretch?
yes
> Does /var/log/journal/ exist?
no, should it?
> If it does, try:
>
> journalctl | grep hid-common
which says I should sudo it, and when I do, grep only finds itself in 3
stanza's with wrong syntax on the 2nd invocation:
COMMAND=/bin/grep -Rhid-common
I'll see if /etc/journal exists but doesn't
a root@coyote:etc$ grep -R log= * shows:
systemd/journald.conf:#ForwardToSyslog=yes
systemd/journald.conf:#MaxLevelSyslog=debug
So I'd assume anything would be sent to syslog. And its pretty verbose
at times.
I did find this in the syslog by scanning backwards in tails output:
May 17 22:46:35 coyote kernel: [ 5.491350] hid-generic
0003:050D:0751.0001: unknown main item tag 0x1
May 17 22:46:35 coyote kernel: [ 5.491899] hid-generic
0003:050D:0751.0001: unbalanced collection at end of report description
May 17 22:46:35 coyote kernel: [ 5.491964] hid-generic: probe of
0003:050D:0751.0001 failed with error -22
But I haven't found 050D:0751 yet. Ahh, it is my Belkin UPS, and nut
appears to be working correctly?
It appears modemmanager could be removed:
May 17 22:46:43 coyote ModemManager[617]: <info> Couldn't check support
for device at '/sys/devices/pci0000:00/0000:00:08.0': not supported by
any plugin
May 17 22:46:43 coyote ModemManager[617]: <info> Couldn't check support
for device at '/sys/devices/pci0000:00/0000:00:09.0': not supported by
any plugin
Removed.
And that syslog is being spammed by:
May 17 22:50:03 coyote kernel: [ 242.370661] INFO: task hpfax:1229
blocked for more than 120 seconds.
May 17 22:50:03 coyote kernel: [ 242.370669] Not tainted
4.9.0-9-rt-amd64 #1 Debian 4.9.168-1+deb9u2
May 17 22:50:03 coyote kernel: [ 242.370672] "echo 0
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 17 22:50:03 coyote kernel: [ 242.370675] hpfax D 0
1229 1 0x00000004
May 17 22:50:03 coyote kernel: [ 242.370680] ffff9b547009ec00
0000000000000000 ffff9b547fce9a00 ffff9b5474a6ba00
May 17 22:50:03 coyote kernel: [ 242.370684] ffff9b5475a12b80
ffffb371c1f0bcc8 ffffffffab639ba5 00ffb371c1f0bda0
May 17 22:50:03 coyote kernel: [ 242.370687] ffff9b547fce9a00
ffffffffab0a9b01 ffff9b5474a6ba00 0000000000000000
May 17 22:50:03 coyote kernel: [ 242.370690] Call Trace:
May 17 22:50:03 coyote kernel: [ 242.370698] [<ffffffffab639ba5>] ?
__schedule+0x275/0x5d0
May 17 22:50:03 coyote kernel: [ 242.370702] [<ffffffffab0a9b01>] ?
__raw_spin_unlock+0x11/0x50
May 17 22:50:03 coyote kernel: [ 242.370704] [<ffffffffab639f43>] ?
schedule+0x43/0xd0
May 17 22:50:03 coyote kernel: [ 242.370709] [<ffffffffab63b918>] ?
__rt_mutex_slowlock+0xb8/0x140
May 17 22:50:03 coyote kernel: [ 242.370711] [<ffffffffab63bd9b>] ?
rt_mutex_slowlock_locked+0xbb/0x220
May 17 22:50:03 coyote kernel: [ 242.370714] [<ffffffffab63bf75>] ?
rt_mutex_slowlock+0x75/0xc0
May 17 22:50:03 coyote kernel: [ 242.370718] [<ffffffffc04be545>] ?
pp_ioctl+0x35/0x910 [ppdev]
May 17 22:50:03 coyote kernel: [ 242.370722] [<ffffffffab230e92>] ?
do_vfs_ioctl+0xa2/0x620
May 17 22:50:03 coyote kernel: [ 242.370724] [<ffffffffab231484>] ?
SyS_ioctl+0x74/0x80
May 17 22:50:03 coyote kernel: [ 242.370728] [<ffffffffab003ca5>] ?
do_syscall_64+0x75/0x110
May 17 22:50:03 coyote kernel: [ 242.370730] [<ffffffffab63e5ce>] ?
entry_SYSCALL_64_after_swapgs+0x58/0xc6
May 17 22:52:04 coyote kernel: [ 363.206449] INFO: task hpfax:1229
blocked for more than 120 seconds.
May 17 22:52:04 coyote kernel: [ 363.206457] Not tainted
4.9.0-9-rt-amd64 #1 Debian 4.9.168-1+deb9u2
May 17 22:52:04 coyote kernel: [ 363.206459] "echo 0
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 17 22:52:04 coyote kernel: [ 363.206462] hpfax D 0
1229 1 0x00000004
May 17 22:52:04 coyote kernel: [ 363.206467] ffff9b547009ec00
0000000000000000 ffff9b547fce9a00 ffff9b5474a6ba00
May 17 22:52:04 coyote kernel: [ 363.206471] ffff9b5475a12b80
ffffb371c1f0bcc8 ffffffffab639ba5 00ffb371c1f0bda0
May 17 22:52:04 coyote kernel: [ 363.206474] ffff9b547fce9a00
ffffffffab0a9b01 ffff9b5474a6ba00 0000000000000000
May 17 22:52:04 coyote kernel: [ 363.206478] Call Trace:
May 17 22:52:04 coyote kernel: [ 363.206485] [<ffffffffab639ba5>] ?
__schedule+0x275/0x5d0
May 17 22:52:04 coyote kernel: [ 363.206489] [<ffffffffab0a9b01>] ?
__raw_spin_unlock+0x11/0x50
May 17 22:52:04 coyote kernel: [ 363.206491] [<ffffffffab639f43>] ?
schedule+0x43/0xd0
May 17 22:52:04 coyote kernel: [ 363.206495] [<ffffffffab63b918>] ?
__rt_mutex_slowlock+0xb8/0x140
May 17 22:52:04 coyote kernel: [ 363.206497] [<ffffffffab63bd9b>] ?
rt_mutex_slowlock_locked+0xbb/0x220
May 17 22:52:04 coyote kernel: [ 363.206499] [<ffffffffab63bf75>] ?
rt_mutex_slowlock+0x75/0xc0
May 17 22:52:04 coyote kernel: [ 363.206503] [<ffffffffc04be545>] ?
pp_ioctl+0x35/0x910 [ppdev]
May 17 22:52:04 coyote kernel: [ 363.206506] [<ffffffffab230e92>] ?
do_vfs_ioctl+0xa2/0x620
May 17 22:52:04 coyote kernel: [ 363.206509] [<ffffffffab231484>] ?
SyS_ioctl+0x74/0x80
May 17 22:52:04 coyote kernel: [ 363.206512] [<ffffffffab003ca5>] ?
do_syscall_64+0x75/0x110
May 17 22:52:04 coyote kernel: [ 363.206515] [<ffffffffab63e5ce>] ?
entry_SYSCALL_64_after_swapgs+0x58/0xc6
must be 20 of them since that reboot, and hpfax cannot found as
installed! There is a fax utility from tde, but removing it, removes
tde. All of it.
And several boatloads of certificates revoked, or untrusted like for FUSE
which I use heavily here.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: