From: Vincent Hanquez <tab@snarc.org>
To: Vitez Gabor <vitezg@niif.hu>
Cc: linux-kernel@vger.kernel.org, Manfred Spraul <manfred@colorfullife.com>
Subject: Re: forcedeth: "received irq with unknown events 0x1"
Date: Mon, 11 Oct 2004 17:49:50 +0200 [thread overview]
Message-ID: <20041011154950.GA22553@snarc.org> (raw)
In-Reply-To: <20041011145104.GA9494@swszl.szkp.uni-miskolc.hu>
[-- Attachment #1: Type: text/plain, Size: 388 bytes --]
On Mon, Oct 11, 2004 at 04:51:04PM +0200, Vitez Gabor wrote:
> Hi,
>
> my forcedeth driver said:
>
> eth1: received irq with unknown events 0x1. Please report
Hi,
In latest 2.6, the 0x1 event is handle as IRQ_RX_ERROR.
the 2.4 driver is not synced with 2.6 and apparently a bit old.
you may consider a backport of the 2.6 driver to the 2.4 to fix the problem.
--
Tab
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-11 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 14:51 forcedeth: "received irq with unknown events 0x1" Vitez Gabor
2004-10-11 15:49 ` Vincent Hanquez [this message]
2004-10-11 16:49 ` Manfred Spraul
2004-10-12 8:20 ` Vitez Gabor
2004-10-12 16:50 ` Manfred Spraul
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=20041011154950.GA22553@snarc.org \
--to=tab@snarc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=vitezg@niif.hu \
/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