linux-kernel - CPU 3: Machine Check Exception: 0000000000000004

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sun, 22 Apr 2007 12:50:16 -0700 (PDT)
From:	"Mr. James W. Laferriere" <babydr@...y-dragons.com>
To:	Linux Kernel Maillist <linux-kernel@...r.kernel.org>
Subject: CPU 3: Machine Check Exception: 0000000000000004


 	Hello All ,  Has anyone else had an occurance of this hard lockup .
 	last time it was the scsi bus that was the last item on the console this 
time it's  CPU #3 ...
 	Everytime I try & run a bonnie on this system something locks the system 
up hard .  I do not trust this system at this time & need to put it into 
production soon .
 	Anybody any pointers    where to look , ... ?

Kernel: Linux 2.6.21-rc7 ,  unpatched .

<<<previous>>>
  root@...esrv1b:~ # CPU 3: Machine Check Exception: 0000000000000004
Kernel panic - not syncing: Unable to continue
Kernel panic - not syncing: Unable to continue

      +-A-+[ sc933s2 jbod chassis ] With 7-FUJITSU-MAP3147NC
      |
      +-B-+[ sc933s2 jbod chassis ] With 7-FUJITSU-MAP3147NC
      |
      + lsi22320 in pci-64-133 slot
[ system ] a SuperServer 6035B-8R
      + aic7902 on board
      |
      +-A-+[ internally ] With 2-Compaq/Seagate-18GB-u320 & 2-FUJITSU-MAP3147NC
      |
      +-B-+[ internally ] With 4-FUJITSU-MAP3147NC

 	lsi22320 is attached to the sc933s2 on channels A & B ,
 	cable lengths are ~ 4 feet on both channels .

 	aic7902 is attached internally thru 'system' ,  a SuperServer 6035B-8R .


  root@(none):~ # ( time bonnie++-1.03a/bonnie++ -u0:0 -d /home -s 524288 ) 2>&1
  | tee 512GB-bonnie++-run-ext3-200704181557.log
Using uid:0, gid:0.
Writing with putc()...mptscsih: ioc0: attempting task abort! (sc=d0795800)
sd 4:0:3:0:
         command: <4>mptscsih: ioc1: attempting task abort! (sc=d8c28500)
sd 5:0:1:0:
         command: Read(10): 28 00 00 1d d1 b9 00 00 08 00
Read(10): 28 00 00 1e 12 b9 00 00 08 00
mptscsih: ioc1: WARNING - TM Handler for type=1: IOC Not operational (0xffffffff)!
sd 1:0:3:0: Attempting to queue an A
<System Hung hard>

<<<\previous>>>



You can get the previous log here .
http://www.baby-dragons.com/new-sc933s2-coming-online-to-linux-scsi.log

 	Any help is greatly appreciated .
 		JimL

-- 
+-----------------------------------------------------------------+
| James   W.   Laferriere | System   Techniques | Give me VMS     |
| Network        Engineer | 663  Beaumont  Blvd |  Give me Linux  |
| babydr@...y-dragons.com | Pacifica, CA. 94044 |   only  on  AXP |
+-----------------------------------------------------------------+
-
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/