From: Madis Janson <madis@ats.cyber.ee>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: netdev@oss.sgi.com
Subject: Re: forcedeth unknown events 0x21
Date: Tue, 24 Feb 2004 18:04:51 +0200 (EET) [thread overview]
Message-ID: <Pine.LNX.4.58.0402241753150.10866@kiku.itsise> (raw)
In-Reply-To: <4001D113.3030302@gmx.net>
On Sun, 11 Jan 2004, Carl-Daniel Hailfinger wrote:
> madis wrote:
> > 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).
> [...]
> >>
> >>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...
>
> Do you use any powermanagement software (athcool, lvcool, fvcool, coolon,
> athlon cooling patch, anything STPGNT related)? Does your BIOS list
> anything STPGNT related?
>
I didn't found anything STPGNT related to be installed or in BIOS.
But seems that the reason for it to not work was actually stupid cable
modem, that remembered other end network cards hardware address and
refused to respond.
That solved, the 2.6.3 kernels forcedeth works, but about half of the
packets are dropped (rtl8139 used for same thing drops almost nothing).
Also it complains now very much about "unknown event 0x1" (instead of
0x21 which was complained when I tried before).
prev parent reply other threads:[~2004-02-24 16:04 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
2004-01-11 22:41 ` Carl-Daniel Hailfinger
2004-02-24 16:04 ` Madis Janson [this message]
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.58.0402241753150.10866@kiku.itsise \
--to=madis@ats.cyber.ee \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--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