On Sat, Sep 03, Ivan Kokshaysky wrote:I had the same problem with an ACER 8101 WLMI. I reverted the 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.
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.
...
Attachment:
pci-assign-res-fix
Description: Binary data
Attachment:
multiple-ioapic-fix
Description: Binary data