Date: Wed, 24 Jan 2007 14:37:23 +0000 (GMT)
From: Hugh Dickins <hugh@veritas.com>
To: Chris Rankin <rankincj@yahoo.com>
cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-stable release plans?
In-Reply-To: <20070124133037.98357.qmail@web52914.mail.yahoo.com>
Message-ID: <Pine.LNX.4.64.0701241425170.10956@blonde.wat.veritas.com>
References: <20070124133037.98357.qmail@web52914.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1075
Lines: 27

On Wed, 24 Jan 2007, Chris Rankin wrote:
> 
> Personally, I dumped 2.6.19.x like a hot coal as soon as I tripped over this bug:
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=7707
> 
> I didn't take much to trigger it, either. But the silence has been deafening.

Oh, the page_remove_rmap BUG, page_mapcount negative.

Sorry for the deafening silence, see I was CC'ed but dropped the ball.

That's surely no reason to dump 2.6.19.x, you'll find the occasional
such report on every(?) release since page mapcount went into 2.6.7.

Oftentimes it's bad RAM (try memtest86), sometimes it's a bad driver
(probably the case for the tainted P report appended to your untainted
one), sometimes it's unidentified memory corruption.  Not once (except
during experimental patch testing) has it been proved due to an actual
VM problem.

Hugh
-
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/