Description of problem: Update FC21 kernel from 4.1.3-100.fc21.x86_64 to any of the following updates resulted upon bootup in a complete laptop freeze at the 'f' fedora logo and doesn't get to the gnome login screen. Version-Release number of selected component (if applicable): Fails using kernel 4.1.4-100.fc21.x86, 4.1.5-100.fc21.x86, 4.1.6-100.fc21.x86_64, 4.1.7-100.fc21.x86_64 and 4.1.8-100.fc21.x86_64. Using linux-firmware-20150521-48.git3161bfa4.fc21.noarch How reproducible: Always. Steps to Reproduce: 1. Turn on wireless in 4.1.3-100.fc21.x86_64, works aok. 2. Reboot computer and load a newer kernel 3. System freezes at bootup at 'f' screen before login screen. Alternatively: 1. Turn off wireless in 4.1.3-100.fc21.x86_64. 2. Reboot computer and load a newer kernel, boots up aok. 3. Log into gnome, everything eg. ethernet etc works aok. 4. turn on wireless, system seems to briefly stutter then hangs. Actual results: Complete system freeze. Requires reboot. Expected results: Wireless turns on etc etc. Additional info: I have a Asus TX201LA laptop, dual boot FC21 / Windows 8 + android tablet (Windows wireless works fine.) Additional similar FC21 experience from user with vivopc VM42: http://forums.fedoraforum.org/showthread.php?t=306441
Is there a reason you believe this is firmware related?
not at all. I don't know how to triage the problem further to identify whether it's the kernel (which changed) or the firmware (which hasn't)
Live install of FC22 (as released, ie. 4.0.4-301.fc22.x86_64) has wireless that starts by default and works ok out of the box. I haven't run the upgrades to see if the >4.1.3 kernels fail.
Installation of FC23 (beta) is unable to install on this machine. During the installation CD startup, it freezes at the 'f' logo. ie. looks like the same problemo.
Possible duplicate https://bugzilla.redhat.com/show_bug.cgi?id=1274305
doing alt-d during FC21 bootup of 4.1.8-100.fc21.x86_64 with network previously enabled in 4.1.3-100.fc21.x86_64 gives all [OK]'s eg. Starting Network Manager... [OK] Started Network Manager. Starting Wait for Plymouth Boot Screen to Quit [OK] Started GNOME Display Manager. [OK] Started Virtualization daemon. where it seems to freeze with no error messages.... ------------------------------------ doing alt-d during bootup of FC23 beta installation disk reveals [OK] Started Network Manager .... [OK] Started GNOME Display Manager then it starts producing errors eg: [166.X] xhci_hcd 0000:00:14.0: Command completion event does not match command [167.X] usb 2-1.4: device not accepting address 6, error -62 [171.X] xhci_hcd 0000:00:14.0: HC died: cleaning up [171.X] usb 1-1.2.4: device descriptor read/all, error -110 [171.X] usb 1-1.2-port4: cannot disable (err = -22) [171.X] usb 1-1.2-port4: cannot reset (err = -22) .... [171.X] usb 1-1.2-port4: cannot reset (err = -22) [171.X] usb 1-1.2-port4: Cannot enable. Maybe the USB cable is bad? which repeats a few times and then the following starts repeating couple of minutes: [181.X] INFO rcu_sched detected stalls on CPUs/tasks { 0} (detected by 3, t=60003 jiffies, g=2719, c=2718, q=0) [187.X] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 29s! [NetworkManager:1261]
*** Bug 1274305 has been marked as a duplicate of this bug. ***
Happens on ASUS X551MA on F22 and F23 as well. Kernel 4.0 works fine. All kernels 4.1, 4.2, (and also 4.3 from fc24 up to git7) have problems.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
There is an independent report on the same hardware model as me: using Fedora 22 4.1.3 works but not the updates. Fedora 23 live doesn't work. ( http://forums.fedoraforum.org/showthread.php?p=1748806#post1748806 ) Should I be changing the component from linux-firmware to something else? We are approaching EOL on my (working, current) Fedora 21 install...
There is a workaround... Can confirm that adding pci=nomsi on grub command line works for me (and others) with 4.1.13-100.fc21.x86_84 as suggested over at https://github.com/lwfinger/rtlwifi_new/issues/64 http://forums.fedoraforum.org/showthread.php?t=306441 will test this modification enables FC23 install
Hi Michael and David, It looks like this is the same problem as in #1297554 [1] and #1154286 [2. The first link contains a fedora 23 kernel with a back ported patch from Kernel 4.4 that resolves the issue. I am wondering if someone can merge all three bug reports. [1]https://bugzilla.redhat.com/show_bug.cgi?id=1297554 [2]https://bugzilla.redhat.com/show_bug.cgi?id=1154286
Should this be fixed in 4.4.6 in updates?
yes. It has been fixed since fedora kernel 4.2.6 and up
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This was fixed in F23 updates. Please mark it as such.