Dead 2400 with "stuck on TLB IPI wait (CPU#1)" message

Basil Hussain basil.hussain at kodakweddings.com
Wed Jun 5 05:16:01 CDT 2002


Hi,

I seem to remember what you describe ("transmit timed out" errors with
eepro100) used to be a problem due to a bug. I might be wrong.

Anyway, perhaps you can find a solution in the eepro100 driver mailing list
archive:
http://www.scyld.com/pipermail/eepro100/

Or, try using Intel's e100 driver instead:
http://downloadfinder2.intel.com/scripts-df/Detail_Desc.asp?ProductID=60&Dwn
ldID=2896

Regards,

Basil Hussain
---------------------------------------
Internet Developer, Kodak Weddings
E-Mail: basil.hussain at kodakweddings.com

> -----Original Message-----
> From: linux-poweredge-admin at dell.com
> [mailto:linux-poweredge-admin at dell.com]On Behalf Of Hubbard, David
> Sent: 04 June 2002 19:12
> To: 'Seth Mos'
> Cc: 'linux-poweredge at dell.com'
> Subject: RE: Dead 2400 with "stuck on TLB IPI wait (CPU#1)" message
>
>
> Upon further investigation, now that it's back up, the
> kernel.log makes it look like the problem was network
> card related, I think, since I've never seen this before.
>
> Here's the useful output from dmesg on the network card
> driver:
>
> eepro100.c:v1.09j-t 9/29/99 Donald Becker
> http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
> eepro100.c: $Revision: 1.20.2.10 $ 2000/05/31 Modified by Andrey V.
> Savochkin <saw at saw.sw.com.sg> and others
> eepro100.c: VA Linux custom, Dragan Stancevic <visitor at valinux.com>
> 2000/11/15
> Intel PCI EtherExpress Pro100 82557, 00:A0:C9:D7:CB:83, I/O at 0xece0, IRQ
> 17.
>
>
> And here's what was in kernel.log just before the
> "stuck on TLB IPI wait" junk started.
>
> Jun  4 12:38:19 mail kernel: eth0: Transmit timed out: status
> f048  0c00 at
> 36775027/36775090 command 000ca000.
> Jun  4 12:38:19 mail kernel: eth0: Tx ring dump,  Tx queue 36775090 /
> 36775027:
> Jun  4 12:38:19 mail kernel: eth0:     0 200ca000.
> Jun  4 12:38:19 mail kernel: eth0:     1 000ca000.
>
> There were hundreds of those lines.  Is this indicative
> of a bad NIC, bad driver, or just bad luck? :-)
>
> Thanks,
>
> David
>
>
>
>
> > -----Original Message-----
> > From: Seth Mos [mailto:knuffie at xs4all.nl]
> > Sent: Tuesday, June 04, 2002 1:59 PM
> > To: Hubbard, David
> > Cc: 'linux-poweredge at dell.com'
> > Subject: Re: Dead 2400 with "stuck on TLB IPI wait (CPU#1)" message
> >
> >
> > On Tue, 4 Jun 2002, Hubbard, David wrote:
> >
> > > stuck on TLB IPI wait (CPU#1)
> > >
> > > Anyone seen that one before, it seems to have something
> > > to do with SMP and the kernel.  I have a dead 2400 right
> > > now that went down with that message on the console,
> > > remote support is supposed to be attempting to reboot
> > > it for me.
> >
> > There is not much else you can do about this. This can
> > happen. Anything
> > special that the machine might have been doing at the time?
> >
> > Cheers
> >
> >
>
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq or search the
> list archives at http://lists.us.dell.com/htdig/
>





More information about the Linux-PowerEdge mailing list