Bug 760348

Summary:	f16 kernel won't boot during installation or from a Live CD
Product:	[Fedora] Fedora	Reporter:	Alex Lancaster <alex>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	gansalmon, itamar, jgotts, jonathan, kernel-maint, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-01 16:09:52 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Alex Lancaster 2011-12-05 21:42:12 UTC

I have a machine for which the kernel panics as soon as I attempt to install.  I have tried the following:

1. Clean installation using a DVD
2. Clean installation using a USB stick
3. Attempt to boot from a Live CD
4. Upgrading from F15 installation using preupgrade

In all cases, the kernel oops's upon attempting to boot as soon as an f16 kernel is loaded (in the first two cases it is the kernel that is run from the installation).  The exact kernel oops is different each time, but typically includes lines like:

kernel: EIP is at print_context_stack

I have successfully installed F15 on this machine and it runs fine.  Here is the smolt profile:

http://www.smolts.org/client/show/pub_db7093ff-7fd5-4cf9-acc7-4d30c881eb0a

I have checked my media for errors, and used both USB and DVD, as well attempting to boot from a live CD, always get the same kind of kernel error.

Is there something specific to recent kernels that might have issues with my hardware?

Comment 1 Alex Lancaster 2011-12-05 22:36:00 UTC

When I boot, I get the "Install" or "Troubleshoot" screen, if I choose "Troubleshoot", then "basic graphics", I still get kernel crash.  Reproducing (by manual typing) the last few lines of the kernel traceback:

[ 1.264009] [<c0ae3094>] ? acpi_pci_slot+0x1b/0x1b
[ 1.264009] [<c0ab983f>] ? kernel_init+0xaf/0x13b
[ 1.264009] [<c0ab9790>] ? start_kerne+0x353/0x353
[ 1.264009] [<c0816b3e>] ? kernel_thread_helper+0x6/0x10
[ 1.264009] --[ end trace fe4ebffb2b8ff188]---

Comment 2 Alex Lancaster 2011-12-05 22:59:03 UTC

OK, booting with "acpi=off" seemed to help.  Then booted with "pci=noacpi" as per:

http://fedoraproject.org/wiki/Common_kernel_problems#Crashes.2FHangs

and now get the traceback shown in this file: http://db.tt/BuRDyctK

Comment 3 Alex Lancaster 2011-12-05 23:19:42 UTC

seems similar to this bug #704085 and maybe bug #746097.

Comment 4 Alex Lancaster 2011-12-06 00:22:20 UTC

Installation worked with "acpi=off", got latest kernel installed on the f16 box:

kernel-3.1.2-1.fc16.i686 installed

tried rebooting without "acpi=off", get same kernel oops, so not fixed in more recent kernel.

Comment 5 John Gotts 2011-12-26 00:37:30 UTC

Does booting with pci=nocrs work?

Comment 6 Alex Lancaster 2011-12-26 18:54:27 UTC

(In reply to comment #5)
> Does booting with pci=nocrs work?

You mean without "acpi=off", just "pci=nocrs"?  I haven't tried that.  I'm not near my box right now, I'll try it when I'm back at work.

Comment 7 John Gotts 2011-12-26 19:25:42 UTC

Yep, just with pci=nocrs. That worked like a champ with my Dell Studio 1536. Let me know what you get.

Comment 8 Josh Boyer 2012-03-01 16:09:52 UTC

There was a regression issue in the ACPICA code recently that impacted a number of machines with the D865PERL chipset you have.  That should be fixed in the 3.2.8 kernel in F16 updates testing.