Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #208764 > unrolled thread

Just had to reset/reboot again, total loss of keyboard & mouse

Back to article view | Back to linux.debian.user

Contents

  Just had to reset/reboot again, total loss of keyboard & mouse Gene Heskett <gheskett@shentel.net> - 2019-05-18 05:20 +0200
    Re: Just had to reset/reboot again, total loss of keyboard & mouse Felix Miata <mrmazda@earthlink.net> - 2019-05-18 07:00 +0200
      Re: Just had to reset/reboot again, total loss of keyboard & mouse Gene Heskett <gheskett@shentel.net> - 2019-05-18 09:50 +0200
        Re: Just had to reset/reboot again, total loss of keyboard & mouse Felix Miata <mrmazda@earthlink.net> - 2019-05-18 10:20 +0200
          Re: Just had to reset/reboot again, total loss of keyboard & mouse Gene Heskett <gheskett@shentel.net> - 2019-05-18 16:40 +0200
            Re: Just had to reset/reboot again, total loss of keyboard & mouse Greg Wooledge <wooledg@eeg.ccf.org> - 2019-05-20 15:00 +0200
              Re: Just had to reset/reboot again, total loss of keyboard & mouse Gene Heskett <gheskett@shentel.net> - 2019-05-20 15:40 +0200
    Re: Just had to reset/reboot again, total loss of keyboard & mouse Henrique de Moraes Holschuh <hmh@debian.org> - 2019-05-18 14:20 +0200
      [OT] ext4 corruption (was: Re: Just had to reset/reboot again, total  loss of keyboard & mouse) Reco <recoverym4n@enotuniq.net> - 2019-05-18 14:30 +0200
        Re: [OT] ext4 corruption (was: Re: Just had to reset/reboot again,  total loss of keyboard & mouse) Curt <curty@free.fr> - 2019-05-18 15:10 +0200
          Re: [OT] ext4 corruption (was: Re: Just had to reset/reboot again,  total loss of keyboard & mouse) Henrique de Moraes Holschuh <hmh@debian.org> - 2019-05-18 16:30 +0200
        Re: [OT] ext4 corruption (was: Re: Just had to reset/reboot again,  total loss of keyboard & mouse) Henrique de Moraes Holschuh <hmh@debian.org> - 2019-05-18 16:20 +0200
      Re: Just had to reset/reboot again, total loss of keyboard & mouse Gene Heskett <gheskett@shentel.net> - 2019-05-18 17:20 +0200
        Re: Just had to reset/reboot again, total loss of keyboard & mouse Felix Miata <mrmazda@earthlink.net> - 2019-05-18 20:10 +0200
      Re: Just had to reset/reboot again, total loss of keyboard & mouse Gene Heskett <gheskett@shentel.net> - 2019-05-18 17:50 +0200

#208764 — Just had to reset/reboot again, total loss of keyboard & mouse

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.

Thanks all.

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>

[toc] | [next] | [standalone]

#208766

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? Does /var/log/journal/ exist? If it does, try:

	journalctl | grep hid-common
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#208774

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>

[toc] | [prev] | [next] | [standalone]

#208775

Gene Heskett composed on 2019-05-18 03:46 (UTC-0400):

> Felix Miata wrote:

>> Does /var/log/journal/ exist?

> no, should it?

It's the home of the optional persistent systemd journal. The option is configured
simply by its presence or not. I resisted it for several years, but no more since
over a year ago.

>> 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

"If it exists". Dunno what's expected when it doesn't exist.

You seem to have picked up youngster's misusage of English. "3 stanzas" do not
possess "with wrong syntax". :-D
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#208797

On Saturday 18 May 2019 04:15:32 am Felix Miata wrote:

