netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Madis Janson <madis@ats.cyber.ee>
Cc: netdev@oss.sgi.com
Subject: Re: forcedeth unknown events 0x21
Date: Mon, 22 Dec 2003 04:39:55 +0100	[thread overview]
Message-ID: <3FE6678B.5070006@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0312180952100.21042@kiku.itsise>

[-- Attachment #1: Type: text/plain, Size: 564 bytes --]

Madis Janson wrote:
> When trying forcedeth_2_6_patch_v19.txt, i got the following message
> fastly repeating after ifup eth0:
> 
> "eth0: received irq with unknown events 0x21. Please report"
> 
> and it didn't work eighter (ifup just stalled).
> 
> kernel:
> 
> 2.6.0 release + patches:
> http://www.held.org.il/patches/patch-lirc-2.6.0-test9-oh.diff.bz2
> http://www.hailfinger.org/carldani/linux/patches/forcedeth/forcedeth_2_6_patch_v19.txt

Please try the attached patch on top of it and report back if it works.


Carl-Daniel
-- 
http://www.hailfinger.org/

[-- Attachment #2: forcedeth_19test1.diff --]
[-- Type: text/plain, Size: 1536 bytes --]

===== drivers/net/forcedeth.c 1.8 vs edited =====
--- 1.8/drivers/net/forcedeth.c	Mon Dec  8 17:58:03 2003
+++ edited/drivers/net/forcedeth.c	Mon Dec 22 04:05:36 2003
@@ -127,6 +127,7 @@
 #define NVREG_IRQSTAT_MIIEVENT	0x040
 #define NVREG_IRQSTAT_MASK		0x1ff
 	NvRegIrqMask = 0x004,
+#define NVREG_IRQ_RX_ERR		0x0001
 #define NVREG_IRQ_RX			0x0002
 #define NVREG_IRQ_RX_NOBUF		0x0004
 #define NVREG_IRQ_TX_ERR		0x0008
@@ -136,7 +137,7 @@
 #define NVREG_IRQ_TX1			0x0100
 #define NVREG_IRQMASK_WANTED_1		0x005f
 #define NVREG_IRQMASK_WANTED_2		0x0147
-#define NVREG_IRQ_UNKNOWN		(~(NVREG_IRQ_RX|NVREG_IRQ_RX_NOBUF|NVREG_IRQ_TX_ERR|NVREG_IRQ_TX2|NVREG_IRQ_TIMER|NVREG_IRQ_LINK|NVREG_IRQ_TX1))
+#define NVREG_IRQ_UNKNOWN		(~(NVREG_IRQ_RX_ERR|NVREG_IRQ_RX|NVREG_IRQ_RX_NOBUF|NVREG_IRQ_TX_ERR|NVREG_IRQ_TX2|NVREG_IRQ_TIMER|NVREG_IRQ_LINK|NVREG_IRQ_TX1))
 
 	NvRegUnknownSetupReg6 = 0x008,
 #define NVREG_UNKSETUP6_VAL		3
@@ -1056,7 +1057,7 @@
 			spin_unlock(&np->lock);
 		}
 
-		if (events & (NVREG_IRQ_RX|NVREG_IRQ_RX_NOBUF)) {
+		if (events & (NVREG_IRQ_RX_ERR|NVREG_IRQ_RX|NVREG_IRQ_RX_NOBUF)) {
 			rx_process(dev);
 			if (alloc_rx(dev)) {
 				spin_lock(&np->lock);
@@ -1071,6 +1072,9 @@
 			link_irq(dev);
 			spin_unlock(&np->lock);
 		}
+		if (events & (NVREG_IRQ_RX_ERR)) {
+			dprintk(KERN_DEBUG "%s: received irq with events 0x%x. Probably RX fail.\n",
+						dev->name, events);
 		if (events & (NVREG_IRQ_TX_ERR)) {
 			dprintk(KERN_DEBUG "%s: received irq with events 0x%x. Probably TX fail.\n",
 						dev->name, events);

  reply	other threads:[~2003-12-22  3:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18  8:05 forcedeth unknown events 0x21 Madis Janson
2003-12-22  3:39 ` Carl-Daniel Hailfinger [this message]
2004-01-05 12:58   ` madis
2004-01-11 22:41     ` Carl-Daniel Hailfinger
2004-02-24 16:04       ` Madis Janson

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=3FE6678B.5070006@gmx.net \
    --to=c-d.hailfinger.kernel.2003@gmx.net \
    --cc=madis@ats.cyber.ee \
    --cc=netdev@oss.sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).