Hi,
3.13.04.00 is very old version. Can you go for version 3.18.00.00-1 driver version ?
Sure, where can I find it? I could not find it at
http://www.lsi.com/storage_home/products_home/standard_product_ics/sas_ics/lsisas1064e/index.html?locale=EN&remote=1
and google did not help.
To enable debug you have to follow these steps.
1. ./makempt (Is this file present for you ? If not then I can send you.)
2. ./update
3. mkinitrd
1. is present so I executed it.
Have a look at this verbose output.
mkinitrd -v -f /boot/initrd-2.6.9-78.0.13.ELlargesmp.img
2.6.9-78.0.13.ELlargesmp
Creating initramfs
Looking for deps of module scsi_mod
Looking for deps of module sd_mod scsi_mod
Looking for deps of module scsi_mod
Looking for deps of module unknown
Looking for deps of module ehci-hcd
Looking for deps of module ohci-hcd
Looking for deps of module uhci-hcd
Looking for deps of module usb-storage scsi_mod
Looking for deps of module scsi_mod
Looking for deps of module ahci libata scsi_mod
Looking for deps of module libata scsi_mod
Looking for deps of module scsi_mod
Looking for deps of module scsi_mod
Looking for deps of module mptsas mptscsi mptbase scsi_mod
Looking for deps of module mptscsi mptbase scsi_mod
Looking for deps of module mptbase
Looking for deps of module scsi_mod
No module mptscsi found for kernel 2.6.9-78.0.13.ELlargesmp, aborting.
Again I copied the files from another node.
Lots of debug information now on boot but debug_level is not there
(probably due to the driver version)
Cheers,
cat /proc/mpt/version
mptlinux-3.13.04.00
Fusion MPT base driver
Fusion MPT SAS host driver
Fusion MPT SPI host driver
Fusion MPT ioctl driver
but still no debug_level
However I did some tricks to get the driver load so I am not sure I did
not mess up.
a) the included binaries are up to 2.6.9-78 kernel so I used the sources
tarball prvided.
b) Executed "compile"
c) Executed "update"
d) c) had problems finding mptscsi.ko which was removed by the process.
e) copied the missing files from another node
f) ran mkinitrd manually
g) rebooted, some complains on dmesg about beeing unable to load mptscsi,
other than that server booted fine.
Preliminary test with the new driver resulted in no errors, but that's not
the same as a real world case. Still the debug_level is not there. Do I
need another driver?
Cheers,
--
=============================================================================
Dimitris Zilaskos
GridAUTH Operations Centre @ Aristotle University of Thessaloniki , Greece
Tel: +302310998988 Fax: +302310994309
http://www.grid.auth.gr
=============================================================================
On Mon, 23 Mar 2009, Desai, Kashyap wrote:
Hi,
After firmware upgrade, you are seeing only MPT logs but system is running fine. Those prints are not harmful, but it requires attention why it happened? I need some information to help you further.
1. Information of driver version. (cat /proc/mpt/version)
2. Information of firmware. (cat /proc/mpt/iocX/info)
3. Driver log level setting.
MPT driver has debug_level settings to get more logs.
Check "cat /sys/class/scsi_host/host*/proc_name"
Use index number for "mptsas" from result of previous command.
"echo 0x8188 > /sys/class/scsi_host/host<index>/debug_level".
NOTE: Above debug level settings are available from some version onwards.
Driver used by you may not have this support, depending upon driver version.
Please provide us log with driver debug enable as mention in #3 will help to debug further.
Added Sisir and Sathya in CC list.
Thanks
Kashyap
-----Original Message-----
From: linux-scsi-owner@xxxxxxxxxxxxxxx [mailto:linux-scsi-owner@xxxxxxxxxxxxxxx] On Behalf Of Dimitris Zilaskos
Sent: Saturday, March 21, 2009 1:41 AM
To: James Bottomley
Cc: linux-scsi@xxxxxxxxxxxxxxx; Moore, Eric
Subject: Re: kernel panics and errors on lsi 1064e
Thank you for you reply,
So that's the right thing to do (or better yet, contact LSI support to
see if they have a newer version).
Will do so
This has become a log information, so the IOC firmware now dealt with
whatever the problem was.
Is something broken here? I am close to ask for the systems to be replaced.
You imply that with the firmware upgrade, nothing now goes wrong, so
everything sounds to be OK.
Well it has been only 3 days, and these strange messages keep showing up,
so I am still worried because it will be harder to get them replaced later
and at the same time have the users complaining. But it looks like my
options are limited.
--
=============================================================================
Dimitris Zilaskos
GridAUTH Operations Centre @ Aristotle University of Thessaloniki , Greece
Tel: +302310998988 Fax: +302310994309
http://www.grid.auth.gr
=============================================================================
--
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
Internal Virus Database is out of date.
Checked by AVG - www.avg.com
Version: 8.0.237 / Virus Database: 270.11.10/1995 - Release Date: 03/11/09 08:28:00
--
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
--
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
