netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: madis <madis@cyber.ee>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: Madis Janson <madis@ats.cyber.ee>, netdev@oss.sgi.com
Subject: Re: forcedeth unknown events 0x21
Date: Mon, 5 Jan 2004 14:58:48 +0200 (EET)	[thread overview]
Message-ID: <Pine.LNX.4.53.0401051456060.1039@alien> (raw)
In-Reply-To: <3FE6678B.5070006@gmx.net>


On Mon, 22 Dec 2003, Carl-Daniel Hailfinger wrote:

> 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.
>

the unknown events message disappeared,
but the network did not start to work...

========================================================
+               if (events & (NVREG_IRQ_RX_ERR)) {
+                       dprintk(KERN_DEBUG "%s: received irq with events
0x%x.
Probably RX fail.\n",
+                                               dev->name, events);
here were '}' missing.

-- 
mzz

  reply	other threads:[~2004-01-05 12:58 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
2004-01-05 12:58   ` madis [this message]
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=Pine.LNX.4.53.0401051456060.1039@alien \
    --to=madis@cyber.ee \
    --cc=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).