Re: Linux kernel panic after installing TSM 5.2.2

Hello. I have a Linux 2.4.9-e27 (no SMP) with TSM 5.2.2 Server, but with an
IBM 3582 LTO library, two LTO2 drives. I see no problems in the
/var/log/IBMtrace.log file. All appears to be working fine here.

Charlie H
charlieh AT tecsys DOT com

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
John Schneider
Sent: Wednesday, January 28, 2004 3:48 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Linux kernel panic after installing TSM 5.2.2


Greetings,
    My thanks to this list for all their support over the years.
    We just migrated our TSM server from AIX to a RedHat Linux server.
It is Enterprise kernel 2.4.9-e27smp, and TSM 5.2.2.  Our tape library
is an Ultrium 3583 with the latest microcode (updated just last week) on
both the library and the drives.  We are running the IBMtape driver
IBMtape-1.4.2-0, also the latest.
    The Linux server has experienced a kernel panic or hang condition
about once a day.  Here is a typical portion of the log:

Jan 27 22:53:30 navy kernel: IBMtape1---17432 IBMTapeCheckResult()
SenseKey: 2 ASC: 4 ASCQ: 1
Jan 27 22:53:36 navy last message repeated 2 times
Jan 27 22:53:44 navy kernel: IBMtape1---17432 IBMTapeCheckResult()
SenseKey: 6 ASC: 28 ASCQ: 0
Jan 27 22:54:02 navy kernel: Unable to handle kernel NULL pointer
dereference at virtual address 0000002c
Jan 27 22:54:02 navy kernel:  printing eip:
Jan 27 22:54:02 navy kernel: c0107147
Jan 27 22:54:02 navy kernel: *pde = 00000000
Jan 27 22:54:02 navy kernel: Oops: 0000
Jan 27 22:54:02 navy kernel: Kernel 2.4.9-e.27smp
Jan 27 22:54:02 navy kernel: CPU:    1

The log stops at this point until the next morning when the system is
reset.  I could send out more of the log to show what has been going on
earlier in the evening, but I didn't want to burden the list with a big log.
These log messages out of IBMtape are a fairly frequent occurance in the
log, in fact, we seem to get a lot of IBMtape.  Here is another stretch
of the log:

Jan 28 09:06:28 navy kernel: IBMtape1---17432 IBMTapeCheckResult()
SenseKey: 2 ASC: 3a ASCQ: 0
Jan 28 09:06:28 navy kernel: IBMtape1---17432 IBMTapeCheckResult()
SenseKey: 2 ASC: 3a ASCQ: 0
Jan 28 09:06:29 navy kernel: IBMChgr0---02441 IBMChangerCheckResult()
SenseKey: 5 ASC: 24 ASCQ: 0
Jan 28 09:06:34 navy last message repeated 2 times
Jan 28 09:07:14 navy kernel: IBMtape0---36477 IBMTapeCheckResult()
SenseKey: 2 ASC: 3a ASCQ: 0
Jan 28 09:07:14 navy kernel: IBMtape0---36477 IBMTapeCheckResult()
SenseKey: 2 ASC: 3a ASCQ: 0
Jan 28 09:07:15 navy kernel: IBMChgr0---02441 IBMChangerCheckResult()
SenseKey: 5 ASC: 24 ASCQ: 0
Jan 28 09:07:19 navy kernel: IBMChgr0---02441 IBMChangerCheckResult()
SenseKey: 5 ASC: 24 ASCQ: 0
Jan 28 09:07:31 navy kernel: IBMtape0---36477 IBMTapeCheckResult()
SenseKey: 2 ASC: 4 ASCQ: 1
Jan 28 09:07:39 navy last message repeated 2 times
Jan 28 09:07:47 navy kernel: IBMtape0---36477 IBMTapeCheckResult()
SenseKey: 6 ASC: 28 ASCQ: 0
Jan 28 10:39:10 navy kernel: IBMChgr0---02441 IBMChangerCheckResult()
SenseKey: 5 ASC: 24 ASCQ: 0

Here we got logs of IBMtape messages, both from the tape devices, and
also from the changer, but no panic or hang.

Anyone seen a similar situation?

Thanks in advance,
John Schneider

***********************************************************************
* John D. Schneider   Email: jdschn AT attglobal DOT net * Phone: 636-492-0247
* Lowery Systems, Inc.
* 1329 Horan                  Disclaimer: Opinions expressed here are
* Fenton, MO 63026                   mine and mine alone.
***********************************************************************