On 4 Nov 1998, Patrick J. LoPresti wrote:
> A couple of weeks ago, we upgraded our master server from Linux 2.0.35
> (tulip.c version 0.88) to 2.0.36pre15 (tulip.c version 0.89H).
>
> Ever since 2.0.33 or so, we have occasionally seen the following
> message logged:
>
> eth0: Re-entering the interrupt handler with proc 1, proc 1 already handling.
This is a bug in the SMP interrupt dispatch code, which the driver is
detecting.
A patch is known -- I'm suprised it's not in pre15.
> Since installing 2.0.36pre15 10 days ago, we had not seen that message
> until last night. Then the message started spewing to the console
> repeatedly (very, very fast) and the system locked up completely. It
> required a hard reset to recover.
..
> Perhaps relevant, perhaps not: The SCSI controller and the Netgear
> card are sharing IRQ 10.
This same problem could hang the other device drivers..
> I note with some interest the following diff between tulip.c versions
> 0.88 and 0.89H:
This exit is cleaner in v0.90, but Alan doesn't want to put in the new
driver version for kernel stability reasons. (I think he's wrong in this
case, but I understand his reasoning and he is the one that makes judgement
calls like this.)
The v0.90 code is:
printk(KERN_ERR "%s: Re-entering the interrupt handler with proc %d,"
" proc %d already handling.\n", dev->name,
tp->smp_proc_id, hard_smp_processor_id());
dev->interrupt = 0;
return;
Donald Becker [EMAIL PROTECTED]
USRA-CESDIS, Center of Excellence in Space Data and Information Sciences.
Code 930.5, Goddard Space Flight Center, Greenbelt, MD. 20771
301-286-0882 http://cesdis.gsfc.nasa.gov/people/becker/whoiam.html
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
