[BUG] >2.6.27 dies at cardbus init on laptop

[BUG] >2.6.27 dies at cardbus init on laptop

[David Pflug]

While trying to boot kernels greater than 2.6.27 on this Toshiba
Satellite 1135-S155, it freezes while initializing Texas Instruments
PCI1410 PC card Cardbus Controller [104c:ac50]. However, it boots with
pci=noacpi. The IRQ of the cardbus is shared by one of the USB
controllers and the IDE controller.

Identical symptoms on 2.6.29rc5.

Last few messages with default kernel line:
pci 0000:00:1e.0:   PREFETCH window: 0x00000040000000-0x0000004bffffff
pci 0000:02:02.0: enabling device (0000 -> 0003)
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
pci 0000:02:02.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11

dmesg with acpi=off:
http://dpaste.com/hold/121766/

Kernel config:
http://dpaste.com/hold/121721/

lspci output:
http://dpaste.com/hold/121768/

Is there anything else I can do to help debug?

--
David Pflug

Re: [BUG] >2.6.27 dies at cardbus init on laptop

[Andrew Morton]

(cc linux-acpi)

On Tue, 17 Feb 2009 14:28:23 -0500 David Pflug <dtpflug@gmail.com> wrote:

> While trying to boot kernels greater than 2.6.27 on this Toshiba
> Satellite 1135-S155, it freezes while initializing Texas Instruments
> PCI1410 PC card Cardbus Controller [104c:ac50]. However, it boots with
> pci=noacpi. The IRQ of the cardbus is shared by one of the USB
> controllers and the IDE controller.
> 
> Identical symptoms on 2.6.29rc5.
> 
> Last few messages with default kernel line:
> pci 0000:00:1e.0:   PREFETCH window: 0x00000040000000-0x0000004bffffff
> pci 0000:02:02.0: enabling device (0000 -> 0003)
> ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
> PCI: setting IRQ 11 as level-triggered
> pci 0000:02:02.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
> 
> dmesg with acpi=off:
> http://dpaste.com/hold/121766/
> 
> Kernel config:
> http://dpaste.com/hold/121721/
> 
> lspci output:
> http://dpaste.com/hold/121768/

presumably an acpi-related thing.

> Is there anything else I can do to help debug?

Best to raise a report against acpi at bugzilla.kernel.org, please.

Often it's better to report kernel bugs via email, but acpi is
exceptional in that regard.  It's all a bit confusing.