lkml.org 
[lkml]   [2005]   [Sep]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-09-03 20:40    [W:0.077 / U:0.292 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site