← Back to team overview

kernel-packages team mailing list archive

[Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller


Hi Chris,

Please let us clarify first, we install the following package first:

We reboot the system and it hangs with above messages.

So we re-installed a new 14.10 system and update packages by the following order again:

Now it seems be able to boot up OS after we installed linux-image-extra.
Would you please help to clarify what the impact is for installation of linux-image-extra?
However, we saw mounting filesystem error with ext4 while installing Ubuntu 15.04, can we emulate this kind of behavior if we just update the kernel from 14.10?


You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:

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

  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. 

  Adi Gangidi

To manage notifications about this bug go to: