public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Shirley" <dave@cs.curtin.edu.au>
To: <vda@port.imtp.ilyichevsk.odessa.ua>, <linux-kernel@vger.kernel.org>
Subject: Re: Help, eth0: transmit timed out!
Date: Wed, 12 Mar 2003 22:41:48 +0800	[thread overview]
Message-ID: <002101c2e8a5$8358d4c0$2400a8c0@compaq3> (raw)
In-Reply-To: 200303121353.h2CDrhu30117@Port.imtp.ilyichevsk.odessa.ua

Tried a different NIC, another 3c905c.

Yeah i know about the modules thing, i turned it off
in case that was the problem.

D
----- Original Message ----- 
From: "Denis Vlasenko" <vda@port.imtp.ilyichevsk.odessa.ua>
To: "David Shirley" <dave@cs.curtin.edu.au>; <linux-kernel@vger.kernel.org>
Sent: Wednesday, March 12, 2003 9:50 PM
Subject: Re: Help, eth0: transmit timed out!


> On 12 March 2003 15:54, David Shirley wrote:
> > Its strange we have another machine, exact same setup,
> > hardware/software and it doesn't have any problems.
> 
> Did you try to swap some hardware? NIC would be the first
> to swap.
> 
> > The other thing is that sometimes the machine freezes totally,
> > and othertimes it comes back after 30 secs??
> 
> If it's a driver problem, anything is possible.
> 
> > FYI: Its not a modular kernel, but ill try the printk thing.
> 
> Modular one will be far easier (faster) to play with.
> You just unload the module, recompile and reload.
> No reboot cycles.
> --
> vda
> 

  reply	other threads:[~2003-03-12 14:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12  5:23 Help, eth0: transmit timed out! David Shirley
2003-03-12 13:37 ` Denis Vlasenko
2003-03-12 13:54   ` David Shirley
2003-03-12 13:50     ` Denis Vlasenko
2003-03-12 14:41       ` David Shirley [this message]
2003-03-12 17:52         ` Hans-Peter Jansen
2003-03-13  1:59           ` David Shirley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002101c2e8a5$8358d4c0$2400a8c0@compaq3' \
    --to=dave@cs.curtin.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox