Date: Wed, 27 Feb 2002 11:22:43 -0500 From: "Yuri Victorovich" <yvictorovich@optima-hyper.com> To: "'Andrew Gallatin'" <gallatin@cs.duke.edu> Cc: <alpha@FreeBSD.ORG> Subject: RE: "unexpected machine check" on AS1000A Message-ID: <E052D8D86575D511A0E1009027D3B86215088C@hqsmail.SNET> In-Reply-To: <E052D8D86575D511A0E1009027D3B86218B4FB@hqsmail.SNET>
next in thread | previous in thread | raw e-mail | index | archive | help
BTW I kinda found the workaround. Limited available memory with MAXMEM. Now I hope it became rocksolid. Playing with MAXMEM and SIMMs rotation will find and isolate bad SIMM when will have time. Yuri. -----Original Message----- From: Andrew Gallatin [mailto:gallatin@cs.duke.edu] Sent: Tuesday, February 26, 2002 16:29 To: Victorovich, Yuri Cc: alpha@FreeBSD.ORG Subject: RE: "unexpected machine check" on AS1000A Yuri Victorovich writes: > Nope, seems that reseating, cleaning, rotating SIMMs doesn't help. > Is it a way to find which SIMM exactly causes the problem? By those > values that it loggs on "unexpected machine check" crash? > Yes & we could also log more information for the correctable errors too. However, doing this requires having sufficient documentation, which I don't think we do. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E052D8D86575D511A0E1009027D3B86215088C>