> Gene Heskett composed on 2019-05-18 03:46 (UTC-0400):
> > Felix Miata wrote:
> >> Does /var/log/journal/ exist?
> >
> > no, should it?
>
> It's the home of the optional persistent systemd journal. The option
> is configured simply by its presence or not. I resisted it for several
> years, but no more since over a year ago.
>
> >> 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
>
> "If it exists". Dunno what's expected when it doesn't exist.
>
> You seem to have picked up youngster's misusage of English. "3
> stanzas" do not possess "with wrong syntax". :-D

Sure they do, journalctl actually finds 6 instances of grep with slightly 
different syntax, I assume to catch all the corner cases.

I only copy/pasted the obviously wrong one above. The lack of a space 
between the -R and the name its searching for is a syntax error, or 
should be, but was not reported as such. Here is the complete output of 
that command:

root@coyote:~$ journalctl | grep hid-common

May 17 23:08:14 coyote sudo[5114]:     gene : TTY=pts/6 ; 
PWD=/home/gene ; USER=root ; COMMAND=/bin/grep 
hid-common /var/log/syslog

May 17 23:08:44 coyote sudo[5132]:     gene : TTY=pts/6 ; 
PWD=/home/gene ; USER=root ; COMMAND=/bin/grep 
hid-common /var/log/syslog

May 17 23:11:13 coyote sudo[5204]:     gene : TTY=pts/6 ; PWD=/var/log ; 
USER=root ; COMMAND=/bin/grep hid-common kern.log

May 17 23:11:58 coyote sudo[5225]:     gene : TTY=pts/6 ; PWD=/var/log ; 
USER=root ; COMMAND=/bin/grep hid-common alternatives.log amanda apache2 
apt apt-cacher-ng aptitude auth.log auth.log.1 auth.log.2.gz 
bootstrap.log btmp clamav cups daemon.log daemon.log.1 daemon.log.2.gz 
debug debug.1 debug.2.gz dmesg dpkg.log exim4 faillog fontconfig.log 
fsck hp httpd installer kern.log kern.log.1 kern.log.2.gz lastlog 
lightdm lpr.log lpr.log.1 lpr.log.2.gz mail.err mail.err.1 mail.err.2.gz 
mail.info mail.info.1 mail.info.2.gz mail.log mail.log.1 mail.log.2.gz 
mail.warn mail.warn.1 mail.warn.2.gz messages messages.1 messages.2.gz 
samba speech-dispatcher syslog syslog.1 syslog.2.gz syslog.3.gz 
syslog.4.gz syslog.5.gz syslog.6.gz syslog.7.gz tdm.log tdm.log.1 
tdm.log.2.gz tdm.log.3.gz tdm.log.4.gz unattended-upgrades user.log 
user.log.1 user.log.2.gz wtmp Xorg.0.log Xorg.0.log.old Xorg.1.log

May 17 23:12:39 coyote sudo[5567]:     gene : TTY=pts/6 ; PWD=/var/log ; 
USER=root ; COMMAND=/bin/grep -Rhid-common alternatives.log amanda 
apache2 apt apt-cacher-ng aptitude auth.log auth.log.1 auth.log.2.gz 
bootstrap.log btmp clamav cups daemon.log daemon.log.1 daemon.log.2.gz 
debug debug.1 debug.2.gz dmesg dpkg.log exim4 faillog fontconfig.log 
fsck hp httpd installer kern.log kern.log.1 kern.log.2.gz lastlog 
lightdm lpr.log lpr.log.1 lpr.log.2.gz mail.err mail.err.1 mail.err.2.gz 
mail.info mail.info.1 mail.info.2.gz mail.log mail.log.1 mail.log.2.gz 
mail.warn mail.warn.1 mail.warn.2.gz messages messages.1 messages.2.gz 
samba speech-dispatcher syslog syslog.1 syslog.2.gz syslog.3.gz 
syslog.4.gz syslog.5.gz syslog.6.gz syslog.7.gz tdm.log tdm.log.1 
tdm.log.2.gz tdm.log.3.gz tdm.log.4.gz unattended-upgrades user.log 
user.log.1 user.log.2.gz wtmp Xorg.0.log Xorg.0.log.old Xorg.1.log

