All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Karchebny <berk@upnet.ru>
To: netdev@oss.sgi.com
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Subject: forcedeth 0.20 eth0: received interrupt report
Date: Sun, 11 Jan 2004 21:33:54 +0500	[thread overview]
Message-ID: <200401112134.05375.berk@upnet.ru> (raw)

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

"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

Feel free to contact me if you need any additional information/debug 
runs/testing help.

-- 
keep in touch. berkus.

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-01-11 16:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11 16:33 Stanislav Karchebny [this message]
2004-01-11 23:04 ` forcedeth 0.20 eth0: received interrupt report Carl-Daniel Hailfinger

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=200401112134.05375.berk@upnet.ru \
    --to=berk@upnet.ru \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.