kernel-packages team mailing list archive

[Bryan Quigley <bryan.quigley@xxxxxxxxxxxxx>]

1)  I would at least try booting multiple times.
If possible I would try partitioning so you have extra space and can set up a new ext4 partition on the Controller for every test.  Then deleting before running the next one.

In fact, I'd recommend for the next test to install 15.04 on a SATA
drive in the system and see if you can reproduce with the controller
just doing the above.  Try reproducing it at least 3 times to be sure it
freezes every time.

Then if you do another Git Kernel build (v3.19) it will use 15.04s
config by default (as well as the new compiler).  This would help rule
out it being an Ubuntu specific patch (or prove that it is).   Please do
post the 14.10 config from your GitKernelBuild so we can see the full
working config you used.

 2) There is no specific raid or ext4 change that I've been able to find
so if we can narrow it more that would help.

Another useful data point would be to try a wily development image (will
be 15.10) - http://cdimage.ubuntu.com/ubuntu-server/daily/current/.

-- 
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:
  Incomplete

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