public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: James Courtier-Dutton <James@superbug.co.uk>,
	Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: Re: Asus K8N-VM Motherboard Ethernet Problem
Date: Wed, 31 May 2006 17:35:37 -0400	[thread overview]
Message-ID: <447E0C29.1030404@tmr.com> (raw)
In-Reply-To: <447B3408.1020001@superbug.co.uk>

James Courtier-Dutton wrote:

> I can concur that the forcedeth is unreliable on nvidia based motherboards.
> I have a ethernet device that works with forcedeth.
> 0000:00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
> 0000:00:0a.0 0680: 10de:0057 (rev a3)
>         Subsystem: 147b:1c12
>         Flags: 66MHz, fast devsel, IRQ 11
>         Memory at fe02f000 (32-bit, non-prefetchable) [size=4K]
>         I/O ports at fc00 [size=8]
>         Capabilities: [44] Power Management version 2
> 
> It works in that it can actually send and receive packets.
> The problems are:
> 1) one cannot rmmod the forcedeth module. Even after ifdown etc.
> 2) the machine hangs randomly.
> Before someone asks, the MB has no serial port, so no stack trace available.
> 3) The netconsole fails to function with it.
> 
> I have installed a standard PCI based intel ethernet card, and only use
> that. Without the forcedeth loaded, no hangs since.
> 
> So, although I can confirm that there are certainly problems with the
> forcedeth driver, without a serial port, I am at a loss at how I might
> help diagnose the problem and fix it.

Watchdog timer? Compile with the appropriate timer(s) and set it with 
wdog or similar. Of course it may not be "hung enough" but it's worth a 
try, I would think.
> 
> The only help this email is, is to confirm that if someone is raising
> problems with the forcedeth driver, it is most likely to be a truthful
> report and if they also have a serial port, they might even be able to
> give some good diagnosis output.

-- 
Bill Davidsen <davidsen@tmr.com>
   Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.


  parent reply	other threads:[~2006-05-31 21:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-28  5:11 Asus K8N-VM Motherboard Ethernet Problem Marc Perkel
2006-05-28  6:07 ` Marc Perkel
2006-05-28 10:18   ` Jan-Benedict Glaw
2006-05-29 17:48     ` James Courtier-Dutton
2006-05-29 17:54       ` Alistair John Strachan
2006-05-29 22:03       ` [BUG 6480]Re: " Ingo Oeser
2006-05-31 21:35       ` Bill Davidsen [this message]
2006-07-08 10:30       ` James Courtier-Dutton
2006-05-28 17:54 ` Alistair John Strachan
2006-05-28 18:20   ` Alistair John Strachan
2006-05-29 14:14     ` Lennart Sorensen
2006-05-29 16:46       ` Alistair John Strachan
2006-05-29 17:26         ` Lennart Sorensen
2006-05-29 22:19 ` Eyal Lebedinsky
2006-05-30 15:56 ` Mike Dresser
2006-05-30 16:03   ` Mike Dresser

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=447E0C29.1030404@tmr.com \
    --to=davidsen@tmr.com \
    --cc=James@superbug.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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