[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4812108D.6020103@gmail.com>
Date: Fri, 25 Apr 2008 19:10:37 +0200
From: Jiri Slaby <jirislaby@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
CC: Zdenek Kabelac <zdenek.kabelac@...il.com>,
Ingo Molnar <mingo@...e.hu>, "Rafael J. Wysocki" <rjw@...k.pl>,
paulmck@...ux.vnet.ibm.com, David Miller <davem@...emloft.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-ext4@...r.kernel.org, herbert@...dor.apana.org.au,
Pekka Enberg <penberg@...helsinki.fi>,
Christoph Lameter <clameter@....com>
Subject: Re: 2.6.25-git2: BUG: unable to handle kernel paging request at ffffffffffffffff
On 04/25/2008 12:41 AM, Linus Torvalds wrote:
> Also, it does seem like you can re-create this at will in ways that others
> can not. Could you try to bisect it a bit? Right now we have no real clue
> what it is all about, except that it seems to be related to suspend/resume
> and there are some indications that it's about networking (and _perhaps_
> wireless in particular).
Yes! I'm able to reproduce it 90%! We can exclude X, 80211 and so ath5k too (I
removed them from /lib/modules, so they won't ever load).
I set the water mark at 1700 megabytes to allocate by the testing programs, so
that it eats almost all free available memory. Then, I wait to "alloced 1" and
then pm-suspend on second console. After resume, it spits out the corruption.
I'm going to bisect it, will be back in few hours ;).
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists