On Fri, 25 Apr 2008, Jiri Slaby wrote:
quoted text
> 
> 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.

quoted text
> 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
--
unsubscribe notice
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/