> 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.
> 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.
> Or maybe just a neutrino hit to the CPU?
> What do you think?
The stack trace will almost always tell you exactly what device timed
out the PIO, you should start there.
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
