Re: Athlon64 + Nforce4 MCE panic

[Rumi Szabolcs]

On Fri, 14 Jul 2006 11:18:38 -0700
"Allen Martin" <AMartin@xxxxxxxxxx> wrote:

> > 1x Asrock NF4G-SATA2 motherboard 
> > (http://www.asrock.com/product/939NF4G-SATA2.htm)
> > 1x Athlon64 "Venice" 3500+ with a huge Arctic cooler
> > 1x Corsair kit of 2 matched 512MB DDR400 modules
> > 1x Seagate 160GB SATA drive
> > 1x well ventilated Chieftec rackmount chassis w/PSU
> 
> You don't have any PATA devices at all?  SATA is a lot more resilient to
> this type of problem.

Exactly. I hooked up a PATA CDROM temporarily when I changed the mobo,
but otherwise the only storage it has is that SATA disk.

> > So I have a reason to believe that this could be a chipset specific
> > problem which not only affects me but quite a number of NF4 users,
> > most of which (using Windo$$$) will probably never know why their
> > system suddenly hung after some weeks or months of use...
> 
> Windows will generate a bugcheck on an MCA exception just like Linux.
> We have really detailed statistics on Windows bugchecks due to OCA, so I
> know this is not a widespread issue at least on Windows.

Do you think that this problem is caused by or at least triggered by
Linux or it's disk usage patterns? At least if you type "b200000000070f0f"
into g00gle you get a lot of hits all of which has something to do with
Linux.

> The stack trace will almost always tell you exactly what device timed
> out the PIO, you should start there.

Well I have to admit I'm not a kernel hacker but a simple user without a clue
so I have no idea how I could have got a stack trace from a kernel that is
paniced, frozen hard, and couldn't even sync it's disks so after I realized
there is no reaction to any input devices on the system I've just hit the
reset button and hoped it will come up again. I guess this is exactly what
Windo$$$ users used to do when they get a blue screen... ;)

Thanks!

Regards,

Sab
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/