May 17 23:12:53 coyote sudo[5979]:     gene : TTY=pts/6 ; PWD=/var/log ; 
USER=root ; COMMAND=/bin/grep -R hid-common alternatives.log amanda 
apache2 apt apt-cacher-ng aptitude auth.log auth.log.1 auth.log.2.gz 
bootstrap.log btmp clamav cups daemon.log daemon.log.1 daemon.log.2.gz 
debug debug.1 debug.2.gz dmesg dpkg.log exim4 faillog fontconfig.log 
fsck hp httpd installer kern.log kern.log.1 kern.log.2.gz lastlog 
lightdm lpr.log lpr.log.1 lpr.log.2.gz mail.err mail.err.1 mail.err.2.gz 
mail.info mail.info.1 mail.info.2.gz mail.log mail.log.1 mail.log.2.gz 
mail.warn mail.warn.1 mail.warn.2.gz messages messages.1 messages.2.gz 
samba speech-dispatcher syslog syslog.1 syslog.2.gz syslog.3.gz 
syslog.4.gz syslog.5.gz syslog.6.gz syslog.7.gz tdm.log tdm.log.1 
tdm.log.2.gz tdm.log.3.gz tdm.log.4.gz unattended-upgrades user.log 
user.log.1 user.log.2.gz wtmp Xorg.0.log Xorg.0.log.old Xorg.1.log

Wordwrap screws it all up, so I put a line feed between instances.

At 84, I think I do understand English, but it has more modifiers and 
variations that any other fairly common language on this ball of rock 
and water we arbitrarily call a planet.

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>

[toc] | [prev] | [next] | [standalone]

#208897

> On Saturday 18 May 2019 04:15:32 am Felix Miata wrote:
> > >> Does /var/log/journal/ exist?
> > >> If it does, try:
> > >>
> > >> 	journalctl | grep hid-common


On Sat, May 18, 2019 at 10:35:29AM -0400, Gene Heskett wrote:
> Sure they do, journalctl actually finds 6 instances of grep with slightly 
> different syntax, I assume to catch all the corner cases.

> May 17 23:08:14 coyote sudo[5114]:     gene : TTY=pts/6 ; 
> PWD=/home/gene ; USER=root ; COMMAND=/bin/grep 
> hid-common /var/log/syslog

Gene, you're missing the forest for the trees.  The goal was to find
any meaningful logged messages with hid-common in them, in order to
diagnose your issues with keyboard and mouse.

But you manually ran some commands with hid-common in them using sudo, and
so those were logged, and now you're picking up those results in the log.
Those are all irrelevant.  They're just photos of you looking for clues,
not actual clues.

In any case, if you did not create a /var/log/journal directory, there is
no persistent journal.  Which means it doesn't save the journal between
reboots (it only lives in RAM).  That's the default behavior, for reasons
I cannot guess.  If you want to change it, there are instructions in
systemd-journald(8).

In order for Felix's commands to be useful, you would have to create
the persistent journal location, boot into the kernel that's having the
problems, shut down cleanly enough that the journal gets saved to disk,
then reboot into the working kernel so you can search the persistent
journal from the broken boot.

[toc] | [prev] | [next] | [standalone]

#208900

On Monday 20 May 2019 08:51:42 am Greg Wooledge wrote:

