CPU Lockup with 2.4.21 and 2.4.22-pre
A message that is not in the archive (sent off-list or not yet received): [email protected]
Am Die, 2003-07-22 um 16.24 schrieb Udo A. Steinberg:
Quoted 6 lines
MT> As you might know, the Compu-Shack fddi products reached end-of-life MT> last year.
Yes. Just thought I'd let you know that we aren't using the same patch as on the website, but one that has been rediffed for 2.4.21 and has an additional fix from you in it.
Mentioned it just to let you know that the company is no longer providing new drivers for new kernels. Probably you better stay with 2.4.18.
[snip]
Seems that a spin lock is already held. Do you get this oops right after opening the device? Then please try NoSelfTest.
Regards,
Michael
On 22 Jul 2003 17:26:10 +0200 Michael Troß (MT) wrote:
MT> Seems that a spin lock is already held. Do you get this oops right after MT> opening the device? Then please try NoSelfTest.
No, the lockup happens during operation. Sometimes the kernel runs only for about one hour, sometimes for a day, but never longer before the lockups happen.
I don't think going back to 2.4.18 will make a difference for this case, or do you think it will?
Regards,
-Udo.