netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yan Seiner" <yan@seiner.com>
To: "John Stoffel" <john@stoffel.org>
Cc: "Gene Heskett" <gene.heskett@verizon.net>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	aabdulla@nvidia.com
Subject: Re: mcp55 forcedeth woes
Date: Tue, 14 Apr 2009 09:47:59 -0700 (PDT)	[thread overview]
Message-ID: <acfb5c7f894e2376902adb7d9d5512f6.squirrel@www.datavault.us> (raw)
In-Reply-To: <18916.47906.73896.346385@stoffel.org>


On Tue, April 14, 2009 9:34 am, John Stoffel wrote:
>
> I've also got one of these boards, but I seem to recall that 2.6.28
> and higher worked just fine, but when I was chasing another problem
> with complete system crashes when running tcpdump, I found the dead
> port problem as well.

Yeah, this one surfaced after I had a memory stick go bad and lock up the
machine several times.

>
> Thanks for posting your workaround, they'll be a big help.  Esp if I
> put them in early to the system boot process as a quick hack.
>
> The M2N-SLI Deluxe boards are nice though, stable stable stable.  I've
> been very happy with mine.  I wonder if there's a newer BIOS which
> might address some of these issues as well, since it seems to me that
> the BIOS, esp on power up, should be reseting the ports to something
> more sane.

There is a newer bios, 1702, that may address these issues - at least teh
writeup for the 17xx bios for the m2n32 talks about a network lockup fix. 
I haven't tried yet.  These are the most stable boards I've found; one of
mine runs 6 SATA drives locally, 9 via eSATA, 2 dual DVI video cards, and
2 15K scsi drives, all without a hitch.  It never glitches - except for
the d*mn network, this board is a piece of perfection.

-- 
Yan Seiner, PE

Support my bid for the 4J School Board
http://www.seiner.com


  reply	other threads:[~2009-04-14 16:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e3e0f4f0ca9fdce35c24b30559d10f31.squirrel@www.datavault.us>
2009-04-13 23:45 ` mcp55 forcedeth woes Andrew Morton
2009-04-15 13:54   ` Yan Seiner
     [not found] ` <200904132100.58056.gene.heskett@verizon.net>
     [not found]   ` <49E3EF9F.6090600@seiner.com>
     [not found]     ` <200904132224.13716.gene.heskett@verizon.net>
2009-04-14 14:35       ` Yan Seiner
2009-04-14 16:34         ` John Stoffel
2009-04-14 16:47           ` Yan Seiner [this message]
2009-04-14 18:27           ` Gene Heskett

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=acfb5c7f894e2376902adb7d9d5512f6.squirrel@www.datavault.us \
    --to=yan@seiner.com \
    --cc=aabdulla@nvidia.com \
    --cc=gene.heskett@verizon.net \
    --cc=john@stoffel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).