> > On Saturday 18 May 2019 04:15:32 am Felix Miata wrote:
> > > >> Does /var/log/journal/ exist?
> > > >> If it does, try:
> > > >>
> > > >> 	journalctl | grep hid-common
>
> On Sat, May 18, 2019 at 10:35:29AM -0400, Gene Heskett wrote:
> > Sure they do, journalctl actually finds 6 instances of grep with
> > slightly different syntax, I assume to catch all the corner cases.
> >
> > May 17 23:08:14 coyote sudo[5114]:     gene : TTY=pts/6 ;
> > PWD=/home/gene ; USER=root ; COMMAND=/bin/grep
> > hid-common /var/log/syslog
>
> Gene, you're missing the forest for the trees.  The goal was to find
> any meaningful logged messages with hid-common in them, in order to
> diagnose your issues with keyboard and mouse.
>
> But you manually ran some commands with hid-common in them using sudo,
> and so those were logged, and now you're picking up those results in
> the log. Those are all irrelevant.  They're just photos of you looking
> for clues, not actual clues.
>
> In any case, if you did not create a /var/log/journal directory, there
> is no persistent journal.  Which means it doesn't save the journal
> between reboots (it only lives in RAM).  That's the default behavior,
> for reasons I cannot guess.  If you want to change it, there are
> instructions in systemd-journald(8).
>
> In order for Felix's commands to be useful, you would have to create
> the persistent journal location, boot into the kernel that's having
> the problems, shut down cleanly enough that the journal gets saved to
> disk, then reboot into the working kernel so you can search the
> persistent journal from the broken boot.

What I haven't reported was that I did find in a bootup section of the 
log, and odd looking reference to hpfax from the trinity install, which 
I reported to the trinity list.  And the reply there was to rename it, 
and if that solved the problem, then nuke it.  I renamed it to hpfox 
last Wednesday, and have had no further trouble with the whole usb tree 
dying since. This is Monday already.

its  part of hplip, but its like N-M, its been relinked and can't be 
removed without taking the whole desktop with it.

So in order to run a dhcpd free host file system which is what I have 
done here for much of 30 years going clear back into my Amiga days, 
using static defined addresses for all the local net, the only thing you 
can do to stop N-M from tearing down a working network is to setup 
the /e.n/i.d/whatever name with the correct static data, and immediately 
chattr +i it so N-M can't tear it down, ditto for the link called 
resolv.conf. Nuke it, touch a real file by that name then edit the 
nameserver stuff into it, and chattr +i it, again so N-M can't tear it 
down. When N-M has been made to leave a net setup labeled "static" alone 
I'll certainly celebrate. But that hasn't happened in the armbian world 
yet.

So unless you make a living sending faxes, rename hpfax to something 
else, others have had the same problems with it. IOW.its a knowm 
troublemaker. So now it has been reported. FWIW, my cpu is running 10C 
cooler too.

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>

[toc] | [prev] | [next] | [standalone]

#208786

On Fri, 17 May 2019, Gene Heskett wrote:
> The first thing I saw as it rebooted was some msgs about hid-common
> This was before recovering the journal on the boot drive.

That's a core component of the Linux *kernel* HID (human interface
device) subsystem.

You need, for a bug report:

1. the *exact* kernel version installed (where you got it from, its full
   version information)
2. stack of loaded modules (output of lsmod)
3. the boot messages (output of "journalctl -b 0 -k")
4. the stack of USB crap plugged to the kernel (output of "lsusb -vvv" as
root).
5. just in case, the output of "lspci -vvv" as root as well.

You can try downgrading (our updating) your kernel to narrow down the
issue, too.

Just don't use any kernel 5.1.x where x < 4: it can corrupt ext4
filesystems.

-- 
  Henrique Holschuh

[toc] | [prev] | [next] | [standalone]

#208787 — [OT] ext4 corruption (was: Re: Just had to reset/reboot again, total loss of keyboard & mouse)

On Sat, May 18, 2019 at 09:16:34AM -0300, Henrique de Moraes Holschuh wrote:
> Just don't use any kernel 5.1.x where x < 4: it can corrupt ext4
> filesystems.

Can you share a bug number please?

Reco

[toc] | [prev] | [next] | [standalone]

#208789 — Re: [OT] ext4 corruption (was: Re: Just had to reset/reboot again, total loss of keyboard & mouse)

On 2019-05-18, Reco <recoverym4n@enotuniq.net> wrote:
> On Sat, May 18, 2019 at 09:16:34AM -0300, Henrique de Moraes Holschuh wrote:
>> Just don't use any kernel 5.1.x where x < 4: it can corrupt ext4
>> filesystems.
>
> Can you share a bug number please?

