Bug 684602

Summary: kernel-2.6.34.8-68.fc13.x86_64 does not boot (workaround: pci=use_crs)
Product: [Fedora] Fedora Reporter: Kronos003 <kronos>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 13CC: gansalmon, itamar, jonathan, kernel-maint, kuehn, 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: 2011-06-27 12:00:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
boottime dmesg of last working kernel = kernel-2.6.34.6-47.fc13.x86_64
none
lspci of system in question
none
lsusb of system in question
none
dmesg from hung boot on Dell Latitude E6500
none
messages from Dell Latitude E6500 none

Description Kronos003 2011-03-13 19:12:24 UTC
Created attachment 484034 [details]
boottime dmesg of last working kernel = kernel-2.6.34.6-47.fc13.x86_64

Here we go yet again. This is an ongoing issue:
kernel-2.6.34.6-54.fc13.x86_64 https://bugzilla.redhat.com/show_bug.cgi?id=633040
kernel-2.6.34.7-61.fc13.x86_64 https://bugzilla.redhat.com/show_bug.cgi?id=650721
kernel-2.6.34.7-63.fc13.x86_64 https://bugzilla.redhat.com/show_bug.cgi?id=664098
kernel-2.6.34.7-66.fc13.x86_64 https://bugzilla.redhat.com/show_bug.cgi?id=665702


in the last bug (665702) a poster suggested i add iommu=soft to the boot arguments and try to disable ricoh hardware. i tried these things against kernel-2.6.34.8-68.fc13.x86_64 got the following results:

cannot disable the hardware - the bios offers no such option that i can see. iommu=soft doesnt work


So here it is again - all the following info has been refreshed and new files attached:

boot process freezes at:

io scheduler cfq registered (default)

Version-Release number of selected component (if applicable):

kernel-2.6.34.8-68.fc13.x86_64



How reproducible:
every time

Steps to Reproduce:
1. boot
2.
3.

Actual results:
doesnt boot

Expected results:
boots and all works as expected

Additional info: (let me know if you need more info)
last working kernel = kernel-2.6.34.6-47.fc13.x86_64

$ rpm -qa |grep kernel
kernel-devel-2.6.34.8-68.fc13.x86_64
kernel-devel-2.6.34.7-66.fc13.x86_64
kernel-2.6.34.6-47.fc13.x86_64
kernel-headers-2.6.34.8-68.fc13.x86_64
kernel-devel-2.6.34.6-47.fc13.x86_64
arm-gp2x-linux-kernel-headers-2.6.12.0-4.fc12.noarch
abrt-addon-kerneloops-1.1.14-1.fc13.x86_64
kernel-2.6.33.8-149.fc13.x86_64
kernel-2.6.34.8-68.fc13.x86_64

$ rpm -qa |grep kmod
kmod-xtables-addons-2.6.34.6-47.fc13.x86_64-1.30-1.fc13.x86_64
akmod-xtables-addons-1.30-1.fc13.x86_64
kmodtool-1-18.fc11.noarch
libmikmod-3.2.0-11.beta2.fc13.x86_64
akmods-0.3.6-3.fc12.noarch
kmod-xtables-addons-2.6.34.8-68.fc13.x86_64-1.30-1.fc13.4.x86_64



Toshiba Satellite A215-S7422
AMD Turion TL-58 + 4GB Ram

Comment 1 Kronos003 2011-03-13 19:13:17 UTC
Created attachment 484035 [details]
lspci of system in question

Comment 2 Kronos003 2011-03-13 19:13:53 UTC
Created attachment 484036 [details]
lsusb of system in question

Comment 3 Kronos003 2011-03-13 19:16:25 UTC
i have time to work on this for the next week or so, so if you have any data you need or things to try, lets do this

Comment 4 Jeff Kuehn 2011-03-17 14:19:36 UTC
Kernel 2.6.34.8-68.fc13.x86_64 hangs on boot for me also.  Hardware is a Dell Latitude E6500 w/ several USB devices. I can provide additional details on request.

Comment 5 Jeff Kuehn 2011-03-17 14:22:17 UTC
Created attachment 486022 [details]
dmesg from hung boot on Dell Latitude E6500

Comment 6 Jeff Kuehn 2011-03-17 14:28:08 UTC
Created attachment 486025 [details]
messages from Dell Latitude E6500

Comment 7 Chuck Ebbert 2011-03-22 00:17:10 UTC
Try adding:

  pci=use_crs

to the kernel boot options.

Comment 8 Jeff Kuehn 2011-03-22 18:35:57 UTC
When adding pci=use_crs, the system seems to survive a bit further into the boot. It now seems to hang after starting 'atd'

Comment 9 Jeff Kuehn 2011-03-22 19:02:42 UTC
Disregard previous comment.  Adding pci=use_crs DOES appear to correct the boot hang.

Comment 10 Chuck Ebbert 2011-03-23 16:31:10 UTC
Unfortunately CRS caused a lot more problems than it fixed in 2.6.34, so it's disabled by default.

Comment 11 Kronos003 2011-03-24 15:19:54 UTC
I concur, adding pci=use_crs corrects my bootup issue as well. the workaround seems to work.

Comment 12 Bug Zapper 2011-05-30 11:00:16 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 WONTFIX if it remains open with a Fedora 
'version' of '13'.

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 prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 13 Bug Zapper 2011-06-27 12:00:29 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.