Subject : My mm-mystery-crash has now sneaked into mainline
Submitter : "Torsten Kaiser" <firstname.lastname@example.org>
Date : 2008-02-11 22:46
References : http://lkml.org/lkml/2008/2/11/424
Handled-By : Stefan Richter <email@example.com>
This entry is being used for tracking a regression from 2.6.24. Please don't
close it until the problem is fixed in the mainline or the report is rejected.
- There is no evidence that this is a drivers/ieee1394 bug.
- There isn't anybody handling this bug.
References : http://lkml.org/lkml/2008/2/16/267
OK, 2.6.25-rc2-mm1 did also die, this one with left a better OOPS. I will attached this info, when I'm done with this comment.
The first reference is a summary what I found, I also posted a message linking to all the crashed I posted to the lkml that I think are cause by this:
I guess something is corrupting skbs or lists of skbs and Stefans ieee1394 is just hit, because I'm using it as the main network on this system. But it also crashed with a real ethernet (tg3 driver).
What I don't really understand is, that the skbs seem to come from SLUB, but turning on slub_debug via kernel commandline only slowed the system down (ok normal) and made it more difficult to provoke the crash, but did not result in additional warnings or errors.
Created attachment 14877 [details]
OOPS from 2.6.25-rc2-mm1
The revert-patch from http://lkml.org/lkml/2008/2/19/231 fixes this for me and seems to be current best way to fix this.
Fixed by: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=00e962c5408b9f2d0bebd2308673fe982cb9a5fe