[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <acfb5c7f894e2376902adb7d9d5512f6.squirrel@www.datavault.us>
Date: Tue, 14 Apr 2009 09:47:59 -0700 (PDT)
From: "Yan Seiner" <yan@...ner.com>
To: "John Stoffel" <john@...ffel.org>
Cc: "Gene Heskett" <gene.heskett@...izon.net>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
aabdulla@...dia.com
Subject: Re: mcp55 forcedeth woes
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists