IA64 test report: 2.6.0-test11/tiger 2003-12-18: 9/9 pass
ACPI Test Report for 2.6 ia64 kernel
=========================
Hardware Configuration:
-----------------------
System Name: ACPI-Tiger
System Type: 4 way 900 Itanium2, tiger
M/B revision: N/A
Processor version: N/A
Firmware Versions: N/A
I/O configuration summary:
MPT scsi host driver
Seagate ST318406LC boot drive
IDE floppy and CDROM
Serial console
USB mouse
USB keyboard
Ethernet Pro 1000
Software Configuration:
1.Bk pull form http://lia64.bkbits.net/linux-ia64-2.5 on 12/18(Shanghai time) 2.bk pull from http://linux-acpi.bkbits.net/linux-acpi-test-2.6.0 on 12/18 (Shanghai time) resolved 2 conflicts manually
ACPI Features Tested: (prioritized).
--------------------
1. Boot tested ok
2. serial console tested ok
3. ATI (run X window system) tested ok
4. usb keyboard tested ok
5. USB mouse tested ok
6. NIC (eg. Ping or ftp) tested ok
7. IDE (eg. r/w floppy or CDROM) tested ok
8. SCI (eg. Press power button) tested ok
9. Soft Power off tested ok
CPU0 CPU1 CPU2 CPU3
29: 0 0 0 0 LSAPIC cmc_poll 30: 0 0 0 0 IO-SAPIC-level cpe_hndlr 31: 0 0 0 0 LSAPIC cmc_hndlr 34: 1 182 2 0 IO-SAPIC-edge ide0 39: 0 5 0 0 IO-SAPIC-level acpi 45: 0 6 1 0 IO-SAPIC-edge serial 48: 0 0 0 0 IO-SAPIC-level ehci_hcd 49: 0 2063 57 0 IO-SAPIC-level uhci_hcd 50: 0 0 0 0 IO-SAPIC-level uhci_hcd 51: 0 4214 60 0 IO-SAPIC-level eth0 56: 0 4097 118 0 IO-SAPIC-level ioc0 57: 0 42 0 0 IO-SAPIC-level ioc1 232: 0 0 0 0 LSAPIC mca_rdzv 238: 0 0 0 0 LSAPIC perfmon 239: 2572798 2566770 2567274 2566821 LSAPIC timer 240: 0 0 0 0 LSAPIC mca_wkup 254: 36 95 106 99 LSAPIC IPI NMI: 0 0 0 0 ERR: 0
Problems:
1.alloc 0xffff-0x0 from PCI IO for PCI Bus 0000:08 failed Known issue, bjorn has idea to fix it.
2. pci_irq-0302 [03] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:1f.1
ACPI: No IRQ known for interrupt pin A of device 0000:00:1f.1 Please refere http://bugzilla.kernel.org/show_bug.cgi?id=1534
3. hda: packet command error: status=0x51 { DriveReady SeekComplete Error } <<2.6.ZIP>>
Quoted 3 lines · Luming
Problems:
1.alloc 0xffff-0x0 from PCI IO for PCI Bus 0000:08 failed Known issue, bjorn has idea to fix it.
Nope. This one:
alloc 0x0-0x5fff from PCI IO for PCI Bus 0000:00 failed
is caused by the VGA driver having allocated ports before we discover the PCI root bridges. We know how to fix that.
All these:
alloc 0xffffffff-0x0 from PCI mem for PCI Bus 0000:02 failed alloc 0xffffffff-0x0 from PCI mem for PCI Bus 0000:08 failed alloc 0xffffffff-0x0 from PCI mem for PCI Bus 0000:08 failed alloc 0xffffffff-0x0 from PCI mem for PCI Bus 0000:08 failed alloc 0xffff-0x0 from PCI IO for PCI Bus 0000:08 failed alloc 0xffffffff-0x0 from PCI mem for PCI Bus 0000:09 failed alloc 0xffffffff-0x0 from PCI mem for PCI Bus 0000:0f failed
just look like bogus _CRS entries. (What does it mean to have an address space descriptor that starts at 0xffffffff and ends at 0x0?) These warnings should be innocuous, because we just ignore these descriptors.
Similarly, these:
acpi_serial_port: zero-length IO port range?
acpi_serial_port: zero-length IO port range?
also look bogus (there's a UART device with an IO port space descriptor with range_length of zero). What's that supposed to mean? Again, these should be harmless, because we ignore these descriptors.
Quoted 3 lines
2. pci_irq-0302 [03]
acpi_pci_irq_derive: Unable to derive IRQ for device 0000:00:1f.1
ACPI: No IRQ known for interrupt pin A of device 0000:00:1f.1 Please refere http://bugzilla.kernel.org/show_bug.cgi?id34
ACPI is supposed to tell us how PCI interrupts are routed. Here's a device that has no routing information. Either the firmware is broken, or the ACPI code in Linux hasn't implemented some piece of the spec.
Can you please ask your firmware folks about
1) Why the strange "0xffffffff-0x0" descriptors in PCI root bridge _CRS?
2) Why the zero-length IO port descriptors in UART _CRS?
3) Why no IRQ routing information for PCI device 0000:00:1f.1?
If it turns out that Linux is just missing the smarts to interpret these things, I'll be happy to fix that. But right now, they all look like firmware defects.
Bjorn
Quoted 2 lines · Bjorn Helgaas
(What does it mean to have an
address space descriptor that starts at0xffffffffand ends at0x0?)
For PCI-PCI bridges, it means disable that particular window/range register. ie don't decode and route transactions. Not sure that's what is intended since since I don't know who is intended to "consume" the offending entries.
grant
Quoted 3 lines
Quoted 2 lines
(What does it mean to have an
address space descriptor that starts at0xffffffffand ends at0x0?)For PCI-PCI bridges, it means disable that particular window/range
register.
Quoted 1 line
ie don't decode and route transactions.
But I didn't find this kind of explanation on ACPI spec.
Quoted 7 lines · Luming
Quoted 3 lines
Quoted 2 lines
(What does it mean to have an
address space descriptor that starts at0xffffffffand ends at0x0?)For PCI-PCI bridges, it means disable that particular window/range
register.
Quoted 1 line
ie don't decode and route transactions.
But I didn't find this kind of explanation on ACPI spec.
I was just commenting on how PCI-PCI Bridges behave and I know OS code (both linux and hpux) expects this behavior.
I have no idea what ACPI says about this or even if ACPI specification should dictate this behavior.
grant