From: Dominik Karall <dominik.karall@gmx.net>
To: Linux Kernel ML <linux-kernel@vger.kernel.org>,
Daniele Venzano <webvenza@libero.it>
Subject: SiS900: NULL pointer encountered in Rx ring, skipping
Date: Fri, 23 Jul 2004 20:52:06 +0200 [thread overview]
Message-ID: <200407232052.06616.dominik.karall@gmx.net> (raw)
After a few hours my network doesn't work on my laptop. There appear a lot of
those messages:
eth0: NULL pointer encountered in Rx ring, skipping
eth0: NULL pointer encountered in Rx ring, skipping
eth0: NULL pointer encountered in Rx ring, skipping
eth0: NULL pointer encountered in Rx ring, skipping
eth0: NULL pointer encountered in Rx ring, skipping
eth0: NULL pointer encountered in Rx ring, skipping
eth0: NULL pointer encountered in Rx ring, skipping
eth0: NULL pointer encountered in Rx ring, skipping
eth0: NULL pointer encountered in Rx ring, skipping
eth0: NULL pointer encountered in Rx ring, skipping
It works again after restarting network. I'm using 2.6.8-rc2 now. It was the
same problem in 2.6.7, but I didn't test it with earlier kernels.
And right now I got one more eth0 message:
eth0: Too much work at interrupt, interrupt status = 0x00000031.
eth0: Too much work at interrupt, interrupt status = 0x00000001.
Here the messages after module loading:
eth0: SiS 900 Internal MII PHY transceiver found at address 1.
eth0: Using transceiver found at address 1 as default
eth0: SiS 900 PCI Fast Ethernet at 0xd000, IRQ 9, 00:a0:cf:c0:8a:dc.
eth0: Media Link On 100mbps full-duplex
eth0: Memory squeeze,deferring packet.
lspci:
0000:00:01.1 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI
Fast Ethernet (rev 80)
Subsystem: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet
Adapter
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 (13000ns min, 2750ns max)
Interrupt: pin C routed to IRQ 9
Region 0: I/O ports at d000 [size=ffda0000]
Region 1: Memory at ffdc0000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at 00020000 [disabled]
Capabilities: [40] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
____________
dominik
next reply other threads:[~2004-07-23 18:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 18:52 Dominik Karall [this message]
2004-07-25 9:21 ` Dominik Karall
2004-07-27 15:26 ` Jeff Garzik
2004-07-27 16:14 ` Dominik Karall
2004-07-27 16:21 ` Jeff Garzik
2004-07-28 12:29 ` Daniele Venzano
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=200407232052.06616.dominik.karall@gmx.net \
--to=dominik.karall@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=webvenza@libero.it \
/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®