1) Even though I was able to boot up with kernels v3.19 or v4.1 smoothly. On closer inspection of Dmesg logs. There is an I/O error during bootup for 3.19 and 4.1 which I don't see for v3.16 kernel. This error is similar to the one we get in 15.04 installation to RAID.
Dmesg logs are attached This gives me the basis for going ahead with bisection. 2) Further I had to forgo and re-build my environment since the build seems to have gone into a bad state when was moving around some files after upgrading kernel to v4.1. BUT now, I am NO longer able to generate the custom .deb kernel packages for PPC64LE arch. Instead make -j `getconf _NPROCESSORS_ONLN` deb-pkg LOCALVERSION=-custom now generates POWERPC arch images instead of PPC64LE. For example: linux-headers-3.18.0-custom_3.18.0-custom-2_powerpc.deb Am I missing something ? I was successfully able to generate kernel deb packages yesterday for PPC64LE. I want to try and replicate that environment so that I can go ahead with bisection ** Attachment added: "dmesg_logs_for_different_kernels.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475166/+attachment/4443660/+files/dmesg_logs_for_different_kernels.zip -- 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 -- 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
