Bug 1966 - Kernel does not boot when pci=noacpi (3ware 7506-8)
Summary: Kernel does not boot when pci=noacpi (3ware 7506-8)
Status: CLOSED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64 (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Andi Kleen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-28 10:05 UTC by Jan "Yenya" Kasprzak
Modified: 2004-12-12 08:55 UTC (History)
0 users

See Also:
Kernel Version: 2.6.1
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Jan "Yenya" Kasprzak 2004-01-28 10:05:53 UTC 
Distribution: Fedora Core 0.96 (x86-64)

Hardware Environment: Tyan Thunder K8S Pro (S2882), 3ware Escalade 7506-8,
4GB RAM, dual Opteron 244

Software Environment: Linux 2.6.1, 64-bit compiled.

Problem Description: The kernel does not boot when pci=noacpi option is in use.
It hangs during the 3ware card initialization - prints the following messages:

3w-xxxx: scsi0: UNIT #0: Command (000001002645b0) timed out, resetting card
3w-xxxx: scsi0: UNIT #0: Command (000001002645b0) timed out, resetting card

Then it tries the same with UNIT #1 (whatever it is, I have only one 3ware card
and only one RAID volume) and then the system locks up.

With acpi=off it boots correctly, as well as without pci=noacpi.

Kernel config and other possible details available on request.
Comment 1 Len Brown 2004-02-06 23:34:02 UTC 
please attach the dmesg and /proc/interrupts for the case where no boot flags are used. 
curious why pci=noacpi is being attempted if the system boots without it. 
 
thanks, 
-Len
Comment 2 Jan "Yenya" Kasprzak 2004-12-12 08:55:13 UTC 
This seems to be fixed in 2.6.10-rc2 (did not check anything between).
Note You need to log in before you can comment on or make changes to this bug.