[Kernel-packages] [Bug 1416548] Re: IBM Power8 requires rootdelay= in order to boot
This was fixed in bug #1326199 -- 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/1416548 Title: IBM Power8 requires rootdelay= in order to boot Status in linux package in Ubuntu: Confirmed Bug description: ubuntu@P8:~$ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 After installing Ubuntu 14.04 onto an IBM Power8 using bare metal mode, the installation will not boot unless setting a rootdelay timeout as a kernel flag. The following error occurs at boot otherwise: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/ad097f75-53df-40dc-9660-2397ac629778 does not exist. Dropping to a shell! A setting of rootdelay=190 seems to work whereas 90 was not long enough. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.6 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: Date: Fri Jan 30 16:11:28 2015 HibernationDevice: RESUME=UUID=f8fdf988-698a-424f-99ec-f1bcd83535fd InstallationDate: Installed on 2015-01-29 (1 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release ppc64el (20140416.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=ad097f75-53df-40dc-9660-2397ac629778 ro splash quiet rootdelay=190 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416548/+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 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
Patch is upstream: 3b8a3c010969 (powerpc/pseries: Fix endiannes issue in RTAS call from xmon). The patch is also marked for -stable. -- 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/1396235 Title: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM) Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- Kernel fails to invoke xmon, instead print following messages # echo x /proc/sysrq-trigger [ 47.600133] SysRq : Entering xmon cpu 0xf: Vector: 0 at [c000e8603b80] pc: c05610c0: write_sysrq_trigger+0x120/0x260 lr: c05610c0: write_sysrq_trigger+0x120/0x260 sp: c000e8603ce0 msr: 80009033 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] pc: 0ee27cc4 lr: 0ee27c44 sp: fc7b4b0 msr: 80001000 dar: 1000 dsisr: 4200 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop xmon: WARNING: bad recursive fault on cpu 0xf ---uname output--- N/A Machine Type = powervm le ---System Hang--- System is hung ---Debugger--- A debugger is not configured ---Steps to Reproduce--- see problem description Stack trace output: no Oops output: see problem description System Dump Info: The system is not configured to capture a system dump. This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+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 1374438] Re: power-nv ppc64el crash with ATI FirePro VGA card (snd_hda_intel)
My guess is the card doesn't support 64bit DMA, it supports something less than that. A quick hack in sound/pci/hda/hda_intel.c to disable 64bit DMA fixes it: - if ((gcap AZX_GCAP_64OK) !pci_set_dma_mask(pci, DMA_BIT_MASK(64))) + if (0 (gcap AZX_GCAP_64OK) !pci_set_dma_mask(pci, DMA_BIT_MASK(64))) pci_set_consistent_dma_mask(pci, DMA_BIT_MASK(64)); We will work on a fix, but for now it would be best to blacklist it on ppc64le. -- 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/1374438 Title: power-nv ppc64el crash with ATI FirePro VGA card (snd_hda_intel) Status in “linux” package in Ubuntu: Confirmed Bug description: I have the following video card in my ppc64 system. When booting ubuntu in power-nv, I get kernel crashes: # lspci | grep AMD 0001:09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar GL [FirePro 2270] 0001:09:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300 Series] The work around we have in place is # cat /etc/modprobe.d/blacklist-ppc64el.conf blacklist snd_hda_intel blacklist snd_hda_controller blacklist snd_hda_codec A snippet of the console log is: [ 70.094661] init: console-setup main process (1262) terminated with status 1 [ 70.953213] EEH: Frozen PE#3 on PHB#1 detected [ 70.953280] EEH: PE location: U78CB.001.WZS007L-P1-004 , PHB location: U78CB.001.WZS007L-P1-C32 [ 71.025925] [drm:rv770_stop_dpm] *ERROR* Could not force DPM to low. [ 71.956221] Unable to handle kernel paging request for data at address 0x444f525000a2 [ 71.956325] Faulting instruction address: 0xc06413dc [ 71.956383] Oops: Kernel access of bad area, sig: 11 [#1] [ 71.956428] SMP NR_CPUS=2048 NUMA PowerNV [ 71.956474] Modules linked in: snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore rtc_generic shpchp uio_pdrv_genirq uio powernv_rng ses enclosure radeon i2c_algo_bit ttm drm_kms_helper drm ipr [ 71.956770] CPU: 0 PID: 779 Comm: kworker/0:1 Tainted: GW 3.16.0-17-generic #23-Ubuntu [ 71.956852] Workqueue: events azx_probe_work [snd_hda_intel] [ 71.956909] task: c00fdee4fe40 ti: c00fdeeb task.ti: c00fdeeb [ 71.956975] NIP: c06413dc LR: c064187c CTR: c0641810 [ 71.957042] REGS: c00fdeeb3730 TRAP: 0300 Tainted: GW (3.16.0-17-generic) [ 71.957119] MSR: 90019033 SF,HV,EE,ME,IR,DR,RI,LE CR: 24002084 XER: [ 71.957287] CFAR: c0009358 DAR: 444f525000a2 DSISR: 4000 SOFTE: 1 GPR00: c064187c c00fdeeb39b0 c13d4ee0 c0c1f8d8 GPR04: 444f52500012 c00fdeeb3a50 0a1c GPR08: c00fdeeb3a60 d0001449f9d0 d000144965b8 GPR12: c0641810 cfb8 c00df668 c00fdf4e0c40 GPR16: GPR20: 0001 c00fd1157824 GPR24: d000144f5ad8 0001 GPR28: 0001 c0c1f8d8 c00fdeeb3a50 444f52500012 [ 71.958172] NIP [c06413dc] __dev_printk+0x3c/0x100 [ 71.958218] LR [c064187c] dev_warn+0x6c/0x90 [ 71.958263] Call Trace: [ 71.958286] [c00fdeeb39b0] [c00fdeeb39f0] 0xc00fdeeb39f0 (unreliable) [ 71.958365] [c00fdeeb3a30] [c064187c] dev_warn+0x6c/0x90 [ 71.958433] [c00fdeeb3a80] [d0001449529c] azx_codec_create+0x41c/0x460 [snd_hda_controller] [ 71.958523] [c00fdeeb3b90] [d000144f1ca0] azx_probe_continue+0x370/0x7c0 [snd_hda_intel] [ 71.958612] [c00fdeeb3c40] [c00d59ec] process_one_work+0x1ac/0x500 [ 71.958690] [c00fdeeb3cd0] [c00d62f0] worker_thread+0x190/0x6c0 [ 71.958757] [c00fdeeb3d80] [c00df770] kthread+0x110/0x130 [ 71.958825] [c00fdeeb3e30] [c000a468] ret_from_kernel_thread+0x5c/0x74 [ 71.958902] Instruction dump: [ 71.958936] fba1ffe8 fbc1fff0 fbe1fff8 f8010010 f821ff81 7c9f2378 7c7d1b78 7cbe2b78 [ 71.959047] 6000 6000 2fbf 41de00a0 e93f0090 887d0001 2fa9 3863ffd0 [ 71.959160] ---[ end trace b21ffc1b5f521aab ]--- ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-17-generic 3.16.0-17.23 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.7-0ubuntu2 Architecture: ppc64el
[Kernel-packages] [Bug 1371634] Re: block devices appear twice
This is a multipath issue. The box has two cards with redundant paths to each disk. Multipath is meant to create /dev/mapper/mpath* devices, and the installer should use them instead of the underlying /dev/sd* devices. -- 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/1371634 Title: block devices appear twice Status in “linux” package in Ubuntu: Confirmed Bug description: $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+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 1374440] Re: power-nv ppc64el need to blacklist shpchp
Talking to benh, the main issue in the PCIE hotplug driver. Unfortunately that is not a module: CONFIG_HOTPLUG_PCI_PCIE=y Could we get that disabled in the ppc64le defconfig? We don't have any hardware that needs it. -- 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/1374440 Title: power-nv ppc64el need to blacklist shpchp Status in “linux” package in Ubuntu: Fix Committed Status in “linux” source package in Utopic: Fix Committed Bug description: The shpchp module seems to be causing issues on some ppc64el hardware. We're able to work around the issue by blacklisting it as: $ cat /etc/modprobe.d/blacklist-ppc64el.conf blacklist shpchp I've discussed this with Anton, and we came up with the above work around. I'll attach a log of the failed boot. Note, that the shpchp.blacklist=yes command line parameters seem not to do anything (ie, just ignore them). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-17-generic 3.16.0-17.23 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.7-0ubuntu2 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' Date: Fri Sep 26 12:54:29 2014 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=aad7f49b-45f2-42ec-83b9-3233a014bae6 ro console=hvc0 ProcLoadAvg: 6.42 2.15 0.79 1/1156 5938 ProcLocks: 1: FLOCK ADVISORY WRITE 2515 00:11:45214 0 EOF 2: POSIX ADVISORY WRITE 2369 00:11:50266 0 EOF 3: POSIX ADVISORY WRITE 2567 00:11:47202 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 3.16.0-17-generic (buildd@fisher03) (gcc version 4.9.1 (Ubuntu 4.9.1-15ubuntu1) ) #23-Ubuntu SMP Fri Sep 19 16:54:14 UTC 2014 RelatedPackageVersions: linux-restricted-modules-3.16.0-17-generic N/A linux-backports-modules-3.16.0-17-generic N/A linux-firmware 1.134 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 19 cpu_dscr: DSCR is 0 cpu_runmode: Could not retrieve current diagnostics mode, No firmware implementation of function cpu_smt: SMT is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1374440/+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 1370425] Re: kernel bug seen while try to use madvise system call with MADV_HWPOISON mode
I've submitted two patches for this: http://patchwork.ozlabs.org/patch/392712/ http://patchwork.ozlabs.org/patch/392713/ -- 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/1370425 Title: kernel bug seen while try to use madvise system call with MADV_HWPOISON mode Status in “linux” package in Ubuntu: Confirmed Bug description: Problem Description kernel bug seen while try to use madvise system call with MADV_HWPOISON mode ---uname output--- Linux u10thp 3.16.0-9-generic #14-Ubuntu SMP Fri Aug 15 15:03:36 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Power 8 Steps to Reproduce 1. Install Ubuntu 14.10 guest on PowerKVM. 2. Setup hugepage backing guest VM. 3. Try madv_poison.c code to test madvise sys. call with HWPOISON mode(test code is attached). gcc -o madv_poison madv_poison.c ./madv_poison -C -i 1 (1 - shm_test) Ubuntu 14.10 LE throws kernel bug : root@u10thp:~# ./madv_poison -C -i 1 vm.memory_failure_early_kill = 0 [pid 2301] start page-poisoning test [pid 2301] there are 1 shm_child [pid 2301] have spawned 1 processes [pid 2301] wait for Pid 2304 [pid 2304] shm dirty poisoning page 0x3fffa7ce [ 7905.009001] Injecting memory failure for page 0xe6a7 at 0x3fffa7ce [ 7905.009359] MCE 0xe6a7: dirty LRU page recovery: Recovered [pid 2304] writing 2 [ 7905.009901] [ cut here ] [ 7905.010164] kernel BUG at /build/buildd/linux-3.16.0/arch/powerpc/mm/fault.c:180! [ 7905.010396] Oops: Exception in kernel mode, sig: 5 [#234] [ 7905.010438] SMP NR_CPUS=2048 NUMA pSeries [ 7905.010480] Modules linked in: pseries_rng rtc_generic ohci_pci [ 7905.010614] CPU: 0 PID: 2304 Comm: madv_poison Tainted: G D 3.16.0-9-generic #14-Ubuntu [ 7905.010686] task: c000e0a92a60 ti: c000e09e8000 task.ti: c000e09e8000 [ 7905.010746] NIP: c09e3314 LR: c09e2e54 CTR: [ 7905.010864] REGS: c000e09eb990 TRAP: 0700 Tainted: G D (3.16.0-9-generic) [ 7905.010924] MSR: 80029033 SF,EE,ME,IR,DR,RI,LE CR: 28002882 XER: [ 7905.011125] CFAR: c09e3170 SOFTE: 1 GPR00: c09e2e54 c000e09ebc10 c13742e0 0010 GPR04: c000e0b37ff8 3fffa7ce 00a9 GPR08: 0010 c000e0a92a60 0020 GPR12: 48002884 cfe4 GPR16: GPR20: 00a9 c000e0597a40 c000e022b060 GPR24: 0010 c000e022b000 c0009568 3fffa7ce GPR28: 0200 c000e09ebea0 [ 7905.012189] NIP [c09e3314] do_page_fault+0x984/0x990 [ 7905.012241] LR [c09e2e54] do_page_fault+0x4c4/0x990 [ 7905.012281] Call Trace: [ 7905.012361] [c000e09ebc10] [c09e2e54] do_page_fault+0x4c4/0x990 (unreliable) [ 7905.012434] [c000e09ebe30] [c0009568] handle_page_fault+0x10/0x30 [ 7905.012494] Instruction dump: [ 7905.012580] e92d0290 e8690460 38630060 4b7274d9 6000 e93f0108 3bc0 792a97e3 [ 7905.012683] 4082f77c 3bc9 6000 4bfff774 0fe0 3c4c0099 [ 7905.012845] ---[ end trace a48a199a061eed79 ]--- [ 7905.019084] [pid 2301] Ins 0: Pid 2304: failed - shared memory test [pid 2301]!!! Page Poisoning Test is FAILED (1 failures found). !!! [pid 2301] page-poisoning test done! root@u10thp:~# == Comment: #1 - Kalpana Shetty kalsh...@in.ibm.com - == The test code works fine with x86/Ubuntu VM so if it is not supported on power then it should have thrown an error not supported as it does with PowerKVM / RHEL 7 VM. Intel/Ubuntu 14.04 VM: = Working fine. root@u04vm14:~# ./madv_poison -C -i 1 (shm_test case) vm.memory_failure_early_kill = 0 [pid 7325] start page-poisoning test [pid 7325] there are 1 shm_child [pid 7325] have spawned 1 processes [pid 7325] wait for Pid 7328 [pid 7328] shm dirty poisoning page 0x7f60ca8ea000 [pid 7328] writing 2 [pid 7328] signal 7 code 4 addr 0x7f60ca8ea000 [pid 7328] pass: recovered [pid 7325] Ins 0: Pid 7328: pass - shared memory test [pid 7325]!!! Page Poisoning Test got PASS. !!! [pid 7325] page-poisoning test done! PowerKVM / RHEL 7 VM: [root@rhel7-web-VM1 ~]# ./madv_poison -C -i 1 sysctl: cannot stat /proc/sys/vm/memory_failure_early_kill: No such file or directory [pid 11512] start page-poisoning test [pid 11512] there are 1 shm_child [pid 11512] have spawned 1 processes [pid 11514] shm dirty
[Kernel-packages] [Bug 1353105] Re: bnx2x crashes on bxn2x_tpa_start
** Tags removed: architecture-ppc64 ** Tags added: architecture-ppc64le -- 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/1353105 Title: bnx2x crashes on bxn2x_tpa_start Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: [Impact] Random crashes when using the bnx2x driver on power 8 [Test Case] heavy use of the bnx2x driver on power 8 [Regression Potential] introduces a simple memory barrier and is therefore very low risk, any such risk would normally affect performanc e not function. === ---Problem Description--- bnx2x may cause crashes or stop working because of a missing memory barrier. Messages like the following appear on the log: bnx2x: [bnx2x_tpa_start:392(eth7)]start of bin not in stop [0] ---uname output--- Linux ubuntu 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:50:31 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- 0001:00:03.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Ethernet (rev 10) 0001:00:03.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Ethernet (rev 10) 0001:00:03.2 Ethernet controller: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Ethernet (rev 10) 0001:00:03.3 Ethernet controller: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Ethernet (rev 10) Machine Type = model : IBM pSeries (emulated by qemu) ---Steps to Reproduce--- Send lots of traffic on a busy workload. Fix for reported issue upstream commit 9aaae044abe95de182d09004cc3fa181bf22e6e0 Fix for EEH related issue upstream commit 0c0e63410a393aae4b615849625f539db775d586 We would like to get those applied to both Ubuntu 14.04 updates and Ubuntu 14.10, please. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353105/+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 1341475] Re: Ubuntu 14.04:linux-crashdump pckg is missing from ubuntu repository
** Tags removed: architecture-ppc64 ** Tags added: architecture-ppc64le -- 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/1341475 Title: Ubuntu 14.04:linux-crashdump pckg is missing from ubuntu repository Status in “linux-meta” package in Ubuntu: Triaged Bug description: Problem Description : I was trying to configure kdump and got below link https://help.ubuntu.com/12.04/serverguide/kernel-crash-dump.html As per above link we need to install linux-crashdump pckg but it seems it is not included in repo as when I tried to install it then it failed with that unable to locate it . root@flyg4:~# apt-get install linux-crashdump Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package linux-crashdump root@flyg4:~# root@flyg4:~# uname -a Linux flyg4 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:29:58 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux root@flyg4:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1341475/+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 1358569] [NEW] ppc64le oopses and userspace process hangs in System V semaphore code
Public bug reported: Canonical have been hitting issues with the System V semaphore code. Sometimes userspace processes would hang, sometimes an oops would pop. We have been able to reproduce this. Michael Ellerman has taken a close look and two fixes have just been merged in the 3.17 merge window: 51d7d5205d33 (powerpc: Add smp_mb() to arch_spin_is_locked()) 78e05b1421fa (powerpc: Add smp_mb()s to arch_spin_unlock_wait()) Could these please be merged into the Utopic and (eventually) the Trusty kernel trees? ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: Incomplete -- 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/1358569 Title: ppc64le oopses and userspace process hangs in System V semaphore code Status in “linux” package in Ubuntu: Incomplete Status in “linux” source package in Trusty: Incomplete Bug description: Canonical have been hitting issues with the System V semaphore code. Sometimes userspace processes would hang, sometimes an oops would pop. We have been able to reproduce this. Michael Ellerman has taken a close look and two fixes have just been merged in the 3.17 merge window: 51d7d5205d33 (powerpc: Add smp_mb() to arch_spin_is_locked()) 78e05b1421fa (powerpc: Add smp_mb()s to arch_spin_unlock_wait()) Could these please be merged into the Utopic and (eventually) the Trusty kernel trees? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358569/+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 1353005] Re: sensors command is not getting executed in Ubuntu 14.10 Non Virtualised environment
It is now upstream, commit: 24c1aa858792 (hwmon: (powerpc/powernv) hwmon driver for power, fan rpm, voltage and temperature) -- 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/1353005 Title: sensors command is not getting executed in Ubuntu 14.10 Non Virtualised environment Status in “linux” package in Ubuntu: Confirmed Bug description: ---Problem Description--- sensors command is not getting executed in Ubuntu 14.10 ---uname output--- Linux lep8d 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P8 ---Steps to Reproduce--- Install Ubuntu 14.10 iso on local hard disk of P8 machine in Non Virtualised environment. Install the lm-sensors ppc64le package on the same. root@lep8d:~# sensors No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. root@lep8d:~# echo $? 1 root@lep8d:~# sensors-detect # sensors-detect revision 6170 (2013-05-20 21:25:22 +0200) # DMI data unavailable, please consider installing dmidecode 2.7 # or later for better results. This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): YES modprobe: FATAL: Module cpuid not found. Failed to load module cpuid. Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors...No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No VIA C7 thermal sensor...No VIA Nano thermal sensor... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): YES Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported. If you find out what chips are on your board, check http://www.lm-sensors.org/wiki/Devices for driver status. After a big more digging I see: in Ubuntu where it is failing, there is: $ cat /boot/config-3.16.0-6-generic | grep -i sensor | grep -i ibm CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m And in PowerKVM where it is working, there is: $ cat /boot/config-3.10.42-2004.pkvm2_1_1.8.ppc64 | grep -i sensors | grep -i ibm CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m CONFIG_SENSORS_IBMPOWERNV=y So now I think problem is: Ubuntu is missing ibmpowernv, i.e. the powernv hwmon driver for sensors, as described here: http://lists.lm-sensors.org/pipermail/lm-sensors/2014-May/041867.html Adding to copy: Neelesh Gupta, who is author of this module. Neelesh: Am I correct that this is the missing module in Ubuntu? Is there a kernel patch Ubuntu needs to pick up, or perhaps they already have the patch but just need to fix their kernel config? Thx -DaveH. Yes, 'ibmpowernv' module is missing from Ubuntu 14.10. It's already been applied to the -next tree and should be available to mainline soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353005/+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 1354459] Re: kernel crash power 8 bare metal
We took an EEH error: [ 44.793204] pnv_pci_dump_phb_diag_data: Unrecognized ioType 33554432 [ 44.793267] EEH: Frozen PE#5 detected on PHB#3 [ 44.793318] CPU: 40 PID: 209 Comm: kworker/40:0 Not tainted 3.13.0-27-generic #50-Ubuntu [ 44.793396] Workqueue: events .work_for_cpu_fn [ 44.793458] Call Trace: [ 44.793487] [c00fe6edb540] [c0016af0] .show_stack+0x170/0x290 (unreliable) [ 44.793575] [c00fe6edb630] [c0966fc0] .dump_stack+0x88/0xb4 [ 44.793651] [c00fe6edb6b0] [c00364b0] .eeh_dev_check_failure+0x430/0x480 [ 44.793737] [c00fe6edb760] [c0036584] .eeh_check_failure+0x84/0xe0 [ 44.793827] [c00fe6edb7f0] [deea33e0] .ipr_mask_and_clear_interrupts+0x190/0x1d0 [ipr] [ 44.793928] [c00fe6edb8a0] [deeaa394] .ipr_probe_ioa+0xc24/0x1370 [ipr] [ 44.794017] [c00fe6edb9d0] [deeb25c4] .ipr_probe+0x44/0x4c0 [ipr] [ 44.794093] [c00fe6edbac0] [c0516cfc] .local_pci_probe+0x4c/0xe0 [ 44.794167] [c00fe6edbb40] [c00bae68] .work_for_cpu_fn+0x38/0x60 [ 44.794242] [c00fe6edbbc0] [c00bf628] .process_one_work+0x1a8/0x4d0 [ 44.794327] [c00fe6edbc60] [c00c04fc] .worker_thread+0x38c/0x4a0 [ 44.794401] [c00fe6edbd30] [c00c98a0] .kthread+0x110/0x130 [ 44.794476] [c00fe6edbe30] [c000a460] .ret_from_kernel_thread+0x5c/0x7c [ 44.794572] EEH: Detected PCI bus error on PHB#3-PE#5 [ 44.794632] EEH: This PCI device has failed 1 times in the last hour [ 44.794693] EEH: Notify device drivers to shutdown [ 44.794749] Unable to handle kernel paging request for data at address 0x0008 [ 44.794821] Faulting instruction address: 0xdeea205c [ 44.794883] Oops: Kernel access of bad area, sig: 11 [#1] [ 44.794931] SMP NR_CPUS=2048 NUMA PowerNV [ 44.794982] Modules linked in: ipr(+) [ 44.795046] CPU: 9 PID: 810 Comm: eehd Not tainted 3.13.0-27-generic #50-Ubuntu [ 44.795120] task: c00fdf7066f0 ti: c00fe33a4000 task.ti: c00fe33a4000 [ 44.795192] NIP: deea205c LR: deea2a14 CTR: c064f720 [ 44.795264] REGS: c00fe33a75b0 TRAP: 0300 Not tainted (3.13.0-27-generic) [ 44.795336] MSR: 90019033 SF,HV,EE,ME,IR,DR,RI,LE CR: 229d0028 XER: 2000 [ 44.795641] CFAR: c0009318 DAR: 0008 DSISR: 4000 SOFTE: 0 GPR00: deea2a14 c00fe33a7830 deec4c58 c00fda20cc60 GPR04: deebc178 0100 90019033 GPR08: 0001 c064f720 GPR12: deeb4978 cfe41f80 c00c9790 c01fd8401600 GPR16: GPR20: c0bf9528 GPR24: c0bf9500 deebc178 0100 GPR28: c00fda20c538 c00fda20c538 [ 44.797447] NIP [deea205c] .ipr_get_free_ipr_cmnd+0x2c/0x90 [ipr] [ 44.797567] LR [deea2a14] ._ipr_initiate_ioa_reset+0xe4/0x130 [ipr] [ 44.797683] Call Trace: [ 44.797736] [c00fe33a78b0] [deea2a14] ._ipr_initiate_ioa_reset+0xe4/0x130 [ipr] [ 44.797900] [c00fe33a7960] [deeab458] .ipr_pci_error_detected+0x1c8/0x230 [ipr] [ 44.798063] [c00fe33a7a00] [c00396bc] .eeh_report_error+0xac/0x120 [ 44.798222] [c00fe33a7a90] [c003840c] .eeh_pe_dev_traverse+0x9c/0x170 [ 44.798382] [c00fe33a7b30] [c0039ce8] .eeh_handle_normal_event+0x128/0x3d0 [ 44.798542] [c00fe33a7bc0] [c0039fd8] .eeh_handle_event+0x48/0x2f0 [ 44.798702] [c00fe33a7c70] [c003a39c] .eeh_event_handler+0x11c/0x1d0 [ 44.798862] [c00fe33a7d30] [c00c98a0] .kthread+0x110/0x130 [ 44.799000] [c00fe33a7e30] [c000a460] .ret_from_kernel_thread+0x5c/0x7c [ 44.799158] Instruction dump: [ 44.799225] 6042 7c0802a6 fbe1fff8 f8010010 f821ff81 7c7f1b78 4808 e8410028 [ 44.799453] 7fe3fb78 e9230729 7fa91840 41de0058 e8e90008 e8c9 3d10 3d400020 [ 44.799678] ---[ end trace 7439fee11bbab045 ]--- This is usually a sign of bad hardware. EEH was not ported for 3.13 but should work on 3.16. -- 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/1354459 Title: kernel crash power 8 bare metal Status in “linux” package in Ubuntu: Incomplete Bug description: I'm seeing crashes on power8 bare metal (powerNV). happens sometimes. [ 66.852889] Workqueue: events .work_for_cpu_fn [ 66.852950] Call Trace: [ 66.852977] [c00fe6edae60] [c0016af0] .show_stack+0x170/0x290 (unreliable) [ 66.853063] [c00fe6edaf50] [c0966fc0] .dump_stack+0x88/0xb4 [ 66.853138] [c00fe6edafd0] [c0111680]
[Kernel-packages] [Bug 1354459] Re: kernel crash power 8 bare metal
I spoke to Gavin about this: 1. EEH has endian issues in 3.13 should work in 3.16. (EEH is our I/O error recovery mechanism) 2. There was an issue in the IPR driver with early EEH errors, fixed in 3.15 with commit 6270e5932a01 [SCSI] ipr: Handle early EEH Would it be possible to update to the Utopic kernel? -- 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/1354459 Title: kernel crash power 8 bare metal Status in “linux” package in Ubuntu: Incomplete Bug description: I'm seeing crashes on power8 bare metal (powerNV). happens sometimes. [ 66.852889] Workqueue: events .work_for_cpu_fn [ 66.852950] Call Trace: [ 66.852977] [c00fe6edae60] [c0016af0] .show_stack+0x170/0x290 (unreliable) [ 66.853063] [c00fe6edaf50] [c0966fc0] .dump_stack+0x88/0xb4 [ 66.853138] [c00fe6edafd0] [c0111680] .rcu_check_callbacks+0x5b0/0x950 [ 66.853225] [c00fe6edb100] [c00ad2f8] .update_process_times+0x58/0xb0 [ 66.853311] [c00fe6edb190] [c011f890] .tick_sched_handle.isra.17+0x40/0xd0 [ 66.853397] [c00fe6edb220] [c011f984] .tick_sched_timer+0x64/0xa0 [ 66.853472] [c00fe6edb2c0] [c00cda50] .__run_hrtimer+0xa0/0x270 [ 66.853546] [c00fe6edb360] [c00ce948] .hrtimer_interrupt+0x148/0x330 [ 66.853633] [c00fe6edb470] [c0020a00] .timer_interrupt+0x120/0x2c0 [ 66.853718] [c00fe6edb520] [c00023d8] decrementer_common+0x158/0x180 [ 66.853805] --- Exception: 901 at ._raw_spin_lock_irqsave+0xb0/0x110 [ 66.853805] LR = ._raw_spin_lock_irqsave+0xe8/0x110 [ 66.853916] [c00fe6edb810] [c00f0cb4] .finish_wait+0x74/0xb0 (unreliable) [ 66.854008] [c00fe6edb8a0] [deeaa4f4] .ipr_probe_ioa+0xd84/0x1370 [ipr] [ 66.854096] [c00fe6edb9d0] [deeb25c4] .ipr_probe+0x44/0x4c0 [ipr] [ 66.854171] [c00fe6edbac0] [c0516cfc] .local_pci_probe+0x4c/0xe0 [ 66.854245] [c00fe6edbb40] [c00bae68] .work_for_cpu_fn+0x38/0x60 [ 66.854319] [c00fe6edbbc0] [c00bf628] .process_one_work+0x1a8/0x4d0 [ 66.854405] [c00fe6edbc60] [c00c04fc] .worker_thread+0x38c/0x4a0 [ 66.854479] [c00fe6edbd30] [c00c98a0] .kthread+0x110/0x130 [ 66.854553] [c00fe6edbe30] [c000a460] .ret_from_kernel_thread+0x5c/0x7c [ 72.412653] BUG: soft lockup - CPU#40 stuck for 22s! [kworker/40:0:209] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354459/+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 1353377] Re: ISST-KVM-UBUNTU1410-LE:kidkvm:ubuntu guest crash running IO stress tests.
zram: Created 1 device(s) ... zram0: detected capacity change from 0 to 536870912 zram0: detected capacity change from 536870912 to 0 [ cut here ] WARNING: at /build/buildd/linux-3.16.0/block/blk-mq.c:727 Modules linked in: lz4_compress rpcsec_gss_krb5 nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache bochs_drm ttm drm_kms_helper drm syscopyarea sysfillrect pseries_rng sysimgblt rtc_generic ohci_pci [last unloaded: zram] zram driver got loaded, resized to 512M, resized back to 0 and unloaded. Can you show us what you are running that did this? -- 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/1353377 Title: ISST-KVM-UBUNTU1410-LE:kidkvm:ubuntu guest crash running IO stress tests. Status in “linux” package in Ubuntu: Confirmed Bug description: Problem Description - ubuntu guest crash running IO stress tests. uname output - uname -a Linux kidg1 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux System Hang System hangs/crashed . Steps to reproduce 1) Used below XML to define the guest [root@kidkvm ~]# virsh dumpxml kidg1 domain type='kvm' id='28' namekidg1/name uuid86748b80-a84b-4c70-b1b3-d2a23d88c7ab/uuid memory unit='KiB'4194304/memory currentMemory unit='KiB'4194304/currentMemory vcpu placement='static'4/vcpu cputune vcpupin vcpu='0' cpuset='0,8'/ vcpupin vcpu='1' cpuset='24,32'/ vcpupin vcpu='2' cpuset='0,40'/ /cputune numatune memory mode='strict' nodeset='0'/ /numatune resource partition/machine/partition /resource os type arch='ppc64' machine='pseries'hvm/type boot dev='hd'/ bootmenu enable='yes'/ /os features acpi/ apic/ /features cpu mode='custom' match='exact' model fallback='allow'power8/model topology sockets='1' cores='2' threads='2'/ /cpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/qemu-system-ppc64/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/kidg1_GTOdisk/kidg1-1a.img'/ target dev='sda' bus='scsi'/ alias name='scsi0-0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/kidg1_SRAID1/kidg1-1SR.img'/ target dev='sdb' bus='scsi'/ alias name='scsi0-0-0-1'/ address type='drive' controller='0' bus='0' target='0' unit='1'/ /disk disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/kidg1_SRAID1/kidg1-2SR.img'/ target dev='vda' bus='virtio'/ alias name='virtio-disk0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /controller controller type='pci' index='0' model='pci-root' alias name='pci.0'/ /controller controller type='scsi' index='0' alias name='scsi0'/ address type='spapr-vio' reg='0x2000'/ /controller interface type='bridge' mac address='52:54:00:f2:d3:e2'/ source bridge='brenP3p5s0f0'/ target dev='vnet3'/ model type='virtio'/ driver name='qemu'/ alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x0'/ /interface serial type='pty' source path='/dev/pts/1'/ target port='0'/ alias name='serial0'/ address type='spapr-vio' reg='0x3000'/ /serial console type='pty' tty='/dev/pts/1' source path='/dev/pts/1'/ target type='serial' port='0'/ alias name='serial0'/ address type='spapr-vio' reg='0x3000'/ /console video model type='vga' vram='9216' heads='1'/ alias name='video0'/ /video memballoon model='none' alias name='balloon0'/ /memballoon /devices seclabel type='none' model='selinux'/ /domain 2) Defined guest xml and started console to start the installation. 3) Installation succeded. 4) Guest is up and running as below [root@magkvm ~]# virsh list --all IdName State 26 kidg1running 5) Initiated IO and BASE stress tests
[Kernel-packages] [Bug 1304754] Re: gccgo compiled binaries are killed by SEGV on 64k ppc64el kernels
Based on the fail, I took a look at how gccgo handles stacks. It relies on the split stack feature in gold, which doesn't appear to be implemented for ppc64. Running one of the go recursion testcases (attached) shows what happens when we run out of stack and don't have the split stack feature to save us: #gccgo -g -O2 -o peano peano.go # ./peano Segmentation fault And we get the setup_rt_frame error in dmesg: peano[4538]: bad frame in setup_rt_frame: 00c20ff7f000 nip 10001018 lr 10001024 As expected, we are just continually recurse without checking out stack pointer for overflow: 0x10001008 +8: cmpdi r3,0 0x1000100c +12:beq 0x10001040 main.count+64 0x10001010 +16:mflrr0 0x10001014 +20:std r0,16(r1) 0x10001018 +24:stdur1,-32(r1) 0x1000101c +28:ld r3,0(r3) 0x10001020 +32:bl 0x10001008 main.count+8 ** Attachment added: peano.go https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304754/+attachment/4079310/+files/peano.go -- 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/1304754 Title: gccgo compiled binaries are killed by SEGV on 64k ppc64el kernels Status in “linux” package in Ubuntu: Incomplete Bug description: On kernels 3.13-18 and 3.13-23 (there may be others) the kernel is killing gccgo compiled binaries [18519.444748] jujud[19277]: bad frame in setup_rt_frame: nip lr [18519.673632] init: juju-agent-ubuntu-local main process (19220) killed by SEGV signal [18519.673651] init: juju-agent-ubuntu-local main process ended, respawning In powerpc/kernel/signal_64.c: sys_rt_sigreturn is jumping to the badframe: label and executing an unconditional force_sigsegv which is delivered to the userland process. Like C++, gccgo tries to decode SIGSEGV as a nil pointer access and blame some random function that happened to be the top stack frame. Reverting to the 3.13-08 kernel appears to resolve the issue which (weakly) points the finger at the recent switch to 64k pages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304754/+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 1301496] Re: kernel crash: Unable to handle kernel paging request for data
Lots going on here. First looking at the syslog file from Matt. I notice a lot of: Apr 3 20:57:45 wolfe-01 kernel: [ 4062.074422] jujud[1929]: bad frame in setup_rt_frame: nip lr Looks like we smashed our stack. This seems to be a separate issue because we continue on even after these failures. At some point dpkg-query starts SEGVing: Apr 3 20:57:54 wolfe-01 kernel: [ 4071.263070] dpkg-query[20115]: unhandled signal 11 at 00010028 nip 10003380 lr 10002968 code 30001 Apr 3 20:57:57 wolfe-01 kernel: [ 4074.437029] dpkg-query[20208]: unhandled signal 11 at 00010028 nip 10003380 lr 10002968 code 30001 Apr 3 20:58:00 wolfe-01 kernel: [ 4077.612284] dpkg-query[20291]: unhandled signal 11 at 00010028 nip 10003380 lr 10002968 code 30001 -- 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/1301496 Title: kernel crash: Unable to handle kernel paging request for data Status in “linux” package in Ubuntu: Confirmed Bug description: We've seen this happen twice now on ppc64el guests that are probably under load. I don't have a lot of the details on what was going on when they failed, but I have the stack traces. [101168.836780] Unable to handle kernel paging request for data at address 0x00010001 [101168.836886] Faulting instruction address: 0xc0954b60 [101168.836934] Oops: Kernel access of bad area, sig: 11 [#1] [101168.836971] SMP NR_CPUS=2048 NUMA pSeries [101168.837020] Modules linked in: veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables dm_crypt [101168.837234] CPU: 1 PID: 19760 Comm: kworker/u4:0 Not tainted 3.13.0-8-generic #28-Ubuntu [101168.837294] Workqueue: netns .cleanup_net [101168.837332] task: c003f99d43e0 ti: c001cce44000 task.ti: c001cce44000 [101168.837386] NIP: c0954b60 LR: c0954b68 CTR: c0954b00 [101168.837439] REGS: c001cce47760 TRAP: 0300 Not tainted (3.13.0-8-generic) [101168.837493] MSR: 80009033 SF,EE,ME,IR,DR,RI,LE CR: 24002024 XER: [101168.837620] CFAR: 1063ea4c DAR: 00010001 DSISR: 4000 SOFTE: 1 GPR00: c0954b68 c001cce479e0 c10b0dd0 00010001 GPR04: f99918f0 c002be072380 c0954b68 c003fe023508 GPR08: 0001 c00209fc 000e 0001 GPR12: 44002028 cfe80300 c00c3f00 c002be1e8bc0 GPR16: GPR20: 0001 c0f630fc GPR24: 0001 fef7 c0f58638 GPR28: 0001 c003fbdc 2000 [101168.838355] NIP [c0954b60] .tcp_net_metrics_exit+0x60/0x110 [101168.838402] LR [c0954b68] .tcp_net_metrics_exit+0x68/0x110 [101168.838448] Call Trace: [101168.838469] [c001cce479e0] [c0954b68] .tcp_net_metrics_exit+0x68/0x110 (unreliable) [101168.838542] [c001cce47a70] [c08cc49c] .ops_exit_list.isra.2+0x6c/0xd0 [101168.838605] [c001cce47b00] [c08ccef0] .cleanup_net+0x150/0x250 [101168.838662] [c001cce47bc0] [c00b9e28] .process_one_work+0x1a8/0x4d0 [101168.838726] [c001cce47c60] [c00baaf0] .worker_thread+0x180/0x4a0 [101168.838783] [c001cce47d30] [c00c4010] .kthread+0x110/0x130 [101168.838841] [c001cce47e30] [c000a160] .ret_from_kernel_thread+0x5c/0x7c [101168.838903] Instruction dump: [101168.838940] 7d295030 2f89 e93d0288 419e0058 3bc0 3b81 6000 6042 [101168.839031] 7bc81f24 7c69402a 2fa3 419e0024 ebe3 4b8b809d 6000 2fbf [101168.839127] ---[ end trace fb028b2b5c006a6a ]--- --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14-0ubuntu1 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-3.13.0-19-generic root=UUID=19eaa2f9-0f24-49b9-ba48-24879242481c ro console=hvc0 earlyprintk ProcVersionSignature: User Name
[Kernel-packages] [Bug 1267707] Re: Logging in to ubuntu guest is displaying (none) in the command prompt
That image has massive filesystem corruption, it looks like it was uncleanly shut down. ** Changed in: linux (Ubuntu) Status: Confirmed = Invalid -- 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/1267707 Title: Logging in to ubuntu guest is displaying (none) in the command prompt Status in “cloud-init” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Bug description: Description: - Used below qemu command to open the guest , qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G -nographic -nodefaults -monitor stdio -serial pty -append root=/dev/sda -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic -device spapr-vscsi -device spapr-vlan,netdev=net0,mac=52:54:00:b3:2d:f8 -netdev bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg-ppc64el.img.qcow2 got as below (qemu) char device redirected to /dev/pts/2 (label serial0) when opening screen for /dev/pts/2 using screen /dev/pts/2 from host, It displayed the below error continuosly 2014-01-10 04:40:35,082 - util.py[WARNING]: Failed writing semaphore file /var/lib/cloud/instances/iid-datasource-none/sem/config_set_passwords 2014-01-10 04:40:35,083 - util.py[WARNING]: Running set-passwords (module 'cloudinit.config.cc_set_passwords' from '/usr/lib/python2.7/dist-packages/cloudinit/config/cc_set_passwords.pyc') failed Later after on opening another screen using new qemu command I got the login prompt. But the issue is .., On logging in to guest we getubuntu@ubuntu:~$but now i am getting ubuntu@(none):~$ after logging in. also as root its diplaying root@(none):~# instaead of root@ubuntu:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1267707/+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 1266399] Re: ext4-fs error messages pop up on command line
Your filesystem is corrupt, and based on previous bugs I suspect you may have corrupted it by running QEMU twice against the one qcow file. ** Changed in: linux (Ubuntu Trusty) Status: Confirmed = Incomplete -- 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/1266399 Title: ext4-fs error messages pop up on command line Status in “linux” package in Ubuntu: Incomplete Status in “linux” source package in Trusty: Incomplete Bug description: Description: === Adhoc ext4-fs errors seen on the command line: No particular pattern observed, pops up adhocly. EXT4-fs error (device sda): mb_free_blocks:1433: group 5, block 196603:freeing already freed block (bit 32763); block bitmap corrupt. EXT4-fs error (device sda): ext4_mb_generate_buddy:756: group 5, 3442 clusters in bitmap, 3444 in gd; block bitmap corrupt. Environment: Host: Power8 Guest : ubuntu hosted on Power8 Command line to spawn the ubuntu guest: qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G -nographic -nodefaults -monitor stdio -serial pty -append root=/dev/sda -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic -device spapr-vscsi -device spapr-vlan,netdev=net0,mac=6c:ae:8b:69:16:11 -netdev bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg-ppc64el.img.qcow2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266399/+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 1267707] Re: Logging in to ubuntu guest is displaying (none) in the command prompt
** Changed in: cloud-init (Ubuntu) Status: New = Invalid -- 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/1267707 Title: Logging in to ubuntu guest is displaying (none) in the command prompt Status in “cloud-init” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Bug description: Description: - Used below qemu command to open the guest , qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G -nographic -nodefaults -monitor stdio -serial pty -append root=/dev/sda -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic -device spapr-vscsi -device spapr-vlan,netdev=net0,mac=52:54:00:b3:2d:f8 -netdev bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg-ppc64el.img.qcow2 got as below (qemu) char device redirected to /dev/pts/2 (label serial0) when opening screen for /dev/pts/2 using screen /dev/pts/2 from host, It displayed the below error continuosly 2014-01-10 04:40:35,082 - util.py[WARNING]: Failed writing semaphore file /var/lib/cloud/instances/iid-datasource-none/sem/config_set_passwords 2014-01-10 04:40:35,083 - util.py[WARNING]: Running set-passwords (module 'cloudinit.config.cc_set_passwords' from '/usr/lib/python2.7/dist-packages/cloudinit/config/cc_set_passwords.pyc') failed Later after on opening another screen using new qemu command I got the login prompt. But the issue is .., On logging in to guest we getubuntu@ubuntu:~$but now i am getting ubuntu@(none):~$ after logging in. also as root its diplaying root@(none):~# instaead of root@ubuntu:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1267707/+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 1266419] Re: Not able to install any packages using dpkg command
Looks fine now, closing ** Changed in: linux (Ubuntu Trusty) Status: Confirmed = Fix Released -- 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/1266419 Title: Not able to install any packages using dpkg command Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Released Bug description: Install a Ubuntu 14.04 alpha1 image as a KVM guest on a Power 8 machine. Then copied some .deb packages to the Ubuntu guest and tried to install them locally as below: ubuntu:/home/ubuntu# sudo dpkg --install libcap-dev_2.22-1.2ubuntu2_ppc64el. EXT4-fs error (device sda): ext4_ext_find_extent:859: inode #54870: comm dpkg: pblk 16257 bad header/extent: invalid magic - magic f1, entries 0, max 1(0), depth 0(0) dpkg: error: unable to create new file '/var/lib/dpkg/info/format-new': Input/output error root@ubuntu:/home/ubuntu# We keep on getting the below messages in dmesg output: EXT3-fs (sda): error: couldn't mount because of unsupported optional features (240) EXT2-fs (sda): error: couldn't mount because of unsupported optional features (244) EXT4-fs (sda): INFO: recovery required on readonly filesystem EXT4-fs (sda): write access will be enabled during recovery EXT4-fs (sda): recovery complete EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: (null) VFS: Mounted root (ext4 filesystem) readonly on device 8:0. devtmpfs: mounted Freeing unused kernel memory: 568K (c0e11000 - c0e9f000) random: init urandom read with 59 bits of entropy available usb 1-1: new full-speed USB device number 2 using ohci-pci input: QEMU QEMU USB Keyboard as /devices/pci:00/:00:02.0/usb1/1-1/1-1:1.0/input/input0 hid-generic 0003:0627:0001.0001: input,hidraw0: USB HID v1.11 Keyboard [QEMU QEMU USB Keyboard] on usb-:00:02.0-1/input0 usb 1-2: new full-speed USB device number 3 using ohci-pci input: QEMU QEMU USB Mouse as /devices/pci:00/:00:02.0/usb1/1-2/1-2:1.0/input/input1 hid-generic 0003:0627:0001.0002: input,hidraw1: USB HID v0.01 Mouse [QEMU QEMU USB Mouse] on usb-:00:02.0-2/input0 IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready init: console-setup main process (210) terminated with status 1 systemd-udevd[230]: starting version 204 random: nonblocking pool is initialized Request for unknown module key 'Magrathea: Glacier signing key: b7c7bf4bb6b278097421a6e76607cb13eb5cebf9' err -11 rtc_generic: disagrees about version of symbol module_layout type=1400 audit(1388171630.212:2): apparmor=STATUS operation=profile_load name=/sbin/dhclient pid=257 comm=apparmor_parser type=1400 audit(1388171630.212:3): apparmor=STATUS operation=profile_load name=/usr/lib/NetworkManager/nm-dhcp-client.action pid=257 comm=apparmor_parser type=1400 audit(1388171630.212:4): apparmor=STATUS operation=profile_load name=/usr/lib/connman/scripts/dhclient-script pid=257 comm=apparmor_parser type=1400 audit(1388171630.212:5): apparmor=STATUS operation=profile_replace name=/usr/lib/NetworkManager/nm-dhcp-client.action pid=257 comm=apparmor_parser type=1400 audit(1388171630.212:6): apparmor=STATUS operation=profile_replace name=/usr/lib/connman/scripts/dhclient-script pid=257 comm=apparmor_parser type=1400 audit(1388171630.222:7): apparmor=STATUS operation=profile_replace name=/usr/lib/connman/scripts/dhclient-script pid=257 comm=apparmor_parser IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Request for unknown module key 'Magrathea: Glacier signing key: b7c7bf4bb6b278097421a6e76607cb13eb5cebf9' err -11 pseries_rng: disagrees about version of symbol module_layout EXT4-fs (sda): warning: mounting fs with errors, running e2fsck is recommended EXT4-fs (sda): re-mounted. Opts: (null) Request for unknown module key 'Magrathea: Glacier signing key: b7c7bf4bb6b278097421a6e76607cb13eb5cebf9' err -11 dm_crypt: disagrees about version of symbol module_layout init: plymouth main process (102) killed by ABRT signal init: plymouth-splash main process (339) terminated with status 2 init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Request for unknown module key 'Magrathea: Glacier signing key: b7c7bf4bb6b278097421a6e76607cb13eb5cebf9' err -11 nfsd: disagrees about version of symbol module_layout init: plymouth-log main process (520) terminated with status 1 init: plymouth-upstart-bridge main process (578) terminated with status 1 init: failsafe main process (527) killed by TERM signal Request for unknown module key 'Magrathea: Glacier signing key: b7c7bf4bb6b278097421a6e76607cb13eb5cebf9' err -11 dm_crypt: disagrees about version of symbol module_layout type=1400
[Kernel-packages] [Bug 1267712] Re: ubuntu guest's file system becoming read only
Massive amounts of file corruption, it looks like you were running LTP at the time. Did you forcibly shutdown the partition? ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- 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/1267712 Title: ubuntu guest's file system becoming read only Status in “linux” package in Ubuntu: Incomplete Bug description: 9.3.189.114 (root/.pasroot) (Host Machine) Run the follwoing command to go to the guest victim machine from (/var/lib/libvirt/images/jagan/new_ubuntu_alpha1) qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G -nographic -nodefaults -monitor stdio -serial pty -append root=/dev/sda -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic -device spapr-vscsi -device spapr- vlan,netdev=net0,mac=6c:ae:8b:69:16:15 -netdev bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg- ppc64el.img.qcow2 after this command you will get the screen number. example: QEMU 1.6.0 monitor - type 'help' for more information (qemu) char device redirected to /dev/pts/16 (label serial0) Then open another host session and execute the below command # screen /dev/pts/16 (qemu) Here the screen number is /dev/pts/16 --Then you will get a blank screen so press ENTER key. The guest machine login: ubuntu/passw0rd Then do ---sudo -i Environment: === Host: Power8 Guest : ubuntu hosted on Power8 The issue: == After logging into the guest some times it becomes read - only file system. Description: === Here i am not able to create directory or a file. root@ubuntu:/opt/ltp# cat /etc/issue Ubuntu Trusty Tahr (development branch) \n \l=ubuntu guest root@ubuntu:~# ifconfig eth0 Link encap:Ethernet HWaddr 6c:ae:8b:69:16:15 inet addr:192.168.122.131 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::6eae:8bff:fe69:1615/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:72 errors:0 dropped:4 overruns:0 frame:0 TX packets:43 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6764 (6.7 KB) TX bytes:3914 (3.9 KB) Interrupt:22 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@ubuntu:/opt/ltp# ./runltp -f timers -p -l timers.log -o timers.out cat: /opt/ltp/Version: No such file or directory INFO: creating /opt/ltp/results directory mktemp: failed to create directory via template â/tmp/ltp-XXâ: Read-only file system==error FATAL: Unable to make temporary directory: root@ubuntu:/opt/ltp# df -k Filesystem 1K-blocksUsed Available Use% Mounted on /dev/sda51573372 1303052 47632556 3% / none 4 0 4 0% /sys/fs/cgroup devtmpfs 5161908 296 5161612 1% /dev none 1032440 184 1032256 1% /run none5120 0 5120 0% /run/lock none 5162192 0 5162192 0% /run/shm none 102400 0102400 0% /run/user root@ubuntu:/opt/ltp# mkdir -m 777 jagan mkdir: cannot create directory âjaganâ: Read-only file systemerror root@ubuntu:/opt/ltp# touch jagan touch: cannot touch âjaganâ: Read-only file systemerror To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1267712/+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 1265722] Re: ppc64el: 14.04 alpha 1 build has call traces -- ERROR: Bad of_node_put() on /pci@800000020000000
** Patch added: of-irq-Fix-device_node-refcount-in-of_irq_parse_raw.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265722/+attachment/3941691/+files/of-irq-Fix-device_node-refcount-in-of_irq_parse_raw.patch -- 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/1265722 Title: ppc64el: 14.04 alpha 1 build has call traces -- ERROR: Bad of_node_put() on /pci@8002000 Status in “linux” package in Ubuntu: Triaged Bug description: Install Ubuntu ppc64el guest image on Power 8 machine using kvm invocation. [root@lep8a Ubuntu_alpha1]# qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp cores=4,threads=1 -m 70G -nographic -append earlyprintk root=/dev/sda console=hvc0 --no-sessions -kernel trusty- server-cloudimg-ppc64el-vmlinuz-generic -device spapr-vscsi -drive file=trusty-server-cloudimg-ppc64el.img.qcow2 -net nic,model=e1000 -net tap,ifname=tap0,script=qemu-ifup,downscript=no Ubuntu Trusty Tahr (development branch) ubuntu hvc0 ubuntu login: ubuntu Password: Last login: Tue Dec 24 18:09:11 UTC 2013 on hvc0 Welcome to Ubuntu Trusty Tahr (development branch) (GNU/Linux 3.13.0-0-generic ppc64le) * Documentation: https://help.ubuntu.com/ System information as of Tue Dec 24 18:09:11 UTC 2013 System load: 0.0 Processes: 86 Usage of /: 1.4% of 49.18GB Users logged in: 0 Memory usage: 0%IP address for eth0: 9.3.189.185 Swap usage: 0% Graph this data and manage this system at: https://landscape.canonical.com/ Get cloud support with Ubuntu Advantage Cloud Guest: http://www.ubuntu.com/business/services/cloud 0 packages can be updated. 0 updates are security updates. ubuntu@ubuntu:~$ dmesg | more IOMMU table initialized, virtual merging enabled ERROR: Bad of_node_put() on /pci@8002000 CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.13.0-0-generic #10+ppc64el-Ubuntu Call Trace: [c0117118b570] [c001553c] .show_stack+0x7c/0x1f0 (unreliable) [c0117118b640] [c09fc480] .dump_stack+0x88/0xb4 [c0117118b6c0] [c0854818] .of_node_release+0xd8/0xf0 [c0117118b750] [c085a2fc] .of_irq_parse_one+0x13c/0x1f0 [c0117118b800] [c085b42c] .of_irq_parse_pci+0x3c/0x1d0 [c0117118b8a0] [c003abbc] .pcibios_setup_device+0x8c/0x190 [c0117118b970] [c003bfa0] .pcibios_setup_bus_devices+0x50/0x80 [c0117118b9f0] [c003d4a4] .__of_scan_bus+0x114/0x1b0 [c0117118baa0] [c003ca1c] .pcibios_scan_phb+0x27c/0x2f0 [c0117118bb60] [c0e1f2c4] .pcibios_init+0x80/0xd8 [c0117118bbf0] [c000bf84] .do_one_initcall+0x154/0x1b0 [c0117118bce0] [c0e14e30] .kernel_init_freeable+0x25c/0x33c [c0117118bdb0] [c000c73c] .kernel_init+0x1c/0x160 [c0117118be30] [c000a160] .ret_from_kernel_thread+0x5c/0x7c PCI: Probing PCI hardware done The above call trace is got in the dmesg output. ubuntu@ubuntu:~$ dpkg --list | grep kernel ii kmod 15-0ubuntu5 ppc64el tools for managing Linux kernel modules ii libdrm2:ppc64el 2.4.50-1 ppc64el Userspace interface to kernel DRM services -- runtime ii linux-headers-3.13.0-0 3.13.0-0.10+ppc64el all Header files related to Linux kernel version 3.13.0 ii linux-headers-3.13.0-0-generic 3.13.0-0.10+ppc64el ppc64el Linux kernel headers for version 3.13.0 on PowerPC 64el SMP ii linux-headers-generic3.13.0.0.1+ppc64el3 ppc64el Generic Linux kernel headers ii linux-image-3.13.0-0-generic 3.13.0-0.10+ppc64el ppc64el Linux kernel image for version 3.13.0 on PowerPC 64el SMP ii linux-image-virtual 3.13.0.0.1+ppc64el3 ppc64el This package will always depend on the latest minimal generic kernel image. ii linux-virtual3.13.0.0.1+ppc64el3 ppc64el Minimal Generic Linux kernel and headers ii rsyslog 7.4.4-1ubuntu2 ppc64el reliable system and kernel logging daemon ubuntu@ubuntu:~$ uname -a Linux ubuntu 3.13.0-0-generic #10+ppc64el-Ubuntu SMP Tue Dec 24 10:56:51 UTC 2013 ppc64le ppc64le ppc64le GNU/Linux ubuntu@ubuntu:~$ lsb_release -rd Description:Ubuntu Trusty Tahr (development branch) Release:14.04 ubuntu@ubuntu:~$ apt-cache policy pkgname N: Unable to locate package pkgname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265722/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1265722] Re: ppc64el: 14.04 alpha 1 build has call traces -- ERROR: Bad of_node_put() on /pci@800000020000000
Looks like a known upstream issue. A fix has been submitted: http://patchwork.ozlabs.org/patch/302312/ -- 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/1265722 Title: ppc64el: 14.04 alpha 1 build has call traces -- ERROR: Bad of_node_put() on /pci@8002000 Status in “linux” package in Ubuntu: Triaged Bug description: Install Ubuntu ppc64el guest image on Power 8 machine using kvm invocation. [root@lep8a Ubuntu_alpha1]# qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp cores=4,threads=1 -m 70G -nographic -append earlyprintk root=/dev/sda console=hvc0 --no-sessions -kernel trusty- server-cloudimg-ppc64el-vmlinuz-generic -device spapr-vscsi -drive file=trusty-server-cloudimg-ppc64el.img.qcow2 -net nic,model=e1000 -net tap,ifname=tap0,script=qemu-ifup,downscript=no Ubuntu Trusty Tahr (development branch) ubuntu hvc0 ubuntu login: ubuntu Password: Last login: Tue Dec 24 18:09:11 UTC 2013 on hvc0 Welcome to Ubuntu Trusty Tahr (development branch) (GNU/Linux 3.13.0-0-generic ppc64le) * Documentation: https://help.ubuntu.com/ System information as of Tue Dec 24 18:09:11 UTC 2013 System load: 0.0 Processes: 86 Usage of /: 1.4% of 49.18GB Users logged in: 0 Memory usage: 0%IP address for eth0: 9.3.189.185 Swap usage: 0% Graph this data and manage this system at: https://landscape.canonical.com/ Get cloud support with Ubuntu Advantage Cloud Guest: http://www.ubuntu.com/business/services/cloud 0 packages can be updated. 0 updates are security updates. ubuntu@ubuntu:~$ dmesg | more IOMMU table initialized, virtual merging enabled ERROR: Bad of_node_put() on /pci@8002000 CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.13.0-0-generic #10+ppc64el-Ubuntu Call Trace: [c0117118b570] [c001553c] .show_stack+0x7c/0x1f0 (unreliable) [c0117118b640] [c09fc480] .dump_stack+0x88/0xb4 [c0117118b6c0] [c0854818] .of_node_release+0xd8/0xf0 [c0117118b750] [c085a2fc] .of_irq_parse_one+0x13c/0x1f0 [c0117118b800] [c085b42c] .of_irq_parse_pci+0x3c/0x1d0 [c0117118b8a0] [c003abbc] .pcibios_setup_device+0x8c/0x190 [c0117118b970] [c003bfa0] .pcibios_setup_bus_devices+0x50/0x80 [c0117118b9f0] [c003d4a4] .__of_scan_bus+0x114/0x1b0 [c0117118baa0] [c003ca1c] .pcibios_scan_phb+0x27c/0x2f0 [c0117118bb60] [c0e1f2c4] .pcibios_init+0x80/0xd8 [c0117118bbf0] [c000bf84] .do_one_initcall+0x154/0x1b0 [c0117118bce0] [c0e14e30] .kernel_init_freeable+0x25c/0x33c [c0117118bdb0] [c000c73c] .kernel_init+0x1c/0x160 [c0117118be30] [c000a160] .ret_from_kernel_thread+0x5c/0x7c PCI: Probing PCI hardware done The above call trace is got in the dmesg output. ubuntu@ubuntu:~$ dpkg --list | grep kernel ii kmod 15-0ubuntu5 ppc64el tools for managing Linux kernel modules ii libdrm2:ppc64el 2.4.50-1 ppc64el Userspace interface to kernel DRM services -- runtime ii linux-headers-3.13.0-0 3.13.0-0.10+ppc64el all Header files related to Linux kernel version 3.13.0 ii linux-headers-3.13.0-0-generic 3.13.0-0.10+ppc64el ppc64el Linux kernel headers for version 3.13.0 on PowerPC 64el SMP ii linux-headers-generic3.13.0.0.1+ppc64el3 ppc64el Generic Linux kernel headers ii linux-image-3.13.0-0-generic 3.13.0-0.10+ppc64el ppc64el Linux kernel image for version 3.13.0 on PowerPC 64el SMP ii linux-image-virtual 3.13.0.0.1+ppc64el3 ppc64el This package will always depend on the latest minimal generic kernel image. ii linux-virtual3.13.0.0.1+ppc64el3 ppc64el Minimal Generic Linux kernel and headers ii rsyslog 7.4.4-1ubuntu2 ppc64el reliable system and kernel logging daemon ubuntu@ubuntu:~$ uname -a Linux ubuntu 3.13.0-0-generic #10+ppc64el-Ubuntu SMP Tue Dec 24 10:56:51 UTC 2013 ppc64le ppc64le ppc64le GNU/Linux ubuntu@ubuntu:~$ lsb_release -rd Description:Ubuntu Trusty Tahr (development branch) Release:14.04 ubuntu@ubuntu:~$ apt-cache policy pkgname N: Unable to locate package pkgname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265722/+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