https://lkml.org/lkml/2019/5/11/74

Is that it?

(All over my head.)

> Reco
>

[toc] | [prev] | [next] | [standalone]

#208795 — Re: [OT] ext4 corruption (was: Re: Just had to reset/reboot again, total loss of keyboard & mouse)

On Sat, 18 May 2019, Curt wrote:
> On 2019-05-18, Reco <recoverym4n@enotuniq.net> wrote:
> > On Sat, May 18, 2019 at 09:16:34AM -0300, Henrique de Moraes Holschuh wrote:
> >> Just don't use any kernel 5.1.x where x < 4: it can corrupt ext4
> >> filesystems.
> >
> > Can you share a bug number please?
> 
> https://lkml.org/lkml/2019/5/11/74
> 
> Is that it?

Yes.  Since that thread was broken by some crap MUA and I won't hunt it
down its other side at LKML right now (where the patches were posted):

current stable queue for 5.1:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.1 

(not all of the ext4 patches in there are related to this issue).

NOTE: unless you're used to working with this level of "not yet made
gold" code, just wait for 5.1.4 to be released.

-- 
  Henrique Holschuh

[toc] | [prev] | [next] | [standalone]

#208794 — Re: [OT] ext4 corruption (was: Re: Just had to reset/reboot again, total loss of keyboard & mouse)

On Sat, 18 May 2019, Reco wrote:
> On Sat, May 18, 2019 at 09:16:34AM -0300, Henrique de Moraes Holschuh wrote:
> > Just don't use any kernel 5.1.x where x < 4: it can corrupt ext4
> > filesystems.
> 
> Can you share a bug number please?

On LKML.  Just look at the ext4 patches in the stable queue for 5.1.4,
it doesn't have a "bug number".

-- 
  Henrique Holschuh

[toc] | [prev] | [next] | [standalone]

#208800

On Saturday 18 May 2019 08:16:34 am Henrique de Moraes Holschuh wrote:

