> > Running X will also aggravate the situation -- this is
> > clearly a sign of some missing or unmatched cli/sti or
> > lock/unlock pair... (in a subtle place, as it doesn't
> > show up often)
>
> Now that you mention it, I was using X at the time of the lock up.
X locks me in 2.0.35 occasionally too. No log of it, no oops,
just dead.
-- Mike A. Harris - Computer Consultant - Linux advocateEscape from the confines of Microsoft's operating systems and push your PC to it's limits with LINUX - a real OS. http://www.redhat.com
- 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.altern.org/andrebalsa/doc/lkml-faq.html