Hi Adi,
1)
We have met a similar problem when we build 3.16 kernel like your C#18&22, and
there goes a solution by Johnny.
You have to modify scripts/package/builddeb in linux kernel source as something
like:
...
ppc*)
debarch=$(grep -q CPU_LITTLE_ENDIAN=y $KCONFIG_CONFIG && echo
ppc64el || echo powerpc) ;;
...
So you can build ppc64el kernel instead of powerpc after fixing the builddeb
script.
2)
We start to bisect v3.16 and v3.19, and consistent I/O error happens during
copying files to RAID volumns in v3.19 but not in v3.16. It seems take lots of
time to finish the bisection so we will keep status post.
--
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 : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
