OK - using the 6.19.11-200.fc43.x86_64 kernel w/o ANY issues, but I do update the newer kernels and “try them out”, w/7.1.9-100 being latest installed (I know, 7.1.10-100 is out…).
But seems that even though I have Firefox performance setting to NOT use hardware acceleration when available, browsing along when Firefox will do its crash report pop up, I select close firefox, then after that go to relaunch Firefox, but I get the infamous black screen w/QRcode and kernel panic message telling me to reboot. Does not happen with my 19.11…
Any ideas why this is going on? (besides the fact I’m using a very old Gateway laptop w/4Gb ram, 2GHz, ext4, triple boot system, etc…)
got this flip phone - or as I call it “stupid phone” (ie NOT a smart phone - no apps, no intenet, no scanning [can take picture of it but unusable - tried that at walmart…], no frills ~ just phone, answering machine, camera), so not able to move the laptop to my table top printer/fax/scanner… any ideas?
should output the logs from your last crashed session
My guess:
Kernel panic Maybe because of kernel regression on old hardware, what smoothly runs on older kernels might hit a restriction on newer kernels?
Ran it and first line was:
Journal file /var/log/journal/9237eaf3828540a2a660af193cc8c7ec/system@000658c54ffe7244-cb2aa809b3c88167.journal~ is truncated, ignoring file.
Then it ran on, but the crash occurred on 26th, so here’s stuff from that date only:
Aug 26 08:03:16 fedora systemd[1]: Failed to start hibernate-resume.service - Disable swap after resuming from hibernation.
Aug 26 09:12:41 fedora kernel: ath: phy1: Could not kill baseband RX
Aug 26 09:12:41 fedora kernel: ath: phy1: Failed to wakeup in 500us
Aug 26 09:12:41 fedora kernel: ath: phy1: Failed to wakeup in 500us
Aug 26 09:12:41 fedora kernel: ath: phy1: Failed to wakeup in 500us
Aug 26 16:37:18 fedora kernel: usb 2-4: device descriptor read/64, error -110
~
~
~
lines 1-34/34 (END)
and it ran on a bit for other dates then:
Aug 26 08:03:16 fedora systemd[1]: Failed to start hibernate-resume.service - Disable swap after resuming from hibernation.
Aug 26 09:12:41 fedora kernel: ath: phy1: Could not kill baseband RX
Aug 26 09:12:41 fedora kernel: ath: phy1: Failed to wakeup in 500us
Aug 26 09:12:41 fedora kernel: ath: phy1: Failed to wakeup in 500us
Aug 26 09:12:41 fedora kernel: ath: phy1: Failed to wakeup in 500us
Aug 26 16:37:18 fedora kernel: usb 2-4: device descriptor read/64, error -110
~
~
~
lines 1-34/34 (END)
…the day before has this:
Aug 25 08:12:37 fedora systemd[1]: Failed to start hibernate-resume.service - Disable swap after resuming from hibernation.
Aug 25 10:59:22 fedora kernel: usb usb5-port2: disabled by hub (EMI?), re-enabling…
Aug 25 13:04:30 fedora systemd[1]: Failed to start hibernate-preparation.service - Enable swap file and disable zram before hibernate.
Seems to be bunch of hibernate things and nothing about Firefox... the Aug 26 16:37:18 time stamp would've been about when kernel paniced and I rebooted using 19.11 ;-)
I do have one wifi on PCI and another on USB (plus using LAN) - could be the USB wifi is making these newer kernels and/or Firefox hick-up?
Its most probably a power supply issue, your laptop is not able to supply enough power to USB (your WIFI) and it stopped communicating. So yes,
is correct.
I think its happening to your 7.1.9-100 Kernel because newer kernels are more agressive in putting your USB devices to sleep, which might cause trouble for older hardware (not sure tho), so i think staying with older kernel is a better option or if you want to stay in newer kernel, you can edit boot parameters—i was not sure how to do it—took help from gemini it said to
I have noticed that while my PCI wifi speed stays constant at 54Mb/s, the USB wifi seems to vary from 72 to 150Mb/s (I can use the USB switch on the device to switch it off then back on and it’ll go from 72 to 150Mb/s…), and sometimes gets disconnected all together for a momment… maybe try just disconnecting the USB wifi and see if it makes a difference with the newer kernels (and/or try another USB wifi I got laying around) - I still have LAN and PCI wifi to browse with
Having similar issue on Ubuntu 24.04lts (triple boot system) with Firefox crashes, but when there after the Firefox crash pop up, it will just log me out (losing any work that’s open), or lockup/freeze requiring holding down power button - also does it with the newer kernels there like 6.8.0-138, but not my 6.8.0-85… hmmmm
After reading some comments on the stackoverflow.com link, the USB wifi has a green blinking LED on it, plus the switch has a blue LED on it that shows power on/off ~ maybe their power demand is adding to the dilemma…
Disabled the USB wifi (used USB dongle switch to cut power to it so no green blinking LED from wifi, or blue LED from switch), and checked my Ubuntu 24.04lts hoping this would also fix similar issues there. One problem with Ubuntu’s newer kernels (besides Firefox crashes and subsequent instabilities) is that upon restoring from hibernation, it will go to login screen and not lock screen and still does it even with USB wifi disabled. However, with the older 6.8.0-85 kernel it goes to lock screen and does not log me out (and lose any open work, plus Firefox crashes are rare) ~ off topic for Fedora 43, but…
Currently running 7.1.12-100.fc43.x86_64 installed today on my Fedora 43 with USB wifi still disabled as noted above ~ we’ll see if Firefox no longer crashes with ensuing kernel panic.
Ran journalctl -b -1 -p err again to see if the usb 2-4: device descriptor read/64, error -110 error is still occurring but got:
lines 1-18
Sep 01 04:02:01 fedora kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
Sep 01 04:02:01 fedora kernel: virt/tdx: TDX not supported by the host platform
Sep 01 09:02:35 fedora abrtd[771]: '/var/spool/abrt/oops-2026-06-06-08:37:03-893-0' is not a problem directory
Sep 01 09:02:36 fedora abrtd[771]: '/var/spool/abrt/oops-2026-05-30-08:10:50-882-0' is not a problem directory
Sep 01 09:02:37 fedora abrtd[771]: '/var/spool/abrt/ccpp-2026-05-30-08:10:40.675866-8243' is not a problem directory
Sep 01 09:02:37 fedora abrtd[771]: '/var/spool/abrt/ccpp-2026-04-01-13:08:58.965701-13735' is not a problem directory
Sep 01 09:02:38 fedora abrtd[771]: '/var/spool/abrt/ccpp-2026-07-04-11:04:19.828399-2156' is not a problem directory
Sep 01 09:02:38 fedora abrtd[771]: '/var/spool/abrt/ccpp-2026-05-16-08:35:06.95500-20582' is not a problem directory
Sep 01 09:02:39 fedora abrtd[771]: '/var/spool/abrt/oops-2026-06-06-08:37:15-893-0' is not a problem directory
Sep 01 09:02:39 fedora abrtd[771]: '/var/spool/abrt/ccpp-2026-06-24-08:27:15.666768-2131' is not a problem directory
Sep 01 09:02:40 fedora abrtd[771]: '/var/spool/abrt/oops-2026-05-16-08:35:32-868-0' is not a problem directory
Sep 01 09:02:40 fedora abrtd[771]: '/var/spool/abrt/ccpp-2026-06-24-08:27:19.655542-19383.new' is not a problem directory
Sep 01 09:02:41 fedora abrtd[771]: '/var/spool/abrt/ccpp-2026-08-05-08:53:40.222807-11071' is not a problem directory
Sep 01 09:02:42 fedora abrtd[771]: '/var/spool/abrt/ccpp-2026-08-05-08:53:47.343181-24937' is not a problem directory
Sep 01 09:03:03 fedora virtqemud[1079]: Unable to open /dev/kvm: No such file or directory
Sep 01 09:03:41 fedora gdm-password][1830]: gkr-pam: unable to locate daemon control file
Sep 01 09:03:53 fedora systemd[1871]: Failed to start app-gnome-vmware\x2duser-2321.scope - Application launched by gnome-session-service.
Sep 01 09:22:11 fedora dbus-broker-launch[737]: Activation request for 'org.freedesktop.Avahi' failed.
Sep 01 09:22:15 fedora dbus-broker-launch[737]: Activation request for 'org.freedesktop.ColorManager' failed.
Sep 01 09:22:21 fedora dbus-broker-launch[737]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Sep 01 09:22:21 fedora dbus-broker-launch[737]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Sep 01 09:22:21 fedora dbus-broker-launch[737]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-22/22 (END)
the usb 2-4: device descriptor read/64, error -110 isn’t there, but a lot of other ‘errors’ are…
OK, so this morning, with USB wifi offline and using 7.1.12-100 kernel, Firefox crash pops up, close Firefox, went to open Firefox and Fedora 43 did its kernel panic please reboot thingy - rebooted and Fedora 43 froze-up half way loading up - rebooted using 6.19.11-200 and all’s fine - even had USB wifi back online… ran journalctl -b -1 -p err again and got this:
journalctl -b -1 -p err
Journal file /var/log/journal/9237eaf3828540a2a660af193cc8c7ec/system@000658c54ffe7244-cb2aa809b3c88167.journal~ is truncated, ignoring file.
Sep 03 08:57:17 fedora abrtd[774]: '/var/spool/abrt/oops-2026-06-06-08:37:03-893-0' is not a problem directory
Sep 03 08:57:20 fedora abrtd[774]: '/var/spool/abrt/oops-2026-05-30-08:10:50-882-0' is not a problem directory
Sep 03 08:57:21 fedora abrtd[774]: '/var/spool/abrt/ccpp-2026-05-30-08:10:40.675866-8243' is not a problem directory
Sep 03 08:57:21 fedora abrtd[774]: '/var/spool/abrt/ccpp-2026-04-01-13:08:58.965701-13735' is not a problem directory
Sep 03 08:57:22 fedora abrtd[774]: '/var/spool/abrt/ccpp-2026-07-04-11:04:19.828399-2156' is not a problem directory
Sep 03 08:57:22 fedora abrtd[774]: '/var/spool/abrt/oops-2026-09-03-08:55:00-928-0' is not a problem directory
Sep 03 08:57:23 fedora abrtd[774]: '/var/spool/abrt/ccpp-2026-05-16-08:35:06.95500-20582' is not a problem directory
Sep 03 08:57:24 fedora abrtd[774]: '/var/spool/abrt/oops-2026-06-06-08:37:15-893-0' is not a problem directory
Sep 03 08:57:24 fedora abrtd[774]: '/var/spool/abrt/ccpp-2026-06-24-08:27:15.666768-2131' is not a problem directory
Sep 03 08:57:24 fedora abrtd[774]: '/var/spool/abrt/oops-2026-05-16-08:35:32-868-0' is not a problem directory
Sep 03 08:57:25 fedora abrtd[774]: '/var/spool/abrt/ccpp-2026-06-24-08:27:19.655542-19383.new' is not a problem directory
Sep 03 08:57:25 fedora abrtd[774]: '/var/spool/abrt/ccpp-2026-09-03-08:54:48.823159-2092' is not a problem directory
Sep 03 08:57:26 fedora abrtd[774]: '/var/spool/abrt/ccpp-2026-08-05-08:53:40.222807-11071' is not a problem directory
Sep 03 08:57:27 fedora abrtd[774]: '/var/spool/abrt/ccpp-2026-08-05-08:53:47.343181-24937' is not a problem directory
Sep 03 08:57:39 fedora virtqemud[1116]: Unable to open /dev/kvm: No such file or directory
Sep 03 08:58:30 fedora gdm-password][1877]: gkr-pam: unable to locate daemon control file
Sep 03 08:58:37 fedora abrt-notification[2170]: [🡕] System encountered a non-fatal error in flush_tlb_mm_range()
Sep 03 08:58:42 fedora systemd[1928]: Failed to start app-gnome-vboxclient-2366.scope - Application launched by gnome-session-service.
lines 2-19/19 (END)
Only other things that were connected to a USB before the kernel panic are my mouse and an XBOX360 game controller…
Seems USB power is apparently not the issue (see previous posts above), but rather it’s just that my older hardware is not compatible with these newer Fedora (or Ubuntu) kernels!
So, that said, forget any upgrade to Fedora 44 (or Ubuntu 26.04lts) on this laptop
I doubt that this is true in general. I have been running a 7.1 kernel with Fedora 44 on hardware from 2010! Usually, the kernel devs are very slow in removing support for ancient hardware. Unless your hardware is way older than 2010, I guess that the specific hardware you are using requires some special handling that the kernel developer(s) who applied the changes were not aware of.
If you want to get the issue fixed, I recommend being more specific in what exact hardware is affected (USB vendor ID, device ID) and the exact kernel version it stopped working. This information, provided upstream at kernel.org, might help getting your issue fixed.
On Fedora, this is generally a bad idea because the older kernel versions don’t receive security updates.
