Bug 924545
Summary: | kernel-3.8.3-103.fc17.x86_64 unusable on Dell Precision M6500 (wusbhc_rh_suspend UNIMPLEMENTED) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Allen Hewes <allen> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-22 18:19:17 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Allen Hewes
2013-03-22 03:11:57 UTC
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. |