2005-09-02 23:38:16

by Andreas Koch

[permalink] [raw]
Subject: 2.6.13: Crash in Yenta initialization

This does not happen in my current kernel (2.6.12-rc6 with Ivan's PCI bridge
patches applied). It is definitely localized in the Yenta code, since the
boot proceeds when I disable the Yenta config option. My hardware is an Acer
Travelmate 8104 with the external ezDock attached.

I can provide more info if you let me know what to look for.

Andreas Koch

Linux version 2.6.13 (root@meneldor) (gcc version 3.3.5-20050130 (Gentoo Linux
3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1)) #2 Fri Sep 2 23:34:19
CEST 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000ce000 - 00000000000d0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007fe80000 (usable)
BIOS-e820: 000000007fe80000 - 000000007fe89000 (ACPI data)
BIOS-e820: 000000007fe89000 - 000000007ff00000 (ACPI NVS)
BIOS-e820: 000000007ff00000 - 0000000080000000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0006000 (reserved)
BIOS-e820: 00000000f0008000 - 00000000f000c000 (reserved)
BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
1150MB HIGHMEM available.
896MB LOWMEM available.
DMI present.
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:13 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x02] address[0xfec20000] gsi_base[24])
IOAPIC[1]: apic_id 2, version 32, address 0xfec20000, GSI 24-47
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Enabling APIC mode: Flat. Using 2 I/O APICs
ACPI: HPET id: 0x8086a201 base: 0x0
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 80000000 (gap: 80000000:60000000)
Built 1 zonelists
Kernel command line: root=/dev/ram0 lvm2root=/dev/vg0/root console=ttyS0
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Detected 1995.744 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 2069152k/2095616k available (3513k kernel code, 25172k reserved, 1575k
data, 212k init, 1178112k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 3995.10 BogoMIPS
(lpj=1997552)
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
mtrr: v2.0 (20020519)
CPU: Intel(R) Pentium(R) M processor 2.00GHz stepping 08
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 pin1=2 pin2=-1
checking if image is initramfs...it isn't (no cpio magic); looks like an
initrd
Freeing initrd memory: 2061k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd6ce, last bus=8
PCI: Using MMCONFIG
ACPI: Subsystem revision 20050408
ACPI-0362: *** Error: Looking up [Z00G] in namespace, AE_NOT_FOUND
search_node c20d9140 start_node c20d9140 return_node 00000000
ACPI-0362: *** Error: Looking up [Z00G] in namespace, AE_NOT_FOUND
search_node c20d9d80 start_node c20d9d80 return_node 00000000
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] segment is 0
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.2
PCI: PXH quirk detected, disabling MSI for SHPC device
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 *10 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: Embedded Controller [EC0] (gpe 29)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 12 devices
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.0
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.0
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.0
PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.2
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.2
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.2
PCI: Cannot allocate resource region 7 of bridge 0000:02:00.0
PCI: Cannot allocate resource region 8 of bridge 0000:02:00.0
PCI: Cannot allocate resource region 4 of device 0000:03:02.0
PCI: Cannot allocate resource region 4 of device 0000:03:02.1
PCI: Cannot allocate resource region 0 of device 0000:03:02.2
PCI: Cannot allocate resource region 4 of device 0000:03:03.0
PCI: Cannot allocate resource region 4 of device 0000:03:03.1
PCI: Cannot allocate resource region 0 of device 0000:03:03.2
PCI: Cannot allocate resource region 0 of device 0000:03:04.0
PCI: Cannot allocate resource region 1 of device 0000:03:04.0
PCI: Cannot allocate resource region 0 of device 0000:03:05.0
PCI: Cannot allocate resource region 0 of device 0000:03:06.0
PCI: Bridge: 0000:00:01.0
IO window: 2000-2fff
MEM window: c8100000-c81fffff
PREFETCH window: d0000000-d7ffffff
PCI: Bridge: 0000:00:1c.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.1
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bus 4, cardbus bridge: 0000:03:05.0
IO window: 00003000-000030ff
IO window: 00003400-000034ff
PREFETCH window: 80000000-81ffffff
MEM window: 84000000-85ffffff
PCI: Bridge: 0000:02:00.0
IO window: 3000-3fff
MEM window: 84000000-86ffffff
PREFETCH window: 80000000-81ffffff
PCI: Bridge: 0000:00:1c.2
IO window: 3000-3fff
MEM window: 84000000-86ffffff
PREFETCH window: 80000000-81ffffff
PCI: Bus 7, cardbus bridge: 0000:06:09.0
IO window: 00004000-000040ff
IO window: 00004400-000044ff
PREFETCH window: 82000000-83ffffff
MEM window: 88000000-89ffffff
PCI: Bridge: 0000:00:1e.0
IO window: 4000-4fff
MEM window: c8400000-c84fffff
PREFETCH window: 82000000-83ffffff
ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Device 0000:00:1c.0 not available because of resource collisions
PCI: Device 0000:00:1c.1 not available because of resource collisions
PCI: Enabling device 0000:00:1c.2 (0000 -> 0003)
ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 17
ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 31 (level, low) -> IRQ 18
ACPI: PCI Interrupt 0000:06:09.0[A] -> GSI 18 (level, low) -> IRQ 17
Simple Boot Flag at 0x36 set to 0x1
Machine check exception polling timer started.
audit: initializing netlink socket (disabled)
audit(1125704367.262:1): initialized
highmem bounce pool size: 64 pages
Installing knfsd (copyright (C) 1996 [email protected]).
NTFS driver 2.1.23 [Flags: R/O].
Initializing Cryptographic API
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
pciehp: add_host_bridge: status 5
pciehp: Fails to gain control of native hot-plug
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
assign_interrupt_mode Found MSI capability
PCI: Device 0000:00:1c.0 not available because of resource collisions
PCI: Device 0000:00:1c.1 not available because of resource collisions
ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 17
assign_interrupt_mode Found MSI capability
ACPI: AC Adapter [ACAD] (on-line)
ACPI: Battery Slot [BAT1] (battery absent)
ACPI: Battery Slot [BAT2] (battery absent)
ACPI: Power Button (FF) [PWRF]
ACPI: Lid Switch [LID]
ACPI: Power Button (CM) [PWRB]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
ACPI: CPU0 (power states: C1[C1] C2[C2])
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI: Thermal Zone [THRM] (64 C)
lp: driver loaded but no devices found
Real Time Clock Driver v1.12
Linux agpgart interface v0.101 (c) Dave Jones
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a NS16550A
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ACPI: PCI Interrupt 0000:03:06.0[A] -> GSI 32 (level, low) -> IRQ 19
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP(,...)]
lp0: using parport0 (interrupt-driven).
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
pktcdvd: v0.2.0a 2004-07-14 Jens Axboe ([email protected]) and [email protected]
tg3.c:v3.37 (August 25, 2005)
ACPI: PCI Interrupt 0000:06:06.0[A] -> GSI 16 (level, low) -> IRQ 16
eth0: Tigon3 [partno(BCM95788A50) rev 3003 PHY(5705)] (PCI:33MHz:32-bit)
10/100/1000BaseT Ethernet 00:c0:9f:75:57:33
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[0] TSOcap[1]
eth0: dma_rwctrl[763f0000]
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 20
ACPI: PCI interrupt for device 0000:00:1f.2 disabled
ahci: probe of 0000:00:1f.2 failed with error -12
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 20
ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x18A0 irq 14
ata1: dev 0 ATA, max UDMA/100, 195371568 sectors: lba48
ata1(0): applying bridge limits
ata1: dev 0 configured for UDMA/100
scsi0 : ata_piix
Vendor: ATA Model: TOSHIBA MK1032GA Rev: AB21
Type: Direct-Access ANSI SCSI revision: 05
ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x18A8 irq 15
ata2: dev 0 ATAPI, max UDMA/33
ata2(0): applying bridge limits
ata2: dev 0 configured for UDMA/33
scsi1 : ata_piix
Vendor: HL-DT-ST Model: DVDRAM GMA-4080N Rev: 0H35
Type: CD-ROM ANSI SCSI revision: 05
SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 5
ohci1394: $Rev: 1299 $ Ben Collins <[email protected]>
ACPI: PCI Interrupt 0000:03:04.0[A] -> GSI 30 (level, low) -> IRQ 21
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[21] MMIO=[86005000-860057ff]
Max Packet=[2048]
ACPI: PCI Interrupt 0000:06:07.0[A] -> GSI 19 (level, low) -> IRQ 20
ohci1394: fw-host1: OHCI-1394 1.1 (PCI): IRQ=[20] MMIO=[c8415000-c84157ff]
Max Packet=[2048]
ieee1394: raw1394: /dev/raw1394 device initialized
sbp2: $Rev: 1306 $ Ben Collins <[email protected]>
ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 31 (level, low) -> IRQ 18
Yenta: CardBus bridge found at 0000:03:05.0 [104c:ac50]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:03:05.0, mfunc 0x00521d22, devctl 0x66
Yenta: ISA IRQ mask 0x0000, PCI irq 18
Socket status: 30000006
pcmcia: parent PCI bridge I/O window: 0x3000 - 0x3fff
pcmcia: parent PCI bridge Memory window: 0x84000000 - 0x86ffffff
pcmcia: parent PCI bridge Memory window: 0x80000000 - 0x81ffffff
ACPI: PCI Interrupt 0000:06:09.0[A] -> GSI 18 (level, low) -> IRQ 17
Yenta: CardBus bridge found at 0000:06:09.0 [1025:0070]
Yenta O2: res at 0x94/0xD4: ff/ea
Yenta O2: enabling read prefetch/write burst
Yenta: ISA IRQ mask 0x0438, PCI irq 17
Socket status: 30000006
pcmcia: parent PCI bridge I/O window: 0x4000 - 0x4fff
pcmcia: parent PCI bridge Memory window: 0xc8400000 - 0xc84fffff
pcmcia: parent PCI bridge Memory window: 0x82000000 - 0x83ffffff
ACPI: PCI Interrupt 0000:06:09.1[A] -> GSI 18 (level, low) -> IRQ 17
Yenta: CardBus bridge found at 0000:06:09.1 [1025:0070]
Unable to handle kernel NULL pointer dereference at virtual address 0000004f
printing eip:
c03af658
*pde = 00000000
Oops: 0000 [#1]
Modules linked in:
CPU: 0
EIP: 0060:[<c03af658>] Not tainted VLI
EFLAGS: 00010292 (2.6.13)
EIP is at yenta_config_init+0xd8/0x170
eax: 00000000 ebx: dfcb7000 ecx: 00000000 edx: e0649000
esi: dff75000 edi: 00001000 ebp: dff75000 esp: dfd9fea8
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, threadinfo=dfd9e000 task=dfdc7a00)
Stack: dff7d880 00000049 0000000d 000000a8 c011f9d7 fffffff4 dfcb7000 c03af810
dfcb7000 dff750d8 00001025 00000070 c05abf20 ffffffed dff75000 c05ac340
c05ac36c c028927f dff75000 c05ac2d8 c05ac340 dff75000 dff75044 c02892bf
Call Trace:
[<c011f9d7>] printk+0x17/0x20
[<c03af810>] yenta_probe+0x120/0x280
[<c028927f>] __pci_device_probe+0x5f/0x70
[<c02892bf>] pci_device_probe+0x2f/0x50
[<c03211c8>] driver_probe_device+0x38/0xb0
[<c03212c0>] __driver_attach+0x0/0x50
[<c0321307>] __driver_attach+0x47/0x50
[<c03207a9>] bus_for_each_dev+0x69/0x80
[<c0321335>] driver_attach+0x25/0x30
[<c03212c0>] __driver_attach+0x0/0x50
[<c0320cfd>] bus_add_driver+0x8d/0xe0
[<c0289580>] pci_register_driver+0x70/0x90
[<c061906f>] yenta_socket_init+0xf/0x20
[<c05fc8cb>] do_initcalls+0x2b/0xc0
[<c0100290>] init+0x0/0x110
[<c0100290>] init+0x0/0x110
[<c01002ba>] init+0x2a/0x110
[<c0101378>] kernel_thread_helper+0x0/0x18
[<c010137d>] kernel_thread_helper+0x5/0x18
Code: ed ff 8b 13 b9 a8 00 00 00 b8 0d 00 00 00 89 4c 24 0c 89 44 24 08 8b 42
20 89 44 24 04 8b 42 10 89 04 24 e8 bb 56 ed ff 8b 4e 14 <0f> b6 51 4f 0f b6
41 4e c1 e2 10 c1 e0 08 09 c2 0f b6 41 4d 8b
<0>Kernel panic - not syncing: Attempted to kill init!


