Bug 2122 - ccis hang on boot unless pci=noacpi - HP Proliant DL360
Summary: ccis hang on boot unless pci=noacpi - HP Proliant DL360
Status: REJECTED UNREPRODUCIBLE
Alias: None
Product: ACPI
Classification: Unclassified
Component: ACPICA-Core (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: Len Brown
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-17 02:40 UTC by miki
Modified: 2006-09-28 13:12 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.2 Original
Subsystem:
Regression: ---
Bisected commit-id:

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

Description miki 2004-02-17 02:40:43 UTC 
Distribution: Debian Woody
Hardware Environment: Xeon, Smart Array 5, ( HP Proliant DL360 )
Software Environment: On Boot
Problem Description: cciss driver stuck on boot becous acpi

Steps to reproduce:

This is the message i get on the screen:

Compaq CISS Driver (v 2.5.0)
ACPI: Unable to set IRQ fo PCI Interrupt Link [IN31] (likely buggy ACPI BIOS).
Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
ACPI: No IRQ known for interrupt pin A of device 0000:00:04.0
cciss: using DAC cycles
      blocks= 71122560 block_size= 512
      heads= 255, sectors= 32, cylinders= 8716

I was able to start the system using pci=noacpi.
Comment 1 Len Brown 2004-02-25 14:36:02 UTC 
if pci=noacpi is required to make the system work, then this is an ACPI bug (or a BIOS bug). 
 
Can you verify that you've got the latest BIOS? 
 
Please attach the output of acpidmp, available in /usr/sbin, or in pmtools: 
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/ 
 
please attach the output from lspci -v and /proc/interrupts for the pci=noacpi case. 
 
If this is not your boot device and you can get up as far as single user without pci=noacpi, then 
please capture dmesg -s40000 for the failure case (or capture a console log) and /proc/interrupts. 
 
any chance you can try a 2.6.3 kernel? 
 
thanks, 
-Len
Comment 2 Len Brown 2004-11-15 19:58:58 UTC 
better luck with linux-2.6.9?
Comment 3 Len Brown 2005-01-03 15:18:42 UTC 
Please re-open if still an issue with linux-2.6.10 or later.
Note You need to log in before you can comment on or make changes to this bug.