> Then it looks like the oops report isn't very helpful, as it's
> pointing us to the results of the corrupted list rather than the place
> where the list is being corrupted in the first place?
Looks like.
> Is there any way we can pinpoint where things are going awry?
The corrupt list is owned by the packet scheduling code, I think. You
could try different packet schedulers to see if that makes a difference.
Tim.
*/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/