> On Fri, 17 May 2019, Gene Heskett wrote:
> > The first thing I saw as it rebooted was some msgs about hid-common
> > This was before recovering the journal on the boot drive.
>
> That's a core component of the Linux *kernel* HID (human interface
> device) subsystem.
>
> You need, for a bug report:
>
> 1. the *exact* kernel version installed (where you got it from, its
> full version information)
This kernel is a hard one to build and get right, its a fully rt-prempt 
version built for running machinery with software step generation for 
stepper motor powered machinery.  Because its a testing version, it will 
become the linuxcnc version 2.8 install iso in due time, although the 
basic build by then might be buster,  All this stuff I'm finding is, if 
related to linuxcnc, being reported back to the developers.
uname -a says:
Linux coyote 4.9.0-9-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.168-1+deb9u2 
(2019-05-13) x86_64 GNU/Linux
> 2. stack of loaded modules (output of lsmod)
root@coyote:~$ lsmod
Module                  Size  Used by
fuse                   98304  11
uinput                 20480  1
binfmt_misc            20480  1
or51132                16384  1
cx88_dvb               36864  0
cx88_vp3054_i2c        16384  1 cx88_dvb
videobuf2_dvb          16384  1 cx88_dvb
dvb_core              122880  3 or51132,videobuf2_dvb,cx88_dvb
ir_rc5_decoder         16384  0
ir_lirc_codec          16384  0
lirc_dev               20480  1 ir_lirc_codec
rc_hauppauge           16384  0
tuner_simple           20480  2
tuner_types            28672  1 tuner_simple
tda9887                16384  1
tda8290                24576  0
snd_hda_codec_analog    16384  1
snd_hda_codec_generic    69632  1 snd_hda_codec_analog
snd_hda_codec_hdmi     49152  4
tuner                  28672  2
nouveau              1564672  4
edac_mce_amd           28672  0
mxm_wmi                16384  1 nouveau
edac_core              57344  0
wmi                    16384  2 mxm_wmi,nouveau
cx8802                 20480  1 cx88_dvb
cx8800                 40960  0
video                  40960  1 nouveau
kvm_amd              2179072  0
cx88xx                 86016  3 cx88_dvb,cx8802,cx8800
ttm                   102400  1 nouveau
tveeprom               24576  1 cx88xx
kvm                   602112  1 kvm_amd
drm_kms_helper        155648  1 nouveau
rc_core                28672  6 
rc_hauppauge,ir_lirc_codec,lirc_dev,cx88xx,ir_rc5_decoder
drm                   364544  7 nouveau,ttm,drm_kms_helper
v4l2_common            16384  3 tuner,cx88xx,cx8800
videobuf2_dma_sg       16384  2 cx88_dvb,cx8800
videobuf2_memops       16384  1 videobuf2_dma_sg
videobuf2_v4l2         24576  2 cx88_dvb,cx8800
videobuf2_core         40960  6 
videobuf2_dvb,cx88_dvb,cx8802,cx88xx,videobuf2_v4l2,cx8800
videodev              184320  6 
tuner,v4l2_common,videobuf2_core,cx88xx,videobuf2_v4l2,cx8800
irqbypass              16384  1 kvm
ftdi_sio               53248  0
pcspkr                 16384  0
usbserial              49152  1 ftdi_sio
evdev                  24576  9
serio_raw              16384  0
joydev                 20480  0
k10temp                16384  0
media                  40960  2 tuner,videodev
i2c_algo_bit           16384  3 cx88_vp3054_i2c,cx88xx,nouveau
usblp                  20480  0
snd_hda_intel          40960  3
snd_hda_codec         135168  4 
snd_hda_intel,snd_hda_codec_analog,snd_hda_codec_hdmi,snd_hda_codec_generic
snd_hda_core           90112  5 
snd_hda_intel,snd_hda_codec,snd_hda_codec_analog,snd_hda_codec_hdmi,snd_hda_codec_generic
snd_hwdep              16384  1 snd_hda_codec
snd_pcm               114688  4 
snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_hdmi
snd_timer              32768  1 snd_pcm
sg                     32768  0
snd                    81920  14 
snd_hda_intel,snd_hwdep,snd_hda_codec,snd_hda_codec_analog,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_pcm
soundcore              16384  1 snd
shpchp                 36864  0
asus_atk0110           20480  0
button                 16384  1 nouveau
nv_tco                 16384  0
parport_pc             28672  1
ppdev                  20480  0
lp                     20480  0
parport                49152  3 lp,parport_pc,ppdev
ip_tables              28672  0
x_tables               36864  1 ip_tables
autofs4                40960  2
uas                    24576  0
usb_storage            73728  1 uas
hid_logitech_hidpp     28672  0
hid_logitech_dj        20480  0
hid_generic            16384  0
usbhid                 49152  0
hid                   122880  6 
hid_generic,usbhid,hid_logitech_dj,hid_logitech_hidpp
ext4                  598016  4
crc16                  16384  1 ext4
jbd2                  110592  1 ext4
crc32c_generic         16384  8
fscrypto               28672  1 ext4
ecb                    16384  0
glue_helper            16384  0
lrw                    16384  0
gf128mul               16384  1 lrw
ablk_helper            16384  0
cryptd                 24576  1 ablk_helper
aes_x86_64             20480  1
mbcache                16384  5 ext4
sr_mod                 24576  0
cdrom                  57344  1 sr_mod
sd_mod                 49152  7
ohci_pci               16384  0
ata_generic            16384  0
ahci                   40960  0
ehci_pci               16384  0
ohci_hcd               49152  1 ohci_pci
libahci                32768  1 ahci
pata_jmicron           16384  0
sata_nv                28672  5
pata_amd               20480  0
ehci_hcd               77824  1 ehci_pci
firewire_ohci          40960  0
libata                249856  6 
pata_amd,ahci,libahci,pata_jmicron,ata_generic,sata_nv
psmouse               131072  0
firewire_core          65536  1 firewire_ohci
usbcore               245760  12 
usbhid,usb_storage,ehci_hcd,ohci_pci,ftdi_sio,usblp,usbserial,uas,ohci_hcd,ehci_pci
crc_itu_t              16384  1 firewire_core
forcedeth              69632  0
scsi_mod              225280  6 sd_mod,usb_storage,libata,uas,sr_mod,sg
usb_common             16384  1 usbcore
i2c_nforce2            16384  0
fan                    16384  0
thermal                20480  0
floppy                 73728  0

