Description of problem: I rebooted from a yum update on my Fedora 17 x86_64 Dell Precision M6500 laptop and the kernel-3.8.3-103.fc17.x86_64 update that was installed doesn't boot. All I see are lines that look like: [ 144.185688] whci-hcd 0000:0d:00.0-1: wusbhc_rh_suspend (ffff88040279e000 [ffff88040279e000]) UNIMPLEMENTED Version-Release number of selected component (if applicable): I have /var/log/message entries that are similar but they have never prevented my laptop from booting up. Specifically, I had the wusbhc_rh_suspend message in the following kernels: Oct 1 22:44:53 fedora-zero kernel: [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.5.4-2.fc17.x86_64 root=/dev/mapper/VolGroup00-LogVol00 ro quiet rhgb Oct 1 22:44:53 fedora-zero kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.5.4-2.fc17.x86_64 root=/dev/mapper/VolGroup00-LogVol00 ro quiet rhgb Oct 2 03:01:53 fedora-zero kernel: [15437.430049] whci-hcd 0000:0d:00.0-1: >wusbhc_rh_suspend (ffff880403f66800 [ffff880403f66800]) UNIMPLEMENTED Oct 2 03:02:25 fedora-zero kernel: [15469.420258] whci-hcd 0000:0d:00.0-1: >wusbhc_rh_suspend (ffff880403f66800 [ffff880403f66800]) UNIMPLEMENTED Oct 2 03:07:21 fedora-zero kernel: [15765.275529] whci-hcd 0000:0d:00.0-1: >wusbhc_rh_suspend (ffff880403f66800 [ffff880403f66800]) UNIMPLEMENTED Oct 2 11:49:06 fedora-zero kernel: [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.5.4-2.fc17.x86_64 root=/dev/mapper/VolGroup00-LogVol00 ro quiet rhgb Oct 2 11:49:06 fedora-zero kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.5.4-2.fc17.x86_64 root=/dev/mapper/VolGroup00-LogVol00 ro quiet rhgb Oct 2 11:51:00 fedora-zero kernel: [ 138.433844] whci-hcd 0000:0d:00.0-1: >wusbhc_rh_suspend (ffff8803f02ab000 [ffff8803f02ab000]) UNIMPLEMENTED How reproducible: Boot into the kernel-3.8.3-103.fc17.x86_64 Fedora 17 update kernel. My laptop never boots successfully with this kernel. Steps to Reproduce: 1. have a running Dell Precision M6500 with kernel-3.7.9-104.fc17.x86_64 2. run yum update 3. reboot into kernel-devel-3.8.3-103.fc17.x86_64 Actual results: Seeing the line [ 144.185688] whci-hcd 0000:0d:00.0-1: wusbhc_rh_suspend (ffff88040279e000 [ffff88040279e000]) UNIMPLEMENTED continually repeat. I killed the power after 20 minutes. Expected results: To boot Fedora 17 into the updated kernel-3.8.3-103.fc17.x86_64 Additional info: This happens on a plain vanilla kernel. I can never boot into the kernel-3.8.3-103.fc17.x86_64. I added the comment from https://bugzilla.redhat.com/show_bug.cgi?id=919289 and that didn't help. The kernels I have ran on this laptop without this error message: kernel-3.5.5-2.fc17.x86_64 kernel-3.5.6-1.fc17.x86_64 kernel-3.6.1-1.fc17.x86_64 kernel-3.6.2-3.fc17.x86_64 kernel-3.6.2-4.fc17.x86_64 kernel-3.6.3-1.fc17.x86_64 kernel-3.6.5-1.fc17.x86_64 kernel-3.6.6-1.fc17.x86_64 kernel-3.6.7-4.fc17.x86_64 kernel-3.6.8-2.fc17.x86_64 kernel-3.6.9-2.fc17.x86_64 kernel-3.6.10-2.fc17.x86_64 kernel-3.6.11-1.fc17.x86_64 kernel-3.6.11-5.fc17.x86_64 kernel-3.7.3-101.fc17.x86_64 kernel-3.7.6-102.fc17.x86_64 kernel-3.7.9-101.fc17.x86_64 kernel-3.7.9-104.fc17.x86_64 The kernels I have seen this message in: kernel-3.5.4-2.fc17.x86_64 (still booted) kernel-3.8.3-103.fc17.x86_64 (computer will NOT boot) Of note is that this device (0000:0d:00.0-1) is a Realtek wi-fi/radio controller: (from kernel-3.7.9-104.fc17.x86_64) 0d:00.0 RF controller: Realtek Semiconductor Co., Ltd. Device 7305 (rev 01) (prog-if 10) Subsystem: Realtek Semiconductor Co., Ltd. Device 7305 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 54 Region 0: Memory at f1eff000 (64-bit, non-prefetchable) [size=4K] Region 2: I/O ports at cc00 [size=256] Region 3: I/O ports at cd00 [size=256] Region 4: I/O ports at ce00 [size=256] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+ Address: 00000000feeff00c Data: 41b2 Capabilities: [70] Express (v1) Endpoint, MSI 02 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [140 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [160 v1] Device Serial Number 00-01-00-03-00-01-00-03 Kernel driver in use: whci
Created attachment 714264 [details] iPhone photo of laptop booting kernel-3.8.3-103.fc17.x86_64
I tried Justin's suggestion from https://bugzilla.redhat.com/show_bug.cgi?id=919289#c4 and it doesn't help, computer never boots.
I think 0d:00.0 RF controller: Realtek Semiconductor Co., Ltd. Device 7305 (rev 01) (prog-if 10) is a bluetooth controller, perhaps? My wi-fi controller is: 0c:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01)
Please provide the dmesg output of a boot with 3.7.9-104 and the output of lsmod on the machine. You can boot 3.8.3 temporarily by blacklisting the whci driver.
Please also provide the output of lspci -nnvv
Created attachment 714698 [details] kernel-3.7.9-104.fc17.x86_64 dmesg output
Created attachment 714699 [details] kernel-3.7.9-104.fc17.x86_64 lsmod output
Created attachment 714700 [details] kernel-3.7.9-104.fc17.x86_64 sudo lspci -nnvv output
Josh, You will find nvidia, wl and vboxdrv kernel modules. I have run these kernel modules for every kernel that has come out for Fedora 17. My normal update process is: 1) notice a kernel update 2) change to multi-user boot target 3) reboot into new kernel 4) remove old nvidia, wl, vbxodrv kernel modules 5) update buildsys 6) make any changes/patches to build new nvidia, wl, vboxdrv kernel modules 7) build new nvidia, wl, vboxdrv kernel modules 8) install new nvidia, wl, vboxdrv kernel modules 9) change to graphical boot target 10) reboot to get graphical environment 11) update initrd and boot menu I have done the exact same 11 steps for every kernel update. I will try to boot into kernel-3.8.3-103.fc17.x86_64 by blacklisting whci driver and report back.
(In reply to comment #9) > Josh, > > You will find nvidia, wl and vboxdrv kernel modules. I have run these kernel > modules for every kernel that has come out for Fedora 17. Right. That would have been helpful to know from the start. This is a duplicate of the bug you already mentioned. If possible, it might still be good to get the dmesg from a fresh boot of 3.8.3-103 so we can compare. *** This bug has been marked as a duplicate of bug 919289 ***
Josh, I can't get a dmesg output, it never gets that far. I can record a video on my iPhone of the booting process. I will try to mess around with blacklisting and disabling stuff in the BIOS. For every other kernel update I listed, I have always been able to reboot into the kernel update and do my thing.
Josh, When I reboot into a kernel update, those modules are not loaded because they don't exist for the updated kernel.
(In reply to comment #12) > Josh, > > When I reboot into a kernel update, those modules are not loaded because > they don't exist for the updated kernel. Still a duplicate. Unless we get the first part of the boot messages, it will be hard to compare.
Yeah, yeah, I know. I'm with you. I am removing all the stuff and I should be able to provide more info about this. I'll update the prior BZ with my findings.