On 2020-06-25 16:36, fedora@xxxxxxxxxxxxxx wrote:
I have a situation that I have not seen before. 1 - I plug a card reader into a USB3 port of a server 2 - I insert an SD card into the reader. It is /dev/sdk. within a few seconds the full set of USB interfaces disconnect and the machine locks up soon after. 3 - I log in through a serial console 4 - I attempt to shut down mythtv at this point the machine totally crashes. No magic sysrq response. Pressing the reset button caused a boot into grub, looping with errors. A full power off/on brought the system up properly. (*1) I did it again, to check that the crash is related to the SD card, with same result. - The card reader is regularly used and never had any problem. - The same card reader and SD card then worked just fine on another machine. The SD card is the only new item here, acquired recently and maybe used for the first time. I find it unusual that an SD card can lead to the whole USB system aborting. The death of MythTV is probably due to the unexpected disappearance of the USB tuners, but it could probably do better than just crash with "NULL pointer dereference". This machine runs latest f30 (I know, I am just about to upgrade to f32). $ uname -a Linux e7.eyal.emu.id.au 5.6.13-100.fc30.x86_64 #1 SMP Fri May 15 00:36:06 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (*1) the fact that a reset did not lead to a good restart makes me suspect that the problem is related to the hardware (the mobo? the fw?).
[trimmed] More relevant data. I have three kernels in /boot. -rwxr-xr-x 1 root root 10799208 Apr 30 04:07 /boot/vmlinuz-5.6.8-100.fc30.x86_64 -rwxr-xr-x 1 root root 10803304 May 7 06:55 /boot/vmlinuz-5.6.11-100.fc30.x86_64 -rwxr-xr-x 1 root root 10803304 May 15 10:52 /boot/vmlinuz-5.6.13-100.fc30.x86_64 The problem happens reliably on 5.6.13. Boot single user. unmount filesystems other than root. Manage from a serial console. New computer (Gigabyte Z390 UD, Intel Core i7-9700) f30 5.6.13-100.fc30 problem reproduces f30 5.6.11-100.fc30 no problem) Live Xfce images: f30 5.0.9-301.fc30 no problem f32 5.6.6-300.fc32 no problem Old computer (Gigabyte GA-G33M-DS2R, Intel Core 2 Quad Q9300} f32 5.6.16-300.fc32 no problem So I now feel that this is a fedora kernel issue. Maybe even a vanilla kernel issue. Not in 5.6.6. Not in 5.6.11. Is in 5.6.13. Not in 5.6.16. Unless I see a reason to continue, I am now closing this issue as "probably fixed since". Thanks everybody. -- Eyal at Home (fedora@xxxxxxxxxxxxxx) _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
