linux-kernel - Re: raid5:md3: read error corrected , followed by , Machine Check Exception: .

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 14 Jul 2007 20:11:04 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	"Mr. James W. Laferriere" <babydr@...y-dragons.com>
cc:	linux-raid maillist <linux-raid@...r.kernel.org>,
	Linux Kernel Maillist <linux-kernel@...r.kernel.org>
Subject: Re: raid5:md3: read error corrected ,  followed by ,  Machine Check
 Exception: .



On Sat, 14 Jul 2007, Mr. James W. Laferriere wrote:

> 	Hello All ,  I was under the impression that a 'machine check' would 
> be caused by some near to the CPU hardware failure ,  Not a bad disk ?
> 	I was also under the impression that software raid s/b a little more 
> resilient than this .
> 	But then maybe one or the other of the subsystems walked all over the 
> other one trying to correct itself .  Who knows .
> 	The below is ALL I'll be able to get .  A log of a previous boot is 
> available at ...
>
> http://www.baby-dragons.com/test-2.6.21.5-mptscsi-4.00.10.00-2007006161326.log

Looks like /dev/sdd is on its way out, repace the drive?  I'm not sure
however why you'd get those MCEs at the end unless you really have bad
CPUs or memory in the system?

Justin.


-
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/