Alan Stern <[email protected]> wrote:
>
> What about those scheduler changes you found through the bisection search?
> Any word on that?
Ingo's gone over them pretty closely. The current theory is that the CPU
scheduler change alters timing sufficiently for the bug to bite.
The machine passes memtest86.
Ingo's suspecting stack corruption. Do you know whether USB anywhere does
DMA into automatically-allocated storage (ie: kernel stacks)?
Am about to reboot into a stack-corruption-detector patch from Ingo.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
