Re: 2.4.4 kernel freeze

[Jens Gecius <jens@gecius.de>]

	Jens Gecius <jens@gecius.de> writes:

> > > what do you mean by freeze?  in theory, the fact that the irq
> > I cannot ping the machine anymore, no Ooops, no kernel messages, the
> > attached screen is freezed (which implies that no more interrupts
> > are handled, right?)
> 
> Excuse me hopping in.
> 
> I have that situation here, too. Screen frozen, no pings from the
> local network, sysrq doesn't work (keyboard dead).
> 
> maniac kernel: NETDEV WATCHDOG: eth1: transmit timed out
> maniac kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3,
> t=21.
> 
> All this happened on 2.4.3 and 2.4.4 (don't excactly remember on
> earlier 2.4).
> 
> I followed your suggestion regarding PCI-slots. Both my nics used to
> use PCI 4 and 5 (on a gigabyte vxd7, dual 1GHz). Only the one in slot
> 4 had the problems. I switched the card to slot 1 and will monitor the
> situation. I'll mail the list in case it doesn't change my situation.

OK - now it even got worse. After just a couple hours slot5 was dead
(that was the one working just fine with the other card in
slot4). Three minutes later slot1 was dead, too. Both cards share
irq12.

Fortunately, the box wasn't frozen this time. X was up and running
fine and I was able to reboot in a sound manner.

I'll try another change in slots, but unfortunately, my nics are the
ones with the lowest traffic: one other is SCSI, the other one
firewire... (even though the latter one is hardly used).
 
> Any other hints are welcome (other than the noapic, which didn't help).

I have to reiterate this one. Any hints are very welcome.

-- 
Tschoe,                    Get my gpg-public-key here
 Jens                     http://gecius.de/gpg-key.txt