Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted

[Jeremy Higdon]

On Wed, Aug 22, 2007 at 03:56:57PM -0700, Luck, Tony wrote:
> [ 20.903201] [<a0000001003aaa50>] swiotlb_full+0x50/0x120
> [ 20.903202] sp=e00000014322fac0 bsp=e000000143229120
> [ 20.916902] [<a0000001003aac40>] swiotlb_map_single+0x120/0x1c0
> [ 20.916904] sp=e00000014322fac0 bsp=e0000001432290d8
> [ 20.931215] [<a0000001003ab630>] swiotlb_alloc_coherent+0x150/0x240
> [ 20.931217] sp=e00000014322fac0 bsp=e000000143229090
> [ 20.945923] [<a000000100550860>] PrimeIocFifos+0x4c0/0xb20
> [ 20.945925] sp=e00000014322fac0 bsp=e000000143229010
> [ 20.959812] [<a000000100556a80>] mpt_do_ioc_recovery+0xd60/0x28e0
> [ 20.959814] sp=e00000014322faf0 bsp=e000000143228f30
> [ 20.974310] [<a00000010055c8f0>] mpt_attach+0x830/0x20e0
> 
> 
> Hmmm!  So you were in the mpt/fusion driver when you ran out
> of SWIOTLB space.  That's an area where we both have the same
> hardware ... and since it booted for me, it means that the
> driver isn't totally broken.
> 
> I'm totally ignorant of what goes on inside this driver though.
> You have more "ioc's" than I do.  I only see messages from mpt
> bringing up ioc0 & ioc1.  Your boot_log also has ioc2 (which is
> where you crash).  Here's the sdiff(1) output comparing the MPT
> part of your boot log with my successful boot of the same kernel
> and config (your log is the one on the left).  Maybe some MPT/Fusion
> expert can spot something important in this bit?

The more ioc's you have, the more space you will use.

jeremy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/