Decoding mptscsih errors
Patrick_Boyd at Dell.com
Patrick_Boyd at Dell.com
Wed Oct 11 09:32:59 CDT 2006
So there isn't a kernel panic or anything else associated with this
problem?
-----Original Message-----
From: Ricardo (Tru64 User) [mailto:tru64user at yahoo.com]
Sent: Tuesday, October 10, 2006 6:45 PM
To: Boyd, Patrick; linux-poweredge-Lists
Subject: RE: Decoding mptscsih errors
When the system locks up, its just that...a complete, hard lockup. No
errors, no clues left behind. If NUMLOCK was on, it stays
lit.....keyboard has no effect anymore....only poweroff is the solution
(hold 5secs or so).
One time i was running Memtest Dell utility, and it got to some
percentage on one of the tests, and simply locked up. Everything remains
on screen...and the counters ofcourse stop.
Its very random, it occurs when system is busy or when completely idle.
Mmmhhh....so that is the backplane.
_thanks
--- Patrick_Boyd at Dell.com wrote:
> No ID 6 is the backplane. By default all Dell backplanes or enclosures
> use target 6 unless the enclosure is in cluster mode and then it will
> use target 15.
>
> Can you tell us what the system is doing when the lockup occurs?
>
> Patrick Boyd
> Dell Storage Software Engineer
> (512)728-3182
>
>
> -----Original Message-----
> From: linux-poweredge-bounces at dell.com
> [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Ricardo (Tru64
> User)
> Sent: Tuesday, October 10, 2006 3:02 PM
> To: linux-poweredge-Lists
> Subject: Decoding mptscsih errors
>
> Hi,
>
>
> Errors (posted at the bottom) seem to only occur during boot. Node is
> experiencing intermittent lockups...so i am trying to follow every
> lead.
> Motherboard has been replaced 2 days ago by Dell....lockups after a
> day or so still occuring. Dell diagnostics (from
> EW5076A0) and MPMemory come
> out clean.
>
> Here are all the devices.
> scsi2 is the where the root device is...where id 0, lun 0 is the root
> disk, and id 6, lun 0 is the controller?
> The failure is in the controller(?),id 6! Trying to understand it.....
>
> # cat /proc/scsi
> Attached devices:
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
> Vendor: IFT Model: A16U-G2421-1 Rev: 347G
> Type: Direct-Access ANSI SCSI
> revision: 03
> Host: scsi0 Channel: 00 Id: 00 Lun: 01
> Vendor: IFT Model: A16U-G2421-1 Rev: 347G
> Type: Direct-Access ANSI SCSI
> revision: 03
> Host: scsi0 Channel: 00 Id: 00 Lun: 02
> Vendor: IFT Model: A16U-G2421-1 Rev: 347G
> Type: Direct-Access ANSI SCSI
> revision: 03
> Host: scsi0 Channel: 00 Id: 00 Lun: 03
> Vendor: IFT Model: A16U-G2421-1 Rev: 347G
> Type: Direct-Access ANSI SCSI
> revision: 03
> Host: scsi0 Channel: 00 Id: 00 Lun: 04
> Vendor: IFT Model: A16U-G2421-1 Rev: 347G
> Type: Direct-Access ANSI SCSI
> revision: 03
> Host: scsi2 Channel: 00 Id: 00 Lun: 00
> Vendor: FUJITSU Model: MAP3147NC Rev: 5608
> Type: Direct-Access ANSI SCSI
> revision: 03
> Host: scsi2 Channel: 00 Id: 06 Lun: 00
> Vendor: PE/PV Model: 1x3 SCSI BP Rev: 1.1
> Type: Processor ANSI SCSI
> revision: 02
> Host: scsi3 Channel: 00 Id: 02 Lun: 00
> Vendor: Promise Model: 7 Disk RAID5 Rev: V0.0
> Type: Direct-Access ANSI SCSI
> revision: 04
> Host: scsi3 Channel: 00 Id: 02 Lun: 01
> Vendor: Promise Model: 7 Disk RAID5 Rev: V0.0
> Type: Direct-Access ANSI SCSI
> revision: 04
>
>
> Error::
> Oct 8 14:07:11 genesis kernel: mptscsih: ioc2:
> attempting task abort!
> (sc=f25f8080)
> Oct 8 14:07:11 genesis kernel: scsi2 : destination target 6, lun 0
> Oct 8 14:07:11 genesis kernel: command:
> Request Sense: 03 00 00
> 00 fc 00
> Oct 8 14:07:11 genesis kernel: mptscsih: ioc2: task
> abort: SUCCESS
> (sc=f25f8080)
> Oct 8 14:07:11 genesis kernel: mptscsih: ioc2:
> attempting target reset!
> (sc=f25f8080)
> Oct 8 14:07:11 genesis kernel: scsi2 : destination target 6, lun 0
> Oct 8 14:07:11 genesis kernel: command:
> Inquiry: 12 00 00 00 32 00
> Oct 8 14:07:15 genesis kernel: mptbase: ioc2:
> IOCStatus(0x004b): SCSI IOC
> Terminated
> Oct 8 14:07:15 genesis kernel: mptbase: ioc2:
> IOCStatus(0x004a): SCSI
> Task Management Failed
> Oct 8 14:07:15 genesis kernel: mptscsih: ioc2:
> target
> reset: SUCCESS
> (sc=f25f8080)
> Oct 8 14:07:25 genesis kernel: mptscsih: ioc2:
> attempting task abort!
> (sc=f25f8080)
> Oct 8 14:07:25 genesis kernel: scsi2 : destination target 6, lun 0
> Oct 8 14:07:25 genesis kernel: command:
> Test
> Unit Ready: 00 00 00
> 00 00 00
> Oct 8 14:07:27 genesis kernel: mptbase: Initiating
> ioc2 recovery
> Oct 8 14:07:32 genesis kernel: mptscsih: ioc2: task
> abort: SUCCESS
> (sc=f25f8080)
> Oct 8 14:07:32 genesis kernel: mptscsih: ioc2:
> attempting bus reset!
> (sc=f25f8080)
> Oct 8 14:07:32 genesis kernel: scsi2 : destination target 6, lun 0
> Oct 8 14:07:32 genesis kernel: command:
> Inquiry: 12 00 00 00 32 00
> Oct 8 14:07:33 genesis kernel: mptscsih: ioc2: bus
> reset: SUCCESS
> (sc=f25f8080)
>
> _Thanks
>
> Richard
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
>
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
More information about the Linux-PowerEdge
mailing list