@ Bryan -
1. This is an issue with Avago Driver. Driver code snippet -
instance->max_sectors_per_req = instance->max_num_sge *
PAGE_SIZE / 512;
if (tmp_sectors && (instance->max_sectors_per_req > tmp_sectors))
instance->max_sectors_per_req = tmp_sectors;
Current Driver count max_sectors based on PAGE_SIZE. This is wrong. We
will fix and send patch to upstream.
On OPAL setup, PAGE_SIZE is 64K, so we will send max_sectors to OS = 8192. This
is higher than FW expect. FW is just 1M capable.
Now kernel has some check at block layer to pick min of two values. One Driver
provided and other BLK defaults.
Ubuntu 14.x kernel might be bringing down value of max_hw_sectors_kb to
1024, but 15.4 kernel keep max_hw_sectors_kb to 4096.
Driver fix is required and root cause is PAGE_SIZE is more than 4K.
Driver will break the moment PAGE_SIZE is more than 4K w.r.t max_sectors
value.
Using max_sectors module parameter of driver, you can reduce the value
but can not increase that value. It can solve this problem. So if
you/customer is looking for quick resolution use max_sectors module
parameter of megasraid_sas driver.
Add below entry in grub
megaraid_sas.max_sectors=512
Thanks, Kashyap
--
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