2005-09-03 00:38:04

by Andrew Morton

[permalink] [raw]
Subject: Re: 2.6.13: Crash in Yenta initialization

Andreas Koch <[email protected]> wrote:
>
> This does not happen in my current kernel (2.6.12-rc6 with Ivan's PCI bridge
> patches applied). It is definitely localized in the Yenta code, since the
> boot proceeds when I disable the Yenta config option. My hardware is an Acer
> Travelmate 8104 with the external ezDock attached.
>
> I can provide more info if you let me know what to look for.
>
> ...
> Yenta: CardBus bridge found at 0000:06:09.1 [1025:0070]
> Unable to handle kernel NULL pointer dereference at virtual address 0000004f
> printing eip:
> c03af658
> *pde = 00000000
> Oops: 0000 [#1]
> Modules linked in:
> CPU: 0
> EIP: 0060:[<c03af658>] Not tainted VLI
> EFLAGS: 00010292 (2.6.13)
> EIP is at yenta_config_init+0xd8/0x170
> eax: 00000000 ebx: dfcb7000 ecx: 00000000 edx: e0649000
> esi: dff75000 edi: 00001000 ebp: dff75000 esp: dfd9fea8
> ds: 007b es: 007b ss: 0068
> Process swapper (pid: 1, threadinfo=dfd9e000 task=dfdc7a00)
> Stack: dff7d880 00000049 0000000d 000000a8 c011f9d7 fffffff4 dfcb7000 c03af810
> dfcb7000 dff750d8 00001025 00000070 c05abf20 ffffffed dff75000 c05ac340
> c05ac36c c028927f dff75000 c05ac2d8 c05ac340 dff75000 dff75044 c02892bf
> Call Trace:
> [<c011f9d7>] printk+0x17/0x20
> [<c03af810>] yenta_probe+0x120/0x280
> [<c028927f>] __pci_device_probe+0x5f/0x70
> [<c02892bf>] pci_device_probe+0x2f/0x50
> [<c03211c8>] driver_probe_device+0x38/0xb0
> [<c03212c0>] __driver_attach+0x0/0x50
> [<c0321307>] __driver_attach+0x47/0x50
> [<c03207a9>] bus_for_each_dev+0x69/0x80
> [<c0321335>] driver_attach+0x25/0x30
> [<c03212c0>] __driver_attach+0x0/0x50
> [<c0320cfd>] bus_add_driver+0x8d/0xe0
> [<c0289580>] pci_register_driver+0x70/0x90
> [<c061906f>] yenta_socket_init+0xf/0x20
> [<c05fc8cb>] do_initcalls+0x2b/0xc0
> [<c0100290>] init+0x0/0x110
> [<c0100290>] init+0x0/0x110
> [<c01002ba>] init+0x2a/0x110
> [<c0101378>] kernel_thread_helper+0x0/0x18
> [<c010137d>] kernel_thread_helper+0x5/0x18
> Code: ed ff 8b 13 b9 a8 00 00 00 b8 0d 00 00 00 89 4c 24 0c 89 44 24 08 8b 42
> 20 89 44 24 04 8b 42 10 89 04 24 e8 bb 56 ed ff 8b 4e 14 <0f> b6 51 4f 0f b6
> 41 4e c1 e2 10 c1 e0 08 09 c2 0f b6 41 4d 8b
> <0>Kernel panic - not syncing: Attempted to kill init!
>

I don't think any of the recent yenta changes would have caused this.

The .config might help.

Also, can you identify which line is going oops? Set CONFIG_DEBUG_INFO,
retest, do

gdb vmlinux
(gdb) l *0xc03af658 (the EIP value)

thanks.

2005-09-03 00:45:18

by Andreas Koch

[permalink] [raw]
Subject: Re: 2.6.13: Crash in Yenta initialization

As a follow-up to my previous mail, I collected a boot log of the working
kernel 2.6.12-rc6 with Ivan's bridge initialization patches below. The
crucial part seem to be the different bridge initialization sections:

2.6.12-rc6 + Ivan's patches:

PCI: Bridge: 0000:00:01.0
IO window: 2000-2fff
MEM window: c8100000-c81fffff
PREFETCH window: d0000000-d7ffffff
PCI: Bridge: 0000:00:1c.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.1
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bus 4, cardbus bridge: 0000:03:05.0
IO window: 00003000-00003fff
IO window: 00004000-00004fff
PREFETCH window: 80000000-81ffffff
MEM window: 88000000-89ffffff
PCI: Bridge: 0000:02:00.0
IO window: 3000-5fff
MEM window: 88000000-8affffff
PREFETCH window: 80000000-81ffffff
PCI: Bridge: 0000:00:1c.2
IO window: 3000-5fff
MEM window: 88000000-8affffff
PREFETCH window: 80000000-81ffffff
PCI: Bus 7, cardbus bridge: 0000:06:09.0
IO window: 00006000-00006fff
IO window: 00007000-00007fff
PREFETCH window: 82000000-83ffffff
MEM window: 8c000000-8dffffff
PCI: Bus 11, cardbus bridge: 0000:06:09.1
IO window: 00008000-00008fff
IO window: 00009000-00009fff
PREFETCH window: 84000000-85ffffff
MEM window: 8e000000-8fffffff
PCI: Bus 15, cardbus bridge: 0000:06:09.3
IO window: 0000a000-0000afff
IO window: 0000b000-0000bfff
PREFETCH window: 86000000-87ffffff
MEM window: 90000000-91ffffff
PCI: Bridge: 0000:00:1e.0
IO window: 6000-bfff
MEM window: c8400000-c84fffff
PREFETCH window: 82000000-87ffffff

... Versus the much shorter output from 2.6.13

PCI: Bridge: 0000:00:01.0
IO window: 2000-2fff
MEM window: c8100000-c81fffff
PREFETCH window: d0000000-d7ffffff
PCI: Bridge: 0000:00:1c.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.1
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bus 4, cardbus bridge: 0000:03:05.0
IO window: 00003000-000030ff
IO window: 00003400-000034ff
PREFETCH window: 80000000-81ffffff
MEM window: 84000000-85ffffff
PCI: Bridge: 0000:02:00.0
IO window: 3000-3fff
MEM window: 84000000-86ffffff
PREFETCH window: 80000000-81ffffff
PCI: Bridge: 0000:00:1c.2
IO window: 3000-3fff
MEM window: 84000000-86ffffff
PREFETCH window: 80000000-81ffffff
PCI: Bus 7, cardbus bridge: 0000:06:09.0
IO window: 00004000-000040ff
IO window: 00004400-000044ff
PREFETCH window: 82000000-83ffffff
MEM window: 88000000-89ffffff
PCI: Bridge: 0000:00:1e.0
IO window: 4000-4fff
MEM window: c8400000-c84fffff
PREFETCH window: 82000000-83ffffff

Below the full boot log for the working 2.6.12-rc6+IvanPatches

I hope this additional info helps to bring this part of 2.6.13 up to the
earlier capability.

Andreas Koch

Linux version 2.6.12-rc6 (root@meneldor) (gcc version 3.3.5-20050130 (Gentoo
Linux 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1)) #11 Sat Sep 3
01:09:47 CEST 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000ce000 - 00000000000d0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007fe80000 (usable)
BIOS-e820: 000000007fe80000 - 000000007fe89000 (ACPI data)
BIOS-e820: 000000007fe89000 - 000000007ff00000 (ACPI NVS)
BIOS-e820: 000000007ff00000 - 0000000080000000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0006000 (reserved)
BIOS-e820: 00000000f0008000 - 00000000f000c000 (reserved)
BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
1150MB HIGHMEM available.
896MB LOWMEM available.
On node 0 totalpages: 523904
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 225280 pages, LIFO batch:31
HighMem zone: 294528 pages, LIFO batch:31
DMI present.
ACPI: RSDP (v000 PTLTD ) @ 0x000f68d0
ACPI: RSDT (v001 PTLTD RSDT 0x06040000 LTP 0x00000000) @ 0x7fe80e14
ACPI: FADT (v001 INTEL ALVISO 0x06040000 LOHR 0x0000005f) @ 0x7fe88e8a
ACPI: MADT (v001 INTEL ALVISO 0x06040000 LOHR 0x0000005f) @ 0x7fe88efe
ACPI: HPET (v001 INTEL ALVISO 0x06040000 LOHR 0x0000005f) @ 0x7fe88f64
ACPI: MCFG (v001 INTEL ALVISO 0x06040000 LOHR 0x0000005f) @ 0x7fe88f9c
ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x06040000 LTP 0x00000001) @ 0x7fe88fd8
ACPI: SSDT (v001 PmRef Cpu0Ist 0x00003000 INTL 0x20030224) @ 0x7fe81249
ACPI: SSDT (v001 PmRef Cpu0Cst 0x00003001 INTL 0x20030224) @ 0x7fe81071
ACPI: SSDT (v001 PmRef CpuPm 0x00003000 INTL 0x20030224) @ 0x7fe80e58
ACPI: DSDT (v001 INTEL ALVISO 0x06040000 MSFT 0x0100000e) @ 0x00000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:13 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x02] address[0xfec20000] gsi_base[24])
IOAPIC[1]: apic_id 2, version 32, address 0xfec20000, GSI 24-47
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 2 I/O APICs
ACPI: HPET id: 0x8086a201 base: 0x0
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 80000000 (gap: 80000000:60000000)
Built 1 zonelists
Kernel command line: root=/dev/ram0 lvm2root=/dev/vg0/root
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
mapped IOAPIC to ffffb000 (fec20000)
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Detected 1995.318 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 2069132k/2095616k available (3516k kernel code, 25232k reserved, 1584k
data, 220k init, 1178112k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 3923.96 BogoMIPS (lpj=1961984)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: afe9fbff 00100000 00000000 00000000
00000180 00000000 00000000
CPU: After vendor identify, caps: afe9fbff 00100000 00000000 00000000 00000180
00000000 00000000
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: After all inits, caps: afe9fbff 00100000 00000000 00000040 00000180
00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel(R) Pentium(R) M processor 2.00GHz stepping 08
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 pin1=2 pin2=-1
checking if image is initramfs...it isn't (no cpio magic); looks like an
initrd
Freeing initrd memory: 2107k freed
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfd6ce, last bus=8
PCI: Using MMCONFIG
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20050309
ACPI-0352: *** Error: Looking up [Z00G] in namespace, AE_NOT_FOUND
search_node dfdc6160 start_node dfdc6160 return_node 00000000
ACPI-0352: *** Error: Looking up [Z00G] in namespace, AE_NOT_FOUND
search_node dfdc6da0 start_node dfdc6da0 return_node 00000000
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.2
Boot video device is 0000:01:00.0
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEGP._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03.PXHA._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 *10 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: Embedded Controller [EC0] (gpe 29)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 12 devices
SCSI subsystem initialized
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.0
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.0
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.0
PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.2
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.2
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.2
PCI: Cannot allocate resource region 7 of bridge 0000:02:00.0
PCI: Cannot allocate resource region 8 of bridge 0000:02:00.0
PCI: Cannot allocate resource region 4 of device 0000:03:02.0
PCI: Cannot allocate resource region 4 of device 0000:03:02.1
PCI: Cannot allocate resource region 0 of device 0000:03:02.2
PCI: Cannot allocate resource region 4 of device 0000:03:03.0
PCI: Cannot allocate resource region 4 of device 0000:03:03.1
PCI: Cannot allocate resource region 0 of device 0000:03:03.2
PCI: Cannot allocate resource region 0 of device 0000:03:04.0
PCI: Cannot allocate resource region 1 of device 0000:03:04.0
PCI: Cannot allocate resource region 0 of device 0000:03:05.0
PCI: Cannot allocate resource region 0 of device 0000:03:06.0
PCI: Bridge: 0000:00:01.0
IO window: 2000-2fff
MEM window: c8100000-c81fffff
PREFETCH window: d0000000-d7ffffff
PCI: Bridge: 0000:00:1c.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.1
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bus 4, cardbus bridge: 0000:03:05.0
IO window: 00003000-00003fff
IO window: 00004000-00004fff
PREFETCH window: 80000000-81ffffff
MEM window: 88000000-89ffffff
PCI: Bridge: 0000:02:00.0
IO window: 3000-5fff
MEM window: 88000000-8affffff
PREFETCH window: 80000000-81ffffff
PCI: Bridge: 0000:00:1c.2
IO window: 3000-5fff
MEM window: 88000000-8affffff
PREFETCH window: 80000000-81ffffff
PCI: Bus 7, cardbus bridge: 0000:06:09.0
IO window: 00006000-00006fff
IO window: 00007000-00007fff
PREFETCH window: 82000000-83ffffff
MEM window: 8c000000-8dffffff
PCI: Bus 11, cardbus bridge: 0000:06:09.1
IO window: 00008000-00008fff
IO window: 00009000-00009fff
PREFETCH window: 84000000-85ffffff
MEM window: 8e000000-8fffffff
PCI: Bus 15, cardbus bridge: 0000:06:09.3
IO window: 0000a000-0000afff
IO window: 0000b000-0000bfff
PREFETCH window: 86000000-87ffffff
MEM window: 90000000-91ffffff
PCI: Bridge: 0000:00:1e.0
IO window: 6000-bfff
MEM window: c8400000-c84fffff
PREFETCH window: 82000000-87ffffff
ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:01.0 to 64
PCI: Device 0000:00:1c.0 not available because of resource collisions
PCI: Setting latency timer of device 0000:00:1c.0 to 64
PCI: Device 0000:00:1c.1 not available because of resource collisions
PCI: Setting latency timer of device 0000:00:1c.1 to 64
PCI: Enabling device 0000:00:1c.2 (0000 -> 0003)
ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1c.2 to 64
PCI: Setting latency timer of device 0000:02:00.0 to 64
ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 31 (level, low) -> IRQ 31
PCI: Setting latency timer of device 0000:00:1e.0 to 64
ACPI: PCI Interrupt 0000:06:09.0[A] -> GSI 18 (level, low) -> IRQ 18
ACPI: PCI Interrupt 0000:06:09.1[A] -> GSI 18 (level, low) -> IRQ 18
PCI: Enabling device 0000:06:09.3 (0080 -> 0083)
ACPI: PCI Interrupt 0000:06:09.3[A] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:06:09.3 to 64
Simple Boot Flag at 0x36 set to 0x1
Machine check exception polling timer started.
audit: initializing netlink socket (disabled)
audit(1125709926.697:0): initialized
highmem bounce pool size: 64 pages
Installing knfsd (copyright (C) 1996 [email protected]).
NTFS driver 2.1.22 [Flags: R/O].
Initializing Cryptographic API
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.4
Evaluate _OSC Set fails. Status = 0x0005
pciehp: add_host_bridge: status 5
pciehp: Fails to gain control of native hot-plug
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:01.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[pcie00]
Allocate Port Service[pcie03]
PCI: Device 0000:00:1c.0 not available because of resource collisions
PCI: Device 0000:00:1c.1 not available because of resource collisions
ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1c.2 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[pcie00]
Allocate Port Service[pcie02]
Allocate Port Service[pcie03]
ACPI: AC Adapter [ACAD] (on-line)
ACPI: Battery Slot [BAT1] (battery absent)
ACPI: Battery Slot [BAT2] (battery absent)
ACPI: Power Button (FF) [PWRF]
ACPI: Lid Switch [LID]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
ACPI: CPU0 (power states: C1[C1] C2[C2])
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI: Thermal Zone [THRM] (55 C)
lp: driver loaded but no devices found
Real Time Clock Driver v1.12
Linux agpgart interface v0.101 (c) Dave Jones
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a NS16550A
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ACPI: PCI Interrupt 0000:03:06.0[A] -> GSI 32 (level, low) -> IRQ 32
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP(,...)]
lp0: using parport0 (interrupt-driven).
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
pktcdvd: v0.2.0a 2004-07-14 Jens Axboe ([email protected]) and [email protected]
tg3.c:v3.29 (May 23, 2005)
ACPI: PCI Interrupt 0000:06:06.0[A] -> GSI 16 (level, low) -> IRQ 16
eth0: Tigon3 [partno(BCM95788A50) rev 3003 PHY(5705)] (PCI:33MHz:32-bit)
10/100/1000BaseT Ethernet 00:c0:9f:75:57:33
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[0] TSOcap[1]
eth0: dma_rwctrl[763f0000]
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH6M: IDE controller at PCI slot 0000:00:1f.2
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
ICH6M: chipset revision 4
ICH6M: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x18a0-0x18a7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x18a8-0x18af, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: TOSHIBA MK1032GAX, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: HL-DT-ST DVDRAM GMA-4080N, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
hda: max request size: 1024KiB
hda: 195371568 sectors (100030 MB), CHS=16383/255/63
hda: cache flushes supported
hda: hda1 hda2 hda3
hdc: ATAPI 24X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
ohci1394: $Rev: 1250 $ Ben Collins <[email protected]>
ACPI: PCI Interrupt 0000:03:04.0[A] -> GSI 30 (level, low) -> IRQ 30
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[30] MMIO=[8a005000-8a0057ff]
Max Packet=[2048]
ACPI: PCI Interrupt 0000:06:07.0[A] -> GSI 19 (level, low) -> IRQ 19
ohci1394: fw-host1: OHCI-1394 1.1 (PCI): IRQ=[19] MMIO=[c8415000-c84157ff]
Max Packet=[2048]
ieee1394: raw1394: /dev/raw1394 device initialized
sbp2: $Rev: 1219 $ Ben Collins <[email protected]>
ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 31 (level, low) -> IRQ 31
Yenta: CardBus bridge found at 0000:03:05.0 [104c:ac50]
yenta 0000:03:05.0: Preassigned resource 0 busy, reconfiguring...
yenta 0000:03:05.0: no resource of type 1200 available, trying to continue...
yenta 0000:03:05.0: Preassigned resource 1 busy, reconfiguring...
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:03:05.0, mfunc 0x00521d22, devctl 0x66
Yenta: ISA IRQ mask 0x0000, PCI irq 31
Socket status: 30000006
ACPI: PCI Interrupt 0000:06:09.0[A] -> GSI 18 (level, low) -> IRQ 18
Yenta: CardBus bridge found at 0000:06:09.0 [1025:0070]
yenta 0000:06:09.0: Preassigned resource 0 busy, reconfiguring...
yenta 0000:06:09.0: no resource of type 1200 available, trying to continue...
yenta 0000:06:09.0: Preassigned resource 1 busy, reconfiguring...
Yenta O2: res at 0x94/0xD4: ea/00
Yenta O2: enabling read prefetch/write burst
Yenta: ISA IRQ mask 0x0438, PCI irq 18
Socket status: 30000006
ACPI: PCI Interrupt 0000:06:09.1[A] -> GSI 18 (level, low) -> IRQ 18
Yenta: CardBus bridge found at 0000:06:09.1 [1025:0070]
yenta 0000:06:09.1: Preassigned resource 1 busy, reconfiguring...
Yenta: ISA IRQ mask 0x0438, PCI irq 18
Socket status: 30000006
ACPI: PCI Interrupt 0000:06:09.3[A] -> GSI 18 (level, low) -> IRQ 18
Yenta: CardBus bridge found at 0000:06:09.3 [1025:0070]
yenta 0000:06:09.3: Preassigned resource 1 busy, reconfiguring...
Yenta: ISA IRQ mask 0x0438, PCI irq 18
Socket status: 30000410
ieee1394: Host added: ID:BUS[0-00:1023] GUID[00c09f0000507951]
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 23
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
USB2 EHCI Controller
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xc8004000
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
ieee1394: Host added: ID:BUS[1-00:1023] GUID[00c09f000038d11c]
ACPI: PCI Interrupt 0000:03:02.2[C] -> GSI 26 (level, low) -> IRQ 26
ehci_hcd 0000:03:02.2: VIA Technologies, Inc. USB 2.0
ehci_hcd 0000:03:02.2: new USB bus registered, assigned bus number 2
ehci_hcd 0000:03:02.2: irq 26, io mem 0x8a005800
ehci_hcd 0000:03:02.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
ACPI: PCI Interrupt 0000:03:03.2[C] -> GSI 29 (level, low) -> IRQ 29
ehci_hcd 0000:03:03.2: VIA Technologies, Inc. USB 2.0 (#2)
ehci_hcd 0000:03:03.2: new USB bus registered, assigned bus number 3
ehci_hcd 0000:03:03.2: irq 29, io mem 0x8a005900
ehci_hcd 0000:03:03.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 4 ports detected
USB Universal Host Controller Interface driver v2.2
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 23
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
USB UHCI #1
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001800
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
USB UHCI #2
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001820
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
USB UHCI #3
usb 2-3: new high speed USB device using ehci_hcd and address 2
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001840
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
USB UHCI #4
hub 2-3:1.0: USB hub found
hub 2-3:1.0: 2 ports detected
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.3: irq 16, io base 0x00001860
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:03:02.0[A] -> GSI 24 (level, low) -> IRQ 24
uhci_hcd 0000:03:02.0: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller
uhci_hcd 0000:03:02.0: new USB bus registered, assigned bus number 8
uhci_hcd 0000:03:02.0: irq 24, io base 0x00005040
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:03:02.1[B] -> GSI 25 (level, low) -> IRQ 25
uhci_hcd 0000:03:02.1: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (#2)
uhci_hcd 0000:03:02.1: new USB bus registered, assigned bus number 9
uhci_hcd 0000:03:02.1: irq 25, io base 0x00005060
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:03:03.0[A] -> GSI 27 (level, low) -> IRQ 27
uhci_hcd 0000:03:03.0: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (#3)
uhci_hcd 0000:03:03.0: new USB bus registered, assigned bus number 10
uhci_hcd 0000:03:03.0: irq 27, io base 0x00005080
hub 10-0:1.0: USB hub found
hub 10-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:03:03.1[B] -> GSI 28 (level, low) -> IRQ 28
uhci_hcd 0000:03:03.1: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (#4)
uhci_hcd 0000:03:03.1: new USB bus registered, assigned bus number 11
uhci_hcd 0000:03:03.1: irq 28, io base 0x000050a0
hub 11-0:1.0: USB hub found
hub 11-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
usbcore: registered new driver auerswald
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: [email protected]
NET: Registered protocol family 2
IP: routing cache hash table of 16384 buckets, 128Kbytes
TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
ip_conntrack version 2.1 (8192 buckets, 65536 max) - 212 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ipt_recent v0.3.1: Stephen Frost <[email protected]>.
http://snowman.net/projects/ipt_recent/
arp_tables: (C) 2002 David S. Miller
NET: Registered protocol family 1
NET: Registered protocol family 17
ACPI wakeup devices:
AZAL RP01 RP02 RP04 USB1 USB2 USB3 USB4 USB7 LANC
ACPI: (supports S0 S3 S4 S5)
RAMDISK: Compressed image found at block 0
usb 2-3.1: new high speed USB device using ehci_hcd and address 4
input: AT Translated Set 2 keyboard on isa0060/serio0
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 220k freed
hub 2-3.1:1.0: USB hub found
hub 2-3.1:1.0: 4 ports detected
usb 2-3.2: new high speed USB device using ehci_hcd and address 5
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
Synaptics Touchpad, model: 1, fw: 5.9, id: 0x126eb1, caps: 0xa04713/0x4000
input: SynPS/2 Synaptics TouchPad on isa0060/serio4
usb 9-2: new low speed USB device using uhci_hcd and address 2
input: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:03:02.1-2
usb 10-2: new full speed USB device using uhci_hcd and address 2
input: USB HID v1.00 Device [USB Audio] on usb-0000:03:03.0-2
Vendor: SMSC Model: 223 U HS-CF Rev: 3.60
Type: Direct-Access ANSI SCSI revision: 00
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete
ReiserFS: dm-0: found reiserfs format "3.6" with standard journal
ReiserFS: dm-0: using ordered data mode
ReiserFS: dm-0: journal params: device dm-0, size 8192, journal first block
18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: dm-0: checking transaction log (dm-0)
ReiserFS: dm-0: Using r5 hash to sort names
Adding 2097144k swap on /dev/vg0/swap. Priority:-1 extents:1
ReiserFS: dm-1: found reiserfs format "3.6" with standard journal
ReiserFS: dm-1: using ordered data mode
ReiserFS: dm-1: journal params: device dm-1, size 8192, journal first block
18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: dm-1: checking transaction log (dm-1)
ReiserFS: dm-1: Using r5 hash to sort names
NTFS volume version 3.1.
ReiserFS: dm-3: found reiserfs format "3.6" with standard journal
ReiserFS: dm-3: using ordered data mode
ReiserFS: dm-3: journal params: device dm-3, size 8192, journal first block
18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: dm-3: checking transaction log (dm-3)
ReiserFS: dm-3: Using r5 hash to sort names
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1b.0 to 64
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, 1.0.3
ieee80211: Copyright (C) 2004-2005 Intel Corporation
<[email protected]>
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.6
ipw2200: Copyright(c) 2003-2004 Intel Corporation
ACPI: PCI Interrupt 0000:06:03.0[A] -> GSI 17 (level, low) -> IRQ 17
ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection
ipw2200: Radio Frequency Kill Switch is On:
Kill switch must be turned off for wireless networking to work.
usbcore: registered new driver snd-usb-audio
cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcffff 0xe0000-0xfffff
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.


Attachments:
(No filename) (28.23 kB)
(No filename) (189.00 B)
Download all attachments

2005-09-03 18:34:29

by Ivan Kokshaysky

[permalink] [raw]
Subject: Re: 2.6.13: Crash in Yenta initialization

On Sat, Sep 03, 2005 at 02:45:08AM +0200, Andreas Koch wrote:
> crucial part seem to be the different bridge initialization sections:

Indeed.

> 2.6.12-rc6 + Ivan's patches:
...
> PCI: Bus 7, cardbus bridge: 0000:06:09.0
> IO window: 00006000-00006fff
> IO window: 00007000-00007fff
> PREFETCH window: 82000000-83ffffff
> MEM window: 8c000000-8dffffff
> PCI: Bus 11, cardbus bridge: 0000:06:09.1
> IO window: 00008000-00008fff
> IO window: 00009000-00009fff
> PREFETCH window: 84000000-85ffffff
> MEM window: 8e000000-8fffffff
> PCI: Bus 15, cardbus bridge: 0000:06:09.3
...
> ... Versus the much shorter output from 2.6.13
...
> PCI: Bus 7, cardbus bridge: 0000:06:09.0
> IO window: 00004000-000040ff
> IO window: 00004400-000044ff
> PREFETCH window: 82000000-83ffffff
> MEM window: 88000000-89ffffff
> PCI: Bridge: 0000:00:1e.0

It's mysterious.
So 2.6.13 doesn't see cardbus bridge functions 06:09.1 and 06:09.3,
which means that these devices are not on the per-bus device list.
OTOH, they are still visible on the global device list, since yenta
driver found them. No surprise that it crashes with some uninitialized
pointer.

I'd suspect some change in PCI probing code between 2.6.12-rc6 and
2.6.13, but so far I'm unable to find what it was...

Maybe you could try 2.6.12 release and 2.6.13-rc kernels to see where
it breaks?
(Note that the PCI setup patches that you're using went into 2.6.13-rc2.)

Ivan.

2005-09-12 17:42:14

by Olaf Hering

[permalink] [raw]
Subject: Re: 2.6.13: Crash in Yenta initialization

On Sat, Sep 03, Ivan Kokshaysky wrote:

> On Sat, Sep 03, 2005 at 02:45:08AM +0200, Andreas Koch wrote:
> > crucial part seem to be the different bridge initialization sections:
>
> Indeed.
>
> > 2.6.12-rc6 + Ivan's patches:
> ...
> > PCI: Bus 7, cardbus bridge: 0000:06:09.0
> > IO window: 00006000-00006fff
> > IO window: 00007000-00007fff
> > PREFETCH window: 82000000-83ffffff
> > MEM window: 8c000000-8dffffff
> > PCI: Bus 11, cardbus bridge: 0000:06:09.1
> > IO window: 00008000-00008fff
> > IO window: 00009000-00009fff
> > PREFETCH window: 84000000-85ffffff
> > MEM window: 8e000000-8fffffff
> > PCI: Bus 15, cardbus bridge: 0000:06:09.3
> ...
> > ... Versus the much shorter output from 2.6.13
> ...
> > PCI: Bus 7, cardbus bridge: 0000:06:09.0
> > IO window: 00004000-000040ff
> > IO window: 00004400-000044ff
> > PREFETCH window: 82000000-83ffffff
> > MEM window: 88000000-89ffffff
> > PCI: Bridge: 0000:00:1e.0
>
> It's mysterious.
> So 2.6.13 doesn't see cardbus bridge functions 06:09.1 and 06:09.3,
> which means that these devices are not on the per-bus device list.
> OTOH, they are still visible on the global device list, since yenta
> driver found them. No surprise that it crashes with some uninitialized
> pointer.

Did you find the reason for this already?
We have a similar report:
https://bugzilla.novell.com/show_bug.cgi?id=113778
...
It dies in yenta_config_init because dev->subordinate is NULL.
...

2005-09-12 20:08:06

by Ivan Kokshaysky

[permalink] [raw]
Subject: Re: 2.6.13: Crash in Yenta initialization

On Mon, Sep 12, 2005 at 07:42:09PM +0200, Olaf Hering wrote:
> Did you find the reason for this already?

Unfortunately, no.

> We have a similar report:
> https://bugzilla.novell.com/show_bug.cgi?id=113778
> ...
> It dies in yenta_config_init because dev->subordinate is NULL.
> ...

Yes, this looks identical to Andreas' report.

Perhaps adding the line

#define DEBUG 1

at the very top of drivers/pci/probe.c could help to catch something
interesting in dmesg.

Ivan.

2005-09-12 20:13:07

by Marcus Wegner

[permalink] [raw]
Subject: Re: 2.6.13: Crash in Yenta initialization

> On Sat, Sep 03, Ivan Kokshaysky wrote:
>
>>On Sat, Sep 03, 2005 at 02:45:08AM +0200, Andreas Koch wrote:
>> > crucial part seem to be the different bridge initialization sections:
>>
>>Indeed.
>>
>> > 2.6.12-rc6 + Ivan's patches:
>>...
>> > PCI: Bus 7, cardbus bridge: 0000:06:09.0
>> > IO window: 00006000-00006fff
>> > IO window: 00007000-00007fff
>> > PREFETCH window: 82000000-83ffffff
>> > MEM window: 8c000000-8dffffff
>> > PCI: Bus 11, cardbus bridge: 0000:06:09.1
>> > IO window: 00008000-00008fff
>> > IO window: 00009000-00009fff
>> > PREFETCH window: 84000000-85ffffff
>> > MEM window: 8e000000-8fffffff
>> > PCI: Bus 15, cardbus bridge: 0000:06:09.3
>>...
>> > ... Versus the much shorter output from 2.6.13
>>...
>> > PCI: Bus 7, cardbus bridge: 0000:06:09.0
>> > IO window: 00004000-000040ff
>> > IO window: 00004400-000044ff
>> > PREFETCH window: 82000000-83ffffff
>> > MEM window: 88000000-89ffffff
>> > PCI: Bridge: 0000:00:1e.0
>>
>>It's mysterious.
>>So 2.6.13 doesn't see cardbus bridge functions 06:09.1 and 06:09.3,
>>which means that these devices are not on the per-bus device list.
>>OTOH, they are still visible on the global device list, since yenta
>>driver found them. No surprise that it crashes with some uninitialized
>>pointer.
>
>Did you find the reason for this already?
>We have a similar report:
>https://bugzilla.novell.com/show_bug.cgi?id=113778
>...
>It dies in yenta_config_init because dev->subordinate is NULL.
>...
I had the same problem with an ACER 8101 WLMI. I reverted the initialization
partly and it works now, but I don't know if it really fixes the bug.
Something seems to wrong in the pci initcode.

But other hardware errors with the acer notebook still remain. The detection
of the ioapic results in a deadlock in the boot process (the
multiple-ioapic-fix or "noapic" solved this).

yenta related:
- pccard hardware is working now
- O2 Micro 4-1 cardreader is not working

Does someone have ideas, configs or patches for the cardreader? Do you need
more info? Let me know.

Marcus


Attachments:
pci-assign-res-fix (785.00 B)
multiple-ioapic-fix (1.86 kB)
Download all attachments

2005-09-12 20:18:40

by Marcus Wegner

[permalink] [raw]
Subject: Re: 2.6.13: Crash in Yenta initialization

> On Sat, Sep 03, Ivan Kokshaysky wrote:
>
>>On Sat, Sep 03, 2005 at 02:45:08AM +0200, Andreas Koch wrote:
>> > crucial part seem to be the different bridge initialization sections:
>>
>>Indeed.
>>
>> > 2.6.12-rc6 + Ivan's patches:
>>...
>> > PCI: Bus 7, cardbus bridge: 0000:06:09.0
>> > IO window: 00006000-00006fff
>> > IO window: 00007000-00007fff
>> > PREFETCH window: 82000000-83ffffff
>> > MEM window: 8c000000-8dffffff
>> > PCI: Bus 11, cardbus bridge: 0000:06:09.1
>> > IO window: 00008000-00008fff
>> > IO window: 00009000-00009fff
>> > PREFETCH window: 84000000-85ffffff
>> > MEM window: 8e000000-8fffffff
>> > PCI: Bus 15, cardbus bridge: 0000:06:09.3
>>...
>> > ... Versus the much shorter output from 2.6.13
>>...
>> > PCI: Bus 7, cardbus bridge: 0000:06:09.0
>> > IO window: 00004000-000040ff
>> > IO window: 00004400-000044ff
>> > PREFETCH window: 82000000-83ffffff
>> > MEM window: 88000000-89ffffff
>> > PCI: Bridge: 0000:00:1e.0
>>
>>It's mysterious.
>>So 2.6.13 doesn't see cardbus bridge functions 06:09.1 and 06:09.3,
>>which means that these devices are not on the per-bus device list.
>>OTOH, they are still visible on the global device list, since yenta
>>driver found them. No surprise that it crashes with some uninitialized
>>pointer.
>
>Did you find the reason for this already?
>We have a similar report:
>https://bugzilla.novell.com/show_bug.cgi?id=113778
>...
>It dies in yenta_config_init because dev->subordinate is NULL.
>...
I had the same problem with an ACER 8101 WLMI. I reverted the initialization
partly and it works now, but I don't know if it really fixes the bug.
Something seems to wrong in the pci initcode.

But other hardware errors with the acer notebook still remain. The detection
of the ioapic results in a deadlock in the boot process (the
multiple-ioapic-fix or "noapic" solved this).

yenta related:
- pccard hardware is working now
- O2 Micro 4-1 cardreader is not working

Does someone have ideas, configs or patches for the cardreader? Do you need
more info? Let me know.

Marcus


Attachments:
pci-assign-res-fix (0.00 B)
multiple-ioapic-fix (0.00 B)
Download all attachments

2005-09-13 06:31:00

by Olaf Hering

[permalink] [raw]
Subject: Re: 2.6.13: Crash in Yenta initialization

On Tue, Sep 13, Ivan Kokshaysky wrote:

> On Mon, Sep 12, 2005 at 07:42:09PM +0200, Olaf Hering wrote:
> > Did you find the reason for this already?
>
> Unfortunately, no.
>
> > We have a similar report:
> > https://bugzilla.novell.com/show_bug.cgi?id=113778
> > ...
> > It dies in yenta_config_init because dev->subordinate is NULL.
> > ...
>
> Yes, this looks identical to Andreas' report.
>
> Perhaps adding the line
>
> #define DEBUG 1
>
> at the very top of drivers/pci/probe.c could help to catch something
> interesting in dmesg.

The reporter has updated the bug.

https://bugzilla.novell.com/attachment.cgi?id=49717
https://bugzilla.novell.com/attachment.cgi?id=49715
https://bugzilla.novell.com/attachment.cgi?id=49716


00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
Capabilities: [e0] Vendor Specific Information
00: 86 80 90 25 06 01 90 20 03 00 00 06 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 25 10 70 00
30: 00 00 00 00 e0 00 00 00 00 00 00 00 00 00 00 00

00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size 08
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: c8100000-c81fffff
Prefetchable memory behind bridge: d0000000-d7ffffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
Capabilities: [88] #0d [0000]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+
Address: fee01004 Data: 4041
Capabilities: [a0] Express Root Port (Slot+) IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s <64ns, L1 <1us
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 2
Link: Latency L0s <256ns, L1 <4us
Link: ASPM L1 Enabled RCB 64 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x16
Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug- Surpise-
Slot: Number 1, PowerLimit 75.000000
Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
Slot: AttnInd Off, PwrInd On, Power-
Root: Correctable- Non-Fatal- Fatal- PME-
00: 86 80 91 25 07 04 10 00 03 00 04 06 08 00 01 00
10: 00 00 00 00 00 00 00 00 00 01 01 00 20 20 00 20
20: 10 c8 10 c8 00 d0 f0 d7 00 00 00 00 00 00 00 00
30: 00 00 00 00 88 00 00 00 00 00 00 00 0a 01 0c 00

00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size 08
Interrupt: pin A routed to IRQ 10
Region 0: Memory at c8000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express Unknown type IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s <64ns, L1 <1us
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed unknown, Width x0, ASPM unknown, Port 0
Link: Latency L0s <64ns, L1 <1us
Link: ASPM Disabled CommClk- ExtSynch-
Link: Speed unknown, Width x0
00: 86 80 68 26 06 00 10 00 04 00 03 04 08 00 00 00
10: 04 00 00 c8 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 25 10 70 00
30: 00 00 00 00 50 00 00 00 00 00 00 00 0a 01 00 00

00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 04) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size 08
Bus: primary=00, secondary=09, subordinate=09, sec-latency=0
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: fff00000-000fffff
Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [40] Express Root Port (Slot+) IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
Device: Latency L0s unlimited, L1 unlimited
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 1
Link: Latency L0s <1us, L1 <4us
Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+
Slot: Number 2, PowerLimit 6.500000
Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
Slot: AttnInd Unknown, PwrInd Unknown, Power-
Root: Correctable- Non-Fatal- Fatal- PME-
Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+
Address: fee01004 Data: 4049
Capabilities: [90] #0d [0000]
Capabilities: [a0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 86 80 60 26 07 04 10 00 04 00 04 06 08 00 81 00
10: 00 00 00 00 00 00 00 00 00 09 09 00 f0 00 00 20
20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 0a 01 04 00

00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 04) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size 08
Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=0
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: fff00000-000fffff
Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [40] Express Root Port (Slot+) IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
Device: Latency L0s unlimited, L1 unlimited
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 2
Link: Latency L0s <1us, L1 <4us
Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+
Slot: Number 3, PowerLimit 6.500000
Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
Slot: AttnInd Unknown, PwrInd Unknown, Power-
Root: Correctable- Non-Fatal- Fatal- PME-
Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+
Address: fee01004 Data: 4051
Capabilities: [90] #0d [0000]
Capabilities: [a0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 86 80 62 26 07 04 10 00 04 00 04 06 08 00 81 00
10: 00 00 00 00 00 00 00 00 00 0a 0a 00 f0 00 00 20
20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 0a 02 04 00

00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 (rev 04) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size 08
Bus: primary=00, secondary=02, subordinate=04, sec-latency=0
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: fff00000-000fffff
Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [40] Express Root Port (Slot+) IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
Device: Latency L0s unlimited, L1 unlimited
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 3
Link: Latency L0s <1us, L1 <4us
Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+
Slot: Number 4, PowerLimit 6.500000
Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
Slot: AttnInd Unknown, PwrInd Unknown, Power-
Root: Correctable- Non-Fatal- Fatal- PME-
Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+
Address: fee01004 Data: 4059
Capabilities: [90] #0d [0000]
Capabilities: [a0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 86 80 64 26 07 04 10 00 04 00 04 06 08 00 81 00
10: 00 00 00 00 00 00 00 00 00 02 04 00 f0 00 00 20
20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 03 04 00

00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 04) (prog-if 00 [UHCI])
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 11
Region 4: I/O ports at 1800 [size=32]
00: 86 80 58 26 05 00 80 02 04 00 03 0c 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 18 00 00 00 00 00 00 00 00 00 00 25 10 70 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 00

00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 04) (prog-if 00 [UHCI])
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin B routed to IRQ 11
Region 4: I/O ports at 1820 [size=32]
00: 86 80 59 26 05 00 80 02 04 00 03 0c 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 21 18 00 00 00 00 00 00 00 00 00 00 25 10 70 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 02 00 00

00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 04) (prog-if 00 [UHCI])
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin C routed to IRQ 11
Region 4: I/O ports at 1840 [size=32]
00: 86 80 5a 26 05 00 80 02 04 00 03 0c 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 41 18 00 00 00 00 00 00 00 00 00 00 25 10 70 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 03 00 00

00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 04) (prog-if 00 [UHCI])
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin D routed to IRQ 10
Region 4: I/O ports at 1860 [size=32]
00: 86 80 5b 26 05 00 80 02 04 00 03 0c 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 61 18 00 00 00 00 00 00 00 00 00 00 25 10 70 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 0a 04 00 00

00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 04) (prog-if 20 [EHCI])
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 11
Region 0: Memory at c8004000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Debug port
00: 86 80 5c 26 06 00 90 02 04 20 03 0c 00 00 00 00
10: 00 40 00 c8 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 25 10 70 00
30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 00

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d4) (prog-if 01 [Subtractive decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=06, subordinate=08, sec-latency=32
I/O behind bridge: 00003000-00004fff
Memory behind bridge: c8200000-c82fffff
Prefetchable memory behind bridge: 0000000020000000-0000000021f00000
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [50] #0d [0000]
00: 86 80 48 24 07 00 10 00 d4 01 04 06 00 00 01 00
10: 00 00 00 00 00 00 00 00 00 06 08 20 30 40 80 22
20: 20 c8 20 c8 01 20 f1 21 00 00 00 00 00 00 00 00
30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 04 00

00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 04)
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
00: 86 80 41 26 07 00 00 02 04 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 25 10 70 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 04) (prog-if 80 [Master])
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin B routed to IRQ 0
Region 0: I/O ports at <unassigned>
Region 1: I/O ports at <unassigned>
Region 2: I/O ports at <unassigned>
Region 3: I/O ports at <unassigned>
Region 4: I/O ports at 18a0 [size=16]
Capabilities: [70] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 86 80 53 26 05 00 b0 02 04 80 01 01 00 00 00 00
10: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00
20: a1 18 00 00 00 00 00 00 00 00 00 00 25 10 70 00
30: 00 00 00 00 70 00 00 00 00 00 00 00 ff 02 00 00

