Messages in this thread | | | Date | Fri, 15 Aug 2003 21:06:01 +0200 | From | Clock <> | Subject | Re: nforce2 lockups |
| |
On Fri, Aug 15, 2003 at 05:38:08PM +0100, Alistair J Strachan wrote: > On Friday 15 August 2003 16:15, Clock wrote: > > On Fri, Aug 15, 2003 at 09:12:17PM +0900, kenton.groombridge@us.army.mil > wrote: > > > Hi, > > > > > > I found your post looking for a solution to my lockups. I bet if you do > > > a dmesg, you will find that your nforce2 chipset revision is 162. > > > > Yeah! Look: > > > > NFORCE2: chipset revision 162 > > [alistair] 05:37 PM [~] dmesg | grep "NFORCE2: chipset" > NFORCE2: chipset revision 162 > > A quick google for "NFORCE2: chipset revision" reveals no chipset revision > dmesg except 162. It seems likely most manufactures are using the same > revision. > > I use APIC and ACPI on my EPoX 8RDA+, and I've never had any IO problems. So > it seems unlikely that it is tied to a chipset revision.
I have had three boards with nforce2 replaced (all of them Soltek SL75FRN2-L) and all three did the same. However it seemed the frequency of the crashes varies with actual piece of board.
The crashes aren't in software - bare 'cat /dev/hda > /dev/null' is often to lock up the machine to the point that poweroff fails.
Cl< - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |