Hi,
I checked var/log/messages
These are the errors reported:
=======================================================
kernel: mptbase: ioc0: IOCStatus(0x0003): Invalid SGL
kernel: mptbase: ioc0: LogInfo(0x11070000): F/W: DMA Error
kernel: mptbase: ioc0: LogInfo(0x11070000): F/W: DMA Error
kernel: mptbase: ioc0: IOCStatus(0x004b): SCSI IOC Terminated
kernel: st0: Error with sense data: Current st0: sense key Unit Attention
kernel: Additional sense: Scsi bus reset occurred
=========================================================
Thanks
On 7/28/09, rohan a <info1686@xxxxxxxxx> wrote:
> Hi all/Hannes,
>
> Any help/suggestions?
>
>
> On Wed, Jul 22, 2009 at 6:56 PM, rohan a<info1686@xxxxxxxxx> wrote:
> > Hi,
> > Thanks for a reply.
> > I have 2 SLES 9 32-bit machines, on one I am using an FC HBA card and
> > another a SCSI HBA card to connect LTO-4 standalone drives and drive
> > based encryption is not working in both cases.
> >
> > Thanks
> >
> > On Mon, Jul 20, 2009 at 5:45 PM, Hannes Reinecke<hare@xxxxxxx> wrote:
> >> James Bottomley wrote:
> >>> On Wed, 2009-07-15 at 20:33 +0530, rohan a wrote:
> >>>> Hi guys,
> >>>>
> >>>> Any suggestions...please help
> >>>
> >>> I know of no kernel bug that could be causing this. The SLES9 kernel is
> >>> just too old though for me to remember clearly. I'd suggest you file a
> >>> support incident with SUSE ... they'll debug and fix this on the older
> >>> kernels; we really only deal with the new kernel and one or two back
> >>> revisions here on linux-scsi.
> >>>
> >> You did that on purpose.
> >> The 'they' is actually me :-(
> >>
> >> Actually, there already _is_ a bug, so no need to open another one.
> >> Which HBA are you using?
> >>
> >> Cheers,
> >>
> >> Hannes
> >> --
> >> Dr. Hannes Reinecke zSeries & Storage
> >> hare@xxxxxxx +49 911 74053 688
> >> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
> >> GF: Markus Rex, HRB 16746 (AG Nürnberg)
> >>
> >
>
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
