All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dionysius Wilson Almeida <dwilson@technolunatic.com>
To: Andrey Savochkin <saw@saw.sw.com.sg>
Cc: dwilson@technologist.com, linux-kernel@vger.kernel.org
Subject: Re: eepro100: wait_for_cmd_done timeout
Date: Fri, 22 Jun 2001 13:06:32 -0700	[thread overview]
Message-ID: <20010622130632.A31329@technolunatic.com> (raw)
In-Reply-To: <20010620163134.A22173@technolunatic.com> <20010620195134.A6877@saw.sw.com.sg> <20010620170202.B22565@technolunatic.com> <20010621183603.A28081@technolunatic.com> <20010622093158.B2448@saw.sw.com.sg>
In-Reply-To: <20010622093158.B2448@saw.sw.com.sg>; from saw@saw.sw.com.sg on Fri, Jun 22, 2001 at 09:31:58AM -0400

[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]

Hi Andrey,

I'm attaching the log file.. please let me know if u need other
details.

-Wilson

* Andrey Savochkin (saw@saw.sw.com.sg) wrote:
> On Thu, Jun 21, 2001 at 06:36:03PM -0700, Dionysius Wilson Almeida wrote:
> > I tried inserting a udelay(1) and increasing the count ..but
> > the same behaviour.  
> > 
> > any clues ? btw, i've been able to compile the redhat 7.1 intel e100
> > driver and it works fine for my card.
> 
> Your problem is different from anyone else's, as I explained.
> You see "netdev watchdog" message first.
> It means that the card just stopped to transmit packets.
> All other messages printed after that, including wait_for_cmd_done timeout,
> are irrelevant to this problem.  Your card just doesn't transmit.
> 
> Please send me a complete log of what the kernel prints, since powering up
> the computer.
> 
> 	Andrey
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Boy!  Eucalyptus!

[-- Attachment #2: kernel.log.gz --]
[-- Type: application/x-gzip, Size: 6389 bytes --]

  reply	other threads:[~2001-06-22 20:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-20 23:31 eepro100: wait_for_cmd_done timeout Dionysius Wilson Almeida
2001-06-20 23:51 ` Andrey Savochkin
2001-06-21  0:02   ` Dionysius Wilson Almeida
2001-06-21 13:46     ` Rafael Martinez
2001-06-22  1:36     ` Dionysius Wilson Almeida
2001-06-22 13:31       ` Andrey Savochkin
2001-06-22 20:06         ` Dionysius Wilson Almeida [this message]
2001-06-21 14:19 ` Masaru Kawashima
2001-06-21 14:37   ` John Madden
2001-06-22  1:27     ` Masaru Kawashima
2001-06-21 16:28   ` Masaru Kawashima
  -- strict thread matches above, loose matches on Subject: below --
2003-02-27 16:56 Paul Rolland
2003-02-27 20:30 ` Andrey Nekrasov
2003-02-28  6:50   ` Paul Rolland
2003-03-28 11:42 Chris Bacott
2003-03-28 17:59 ` Jeff Garzik

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=20010622130632.A31329@technolunatic.com \
    --to=dwilson@technolunatic.com \
    --cc=dwilson@technologist.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.