Bug 1127 - Asus PR-DLSW: Cannot boot with ACPI enabled
Summary: Asus PR-DLSW: Cannot boot with ACPI enabled
Status: REJECTED DUPLICATE of bug 1662
Alias: None
Product: ACPI
Classification: Unclassified
Component: BIOS (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Len Brown
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-19 21:17 UTC by Erich Stamberger
Modified: 2004-04-22 13:15 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.0-test3-bk7
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
dmesg with acpi turned on (13.70 KB, text/plain)
2004-01-05 08:10 UTC, Erich Stamberger
Details
dmesg with acpi=ht (12.06 KB, text/plain)
2004-01-05 08:13 UTC, Erich Stamberger
Details
dmesg with pci=noacpi (15.60 KB, text/plain)
2004-01-05 08:15 UTC, Erich Stamberger
Details
output of dmidecode (15.09 KB, text/plain)
2004-01-05 08:16 UTC, Erich Stamberger
Details
acpidmp output (70.48 KB, text/plain)
2004-01-05 08:17 UTC, Erich Stamberger
Details

Description Erich Stamberger 2003-08-19 21:17:11 UTC
Distribution:
   Debian Testing

Hardware Environment:
   Asus PR-DLSW Mainboard
   ASUS PR-DLSW ACPI BIOS Revision 1008 

Software Environment:
   gcc-2.95.4

Problem Description:

 o Can only boot with acpi=off or acpi=ht

 o System fails to boot when ACPI support is enabled. Doesn't
   detect all PCI busses / controllers:

   VFS: Cannot open root device "801" or unknown-block(8,1)
   Please append a correct "root=" boot option
   Try booting with pci=noacpi, acpi=ht, or acpi=off on the
   command line.
   If one helps, please report the following lines:
   DMI: BIOS: Award Software, Inc., ASUS PR-DLSW ACPI BIOS
   Revision 1008, 09/25/2002
   DMI: System: System Manufacturer, System Name, System Version
   DMI: Board: ASUSTeK Computer INC., PR-DLSW, REV 1.xx
   Kernel panic: VFS: Unable to mount root fs on unknown-block(8,1)

 o System hangs with pci=noapci

   scsi0 : sym-2.1.16a
   sym0:0:0: ABORT operation started.
   sym0:0:0: ABORT operation timed-out.
   sym0:0:0: DEVICE RESET operation started.
   sym0:0:0: DEVICE RESET operation timed-out.
   sym0:0:0: BUS RESET operation started.
   sym0: SCSI BUS reset detected.
   sym0: SCSI BUS has been reset.
   sym0:0:0: BUS RESET operation complete.
   sym0:0:0: ABORT operation started.
   sym0:0:0: ABORT operation timed-out.
   sym0:0:0: HOST RESET operation started.
   sym0: SCSI BUS has been reset.


Steps to reproduce:

   Compile kernel and try to boot.

Complete logs, config, output of acpidmp and dmidecode are at
http://gewi.kfunigraz.ac.at/~eberger/pr-dlsw
Comment 1 Luming Yu 2003-09-03 07:37:53 UTC
Please reference bug#10 , It looks like a similar issue fixed there.
Comment 2 Len Brown 2003-11-12 20:39:21 UTC
The link with the info doesn't answer, so I've got nothing to work with here. 
If you're running the latest BIOS and the latest 2.4 or 2.6 kernel still fails, 
please re-open this bug and attach the acpidmp and dmidecode 
and dmesg from the acpi=ht case. 
 
Comment 3 Erich Stamberger 2004-01-05 08:10:10 UTC
Created attachment 1797 [details]
dmesg with acpi turned on
Comment 4 Erich Stamberger 2004-01-05 08:13:06 UTC
Created attachment 1798 [details]
dmesg with acpi=ht
Comment 5 Erich Stamberger 2004-01-05 08:15:09 UTC
Created attachment 1799 [details]
dmesg with pci=noacpi
Comment 6 Erich Stamberger 2004-01-05 08:16:22 UTC
Created attachment 1800 [details]
output of dmidecode
Comment 7 Erich Stamberger 2004-01-05 08:17:35 UTC
Created attachment 1801 [details]
acpidmp output
Comment 8 Shaohua 2004-01-05 19:35:41 UTC
>ACPI: PCI Root Bridge [PCI0] (00:00)
>ACPI: PCI Root Bridge [PCI1] (00:00)
>ACPI: PCI Root Bridge [PCI2] (00:00)
the same problem as bug 1162
Comment 9 Shaohua 2004-01-05 19:38:32 UTC
oh, oops, should be the same as Bug 1662
Comment 10 Len Brown 2004-01-08 18:10:39 UTC

*** This bug has been marked as a duplicate of 1662 ***

Note You need to log in before you can comment on or make changes to this bug.