[Kernel-packages] [Bug 1469965] Re: ISST-KVM:R3-0:quenv:Ubuntu 14.04.03 installation using Netboot fails on PowerNV machine
Thanks, Canonical. Seems pretty certain this is the problem. We will test as soon as the fix is in the daily build. -- 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/1469965 Title: ISST-KVM:R3-0:quenv:Ubuntu 14.04.03 installation using Netboot fails on PowerNV machine Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Trusty: Fix Committed Bug description: SRU Justification: [Impact] Users of the 3.19 kernel in Trusty will be unable to netboot if using bnx2x drivers that utilize 7.10.51.0 firmware. [Test Case] Try netboot installing on a machine that has a bnx2x driver that uses 7.10.51.0 firmware [Fix] Adding 7.10.51.0 firmware to the linux-firmware udeb -- == Comment: #0 - INDIRA P. JOGA - 2015-06-25 06:09:52 == Classification the type of defect: -- DEFECT : Distros Description: I tried to install ubuntu build 14.04.03 on powernv machine, quenv.isst.aus.stglabs.ibm.com via netboot it is failing with network configuration error. > I have tried with 'configure network manually' option , that also fails. > Tried ubuntu 14.04 installation as well, it also fails with network configuration. > Tried ubuntu 15.10 and it installed successfully. root@quenv:~# cat /etc/issue Ubuntu Wily Werewolf (development branch) \n \l FYI --- Error seen is ?? [!!] Configure the network ??? ? ? Network autoconfiguration failed ? ? Your network is probably not using the DHCP protocol. Alternatively, ? ? the DHCP server may be slow or some network hardware is not working properly. ? RECENT SYSTEM CHANGES : none - none == Comment: #1 - Richard M. Scheller - 2015-06-25 11:10:13 == The network interface is using the bnx2x driver: root@quenv:~# lspci |grep -i broadcom 0003:0e:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Ethernet (rev 10) 0003:0e:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Ethernet (rev 10) 0003:0e:00.2 Ethernet controller: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Ethernet (rev 10) 0003:0e:00.3 Ethernet controller: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Ethernet (rev 10) Since Ubuntu 15.10 is working, but 14.04.3 is not, can someone check to see if there are some driver fixes that need to be backported? == Comment: #2 - David Heller - 2015-06-25 19:18:01 == You are probably correct: there may be some patches that need to be backported. But it's not clear whether it's a bnx2x driver issue just yet. I say that because of recent bug 122410 and bug 122009 which found some things lacking in the "linux-firmware" package. Can you please check your logs to see if you have the same error messages seen there, regarding cannot load firmware? At the point the install fails you should be able to "go back" and then "execute a shell", and then you can tail your /var/log/syslog and see if you see those messages, or whatever the issue is you should see some evidence there. You also should be able to run "lsmod", "modinfo bnx2x" and "ip link" from the installer shell so please collect that as well. If you can get the system booted into 14.04,3, perhaps by installing over a different NIC, you could check these things and the linux- firmware package level also. When I logged into your node it was already booted into 15.10, so I went ahead and collected the info there. If you could do the same for 14.04,3 we can compare. With that, and the install log information, we should be able to see what the problem is. Thx. == Comment: #3 - David Heller - 2015-06-25 19:21:44 == The bnx2x driver and linux-firmware versions for Wily (working case): root@quenv:~# uname -a Linux quenv 3.19.0-22-generic #22-Ubuntu SMP Tue Jun 16 17:15:17 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux root@quenv:~# cat /etc/os-release NAME="Ubuntu" VERSION="15.10 (Wily Werewolf)" ... root@quenv:~# lsmod | grep bnx2x bnx2x 891548 0 mdio5849 2 bnx2x,cxgb3 libcrc32c 1750 2 bnx2x,iw_nes root@quenv:~# modinfo bnx2x filename: /lib/modules/3.19.0-22-generic/kernel/drivers/net/ethernet/broadcom/bnx2x/bnx2x.ko firmware: bnx2x/bnx2x-e2-7.10.51.0.fw firmware: bnx2x/bnx2x-e1h-7.10.51.0.fw firmware: bnx2x/bnx2x-e1-7.10.51.0.fw version:1.710.51-0 license:GPL description:Broadcom Ne
[Kernel-packages] [Bug 1461688] Re: Ubuntu 14.04.2 daily build fails to install
** Package changed: ubuntu => linux (Ubuntu) -- 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/1461688 Title: Ubuntu 14.04.2 daily build fails to install Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Murilo Fossa Vicentini - 2015-06-03 14:01:29 == Ubuntu 14.04.2 daily build (tested with June 3rd release) fails to install in a PowerVM LPAR of a P8 system. This issue seems to be a regression since I don't see it in the Ubuntu 14.04.2 GA release. The installation method use was a VIOS Virtual DVD loaded with the Ubuntu 14.04.2 ISO from June 3rd. I'll attach below the error that shows up in the middle of the installation, it doesn't seem to be related to any particular activity being performed by the user during the installation, it just randomly happens after some time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461688/+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
[Kernel-packages] [Bug 1452473] Re: sensors command requires manual loading of 'ibmpowernv' module
** Package changed: ubuntu => linux (Ubuntu) -- 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/1452473 Title: sensors command requires manual loading of 'ibmpowernv' module Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Shilpasri G. Bhat - 2015-05-06 12:55:40 == "ibmpowernv" module is not auto loaded. This leads to failure of 'sensors' command. Either have 'CONFIG_SENSORS_IBMPOWERNV=y' to statically build this module or an rc script to load this during init to promote seamless operation of 'sensors' command. ---uname output--- 3.19.0-15-generic ---Steps to Reproduce--- #sensors No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. Contact Information = Shilpasri G Bhat / shilpa.b...@linux.vnet.ibm.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452473/+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
[Kernel-packages] [Bug 1425773] Re: multipath command not showing boot disk information
(I had trouble setting the package here as several choices like "init- scripts" or "device-mapper" kept telling me there was no such package, even if they came up in the search. IMO this could be an install issue also). -- 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/1425773 Title: multipath command not showing boot disk information Status in linux package in Ubuntu: New Bug description: == Comment: #0 - GIRISH SHRIGIRI - 2015-02-18 05:57:13 == multipath -ll command not showing proper boot disk . i have assigned 60G ds8k SAN disk and rest IO Disk of sizes 20G and 10G from ds8k and XIV. lsblk and lsscsi -s shows proper boot disk name ( sdq ) but multipath -ll shows wrong result and also shows wrong size ( showing 20G ) please have a look into it . root@zop01:/# multipath -ll mpath2 (200173800277f06f5) dm-4 IBM,2810XIV size=16G features='0' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=1 status=active | `- 2:0:6:2 sdj 8:144 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 2:0:7:2 sdn 8:208 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 3:0:6:2 sdz 65:144 active ready running `-+- policy='round-robin 0' prio=1 status=enabled `- 3:0:7:2 sdad 65:208 active ready running mpath1 (200173800277f06f7) dm-6 IBM,2810XIV size=16G features='0' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=1 status=active | `- 2:0:6:4 sdl 8:176 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 2:0:7:4 sdp 8:240 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 3:0:6:4 sdab 65:176 active ready running `-+- policy='round-robin 0' prio=1 status=enabled `- 3:0:7:4 sdaf 65:240 active ready running mpath0 (200173800277f06f4) dm-3 IBM,2810XIV size=16G features='0' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=1 status=active | `- 2:0:6:1 sdi 8:128 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 2:0:7:1 sdm 8:192 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 3:0:6:1 sdy 65:128 active ready running `-+- policy='round-robin 0' prio=1 status=enabled `- 3:0:7:1 sdac 65:192 active ready running mpath9 (200173800277f06f0) dm-7 IBM,2810XIV size=16G features='0' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=1 status=active | `- 4:0:2:1 sdag 66:0 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 4:0:4:1 sdan 66:112 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 5:0:2:1 sdar 66:176 active ready running `-+- policy='round-robin 0' prio=1 status=enabled `- 5:0:4:1 sday 67:32 active ready running mpath8 (200173800277f06f3) dm-10 IBM,2810XIV size=16G features='0' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=1 status=active | `- 4:0:2:4 sdaj 66:48 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 5:0:4:4 sdbb 67:80 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 4:0:4:4 sdaq 66:160 active ready running `-+- policy='round-robin 0' prio=1 status=enabled `- 5:0:2:4 sdau 66:224 active ready running mpath14 (36005076309ffc2f00331) dm-13 IBM,2107900 size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active |- 4:0:3:1076969475 sdam 66:96 active ready running `- 5:0:3:1076969475 sdax 67:16 active ready running mpath13 (36005076309ffc2f00330) dm-12 IBM,2107900 size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active |- 4:0:3:1076903939 sdal 66:80 active ready running `- 5:0:3:1076903939 sdaw 67:0 active ready running mpath6 (36005076309ffc2f0032e) dm-2 IBM,2107900 size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active |- 2:0:0:1076772867 sdd 8:48 active ready running |- 2:0:1:1076772867 sdh 8:112 active ready running |- 3:0:0:1076772867 sdt 65:48 active ready running `- 3:0:1:1076772867 sdx 65:112 active ready running mpath12 (36005076309ffc2f0032f) dm-11 IBM,2107900 size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active |- 4:0:3:1076838403 sdak 66:64 active ready running `- 5:0:3:1076838403 sdav 66:240 active ready running mpath5 (36005076309ffc2f0032d) dm-1 IBM,2107900 size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active
[Kernel-packages] [Bug 1425773] Re: multipath command not showing boot disk information
** Package changed: ubuntu => linux (Ubuntu) -- 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/1425773 Title: multipath command not showing boot disk information Status in linux package in Ubuntu: New Bug description: == Comment: #0 - GIRISH SHRIGIRI - 2015-02-18 05:57:13 == multipath -ll command not showing proper boot disk . i have assigned 60G ds8k SAN disk and rest IO Disk of sizes 20G and 10G from ds8k and XIV. lsblk and lsscsi -s shows proper boot disk name ( sdq ) but multipath -ll shows wrong result and also shows wrong size ( showing 20G ) please have a look into it . root@zop01:/# multipath -ll mpath2 (200173800277f06f5) dm-4 IBM,2810XIV size=16G features='0' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=1 status=active | `- 2:0:6:2 sdj 8:144 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 2:0:7:2 sdn 8:208 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 3:0:6:2 sdz 65:144 active ready running `-+- policy='round-robin 0' prio=1 status=enabled `- 3:0:7:2 sdad 65:208 active ready running mpath1 (200173800277f06f7) dm-6 IBM,2810XIV size=16G features='0' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=1 status=active | `- 2:0:6:4 sdl 8:176 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 2:0:7:4 sdp 8:240 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 3:0:6:4 sdab 65:176 active ready running `-+- policy='round-robin 0' prio=1 status=enabled `- 3:0:7:4 sdaf 65:240 active ready running mpath0 (200173800277f06f4) dm-3 IBM,2810XIV size=16G features='0' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=1 status=active | `- 2:0:6:1 sdi 8:128 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 2:0:7:1 sdm 8:192 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 3:0:6:1 sdy 65:128 active ready running `-+- policy='round-robin 0' prio=1 status=enabled `- 3:0:7:1 sdac 65:192 active ready running mpath9 (200173800277f06f0) dm-7 IBM,2810XIV size=16G features='0' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=1 status=active | `- 4:0:2:1 sdag 66:0 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 4:0:4:1 sdan 66:112 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 5:0:2:1 sdar 66:176 active ready running `-+- policy='round-robin 0' prio=1 status=enabled `- 5:0:4:1 sday 67:32 active ready running mpath8 (200173800277f06f3) dm-10 IBM,2810XIV size=16G features='0' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=1 status=active | `- 4:0:2:4 sdaj 66:48 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 5:0:4:4 sdbb 67:80 active ready running |-+- policy='round-robin 0' prio=1 status=enabled | `- 4:0:4:4 sdaq 66:160 active ready running `-+- policy='round-robin 0' prio=1 status=enabled `- 5:0:2:4 sdau 66:224 active ready running mpath14 (36005076309ffc2f00331) dm-13 IBM,2107900 size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active |- 4:0:3:1076969475 sdam 66:96 active ready running `- 5:0:3:1076969475 sdax 67:16 active ready running mpath13 (36005076309ffc2f00330) dm-12 IBM,2107900 size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active |- 4:0:3:1076903939 sdal 66:80 active ready running `- 5:0:3:1076903939 sdaw 67:0 active ready running mpath6 (36005076309ffc2f0032e) dm-2 IBM,2107900 size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active |- 2:0:0:1076772867 sdd 8:48 active ready running |- 2:0:1:1076772867 sdh 8:112 active ready running |- 3:0:0:1076772867 sdt 65:48 active ready running `- 3:0:1:1076772867 sdx 65:112 active ready running mpath12 (36005076309ffc2f0032f) dm-11 IBM,2107900 size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active |- 4:0:3:1076838403 sdak 66:64 active ready running `- 5:0:3:1076838403 sdav 66:240 active ready running mpath5 (36005076309ffc2f0032d) dm-1 IBM,2107900 size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active |- 2:0:0:1076707331 sdc 8:32 active ready running |- 2:0:1:1076707331 sdg 8:96 active ready running |- 3:0:0:1076707331 sds 65:32 active ready running `-
[Kernel-packages] [Bug 1416515] Re: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled
** Package changed: ubuntu => linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1416515 Title: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Sowmya G. Parvathi - 2015-01-29 12:43:30 == I have a lpar installed with ubuntu 15.04.I enabled kdump and on reboot getting error message "Cannot open `/boot/vmlinuz`". Steps to recreate: 1. Install ubuntu 15.04 (netboot) 2. sudo passwd root 3. apt-get update, apt-get install openssh-server, apt-get nfs-common 4. service ssh restart 5. apt-get install linux-crashdump: ??? Configuring kexec-tools ?? ? ? ? If you choose this option, a system reboot will trigger a restart into a ? ? kernel loaded by kexec instead of going through the full system boot ? ? loader process. ? ? ? ? Should kexec-tools handle reboots?? ? ? ? ? ? ? ? Selected "Yes" 6. vi /etc/default/grub.d/kexec-tools.cfg (set crashkernel=1024M) 7. update-grub 8. reboot .wait-for-state stop/waiting * Starting userspace bootsplash utility [ OK ] Cannot open `/boot/vmlinuz': No such file or directory * Loading new kernel image into memory... [fail] * Stopping uuidd generator uuidd[ OK ] * Asking all remaining processes to terminate...[ OK ] * All processes ended within 1 seconds... [ OK ] * Stopping NSM status monitor [ OK ] rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" * Stopping RPC portmapper replacement [ OK ] * Stopping D-Bus system message bus [ OK ] * Stopping NFSv4 id <-> name mapper [ OK ] * Stopping configure virtual network devices[ OK ] * Stopping configure network device security[ OK ] * Deactivating swap... [ OK ] * Will now restart [ 20.328664] reboot: Restarting system lpar will be up, but i am not sure of this error. uname -a Linux pole2lp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Contact Info: sowpa...@in.ibm.com == Comment: #2 - David Heller - 2015-01-29 14:19:43 == On ppc, it should be looking for a file "vmlinux", not "vmlinuz". The former is the filename on the ppc distributions, the latter on amd64. Can you try editing the grub.cfg to see if that fixes it? if so, it's possible that whichever package modified the grub.cfg here, cannot handle the ppc case and need to be patched == Comment: #3 - Sowmya G. Parvathi - 2015-01-30 05:50:32 == I think the issue is with /etc/default/kexec file and not grub.cfg. kexec: # Defaults for kexec initscript # sourced by /etc/init.d/kexec and /etc/init.d/kexec-load # Load a kexec kernel (true/false) LOAD_KEXEC=true # Kernel and initrd image KERNEL_IMAGE="/boot/vmlinuz" INITRD="/boot/initrd.img" # If empty, use current /proc/cmdline APPEND="" # Load the default kernel from grub config (true/false) USE_GRUB_CONFIG=false Here KERNEL_IMAGE="/boot/vmlinuz" instead of "/boot/vmlinux". I changed vmlinuz to vmlinux, did a reboot and issue did not occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416515/+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
[Kernel-packages] [Bug 1407702] Re: Console message "could not open builtin file '/lib/modules/3.16.0-28-generic/modules.builtin.bin' " is got while installing Ubuntu15.04
** Package changed: ubuntu => linux (Ubuntu) -- 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/1407702 Title: Console message "could not open builtin file '/lib/modules/3.16.0-28-generic/modules.builtin.bin' " is got while installing Ubuntu15.04 Status in linux package in Ubuntu: New Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2015-01-05 04:12:45 == ---Problem Description--- could not open builtin file '/lib/modules/3.16.0-28-generic/modules.builtin.bin' message is got on the console ---uname output--- Linux ubuntu 3.16.0-28-generic #38-Ubuntu SMP Fri Dec 12 17:39:43 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P8 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a Ubuntu 15.04 guest VM over Power KVM Host on a P8 machine. While trying to install the guest VM, we keep on getting the below messages in the console when we try the options of the Installation menu. ? [!!] Select a language ?? ? ? ? Choose the language to be used for the installation process. The? ? selected language will also be the default language for the installed ? ? system. ? ? ? ? Language: ? ? ? ? C ? ? English ? ? ? ?? ? ? ??? [!!] Select your location ? ? ? The selected location will be used to set your time zone and also for ? ? example to help select the system locale. Normally this should be the ? ? country where you live. ? ? ? ? This is a shortlist of locations based on the language you selected.? ? Choose "other" if your location is not listed. ? ? ? ? Country, territory or area: ? ? ? ? Nigeria ? ? Philippines ? ? ? Singapore? ? ? South Africa? ? United Kingdom ? ? ? United States ? ? ? ?? ? ? ??? moves; selects; activates buttons Detecting hardware to find CD-ROM drives ? ? ? ?0% ? ? ? ? Network interface NamePolicy= disabled on kernel command line, ignoring.? ? could not open builtin file '/lib/modules/3.16.0-28-generic/modules.builtin.bin'could not open builtin file '/lib/modules/3.16.0-28-generic/modules.builtin.bin' could not open builtin file '/lib/modules/3.16.0-28-generic/modules.builtin.bin' could not open builtin file '/lib/modules/3.16.0-28-generic/modules.builtin.bin' could not open builtin file '/lib/modules/3.16.0-28-generic/modules.builtin.bin' could not o
[Kernel-packages] [Bug 1392021] Re: Ubuntu 15.04 [genwqe_start] err: could not setup servicelayer
** Package changed: ubuntu => linux (Ubuntu) -- 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/1392021 Title: Ubuntu 15.04 [genwqe_start] err: could not setup servicelayer Status in “linux” package in Ubuntu: New Bug description: == Comment: #0 - Christian Rund - 2014-11-11 10:45:12 == ---Problem Description--- In our opinion the 2.0.15 version of the IBM GenWQE Accelerator Adapter driver part of Ubuntu 15.04 is not working. A higher version would be needed. The driver is part of the linux-image-extra-3.16.0-24-generic package. [3.330906] genwqe 0001:00:02.0: enabling device (0140 -> 0142) [3.332443] genwqe 0001:00:02.0: ibm,query-pe-dma-windows(2620) 1 800 2001 returned 0 [3.333159] genwqe 0001:00:02.0: ibm,create-pe-dma-window(2720) 1 800 2001 10 1f returned -1 (liobn = 0x0 starting addr = 0 0) [4.403223] genwqe 0001:00:02.0: [genwqe_start] err: could not setup servicelayer! [4.40] genwqe 0001:00:02.0: err: cannot start card services! (err=-5) [4.404471] genwqe: probe of 0001:00:02.0 failed with error -5 [321140.194392] genwqe_card: module verification failed: signature and/or required key missing - tainting kernel modinfo genwqe_card filename: /lib/modules/3.16.0-24-generic/kernel/drivers/misc/genwqe/genwqe_card.ko license:GPL version:2.0.15 description:GenWQE Card author: Michal Jung author: Joerg-Stephan Vogt author: Michael Ruettger author: Frank Haverkamp srcversion: 69FBCA52AFAF3B71342E43B alias: pci:v1014d044Bsv1014sd044Bbc12sc00i00* alias: pci:v1014dsvsd035Fbc12sc00i00* alias: pci:v1014d044Bsvsd035Fbc12sc00i00* alias: pci:v1014dsvsdbc12sc00i00* alias: pci:v1014d044Bsvsdbc12sc00i00* alias: pci:v1014d044Bsv1014sd035Fbc12sc00i00* depends:crc-itu-t intree: Y vermagic: 3.16.0-24-generic SMP mod_unload modversions signer: Magrathea: Glacier signing key sig_key:32:F4:D0:34:89:C6:7C:D7:71:67:94:F6:0C:00:D7:F7:E8:D2:78:0E sig_hashalgo: sha512 Contact Information = christian.r...@de.ibm.com, Frank Haverkamp haver...@de.ibm.com ---uname output--- Linux tulg3 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:06:19 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- 0001:00:02.0 Processing accelerators: IBM GenWQE Accelerator Adapter Class: 1200 VendorID: 1014 DeviceId: 044b assigned to the PowerKVM guest via PCI passthrough (vfio-pci) Machine Type = 8284-22A PowerKVM ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1) Create a guest system on PowerKVM using image disk file, install from virutal SCSI DVD. Especially assign the GenWQE card via PCI passthrough. 2) Start up the guest 3) lspci -knd :044b 3) dmesg|grep genwqe 4) ) modprobe genwqe_card.ko No module is assigned to the card 5) ls -l /dev/genwq* shows no file at all. One device file would be expected here. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for christian.r...@de.ibm.com, Frank Haverkamp haver...@de.ibm.com: -Attach sysctl -a output output to the bug. == Comment: #2 - Frank Haverkamp - 2014-11-12 05:09:24 == Christian and I tried out CVS version of the driver and that works. Ubuntu picked and unfortunate intermediate version of the driver which had broken irq registration. This was fixed later by Sebastian Ott and Kleber and I added on top of that some more patches which did cleanups and more importantly added System p specific recovery features e.g. like EEH handlers and a method to reload the bitstream for p. Therefore it would be great if someone could have the Ubuntu folks pickup the latest version from Kernel.org. I know that Greg KH has a good version of the code in his tree. We need to check if that has made it yet into Linux version (both should be the same). == Comment: #3 - Frank Haverkamp - 2014-11-12 07:58:03 == Christian has checked the linux.git version of the genwqe_card driver compiled against his Ubuntu kernel and found it working. SHA is 206c5f60a3d902bc4b56dab2de3e88de5eb06108. Patched affecting the driver are usually prefixed with GenWQE or genwqe 7276883f1f98cd0a92fdc049f69bdc0912f7fc16 misc/GenWQE: fix pci_enable_msi usage was the one which fixed the problem introduced by a30d0108b09ae46d24594a2e699c4dad21bb4af4 Use pci_enable_msi_exact() instead of pci_enable_msi_block() So please have a look how we convin
[Kernel-packages] [Bug 1357015] Re: DKMS build failed due to compiler version mismatch
Changing the state to invalid on the LP side. I hope that is the correct action. ** Changed in: dkms (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1357015 Title: DKMS build failed due to compiler version mismatch Status in “dkms” package in Ubuntu: Invalid Bug description: == Comment: #0 - Dave Marquardt - 2014-08-11 15:36:47 == ---Problem Description--- DKMS build for kernel module failed with this message: gcc-version-check failed: The compiler used to compile the kernel (gcc 4.8) does not exactly match the current compiler (gcc 4.9). The Linux 2.6 kernel module loader rejects kernel modules built with a version of gcc that does not exactly match that of the compiler used to build the running kernel. If you know what you are doing and want to override the gcc version check, you can do so by setting the IGNORE_CC_MISMATCH environment variable to "1". In any other case, set the CC environment variable to the name of the compiler that was used to compile the kernel. Contact Information = Dave Marquardt/davem...@linux.vnet.ibm.com ---uname output--- Linux tul115p1 3.16.0-5-generic #10-Ubuntu SMP Mon Jul 21 16:17:25 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8286-42A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Installed back-level kernel and headers 3.16.0-5. Installed a third-party device driver (i.e. out-of-tree kernel module), which did a DKMS build which failed. Install method: DVD Install disk info: /dev/sda2 Install ISO Information: Ubuntu 14.10 Userspace tool common name: dkms The userspace tool has the following bit modes: 64-bit Userspace rpm: na Userspace tool obtained from project website: na *Additional Instructions for Dave Marquardt/davem...@linux.vnet.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. == Comment: #3 - Dave Marquardt - 2014-08-13 15:16:08 == I just tested DKMS with this module on Ubuntu 14.04. I installed DKMS, installed the module, then upgraded the kernel, and the module was correctly built and installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1357015/+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
[Kernel-packages] [Bug 1357015] Re: DKMS build failed due to compiler version mismatch
** Package changed: ubuntu => dkms (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1357015 Title: DKMS build failed due to compiler version mismatch Status in “dkms” package in Ubuntu: New Bug description: == Comment: #0 - Dave Marquardt - 2014-08-11 15:36:47 == ---Problem Description--- DKMS build for kernel module failed with this message: gcc-version-check failed: The compiler used to compile the kernel (gcc 4.8) does not exactly match the current compiler (gcc 4.9). The Linux 2.6 kernel module loader rejects kernel modules built with a version of gcc that does not exactly match that of the compiler used to build the running kernel. If you know what you are doing and want to override the gcc version check, you can do so by setting the IGNORE_CC_MISMATCH environment variable to "1". In any other case, set the CC environment variable to the name of the compiler that was used to compile the kernel. Contact Information = Dave Marquardt/davem...@linux.vnet.ibm.com ---uname output--- Linux tul115p1 3.16.0-5-generic #10-Ubuntu SMP Mon Jul 21 16:17:25 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8286-42A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Installed back-level kernel and headers 3.16.0-5. Installed a third-party device driver (i.e. out-of-tree kernel module), which did a DKMS build which failed. Install method: DVD Install disk info: /dev/sda2 Install ISO Information: Ubuntu 14.10 Userspace tool common name: dkms The userspace tool has the following bit modes: 64-bit Userspace rpm: na Userspace tool obtained from project website: na *Additional Instructions for Dave Marquardt/davem...@linux.vnet.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. == Comment: #3 - Dave Marquardt - 2014-08-13 15:16:08 == I just tested DKMS with this module on Ubuntu 14.04. I installed DKMS, installed the module, then upgraded the kernel, and the module was correctly built and installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1357015/+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
