From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Stanislav Karchebny <berk@upnet.ru>
Cc: netdev@oss.sgi.com
Subject: Re: forcedeth 0.20 eth0: received interrupt report
Date: Mon, 12 Jan 2004 00:04:17 +0100 [thread overview]
Message-ID: <4001D671.6030008@gmx.net> (raw)
In-Reply-To: <200401112134.05375.berk@upnet.ru>
Stanislav Karchebny wrote:
> "eth0: received irq with unknown events 0x21. Please report"
>
> This happens when i enable software CPU cooling on nForce2 chipset using
> FVcool - this causes all nforce-net connections to fail miserably and these
> events are generated in dmesg log.
>
> The very moment i disable softcooling using fvcool -d the network resumes
> normal operations.
>
> Linux Kernel 2.6.0 final
> forcedeth 0.20
> ASUS A7N8X Deluxe mobo
Great! You're the first one finding out why this unknown event 0x01
happens. (0x20 is timer event)
Since another user saw the same message but wasn't able to get the network
running at all, I was stuck. Enabling normal receive doesn't help to get
rid of the error.
I know that nvnet is proprietary software and also not that stable
according to user reports, but could you perhaps try nvnet instead of
forcedeth?
If nvnet still works when you enable softcooling, I can try to add a
workaround to forcedeth so that it works, too.
If nvnet fails, I still can try a few tricks but I'd have to know more
than the nvnet driver writers about the nforce chipset and they are inside
nvidia and I don't even have any docs.
Thanks for your coperation,
Carl-Daniel
prev parent reply other threads:[~2004-01-11 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 16:33 forcedeth 0.20 eth0: received interrupt report Stanislav Karchebny
2004-01-11 23:04 ` Carl-Daniel Hailfinger [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=4001D671.6030008@gmx.net \
--to=c-d.hailfinger.kernel.2003@gmx.net \
--cc=berk@upnet.ru \
--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).