[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0804241539150.2779@woody.linux-foundation.org>
Date: Thu, 24 Apr 2008 15:41:27 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Jiri Slaby <jirislaby@...il.com>
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 Fri, 25 Apr 2008, Jiri Slaby wrote:
>
> 20 arpings running on wlan0 (don't know if this is related so far), suspend,
> resume, right after resume:
>
> freed 114
> alloced 115
> freed 115
> alloced 116
> WHAT THE HELL (000a3ff8):
> ff00aa00deadcc22 ff00aa00deadcc22 ff00aa00deadcc22 ff00aa00deadcc22
Very interesting indeed.
> Shouldn't be 2.6.25 uttered as broken until this is solved to not corrupt
> anyone's data? I'm going to play with that testing program further in the
> meantime.
Do you actually see this with _plain_ 2.6.25? So far I've assumed that all
the reports are about post-2.6.25 issues.
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).
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists