(In reply to comment #11)
> I'm not sure what to tell you. This seems to be an isolated event. Without
> debugging information, I don't have much to go on.
I fully understand.
> If you have the will and time, you could try compling your own stock 2.6.13
> kernel and see if the problem still occurs with that
(In reply to comment #11)
> I'm not sure what to tell you. This seems to be an isolated event. Without
> debugging information, I don't have much to go on.
I fully understand.
> If you have the will and time, you could try compling your own stock 2.6.13
> kernel and see if the problem still occurs with that
Will try.