00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 04)
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin B routed to IRQ 11
Region 4: I/O ports at 18e0 [size=32]
00: 86 80 6a 26 01 00 80 02 04 00 05 0c 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: e1 18 00 00 00 00 00 00 00 00 00 00 25 10 70 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 02 00 00

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X700 (PCIE) (prog-if 00 [VGA])
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size 08
Interrupt: pin A routed to IRQ 10
Region 0: Memory at d0000000 (32-bit, prefetchable) [size=128M]
Region 1: I/O ports at 2000 [size=256]
Region 2: Memory at c8100000 (32-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at c8120000 [disabled] [size=128K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
Device: Latency L0s <256ns, L1 <4us
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 0
Link: Latency L0s <256ns, L1 <2us
Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x16
Capabilities: [80] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
00: 02 10 53 56 07 00 10 00 00 00 00 03 08 00 00 00
10: 08 00 00 d0 01 20 00 00 00 00 10 c8 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 25 10 70 00
30: 00 00 00 00 50 00 00 00 00 00 00 00 0a 01 00 00

06:03.0 Network controller: Intel Corporation PRO/Wireless 2915ABG MiniPCI Adapter (rev 05)
Subsystem: Intel Corporation: Unknown device 1001
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 11
Region 0: Memory at c8214000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
00: 86 80 23 42 12 00 90 02 05 00 80 02 08 20 00 00
10: 00 40 21 c8 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 01 10
30: 00 00 00 00 dc 00 00 00 00 00 00 00 0b 01 03 18

06:06.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5788 Gigabit Ethernet (rev 03)
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (16000ns min), Cache Line Size 08
Interrupt: pin A routed to IRQ 10
Region 0: Memory at c8200000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
Address: ff7bffbfbffbbffc Data: ffff
00: e4 14 9c 16 06 00 b0 02 03 00 00 02 08 20 00 00
10: 00 00 20 c8 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 07 00 00 00 25 10 70 00
30: 00 00 00 00 48 00 00 00 00 00 00 00 0a 01 40 00

06:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI])
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (750ns min, 1000ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 11
Region 0: Memory at c8215000 (32-bit, non-prefetchable) [size=2K]
Region 1: Memory at c8210000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME+
00: 4c 10 26 80 16 00 10 02 00 10 00 0c 08 20 00 00
10: 00 50 21 c8 00 00 21 c8 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 25 10 70 00
30: 00 00 00 00 44 00 00 00 00 00 00 00 0b 01 03 04

06:09.0 CardBus bridge: O2 Micro, Inc. OZ711M3/MC3 4-in-1 MemoryCardBus Controller
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 168
Interrupt: pin A routed to IRQ 11
Region 0: Memory at c8216000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=06, secondary=07, subordinate=08, sec-latency=176
Memory window 0: 20000000-21fff000 (prefetchable)
Memory window 1: 22000000-23fff000
I/O window 0: 00003000-00003fff
I/O window 1: 00004000-00004fff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ PostWrite+
16-bit legacy interface ports at 0001
00: 17 12 23 72 87 00 10 04 00 00 07 06 00 a8 82 00
10: 00 60 21 c8 a0 00 00 02 06 07 08 b0 00 00 00 20
20: 00 f0 ff 21 00 00 00 22 00 f0 ff 23 01 30 00 00
30: fd 3f 00 00 01 40 00 00 fd 4f 00 00 0b 01 80 05
40: 25 10 70 00 01 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

06:09.1 CardBus bridge: O2 Micro, Inc. OZ711M3/MC3 4-in-1 MemoryCardBus Controller
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 168
Interrupt: pin A routed to IRQ 10
Region 0: Memory at c8217000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=06, secondary=08, subordinate=08, sec-latency=36
Memory window 0: fff00000-000ff000
Memory window 1: 00000000-00000000
I/O window 0: 0000f000-00000fff
I/O window 1: 00000000-00000003
BridgeCtl: Parity- SERR- ISA+ VGA- MAbort- >Reset- 16bInt+ PostWrite-
16-bit legacy interface ports at 0001
00: 17 12 23 72 87 00 10 04 00 00 07 06 00 a8 82 00
10: 00 70 21 c8 a0 00 00 02 06 08 08 24 00 00 f0 ff
20: 00 f0 0f 00 00 00 00 00 00 00 00 00 01 f0 00 00
30: fd 0f 00 00 01 00 00 00 01 00 00 00 0a 01 84 00
40: 25 10 70 00 01 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

06:09.2 System peripheral: O2 Micro, Inc. OZ711Mx 4-in-1 MemoryCardBus Accelerator
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 11
Region 0: Memory at c8218000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [a0] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 17 12 10 71 03 00 10 04 00 00 80 08 08 20 80 00
10: 00 80 21 c8 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 25 10 70 00
30: 00 00 00 00 a0 00 00 00 00 00 00 00 0b 01 00 00

06:09.3 CardBus bridge: O2 Micro, Inc. OZ711M3/MC3 4-in-1 MemoryCardBus Controller
Subsystem: Acer Incorporated [ALI]: Unknown device 0070
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 0
Region 0: Memory at c8219000 (32-bit, non-prefetchable) [disabled] [size=4K]
Bus: primary=00, secondary=00, subordinate=00, sec-latency=0
Memory window 0: 00000000-00000000 [disabled]
Memory window 1: 00000000-00000000 [disabled]
I/O window 0: 00000000-00000003 [disabled]
I/O window 1: 00000000-00000003 [disabled]
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt- PostWrite-
16-bit legacy interface ports at 0001
00: 17 12 23 72 80 00 10 04 00 00 07 06 00 00 82 00
10: 00 90 21 c8 a0 00 00 02 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00
30: 01 00 00 00 01 00 00 00 01 00 00 00 00 01 00 00
40: 25 10 70 00 01 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

2005-09-13 11:45:47

by Ivan Kokshaysky

[permalink] [raw]
Subject: Re: 2.6.13: Crash in Yenta initialization

On Tue, Sep 13, 2005 at 08:30:53AM +0200, Olaf Hering wrote:
> The reporter has updated the bug.
>
> https://bugzilla.novell.com/attachment.cgi?id=49717
> https://bugzilla.novell.com/attachment.cgi?id=49715
> https://bugzilla.novell.com/attachment.cgi?id=49716

Thanks, that helped.

The reason was that Acer BIOS left only _two_ bus numbers available
for _three_ cardbus controllers, so pci_scan_bridge() assigns both
numbers to the first controller and leaves two other ones uninitialized.

Please try the patch here, but note that you'll apparently have only
one cardbus slot working. If you want more, use "pci=assign-busses"
boot option.

Ivan.

--- 2.6.14-rc1/drivers/pcmcia/yenta_socket.c Tue Sep 13 14:16:34 2005
+++ linux/drivers/pcmcia/yenta_socket.c Tue Sep 13 14:40:40 2005
@@ -1045,7 +1045,18 @@ static int __devinit yenta_probe (struct
{
struct yenta_socket *socket;
int ret;
-
+
+ /*
+ * If we failed to assign proper bus numbers for this cardbus
+ * controller during PCI probe, its subordinate pci_bus is NULL.
+ * Bail out if so.
+ */
+ if (!dev->subordinate) {
+ printk(KERN_ERROR "Yenta: no bus associated with %s!\n",
+ pci_name(dev));
+ return -ENODEV;
+ }
+
socket = kmalloc(sizeof(struct yenta_socket), GFP_KERNEL);
if (!socket)
return -ENOMEM;

2005-09-13 12:43:15

by Andreas Koch

[permalink] [raw]
Subject: Re: 2.6.13: Crash in Yenta initialization

On Tue, Sep 13, 2005 at 02:36:04PM +0200, Andreas Koch wrote:
> Igor,

^^^^^^^ That should be Ivan, sorry for the mix-up (I just had a long
phone call with an Igor).

Andreas

>
> I just had a chance to do some more testing, and the crash even occurs
> in 2.6.13-rc2. I haven't had a chance to get serial console logs yet,
> but I assume they will turn out similarly to the ones captured on
> 2.6.13 (glancing at the text as it scrolled by). So, something must
> have changed between 2.6.12-rc6+patches and 2.6.13-rc2 (including the
> patches).
>
> Is there anything specific you want me to look for?
>
> Andreas
>
>
> On Sat, Sep 03, 2005 at 10:34:01PM +0400, Ivan Kokshaysky wrote:
> > On Sat, Sep 03, 2005 at 02:45:08AM +0200, Andreas Koch wrote:
> > > crucial part seem to be the different bridge initialization sections:
> >
> > Indeed.
> >
> > > 2.6.12-rc6 + Ivan's patches:
> > ...
> > > PCI: Bus 7, cardbus bridge: 0000:06:09.0
> > > IO window: 00006000-00006fff
> > > IO window: 00007000-00007fff
> > > PREFETCH window: 82000000-83ffffff
> > > MEM window: 8c000000-8dffffff
> > > PCI: Bus 11, cardbus bridge: 0000:06:09.1
> > > IO window: 00008000-00008fff
> > > IO window: 00009000-00009fff
> > > PREFETCH window: 84000000-85ffffff
> > > MEM window: 8e000000-8fffffff
> > > PCI: Bus 15, cardbus bridge: 0000:06:09.3
> > ...
> > > ... Versus the much shorter output from 2.6.13
> > ...
> > > PCI: Bus 7, cardbus bridge: 0000:06:09.0
> > > IO window: 00004000-000040ff
> > > IO window: 00004400-000044ff
> > > PREFETCH window: 82000000-83ffffff
> > > MEM window: 88000000-89ffffff
> > > PCI: Bridge: 0000:00:1e.0
> >
> > It's mysterious.
> > So 2.6.13 doesn't see cardbus bridge functions 06:09.1 and 06:09.3,
> > which means that these devices are not on the per-bus device list.
> > OTOH, they are still visible on the global device list, since yenta
> > driver found them. No surprise that it crashes with some uninitialized
> > pointer.
> >
> > I'd suspect some change in PCI probing code between 2.6.12-rc6 and
> > 2.6.13, but so far I'm unable to find what it was...
> >
> > Maybe you could try 2.6.12 release and 2.6.13-rc kernels to see where
> > it breaks?
> > (Note that the PCI setup patches that you're using went into 2.6.13-rc2.)
> >
> > Ivan.


Attachments:
(No filename) (2.42 kB)
(No filename) (189.00 B)
Download all attachments

2005-09-13 12:36:07

by Andreas Koch

[permalink] [raw]
Subject: Re: 2.6.13: Crash in Yenta initialization

Igor,

I just had a chance to do some more testing, and the crash even occurs
in 2.6.13-rc2. I haven't had a chance to get serial console logs yet,
but I assume they will turn out similarly to the ones captured on
2.6.13 (glancing at the text as it scrolled by). So, something must
have changed between 2.6.12-rc6+patches and 2.6.13-rc2 (including the
patches).

Is there anything specific you want me to look for?

Andreas


On Sat, Sep 03, 2005 at 10:34:01PM +0400, Ivan Kokshaysky wrote:
> On Sat, Sep 03, 2005 at 02:45:08AM +0200, Andreas Koch wrote:
> > crucial part seem to be the different bridge initialization sections:
>
> Indeed.
>
> > 2.6.12-rc6 + Ivan's patches:
> ...
> > PCI: Bus 7, cardbus bridge: 0000:06:09.0
> > IO window: 00006000-00006fff
> > IO window: 00007000-00007fff
> > PREFETCH window: 82000000-83ffffff
> > MEM window: 8c000000-8dffffff
> > PCI: Bus 11, cardbus bridge: 0000:06:09.1
> > IO window: 00008000-00008fff
> > IO window: 00009000-00009fff
> > PREFETCH window: 84000000-85ffffff
> > MEM window: 8e000000-8fffffff
> > PCI: Bus 15, cardbus bridge: 0000:06:09.3
> ...
> > ... Versus the much shorter output from 2.6.13
> ...
> > PCI: Bus 7, cardbus bridge: 0000:06:09.0
> > IO window: 00004000-000040ff
> > IO window: 00004400-000044ff
> > PREFETCH window: 82000000-83ffffff
> > MEM window: 88000000-89ffffff
> > PCI: Bridge: 0000:00:1e.0
>
> It's mysterious.
> So 2.6.13 doesn't see cardbus bridge functions 06:09.1 and 06:09.3,
> which means that these devices are not on the per-bus device list.
> OTOH, they are still visible on the global device list, since yenta
> driver found them. No surprise that it crashes with some uninitialized
> pointer.
>
> I'd suspect some change in PCI probing code between 2.6.12-rc6 and
> 2.6.13, but so far I'm unable to find what it was...
>
> Maybe you could try 2.6.12 release and 2.6.13-rc kernels to see where
> it breaks?
> (Note that the PCI setup patches that you're using went into 2.6.13-rc2.)
>
> Ivan.


Attachments:
(No filename) (2.14 kB)
(No filename) (189.00 B)
Download all attachments

2005-09-14 04:10:50

by Olaf Hering

[permalink] [raw]
Subject: Re: 2.6.13: Crash in Yenta initialization

On Tue, Sep 13, Ivan Kokshaysky wrote:

> On Tue, Sep 13, 2005 at 08:30:53AM +0200, Olaf Hering wrote:
> > The reporter has updated the bug.
> >
> > https://bugzilla.novell.com/attachment.cgi?id=49717
> > https://bugzilla.novell.com/attachment.cgi?id=49715
> > https://bugzilla.novell.com/attachment.cgi?id=49716
>
> Thanks, that helped.
>
> The reason was that Acer BIOS left only _two_ bus numbers available
> for _three_ cardbus controllers, so pci_scan_bridge() assigns both
> numbers to the first controller and leaves two other ones uninitialized.
>
> Please try the patch here, but note that you'll apparently have only
> one cardbus slot working. If you want more, use "pci=assign-busses"
> boot option.

Yes, this patch fixes the oops. The pci= option doesnt help.

2005-09-20 10:02:33

by Andreas Koch

[permalink] [raw]
Subject: Continuing PCI and Yenta troubles in 2.6.13.1 and 2.6.14-rc1

Ivan,

I backported your Yenta fix into 2.6.13.1 (that's what I am currently using on
my production machine). However, the reliability of this setup is
significantly decreased over my previous 2.6.12-rc6+your PCI patches
configuration.

Specifically, the machine (Acer TM8104 notebook+ezDock docking station) now
often hangs (without an oops), sometimes during startup, sometimes a bit
later during use.

I have attached a console log of a successful start (ok26131.log), where the
machine lost access to the USB ports on the docking station (behind the PCI
Express/PCI bridge) later during normal use. I note that there are quite a
few more errors concerning the bridge initialization (compared to
2.6.12-rc6).

I attach a second log (stop26131.log) where the machine hangs during booting
in Yenta initialization.

I have also made an attempt to use 2.6.14-rc1 with your fix. However, two
things occur here: First, the machine is extremely unresponsive right after
booting (console input echoed with the speed of a 75 baud terminal [at
best ...]). Second, after some time, the USB ports in the docking station
disappear (with a message indicating PCI problems).

Thus, I believe there is still something rotten in the PCI code since the
2.6.12-rc6 days. Again, if you'd like me to run specific tests, please let me
know.

Andreas


Attachments:
(No filename) (1.32 kB)
ok26131.log (21.29 kB)
stop26131.log (12.42 kB)
slow2614rc1.log (19.31 kB)
Download all attachments

2005-09-20 12:59:25

by Ivan Kokshaysky

[permalink] [raw]
Subject: Re: Continuing PCI and Yenta troubles in 2.6.13.1 and 2.6.14-rc1

On Tue, Sep 20, 2005 at 12:02:23PM +0200, Andreas Koch wrote:
> Thus, I believe there is still something rotten in the PCI code since the
> 2.6.12-rc6 days.

Thanks a lot for the report.

You are right, and I believe the change that broke things is
introduction of pci_fixup_parent_subordinate_busnr()...

The patch here does two things:
- hunk #1 should fix the problems you've seen when you boot without
additional "pci" kernel options;
- hunk #2 supposedly fixes boot with "pci=assign-busses" option which
otherwise hangs Acer TM81xx machines as reported.

Please try this with and without "pci=assign-busses". If it boots,
I'd like to see 'lspci -vvx' for both cases.

Ivan.

--- 2.6.13.2/drivers/pci/probe.c Mon Aug 8 12:20:28 2005
+++ linux/drivers/pci/probe.c Tue Sep 20 16:17:23 2005
@@ -400,6 +400,12 @@ static void pci_enable_crs(struct pci_de
static void __devinit pci_fixup_parent_subordinate_busnr(struct pci_bus *child, int max)
{
struct pci_bus *parent = child->parent;
+
+ /* Attempts to fix that up are really dangerous unless
+ we're going to re-assign all bus numbers. */
+ if (!pcibios_assign_all_busses())
+ return;
+
while (parent->parent && parent->subordinate < max) {
parent->subordinate = max;
pci_write_config_byte(parent->self, PCI_SUBORDINATE_BUS, max);
@@ -476,8 +482,18 @@ int __devinit pci_scan_bridge(struct pci
* We need to assign a number to this bus which we always
* do in the second pass.
*/
- if (!pass)
+ if (!pass) {
+ if (pcibios_assign_all_busses())
+ /* Temporarily disable forwarding of the
+ configuration cycles on all bridges in
+ this bus segment to avoid possible
+ conflicts in the second pass between two
+ bridges programmed with overlapping
+ bus ranges. */
+ pci_write_config_dword(dev, PCI_PRIMARY_BUS,
+ buses & ~0xffffff);
return max;
+ }

/* Clear errors */
pci_write_config_word(dev, PCI_STATUS, 0xffff);

2005-09-21 15:56:00

by Ivan Kokshaysky

[permalink] [raw]
Subject: Re: Continuing PCI and Yenta troubles in 2.6.13.1 and 2.6.14-rc1

On Tue, Sep 20, 2005 at 08:06:15PM +0200, Andreas Koch wrote:
> many thanks for the quick patch. I have applied it and your previous Yenta
> patch (is that still necessary with the new patch?) to 2.6.13.2.

Yenta patch is still needed (it will be included in 2.6.13.3).

> With pci=assign-busses, I don't see any obvious oops or slow-downs either.
> However: As you can see from the attached boot log (assign-busses-26132.log),
> there are now problems with the USB ports 9-2 and 10-2, on
> uhci_hcd 0000:05:02.1 and uhci_hcd 0000:05:03.0, respectively. This delays the
> boot for about 5 seconds per error, but does continue. The system doesn't
> hang afterwards, either (again, tested for roughly 15min). The lspci-vvx
> output is attached as assign-busses-26132.lspci.

These errors most likely mean that there are no interrupts form PCI
devices in the docking station. I'd suppose that massively changed bus
numbers make ACPI confused wrt interrupt routing, but all relevant IRQs
are exactly the same as without "assign-busses", so I'm puzzled...

> I'll try using the patched 2.6.13.2 without pci=assign-busses in the next few
> days and test whether other instabilities come up. If you want me to try
> further patches for fixing the assign-busses option, I'm game.

At the moment I can only think of something like this: the PCIE-to-PCI bridge
(Intel 6702PXH) in your docking station also has IOxAPIC as PCI function #1,
but its config space is turned off by BIOS for some reason. However, its MMIO
registers are still present somewhere in PCI address space - we just don't
know where.
So there is a small possibility that we have accidentally stepped on them
and destroyed IRQ routing setup writing to MMIO registers of totally
unrelated device.

Please test this patch, though chances that it helps are quite small...
In either case lspci output will be useful.

Ivan.

--- 2.6.13.2/drivers/pci/quirks.c Mon Aug 29 03:41:01 2005
+++ linux/drivers/pci/quirks.c Wed Sep 21 16:58:01 2005
@@ -1298,6 +1298,12 @@ DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_IN
*/
static void __devinit quirk_pcie_pxh(struct pci_dev *dev)
{
+ u16 ctrl;
+
+ /* Enable config access to I/OxAPIC function. */
+ pci_read_config_word(dev, 0x40, &ctrl);
+ pci_write_config_word(dev, 0x40, ctrl | 0x2000);
+
disable_msi_mode(dev, pci_find_capability(dev, PCI_CAP_ID_MSI),
PCI_CAP_ID_MSI);
dev->no_msi = 1;