> Another followup...
>
> people have posted a few suggestions about why my 2.0.34pre2 box has been
> deadlocking, thought I'd add some more data points to the list...
Try 2.0.34pre7? There's a nasty memory corruption bug fixed, introduced in
2.0.33.... I'm now thinking it maybe caused one of my 2.0.33 crashes. Did
you have stability troubles with 2.0.32?
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu