mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* e100_wait_exec_cmd && e100_wait_exec_simple: Wait failed
@ 2002-07-10 11:13 Richard Ems
  2002-07-10 11:24 ` Andrea Arcangeli
  0 siblings, 1 reply; 2+ messages in thread
From: Richard Ems @ 2002-07-10 11:13 UTC (permalink / raw)
  To: andrea, linux-kernel

Hi Andrea, hi list!

Using SuSE's 8.0 default kernel (k_deflt-2.4.18-58):

Intel(R) PRO/100 Fast Ethernet Adapter - Loadable driver, ver 1.8.37
...
eth0 e100_wait_exec_cmd: Wait failed.
...
last message repeated 23 times
last message repeated 34 times
...



And using SuSE's k_deflt-2.4.18-186:
Intel(R) PRO/100 Fast Ethernet Adapter - Loadable driver, ver 2.0.30-k1
...
eth0 e100_wait_exec_simple: Wait failed
...
last message repeated 8 times
last message repeated 25 times
...

I also had machine hangs with both drivers during heavy network load.
Could these hangup's be related to the driver's "error"? Or is it just a 
  "warning"?


from lspci -vvv:

...
02:08.0 Ethernet controller: Intel Corp. 82801BA/BAM/CA/CAM Ethernet 
Controller (rev 01)
         Subsystem: Intel Corp.: Unknown device 3013
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- 
ParErr- Stepping- SERR+ FastB2B-
         Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Latency: 66 (2000ns min, 14000ns max), cache line size 08
         Interrupt: pin A routed to IRQ 9
         Region 0: Memory at f5000000 (32-bit, non-prefetchable) [size=4K]
         Region 1: I/O ports at 3400 [size=64]
         Capabilities: [dc] Power Management version 2
                 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA 
PME(D0+,D1+,D2+,D3hot+,D3cold+)
                 Status: D0 PME-Enable- DSel=0 DScale=2 PME-
...

Do you need any more information?
(P III 800 Mhz, 256 MB RAM)


Thanks for any help, Richard

P.S.: Please reply to r.ems@gmx.net, I'm not on lkml.


-- 
Richard Ems
... e-mail: r.ems@gmx.net
... Computer Science, University of Hamburg

Unix IS user friendly. It's just selective about who its friends are.


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: e100_wait_exec_cmd && e100_wait_exec_simple: Wait failed
  2002-07-10 11:13 e100_wait_exec_cmd && e100_wait_exec_simple: Wait failed Richard Ems
@ 2002-07-10 11:24 ` Andrea Arcangeli
  0 siblings, 0 replies; 2+ messages in thread
From: Andrea Arcangeli @ 2002-07-10 11:24 UTC (permalink / raw)
  To: r.ems; +Cc: linux-kernel, linux.nics

On Wed, Jul 10, 2002 at 01:13:17PM +0200, Richard Ems wrote:
> Hi Andrea, hi list!

Hello Richard,

> 
> Using SuSE's 8.0 default kernel (k_deflt-2.4.18-58):
> 
> Intel(R) PRO/100 Fast Ethernet Adapter - Loadable driver, ver 1.8.37
> ...
> eth0 e100_wait_exec_cmd: Wait failed.
> ...
> last message repeated 23 times
> last message repeated 34 times
> ...
> 
> 
> 
> And using SuSE's k_deflt-2.4.18-186:
> Intel(R) PRO/100 Fast Ethernet Adapter - Loadable driver, ver 2.0.30-k1
> ...
> eth0 e100_wait_exec_simple: Wait failed
> ...
> last message repeated 8 times
> last message repeated 25 times
> ...
> 
> I also had machine hangs with both drivers during heavy network load.
> Could these hangup's be related to the driver's "error"? Or is it just a 
>  "warning"?
> 
> 
> from lspci -vvv:
> 
> ...
> 02:08.0 Ethernet controller: Intel Corp. 82801BA/BAM/CA/CAM Ethernet 
> Controller (rev 01)
>         Subsystem: Intel Corp.: Unknown device 3013
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- 
> ParErr- Stepping- SERR+ FastB2B-
>         Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium 
> >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 66 (2000ns min, 14000ns max), cache line size 08
>         Interrupt: pin A routed to IRQ 9
>         Region 0: Memory at f5000000 (32-bit, non-prefetchable) [size=4K]
>         Region 1: I/O ports at 3400 [size=64]
>         Capabilities: [dc] Power Management version 2
>                 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA 
> PME(D0+,D1+,D2+,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=2 PME-
> ...
> 
> Do you need any more information?
> (P III 800 Mhz, 256 MB RAM)
> 
> 
> Thanks for any help, Richard
> 
> P.S.: Please reply to r.ems@gmx.net, I'm not on lkml.

I'm probably not the best person to handle these reports. You should
report to linux.nics@intel.com (CC'ed), they are the authors of the e100
driver.

Until a fix is available I would suggest to try to use the original
linux eepro100 driver and see if the machine hangs goes away that way.

thanks,

Andrea

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-07-10 11:20 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-07-10 11:13 e100_wait_exec_cmd && e100_wait_exec_simple: Wait failed Richard Ems
2002-07-10 11:24 ` Andrea Arcangeli

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®