Re: Top kernel oopses/warnings for the week of May 16th 2008

From: Andrea Arcangeli
Date: Sat May 17 2008 - 10:13:15 EST

On Fri, May 16, 2008 at 07:55:39PM -0600, Robert Hancock wrote:
> Arjan van de Ven wrote:
>> Rank 10: __alloc_pages
>> Reported 16 times (31 total reports)
>> Sleeping allocation in interrupt context, some in netlink, some in the
>> nv sata driver
>> This oops was last seen in version, and first seen in
>> 2.6.18-rc1.
>> More info:
> In the case of the sata_nv error, it appears this is happening now because
> blk_queue_bounce_limit is initializing emergency ISA pools which can't be
> done under spinlock. This is happening because the code in
> blk_queue_bounce_limit now thinks that a 32-bit DMA mask requires
> allocating with GFP_DMA. This is only needed for a DMA mask less than
> 32-bit, which is what the original code did. It looks like this was broken
> by this commit:

Looks like or you're certain? I ask because I had your exact same
problem with a regression introduced in 2.6.25-rc, and my patch
attempted to fix it. It looks like it wasn't enough to fix all of it,
but at least it looked like to improve things a bit to reduce the
regression impact without introducing any other problem compared to
the previous 2.6.25-rc code.

> author Andrea Arcangeli <andrea@xxxxxxxxxxxx>
> Wed, 2 Apr 2008 07:06:44 +0000 (09:06 +0200)
> committer Jens Axboe <jens.axboe@xxxxxxxxxx>
> Wed, 2 Apr 2008 07:06:44 +0000 (09:06 +0200)
> Fix bounce setting for 64-bit
> Not sure what this was intended to fix, but I don't think it's right..

The reason I touched that code, is that a change introduced during
2.6.25-rc initialized the isa dma pool even if not necessary and that
broke the reserved-ram patch that requires no __GFP_DMA
allocations. There was no crash in 2.6.24 based kernels, the
regression started in 2.6.25-rc.

I think my patch isn't enough yet as I had another crash for the same
reason but it doesn't seem to trigger with all controllers, simulated
ata under kvm looked ok so I thought the regression was fixed after
the problem was gone under kvm, but it seems other hardware
configuration can still trigger the same problem. At least my patch
reduced the impact of the regression.

Please try to backout my patch, I suspect it'll make thing worse for
you and no btter. You'll have to backout the other change as well to
get back to 2.6.24 correct behavior like I still have too.

Then the fact that the isa pool may be initialized under spinlock that
seems another orthogonal problem, the reason I noticed this wasn't
because of some debug check but because there are no __GFP_DMA pages
in my boot.

Can't work on this right now, but I'm confident my change only
improved things, and the real trouble was with the previous commit.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at