@kashyap-desai thanks for that, it could be a simple firmware reporting issue
or the kernel code needs to be updated to handle a new case.
megaraid_sas_base.c [1] mentions that it generates the max_sectors limits from
data provided from the firmware.
4096 is defined in a few other places within the driver [2] so I'm guessing
other megaraids do support 4096?
Testing on non-powerpc would still be useful as would reverting to a
released firmware to see if max_sectors changes or the error changes.
[1] /*
* Compute the max allowed sectors per IO: The controller info has two
* limits on max sectors. Driver should use the minimum of these two.
*
* 1 << stripe_sz_ops.min = max sectors per strip
*
* Note that older firmwares ( < FW ver 30) didn't report information
* to calculate max_sectors_1. So the number ended up as zero always.
*/
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/megaraid/megaraid_sas_base.c
[2]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/megaraid.h
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1475166
Title:
Ubuntu 15.04 Install Error with Avago Controller
Status in linux package in Ubuntu:
Triaged
Bug description:
Hello Canonical Team
We are running to an issue installing ubuntu PPC64LE 15.04 full blown
image on our servers (with RAID controller). Installation hangs
around 70% of progress.
An important part of our configuration is Avago RAID controller:
9361-8i Firmware version we used is 4.300.00-4429, and the package is
24.10.0-0002.
IMPORTANT: It has to be noted that with same hardware configuration
14.10 full blown image installs fine.
Dmesg logs are attached:
Looking at dmesg logs point out that:
LSI (avago) driver loads fine
During further interaction with raid volume during the installation process,
firmware errors are seen
[ 196.991417] megasas: FW status 0x3
[ 196.999376] megasas: FW status 0x3
[ 197.007376] megasas: FW status 0x3
Further down the process I/O errors are thrown
[ 217.438664] Buffer I/O error on device sda2, logical block 22052864
[ 217.438671] Buffer I/O error on device sda2, logical block 22052865
[ 217.438678] Buffer I/O error on device sda2, logical block 22052866
[ 217.438686] Buffer I/O error on device sda2, logical block 22052867
Full dmesg log is attached. Snippet is pasted below highlighting:
It can be noted that there’s a Mellanox Connectx 3 pro card with some test
Firmware on our setup.
We can Ignore any diagnostic messages from that card in dmesg logs for the
purpose of this bug.
Thanks
Adi Gangidi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475166/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
