Hi Andrey,
I'm attaching the log file.. please let me know if u need other
details.
-Wilson
* Andrey Savochkin ([EMAIL PROTECTED]) 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 beh
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 differ
20 16:10:18 debianlap kernel: eth0: Tx ring dump, Tx queue 342 / 314:
> > > Jun 20 16:14:07 debianlap kernel: eepro100: wait_for_cmd_done timeout!
> > > Jun 20 16:14:38 debianlap last message repeated 5 times
>
> --
> Eat shit -- billions of flies can't be wrong.
>
On Thu, 21 Jun 2001 09:37:47 -0500
John Madden <[EMAIL PROTECTED]> wrote:
> errors. Think the patch with the udelay() will still work?
In my system, the patch with the udelay() is working.
--
Masaru Kawashima
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
t; On Wed, 20 Jun 2001 16:31:34 -0700
> Dionysius Wilson Almeida >
>wrote:
> > Jun 20 16:14:07 debianlap kernel: eepro100: wait_for_cmd_done timeout!
> > Jun 20 16:14:38 debianlap last message repeated 5 times
>
> I saw the same message.
>
> The comment bef
> Dionysius Wilson Almeida >
>wrote:
> > Jun 20 16:14:07 debianlap kernel: eepro100: wait_for_cmd_done timeout!
> > Jun 20 16:14:38 debianlap last message repeated 5 times
>
> I saw the same message.
>
> The comment before wait_for_cmd_done() function in
&g
Hi!
On Wed, 20 Jun 2001 16:31:34 -0700
Dionysius Wilson Almeida > wrote:
> Jun 20 16:14:07 debianlap kernel: eepro100: wait_for_cmd_done timeout!
> Jun 20 16:14:38 debianlap last message repeated 5 times
I saw the same message.
The comment before wait_for_cmd_done() function in
linu
---Reply to mail from Dionysius Wilson Almeida about eepro100: wait_for_cmd_done
timeout
> No..that was pretty much what i saw in the logs.
>
> I see wait_for_cmd_done timeout being the only one being repeated in the
> logs
>
The same here with 2.4.1 and 2.4.3.
Rafael
queue 342 / 314:
> > Jun 20 16:14:07 debianlap kernel: eepro100: wait_for_cmd_done timeout!
> > Jun 20 16:14:38 debianlap last message repeated 5 times
--
Eat shit -- billions of flies can't be wrong.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel
16:10:18 debianlap kernel: eth0: Tx ring dump, Tx queue 342 / 314:
> Jun 20 16:14:07 debianlap kernel: eepro100: wait_for_cmd_done timeout!
> Jun 20 16:14:38 debianlap last message repeated 5 times
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bod
20 16:10:18 debianlap kernel: eth0:27 0001.
Jun 20 16:10:18 debianlap kernel: eth0:28 0001.
Jun 20 16:10:18 debianlap kernel: eth0:29 0001.
Jun 20 16:10:18 debianlap kernel: eth0:30 0001.
Jun 20 16:10:18 debianlap kernel: eth0:31 0001.
Jun 20 16:14:07 debianlap
Hello,
I'm seeing the message periodically:
Nov 8 09:52:59 kgate last message repeated 5 times
Nov 8 11:26:54 kgate kernel: eepro100: wait_for_cmd_done timeout!
Nov 8 11:56:12 kgate kernel: eepro100: wait_for_cmd_done timeout!
Nov 8 14:38:45 kgate kernel: eepro100: wait_for_cmd_done ti
12 matches
Mail list logo
