From: Francois Romieu <romieu@cogenit.fr>
To: Juergen Wolf <JuWo@N-Club.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with SMC Etherpower II + kernel newer 2.4.2
Date: Wed, 4 Jul 2001 14:57:52 +0200 [thread overview]
Message-ID: <20010704145752.A29311@se1.cogenit.fr> (raw)
In-Reply-To: <Pine.LNX.4.30.0107021014230.15054-100000@flash.datafoundation.com> <3B42DEC2.AAB1E65B@N-Club.de>
In-Reply-To: <3B42DEC2.AAB1E65B@N-Club.de>; from JuWo@N-Club.de on Wed, Jul 04, 2001 at 11:15:46AM +0200
Juergen Wolf <JuWo@N-Club.de> ecrit :
[...]
Jul 2 13:06:59 localhost kernel: eth0: Too much work at interrupt, IntrStatus=0x008d0004.
Receive Status Valid
Receive Copy In Progress
Transmit Idle
Receive Queue Empty -> no more receive buffer available
It looks like one waits too long before processing incoming data
but I'm curious to know where they come from if nothing is plugged.
[...]
> Bus 1, device 0, function 0:
> VGA compatible controller: nVidia Corporation NV11 (rev 161).
> IRQ 10.
> Master Capable. Latency=32. Min Gnt=5.Max Lat=1.
> Non-prefetchable 32 bit memory at 0xdc000000 [0xdcffffff].
> Prefetchable 32 bit memory at 0xd0000000 [0xd7ffffff].
Is X or something like a nvidia module enabled ?
--
Ueimor
next prev parent reply other threads:[~2001-07-04 12:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 11:55 Problem with SMC Etherpower II + kernel newer 2.4.2 Juergen Wolf
2001-07-02 14:18 ` John Jasen
2001-07-04 9:15 ` Juergen Wolf
2001-07-04 12:57 ` Francois Romieu [this message]
2001-07-06 7:48 ` Juergen Wolf
2001-07-06 11:44 ` Francois Romieu
2001-07-06 12:27 ` Juergen Wolf
2001-07-06 12:34 ` Jeff Garzik
2001-07-06 12:51 ` Juergen Wolf
2001-07-06 12:59 ` [PATCH] " Jeff Garzik
2001-07-06 15:04 ` Francois Romieu
2001-07-03 9:31 ` Florian Schmitt
2001-07-03 14:57 ` Olivier Sessink
2001-07-04 9:19 ` Francois Romieu
2001-07-04 15:30 ` Florian Schmitt
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=20010704145752.A29311@se1.cogenit.fr \
--to=romieu@cogenit.fr \
--cc=JuWo@N-Club.de \
--cc=linux-kernel@vger.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 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.