> 3. the boot messages (output of "journalctl -b 0 -k")

I've made some changes, so I'll reboot to get a currant log. Back later 
with more.

> 4. the stack of USB crap plugged to the kernel (output of "lsusb -vvv"
> as root).
> 5. just in case, the output of "lspci -vvv" as root as well.
>
> You can try downgrading (our updating) your kernel to narrow down the
> issue, too.
>
> Just don't use any kernel 5.1.x where x < 4: it can corrupt ext4
> filesystems.


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>

[toc] | [prev] | [next] | [standalone]

#208808

Gene Heskett composed on 2019-05-18 11:18 (UTC-0400):

> videobuf2_dvb          16384  1 cx88_dvb
> dvb_core              122880  3 or51132,videobuf2_dvb,cx88_dvb
> nouveau              1564672  4
> mxm_wmi                16384  1 nouveau
> wmi                    16384  2 mxm_wmi,nouveau
> video                  40960  1 nouveau
> ttm                   102400  1 nouveau
> drm_kms_helper        155648  1 nouveau
> drm                   364544  7 nouveau,ttm,drm_kms_helper
> videobuf2_dma_sg       16384  2 cx88_dvb,cx8800
> videobuf2_memops       16384  1 videobuf2_dma_sg
> videobuf2_v4l2         24576  2 cx88_dvb,cx8800
> videobuf2_core         40960  6 
> videobuf2_dvb,cx88_dvb,cx8802,cx88xx,videobuf2_v4l2,cx8800
> videodev              184320  6 
> tuner,v4l2_common,videobuf2_core,cx88xx,videobuf2_v4l2,cx8800
> media                  40960  2 tuner,videodev
> i2c_algo_bit           16384  3 cx88_vp3054_i2c,cx88xx,nouveau

Do all CNC controllers need all this video stuff? Is it established fact that the
normally power hungry NVidia cards work better than Intel IGP? Is this running a
WM or DE? If so, which? What is output in Xterm from 'inxi -SCGxx' using current
inxi version? Stretch's is ancient. Author prefers users use latest and keep it up
to date using its U switch. (It's just a script.)
https://smxi.org/docs/inxi-installation.htm
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#208801

On Saturday 18 May 2019 08:16:34 am Henrique de Moraes Holschuh wrote:

> On Fri, 17 May 2019, Gene Heskett wrote:
> > The first thing I saw as it rebooted was some msgs about hid-common
> > This was before recovering the journal on the boot drive.
>
> That's a core component of the Linux *kernel* HID (human interface
> device) subsystem.
>
> You need, for a bug report:

And I need the url to submit it to all to, this will be way too big for 
an email message. Its been years since I've done this.

> 1. the *exact* kernel version installed (where you got it from, its
> full version information)
> 2. stack of loaded modules (output of lsmod)
> 3. the boot messages (output of "journalctl -b 0 -k")
> 4. the stack of USB crap plugged to the kernel (output of "lsusb -vvv"
> as root).
> 5. just in case, the output of "lspci -vvv" as root as well.
>
> You can try downgrading (our updating) your kernel to narrow down the
> issue, too.
>
> Just don't use any kernel 5.1.x where x < 4: it can corrupt ext4
> filesystems.


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>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web