Bug 144607

Summary:	Kernel Panic: pci_bios_find_device on MSI 915P Combo, P4 HT, ATI X800 PCI Express
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Andreas Kohn <andreas>
Component:	Kernel	Assignee:	Thomas Renninger <trenn>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Blocker
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	PC
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Picture of the panic (part one, taken with mobile phone) Picture of the panic (part two) Picture of the panic (part three)

Description Andreas Kohn 2006-01-21 14:51:52 UTC

Friend tries to install Suse 10.0 on his computer:
- MSI 915P Combo board
- Pentium 4 3.4GHz Hyperthreading
- ATI x800 PCI Express graphics card
- SATA on-board controller with 80G sata hard drive

Kernel panic happens everytime, regardless of 
- booting safe mode or booting regular
- disabling or enabling HT in the  bios

Knoppix 4.0.2 (CD-version) with kernel 2.6.12 boots, and seems to detect everything except the network card.

Comment 1 Andreas Kohn 2006-01-21 14:53:42 UTC

Created attachment 64394 [details]
Picture of the panic (part one, taken with mobile phone)

Comment 2 Andreas Kohn 2006-01-21 14:54:22 UTC

Created attachment 64395 [details]
Picture of the panic (part two)

Comment 3 Andreas Kohn 2006-01-21 14:54:57 UTC

Created attachment 64396 [details]
Picture of the panic (part three)

Comment 5 Thomas Renninger 2006-01-24 11:06:59 UTC

Here the interesting part of the pictures:

EIP: 0060:<0xc00f0488>
pci_bios_find_device (0x1e/0x40)
pci_bios_sort
pci_bios_init
do_initcalls

Please try pci=noacpi - if this does not help try noapic boot options.
One of both should help.
BTW: There is a patch pending for YOU update kernel that solves a problem on some P4 HT. However this is not available yet, so better disable HT for now (only some are affected, but you never know).

I close this one for as this seem to me like a very machine specific bug, for which we probably won't put anything into 10.0.

Please try the latest OpenSuse 10.1 version and reopen if you still face this problem (or if above boot params did not work).