From: "Jaswinder Singh Rajput" <jaswinderlinux@gmail.com>
To: wtarreau@hera.kernel.org, kernel-testers@vger.kernel.org,
netdev@vger.kernel.org, jeff@garzik.org,
linux-kernel@vger.kernel.org
Subject: BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out
Date: Fri, 2 Jan 2009 20:10:50 +0530 [thread overview]
Message-ID: <3f9a31f40901020640m4a9a63caq9c96ba84ccd64d88@mail.gmail.com> (raw)
Hello all,
Now I tested fealnx driver from 2.4.37 (2.4 git). I am still getting
"NETDEV WATCHDOG: eth0: transmit timed out". Please let me know how
can I fix this problem.
fealnx.c:v2.51 Nov-17-2001
eth0: 100/10M Ethernet PCI Adapter at 0x6200, 00:40:95:78:05:73, IRQ 11.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 00000000, resetting...
Rx ring c11bf000: 80000000 80000000 80000000 80000000 80000000
80000000 80000000 80000000 80000000 80000000 80000000 80000000
Tx ring c11be000: 80000000 80000000 80000000 80000000 0000 80000000
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 00000000, resetting...
Rx ring c11bf000: 80000000 80000000 80000000 80000000 80000000
80000000 80000000 80000000 80000000 80000000 80000000 80000000
Tx ring c11be000: 80000000 0000 80000000 80000000 80000000 80000000
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 00000000, resetting...
Rx ring c11bf000: 80000000 80000000 80000000 80000000 80000000
80000000 80000000 80000000 80000000 80000000 80000000 80000000
Tx ring c11be000: 80000000 80000000 80000000 80000000 80000000 0000
00:0a.0 Ethernet controller: MYSON Technology Inc: Unknown device 0803
Subsystem: MYSON Technology Inc: Unknown device 0803
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: 32 (8000ns min, 16000ns max), cache line size 08
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 6200 [size=256]
Region 1: Memory at e1000000 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [88] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0-,D1+,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Thank you,
JSR
next reply other threads:[~2009-01-02 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 14:40 Jaswinder Singh Rajput [this message]
2009-01-02 14:48 ` Willy Tarreau
2009-01-02 15:48 ` Jaswinder Singh Rajput
2009-01-02 18:57 ` Francois Romieu
2009-01-03 11:10 ` Jaswinder Singh Rajput
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=3f9a31f40901020640m4a9a63caq9c96ba84ccd64d88@mail.gmail.com \
--to=jaswinderlinux@gmail.com \
--cc=jeff@garzik.org \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wtarreau@hera.kernel.org \
/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
all inboxes | Powered by JetHome®