[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
Do you have anything connects to the USB type-c or thunderbolt port? Can you try disable thunderbolt in the BIOS and check if this still happens? -- 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/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+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 1718107] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1718107 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => 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/1718107 Title: brk_near_huge test will hang on IBM s390x zKVM / zVM Status in linux package in Ubuntu: Incomplete Bug description: Steps: 1. Clone git://kernel.ubuntu.com/ubuntu/autotest-client-tests 2. Untar libhugetlbfs/libhugetlbfs-2.20.tar.gz 3. Run `sudo BUILDTYPE=NATIVEONLY make check` in the extracted libhugetlbfs-2.20 directory 4. Hit Ctrl + C to terminate it From the output you will see it get stuck: truncate_above_4GB (1024K: 64): PASS brk_near_huge (1024K: 64):brk_near_huge: malloc.c:2427: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed. task-size-overrun (1024K: 64): From the syslog you can see brk_near_huge has crashed: Sep 19 07:28:25 s2lp6g004 rsyslogd-2007: action 'action 10' suspended, next retry is Tue Sep 19 07:29:55 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Application brk_near_huge, PID 10474 crashed Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Writing core files to ['/home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.brk_near_huge.10474'] Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Could not determine from which application core file /home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.brk_near_huge.10474/core is from After hitting Ctrl + C to interrupt, kernel trace could be found in syslog: Sep 19 07:30:02 s2lp6g004 kernel: [11224.325504] report_user_fault: 35 callbacks suppressed Sep 19 07:30:02 s2lp6g004 kernel: [11224.325507] User process fault: interruption code 0010 ilc:3 in stack_grow_into_huge[12f88+4000] Sep 19 07:30:02 s2lp6g004 kernel: [11224.325520] Failing address: 03ffe72fe000 TEID: 03ffe72fe400 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325521] Fault in primary space mode while using user ASCE. Sep 19 07:30:02 s2lp6g004 kernel: [11224.325523] AS:551701c7 R3:48d88007 S:0020 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325527] CPU: 0 PID: 10481 Comm: stack_grow_into Tainted: P DO4.13.0-11-generic #12-Ubuntu Sep 19 07:30:02 s2lp6g004 kernel: [11224.325527] Hardware name: IBM 2964 N63 400 (KVM/Linux) Sep 19 07:30:02 s2lp6g004 kernel: [11224.325528] task: 6245 task.stack: 62b3c000 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325529] User PSW : 070530018000 00012f8819a8 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325530]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:3 PM:0 RI:0 EA:3 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325531] User GPRS: 02001c51e2f8 f000 0004 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325531]03fff72fe5c0 0003 000157806000 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325532]fff0 0010 03fff700 03fff72fe520 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325532]02001c426000 0003 00012f8819a2 03ffe72fe518 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540] User Code: 00012f881996: e548b0a80001mvghi 168(%r11),1 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f88199c: c0e5fc86brasl %r14,12f8812a8 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540] #00012f8819a2: c2f41008slgfi %r15,268435464 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540] >00012f8819a8: e54cf0a1mvhi160(%r15),1 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819ae: 4110f0a0la %r1,160(%r15) Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819b2: ec1afff8a065clgrj %r1,%r10,10,12f8819a2 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819b8: b24f0010ear %r1,%a0 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819bc: eb11002dsllg%r1,%r1,32 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325549] Last Breaking-Event-Addre
[Kernel-packages] [Bug 1718107] Re: brk_near_huge test will hang on IBM s390x zKVM / zVM
** Description changed: + This issue does not exist on other amd64 / i386 / arm64 boxes. + Steps: 1. Clone git://kernel.ubuntu.com/ubuntu/autotest-client-tests 2. Untar libhugetlbfs/libhugetlbfs-2.20.tar.gz 3. Run `sudo BUILDTYPE=NATIVEONLY make check` in the extracted libhugetlbfs-2.20 directory 4. Hit Ctrl + C to terminate it From the output you will see it get stuck: truncate_above_4GB (1024K: 64): PASS brk_near_huge (1024K: 64):brk_near_huge: malloc.c:2427: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed. task-size-overrun (1024K: 64): - From the syslog you can see brk_near_huge has crashed: Sep 19 07:28:25 s2lp6g004 rsyslogd-2007: action 'action 10' suspended, next retry is Tue Sep 19 07:29:55 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Application brk_near_huge, PID 10474 crashed Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Writing core files to ['/home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.brk_near_huge.10474'] Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Could not determine from which application core file /home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.brk_near_huge.10474/core is from After hitting Ctrl + C to interrupt, kernel trace could be found in syslog: Sep 19 07:30:02 s2lp6g004 kernel: [11224.325504] report_user_fault: 35 callbacks suppressed Sep 19 07:30:02 s2lp6g004 kernel: [11224.325507] User process fault: interruption code 0010 ilc:3 in stack_grow_into_huge[12f88+4000] Sep 19 07:30:02 s2lp6g004 kernel: [11224.325520] Failing address: 03ffe72fe000 TEID: 03ffe72fe400 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325521] Fault in primary space mode while using user ASCE. - Sep 19 07:30:02 s2lp6g004 kernel: [11224.325523] AS:551701c7 R3:48d88007 S:0020 + Sep 19 07:30:02 s2lp6g004 kernel: [11224.325523] AS:551701c7 R3:48d88007 S:0020 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325527] CPU: 0 PID: 10481 Comm: stack_grow_into Tainted: P DO4.13.0-11-generic #12-Ubuntu Sep 19 07:30:02 s2lp6g004 kernel: [11224.325527] Hardware name: IBM 2964 N63 400 (KVM/Linux) Sep 19 07:30:02 s2lp6g004 kernel: [11224.325528] task: 6245 task.stack: 62b3c000 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325529] User PSW : 070530018000 00012f8819a8 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325530]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:3 PM:0 RI:0 EA:3 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325531] User GPRS: 02001c51e2f8 f000 0004 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325531]03fff72fe5c0 0003 000157806000 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325532]fff0 0010 03fff700 03fff72fe520 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325532]02001c426000 0003 00012f8819a2 03ffe72fe518 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540] User Code: 00012f881996: e548b0a80001mvghi 168(%r11),1 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f88199c: c0e5fc86brasl %r14,12f8812a8 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540] #00012f8819a2: c2f41008slgfi %r15,268435464 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540] >00012f8819a8: e54cf0a1mvhi160(%r15),1 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819ae: 4110f0a0la %r1,160(%r15) Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819b2: ec1afff8a065clgrj %r1,%r10,10,12f8819a2 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819b8: b24f0010ear %r1,%a0 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819bc: eb11002dsllg%r1,%r1,32 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325549] Last Breaking-Event-Address: Sep 19 07:30:02 s2lp6g004 kernel: [11224.325552] [<02001c7f26e8>] 0x2001c7f26e8 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325562] Process 10481(stack_grow_into) has RLIMIT_CORE set to 1 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325563] Aborting core Please find attachment for a more detailed syslog and core dump file. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-11-generic 4.13.0-11.12 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls:
[Kernel-packages] [Bug 1700606] Comment bridged from LTC Bugzilla
--- Comment From christophe_lomb...@fr.ibm.com 2017-09-19 03:34 EDT--- (In reply to comment #13) > Sorry for the delay. I built a ppc64le Zesty test kernel with the requested > 7 patches. The test kernel can be downloaded from: > > http://kernel.ubuntu.com/~jsalisbury/lp1700606/ We need the source of this kernel because we have to check the content of the cxl driver and we have also to patch this one due a limitation on the CAPI card plugged on the machine. If I'm not mistaken, the package is empty linux-source-4.10.0_4.10.0-33.37~lp1700606_all.deb 2017-09-05 19:37 229K clombard@ltc-boston20:~/capi$ dpkg-query -l linux-source-4.10.0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-===-===-=== ii linux-source-4.10.0 4.10.0-33.37~lp1700 all Linux kernel source for version 4.10.0 with Ubuntu patches clombard@ltc-boston20:~/capi$ dpkg-query -l xml-core Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-===-===-=== ii xml-core 0.17all XML infrastructure and XML catalog file support clombard@ltc-boston20:~/capi$ dpkg-query -L linux-source-4.10.0 /. /usr /usr/share /usr/share/doc /usr/share/doc/linux-source-4.10.0 /usr/share/doc/linux-source-4.10.0/changelog.Debian.gz /usr/share/doc/linux-source-4.10.0/copyright /usr/src /usr/src/linux-source-4.10.0 Thanks -- 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/1700606 Title: POWER9: CAPI2 enablement - Fixes Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: = Comment: #2 - Christophe Lombard - 2017-06-26 11:15:53 == Here are new cxl patches we would like to include on Zesty kernel. These patches bring fixes for the CXL device driver for CAPI and CAPI2. They apply on top of https://bugzilla.linux.ibm.com/show_bug.cgi?id=153737 commit ids: ea9a26d117cf0637c71d3e0076f4a124bf5859df cxl: Force context lock during EEH flow 4f58f0bf155e87dda31a3088b1e107fa9dd79f0e cxl: Route eeh events to all drivers in cxl_pci_error_detected() a715626a8e904e7226915d1bc4885317ea9da141 cxl: Mask slice error interrupts after first occurrence b3aa20ba2ba8072b73bd799605b8c98927b7056c cxl: Avoid double free_irq() for psl,slice interrupts cec422c11caeeccae709e9942058b6b644ce434c cxl: Fix error path on bad ioctl 797625deaedd9a0621376817db2813244b3246e3 cxl: Fixes for Coherent Accelerator Interface Architecture 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1700606/+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 1704972] Comment bridged from LTC Bugzilla
--- Comment From mahesh.salgaon...@in.ibm.com 2017-09-19 04:46 EDT--- Any idea which kernel version the fix is available ? -- 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/1704972 Title: [LTCTest][Opal][FW910] HMI TFMR HDEC parity error is throwing Severe Machine check interrupt Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2017-05-22 05:12:38 == ---Problem Description--- HMI TFMR HDEC parity error is throwing Severe Machine check interrupt ---uname output--- Linux zz376p1 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---System Hang--- The system hangs indefinitely and we have to reboot the system to recover back. ---Debugger--- A debugger is not configured Immediately after injecting the above error, we get Severe Machine check interrupt [[Not recovered] Contact Information = pavsu...@in.ibm.com Stack trace output: no Oops output: [ 288.655336] Severe Machine check interrupt [[Not recovered] [ 288.655339] Severe Machine check interrupt [[Not recovered] [ 288.655342] Severe Machine check interrupt [[Not recovered] [ 288.655345] Severe Machine check interrupt [[Not recovered] [ 288.655348] Initiator: CPU [ 288.655349] Initiator: CPU [ 288.655352] Error type: Real address [Load/Store (foreign)] [ 288.655354] Initiator: CPU [ 288.655357] Effective address: 333035342dfe3030 [ 288.655360] Error type: Real address [Load/Store (foreign)] [ 288.655366] Error type: Real address [Load/Store (foreign)] [ 288.655369] Effective address: 333035342e013030 [ 288.655371] Effective address: 333035342e073030 [ 288.655418] opal: Reboot type 1 not supported [ 288.655420] opal: Reboot type 1 not supported [ 288.655422] opal: Reboot type 1 not supported [ 288.655423] Kernel panic - not syncing: PowerNV Unrecovered Machine Check [ 288.655430] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G M 4.10.0-21-generic #23~16.04.1-Ubuntu [ 288.655433] Call Trace: [ 288.655450] Sending IPI to other CPUs [ 288.656767] Initiator: CPU [ 288.656834] Error type: Real address [Load/Store (foreign)] [ 288.656945] Effective address: 333035342e043030 [ 288.657060] opal: Reboot type 1 not supported [ 298.655034] ERROR: 3 cpu(s) not responding [ 298.655183] Activate system reset (dumprestart) to stop other cpu(s) System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for pavsu...@in.ibm.com: -Attach sysctl -a output output to the bug. == Comment: #3 - MAHESH J. SALGAONKAR - 2017-06-29 03:23:30 == (In reply to comment #2) > We need upstream commit > https://git.kernel.org/powerpc/c/be5c5e843c4afa1c8397cb740b6032 that fixes > this issue. > > Hi Breno, > We will be needing this upstream commit to be included in Ubuntu 16.04.3 Did this patch make into Ubuntu 16.04.3 ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1704972/+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 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services
I have tested the kernel provided with commit ef754413085f5 and the bug persists. The daemons do not stop if the integration services are being disabled. The kernel provided in comment #36 was not affected by the bug. That was the first good commit. Regarding comment #27, the kernel tested was reported as bad (the daemon still remains running after the integration service is being disabled). Just to make sure we got this right, there are 2 issues right now: 1. The daemons do not stop if the integration service is being disabled, they remain running in the process list, but are not functional. This issue is present in the kernels tested up to 4.4.0-2. This issue is NOT present in kernel 4.4.0-3, here the daemons processes do stop if the integration service is disabled. Regarding this issue, the kernel provided in comment #36 is a good kernel. 2. The daemons do not automatically start after the integration service is disabled and then enabled again. This is the initial bug discovered in 16.04 and 17.04. Kernel 4.4.0-3 does not have the first issue, but it has the second one. -- 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/1701222 Title: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: In Progress Bug description: Issue description: Hyper-V daemons fail to start after disable/re- enable VM integration services. Platform: host independent Affected daemons - KVP, FCOPY and VSS. Distribution name and release: Ubuntu 16.04, Ubuntu 17.04 Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 4.10.0-19-generic (for Ubuntu 17.04) Repro rate: 100% Steps to reproduce: 1.Start VM with Guest Services enabled (FCopy daemon starts automatically) 2.Go to File > Settings > Integration Services, uncheck Guest Services and apply (FCopy daemon will stop at this point) 3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running). This is the issue. systemd monitors for the service and if we have the hook for the Guest Service, it tries to start the daemon again. systemd attempt to start any of the LIS daemons will fail, but manually executing the daemon binary, it will start the daemon. Additional Info: - the steps above can be repro'd with KVP / Data Exchange integration service as well. - Manually starting hv_fcopy_daemon works fine. - other distros (RHEL) does not have this behavior, the LIS daemons are started automatically by systemd once we re-enable the integration service. On the upstream kernel and the upstream hv daemons, these messages are recorded in syslog, once we re-enable the Guest service: HV_FCOPY: pread failed: Bad file descriptor systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: hv-fcopy-daemon.service: Unit entered failed state. systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701222/+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 77370] Re: Laptop Fan always on after resume from suspend to RAM
I am having this problem on a thinkpad t470s, ubuntu 16:04 LTS. It does not occur all the time, but in about 30 % of the cases after coming back from suspend. -- 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/77370 Title: Laptop Fan always on after resume from suspend to RAM Status in acpi package in Ubuntu: Invalid Status in linux package in Ubuntu: Won't Fix Status in linux-source-2.6.17 package in Ubuntu: Won't Fix Bug description: Binary package hint: initramfs-tools After doing a suspend to RAM, the fan is always "on" on my laptop, even if temperatures are low (where the fan would normally be off before going to sleep mode for the first time). I removed the /usr/share/initramfs-tools/hooks/thermal script and now everything works fine (fan behaviour is not anymore affected by the suspend to RAM). It seems like this script does a wrong initialization of something which is not needed on my PC. My laptop is a Toshiba satellite A100-308 with dual core centrino. I have a basic standard ACPI support, toshiba_acpi and omnibook kernel modules do not work with my hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/77370/+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 1713729] Re: Xenial update to 4.4.84 stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1713729 Title: Xenial update to 4.4.84 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.84 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.84 stable release shall be applied: * audit: Fix use after free in audit_remove_watch_rule() * parisc: pci memory bar assignment fails with 64bit kernels on dino/cujo * crypto: x86/sha1 - Fix reads beyond the number of blocks passed * Input: elan_i2c - add ELAN0608 to the ACPI table * Input: elan_i2c - Add antoher Lenovo ACPI ID for upcoming Lenovo NB * ALSA: seq: 2nd attempt at fixing race creating a queue * ALSA: usb-audio: Apply sample rate quirk to Sennheiser headset * ALSA: usb-audio: Add mute TLV for playback volumes on C-Media devices * mm/mempolicy: fix use after free when calling get_mempolicy * mm: revert x86_64 and arm64 ELF_ET_DYN_BASE base changes * xen: fix bio vec merging * x86/asm/64: Clear AC on NMI entries * irqchip/atmel-aic: Fix unbalanced of_node_put() in aic_common_irq_fixup() * irqchip/atmel-aic: Fix unbalanced refcount in aic_common_rtc_irq_fixup() * Sanitize 'move_pages()' permission checks * pids: make task_tgid_nr_ns() safe * perf/x86: Fix LBR related crashes on Intel Atom * usb: optimize acpi companion search for usb port devices * usb: qmi_wwan: add D-Link DWM-222 device ID * Linux 4.4.84 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713729/+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 1714298] Re: Xenial update to 4.4.85 stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1714298 Title: Xenial update to 4.4.85 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.85 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.85 stable release shall be applied: * af_key: do not use GFP_KERNEL in atomic contexts * dccp: purge write queue in dccp_destroy_sock() * dccp: defer ccid_hc_tx_delete() at dismantle time * ipv4: fix NULL dereference in free_fib_info_rcu() * net_sched/sfq: update hierarchical backlog when drop packet * ipv4: better IP_MAX_MTU enforcement * sctp: fully initialize the IPv6 address in sctp_v6_to_addr() * tipc: fix use-after-free * ipv6: reset fn->rr_ptr when replacing route * ipv6: repair fib6 tree in failure case * tcp: when rearming RTO, if RTO time is in past then fire RTO ASAP * irda: do not leak initialized list.dev to userspace * net: sched: fix NULL pointer dereference when action calls some targets * net_sched: fix order of queue length updates in qdisc_replace() * mei: me: add broxton pci device ids * mei: me: add lewisburg device ids * Input: trackpoint - add new trackpoint firmware ID * Input: elan_i2c - add ELAN0602 ACPI ID to support Lenovo Yoga310 * ALSA: core: Fix unexpected error at replacing user TLV * ALSA: hda - Add stereo mic quirk for Lenovo G50-70 (17aa:3978) * ARCv2: PAE40: Explicitly set MSB counterpart of SLC region ops addresses * i2c: designware: Fix system suspend * drm: Release driver tracking before making the object available again * drm/atomic: If the atomic check fails, return its value first * drm: rcar-du: lvds: Fix PLL frequency-related configuration * drm: rcar-du: lvds: Rename PLLEN bit to PLLON * drm: rcar-du: Fix crash in encoder failure error path * drm: rcar-du: Fix display timing controller parameter * drm: rcar-du: Fix H/V sync signal polarity configuration * tracing: Fix freeing of filter in create_filter() when set_str is false * cifs: Fix df output for users with quota limits * cifs: return ENAMETOOLONG for overlong names in cifs_open()/cifs_lookup() * nfsd: Limit end of page list when decoding NFSv4 WRITE * perf/core: Fix group {cpu,task} validation * Bluetooth: hidp: fix possible might sleep error in hidp_session_thread * Bluetooth: cmtp: fix possible might sleep error in cmtp_session * Bluetooth: bnep: fix possible might sleep error in bnep_session * binder: use group leader instead of open thread * binder: Use wake up hint for synchronous transactions. * ANDROID: binder: fix proc->tsk check. * iio: imu: adis16480: Fix acceleration scale factor for adis16480 * iio: hid-sensor-trigger: Fix the race with user space powering up sensors * staging: rtl8188eu: add RNX-N150NUB support * ASoC: simple-card: don't fail if sysclk setting is not supported * ASoC: rsnd: disable SRC.out only when stop timing * ASoC: rsnd: avoid pointless loop in rsnd_mod_interrupt() * ASoC: rsnd: Add missing initialization of ADG req_rate * ASoC: rsnd: ssi: 24bit data needs right-aligned settings * ASoC: rsnd: don't call update callback if it was NULL * ntb_transport: fix qp count bug * ntb_transport: fix bug calculating num_qps_mw * ACPI: ioapic: Clear on-stack resource before using it * ACPI / APEI: Add missing synchronize_rcu() on NOTIFY_SCI removal * Linux 4.4.85 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714298/+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 1715430] Re: Xenial update to 4.4.86 stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1715430 Title: Xenial update to 4.4.86 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.86 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.86 stable release shall be applied: * scsi: isci: avoid array subscript warning * ALSA: au88x0: Fix zero clear of stream->resources * btrfs: remove duplicate const specifier * i2c: jz4780: drop superfluous init * gcov: add support for gcc version >= 6 * gcov: support GCC 7.1 * lightnvm: initialize ppa_addr in dev_to_generic_addr() * p54: memset(0) whole array * lpfc: Fix Device discovery failures during switch reboot test. * arm64: mm: abort uaccess retries upon fatal signal * x86/io: Add "memory" clobber to insb/insw/insl/outsb/outsw/outsl * arm64: fpsimd: Prevent registers leaking across exec * scsi: sg: protect accesses to 'reserved' page array * scsi: sg: reset 'res_in_use' after unlinking reserved array * drm/i915: fix compiler warning in drivers/gpu/drm/i915/intel_uncore.c * Linux 4.4.86 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715430/+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 1333294] Re: 32-bit kernel HDD slow write speed
** Changed in: linux (Debian) Status: Unknown => Confirmed -- 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/1333294 Title: 32-bit kernel HDD slow write speed Status in linux package in Ubuntu: Incomplete Status in linux package in Debian: Confirmed Bug description: Summary After upgrading my Ubuntu 32-bit from 12.04 to 14.04 the write performance is painfully slow (less than 4.6MB/s) of both my SSD drives. The read speed is still fine. I've tested with the latest version of System Rescue CD (4.2.0 at this time) to see if was a hardware problem. However the performance of my drives was even better better than using Ubuntu 12.04. I've also tried to make a fresh installation of Ubuntu 14.04 on a spare SSD drive of mine to see if its because I upgraded from 12.04. But after waiting 4 hours for it to install, I finally lost patience, and stopped the installation. I'm using the deadline scheduler, but it doesn't matter which one I use. I'm also using the lowlatency kernel, but using the generic kernel doesn't have any effect. I've tested with mechanical hard drives, and the problem also occurs there. I've also tried to update to the proposed updates, and updated to kernel 3.13.0-30.54, but problem still exists there. The only think that helps is telling the kernel only to address 8GB RAM using the "mem=8GB" kernel option, but that is obviously not a solution when I need to utilize all the 32GB RAM that I have . The reason that I use a 32-bit OS is because most of the applications I use on my laptop are propriety software that only exists in 32-bit versions. Details Kernel version root@ubuntu:~# uname -a Linux fk20563 3.13.0-29-lowlatency #53-Ubuntu SMP PREEMPT Wed Jun 4 21:20:42 UTC 2014 i686 i686 i686 GNU/Linux List hardware lshw > lshw.txt Timings of devices (which is also 4x slower than normal) root@ubuntu:~# hdparm -t /dev/sda && hdparm -t /dev/sda && hdparm -t /dev/sda /dev/sda: Timing buffered disk reads: 470 MB in 3.01 seconds = 156.33 MB/sec /dev/sda: Timing buffered disk reads: 530 MB in 3.03 seconds = 174.86 MB/sec /dev/sda: Timing buffered disk reads: 500 MB in 3.01 seconds = 166.36 MB/sec root@ubuntu:~# hdparm -t /dev/sdb && hdparm -t /dev/sdb && hdparm -t /dev/sdb /dev/sdb: Timing buffered disk reads: 500 MB in 3.32 seconds = 150.61 MB/sec /dev/sdb: Timing buffered disk reads: 508 MB in 3.03 seconds = 167.49 MB/sec /dev/sdb: Timing buffered disk reads: 500 MB in 3.21 seconds = 155.81 MB/sec SSD partition alignment check root@ubuntu:~# fdisk -l Disk /dev/sda: 256.1 GB, 256060514304 bytes 255 heads, 63 sectors/track, 31130 cylinders, total 500118192 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xd162fc6d Device Boot Start End Blocks Id System /dev/sda1 2048 483332095 241665024 83 Linux /dev/sda2 483332096 500117503 8392704 5 Extended /dev/sda5 483334144 500117503 8391680 82 Linux swap / Solaris Disk /dev/sdb: 480.1 GB, 480103981056 bytes 255 heads, 63 sectors/track, 58369 cylinders, total 937703088 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Device Boot Start End Blocks Id System /dev/sdb1 2048 937703087 468850520 83 Linux root@ubuntu:~# parted GNU Parted 2.3 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) select /dev/sda Using /dev/sda (parted) align-check opt 1 1 aligned (parted) select /dev/sdb Using /dev/sdb (parted) align-check opt 1 1 aligned (parted) quit Scheduler: root@ubuntu:~# cat /sys/block/sd{a,b}/queue/scheduler noop [deadline] cfq noop [deadline] cfq Mount options: root@fk20563:~# mount | grep sda /dev/sda1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,discard) root@fk20563:~# mount | grep sdb /dev/sdb1 on /media/vmware type xfs (rw,noatime,nodiratime,logbsize=256k,discard) FS read/write check of /dev/sda1 on Ubuntu root@fk20563:~# dd if=/dev/zero of=/test.raw bs=1M count=1000 1000+0 records in 1000+0 records out 1048576000 bytes (1.0 GB) copied, 229.091 s, 4.6 MB/s root@fk20563:~# dd of=/dev/null if=/test.raw 2048000+0 records in 2048000+0 records out 1048576000 bytes (1.0 GB) copied, 2.58461 s, 406 MB/s FS read/write check of /dev/sdb1 on Ubuntu root@fk20563:~# dd if=/dev/zero of=/media/vmware/test.raw bs=1M count=1000 1000+0 records in 1000+0 records out 1048576000 bytes (1.0 GB) copied, 229.395 s, 4.6 MB/s root@fk20563:~# dd of=/dev/null if=/media/vmware/test.raw 2048000+0 records in 2048000+0 records out 10
[Kernel-packages] [Bug 1718143] [NEW] linux: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718145,1718146 derivatives: 1718147 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Zesty) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2017.09.18-1 kernel-sru-master-kernel zesty ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Tags added: zesty ** Changed in: linux (Ubuntu Zesty) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta
[Kernel-packages] [Bug 1704972] Comment bridged from LTC Bugzilla
--- Comment From mainam...@in.ibm.com 2017-09-19 05:09 EDT--- (In reply to comment #15) > It looks like it was commited in the master-next branch in bug 1684054 Is this fix committed in to Ubuntu 16.04.3 release? which kernel version of 16.04.3 has this fix? -- 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/1704972 Title: [LTCTest][Opal][FW910] HMI TFMR HDEC parity error is throwing Severe Machine check interrupt Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2017-05-22 05:12:38 == ---Problem Description--- HMI TFMR HDEC parity error is throwing Severe Machine check interrupt ---uname output--- Linux zz376p1 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---System Hang--- The system hangs indefinitely and we have to reboot the system to recover back. ---Debugger--- A debugger is not configured Immediately after injecting the above error, we get Severe Machine check interrupt [[Not recovered] Contact Information = pavsu...@in.ibm.com Stack trace output: no Oops output: [ 288.655336] Severe Machine check interrupt [[Not recovered] [ 288.655339] Severe Machine check interrupt [[Not recovered] [ 288.655342] Severe Machine check interrupt [[Not recovered] [ 288.655345] Severe Machine check interrupt [[Not recovered] [ 288.655348] Initiator: CPU [ 288.655349] Initiator: CPU [ 288.655352] Error type: Real address [Load/Store (foreign)] [ 288.655354] Initiator: CPU [ 288.655357] Effective address: 333035342dfe3030 [ 288.655360] Error type: Real address [Load/Store (foreign)] [ 288.655366] Error type: Real address [Load/Store (foreign)] [ 288.655369] Effective address: 333035342e013030 [ 288.655371] Effective address: 333035342e073030 [ 288.655418] opal: Reboot type 1 not supported [ 288.655420] opal: Reboot type 1 not supported [ 288.655422] opal: Reboot type 1 not supported [ 288.655423] Kernel panic - not syncing: PowerNV Unrecovered Machine Check [ 288.655430] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G M 4.10.0-21-generic #23~16.04.1-Ubuntu [ 288.655433] Call Trace: [ 288.655450] Sending IPI to other CPUs [ 288.656767] Initiator: CPU [ 288.656834] Error type: Real address [Load/Store (foreign)] [ 288.656945] Effective address: 333035342e043030 [ 288.657060] opal: Reboot type 1 not supported [ 298.655034] ERROR: 3 cpu(s) not responding [ 298.655183] Activate system reset (dumprestart) to stop other cpu(s) System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for pavsu...@in.ibm.com: -Attach sysctl -a output output to the bug. == Comment: #3 - MAHESH J. SALGAONKAR - 2017-06-29 03:23:30 == (In reply to comment #2) > We need upstream commit > https://git.kernel.org/powerpc/c/be5c5e843c4afa1c8397cb740b6032 that fixes > this issue. > > Hi Breno, > We will be needing this upstream commit to be included in Ubuntu 16.04.3 Did this patch make into Ubuntu 16.04.3 ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1704972/+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 1715678] Re: Xenial update to 4.4.87 stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1715678 Title: Xenial update to 4.4.87 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.87 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.87 stable release shall be applied: * irqchip: mips-gic: SYNC after enabling GIC region * i2c: ismt: Don't duplicate the receive length for block reads * i2c: ismt: Return EMSGSIZE for block reads with bogus length * ceph: fix readpage from fscache * cpumask: fix spurious cpumask_of_node() on non-NUMA multi-node configs * cpuset: Fix incorrect memory_pressure control file mapping * alpha: uapi: Add support for __SANE_USERSPACE_TYPES__ * CIFS: Fix maximum SMB2 header size * CIFS: remove endian related sparse warning * wl1251: add a missing spin_lock_init() * xfrm: policy: check policy direction value * drm/ttm: Fix accounting error when fail to get pages for pool * kvm: arm/arm64: Fix race in resetting stage2 PGD * kvm: arm/arm64: Force reading uncached stage2 PGD * epoll: fix race between ep_poll_callback(POLLFREE) and ep_free()/ep_remove() * crypto: algif_skcipher - only call put_page on referenced and used pages * Linux 4.4.87 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715678/+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 1718150] [NEW] linux-aws: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1718149 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1718149 kernel-sru-cycle-2017.09.18-1 trusty ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: trusty ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-t
[Kernel-packages] [Bug 1718149] [NEW] linux: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2017.09.18-1 kernel-sru-master-kernel xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel T
[Kernel-packages] [Bug 1718149] Re: linux: -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + backports: 1718150,1718151 + derivatives: 1718153,1718154,1718155,1718156,1718157 -- 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/1718149 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718150,1718151 derivatives: 1718153,1718154,1718155,1718156,1718157 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718149/+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 1718155] [NEW] linux-aws: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1718149 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-aws (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2017.09.18-1 kernel-sru-derivative-of-1718149 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux-aws (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: k
[Kernel-packages] [Bug 1718143] Re: linux: 4.10.0-36.40 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.10.0-36.40 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1718143 Title: linux: 4.10.0-36.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718145,1718146 derivatives: 1718147 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718143/+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 1718161] [NEW] linux-lts-trusty: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1718159 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1718159 kernel-sru-cycle-2017.09.18-1 precise ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-lts-trusty (Ubuntu Precise) Importance: Undecided Status: New ** Tags added: precise ** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/
[Kernel-packages] [Bug 1718159] [NEW] linux: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718161 derivatives: ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2017.09.18-1 kernel-sru-master-kernel trusty ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Tags added: trusty ** Changed in: linux (Ubuntu Trusty) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (
[Kernel-packages] [Bug 1718150] Re: linux-aws: -proposed tracker
** Also affects: linux-aws (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1718150 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1718149 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718150/+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 1550301] Re: ZFS: Set elevator=noop on disks in the root pool
Since this affects root on ZFS and the original patch no longer applies (and ZFS on root) is not currently supported, I am reluctantly going to close is issue. If a clean fix for ZFS on root for newer Zesty+ initramfs scripts is available I am happy to re-apply them for newer releases. However, I am not going to forward port the original changes since the delta is too large and I am not able to test these (as we don't have ZFS on root by default). ** Changed in: zfs-linux (Ubuntu Zesty) Status: Confirmed => Won't Fix ** Changed in: zfs-linux (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1550301 Title: ZFS: Set elevator=noop on disks in the root pool Status in zfs-linux package in Ubuntu: Won't Fix Status in zfs-linux source package in Xenial: Fix Released Status in zfs-linux source package in Zesty: Won't Fix Bug description: ZFS-on-Linux has its own I/O scheduler, so it sets the "noop" elevator on whole disks used in a pool. https://github.com/zfsonlinux/zfs/issues/90 It does not set the scheduler for a disk if a partition is used in a pool out of respect for the possibility that there are non-ZFS partitions on the same disk. https://github.com/zfsonlinux/zfs/issues/152 For regular pools, the recommendation is to use whole disks. For a root pools, it's just the opposite. The typical case is that partitions are used. And, for root pools, it is unlikely that the same disks have non-ZFS filesystems. The debdiff in comment #5 applies cleanly to the latest package and functions correctly. This is an important change for root-on-ZFS users. It has no effect on non-root-on-ZFS installs, because the code is only in the zfs-initramfs package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1550301/+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 1670137] Re: cache on NVMe inhibits proper suspend/hibernate - zfs l2arc
@Joseph, out of interest for users seeing the same issue, can you supply the script so others can use this as a temporary workaround? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1670137 Title: cache on NVMe inhibits proper suspend/hibernate - zfs l2arc Status in zfs-linux package in Ubuntu: In Progress Bug description: Please see: 2017-03-05 09:03 2017-03-05 14:03 UTCKernelOops linux-image-4.4.0-31-generic https://errors.ubuntu.com/oops/7bb2122e-01b1-11e7-ba2a-fa163e839e11 Running zfs [root] with l2arc cache enabled fails to suspend properly, screen goes blank but power stays on, when I disable the cache it works fine. Unsure if this happens with non-root install of zfs, slog does not cause this problem. Linux mp 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ii zfs-initramfs 0.6.5.6-0ubuntu15 all Native OpenZFS root filesystem capabilities for Linux ii zfs-zed0.6.5.6-0ubuntu15 amd64OpenZFS Event Daemon (zed) ii zfsutils-linux 0.6.5.6-0ubuntu15 amd64Native OpenZFS management utilities for Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1670137/+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 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
I've just tried 4.13.2, screen is still blinking while on with the default i915.enable_rc6=1. There is an improvement though. On the kernel version 4.13 my laptop was totally crashing after hitting caps-lock twice. Now this ridiculous one is at least gone. Although I still need to keep the rc6=0 flag at kernel boot params to prevent screen flickering (an external one, connected via HDMI). -- 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/1550779 Title: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches Status in linux package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1270676] Re: SD Card Reader broken on UX302LG
The vendor's driver gives out a Makefile. If the driver works in the first place, can't we wrap it as a DKMS module and install that? Their code seems to handle the AU6621 and AU6601 families of chips. -- 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/1270676 Title: SD Card Reader broken on UX302LG Status in linux package in Ubuntu: Triaged Bug description: SD card reader (controller Alcor Micro AU6601) is dysfunctional in UX302LG laptop. USB readers work without problem. Nothing happens when pluggin SD/mSD/SDHC/mSDHC cards in the reader (might as well use a piece of wood). Nothing is listed in lsusb -v that could be the reader. Nohting is listed in lspci -k -vv -nnn. Nothing in acpi_listen. Nothing in kern.log etc. According to (select "Windows 8" then "Card Reader") : http://support.asus.com/download.aspx?SLanguage=en&p=3&s=597&m=UX302LG&os=&hashedid=GEZaY8oaj8oSlQ3U Reader vendor is : Alcor Multi-Card Reader Driver http://www.pcidatabase.com/vendor_details.php?id=1672 There is only one device that is "Unassigned class" 1aea:6601 but searching this online only pops up my other bug reports (sigh) and vendor is unassigned on pcidatabase.com. But...Downloading the 14M Win driver for the reader, vendor id 1aea and device id 6601 is present at multiple instances : [DeviceList.NTamd64] ; For XP and later %AMPCIECR% = DriverInstall_6601, PCI\VEN_1aea&DEV_6601 Also there is mention of _Gen instance in the .inf, might point to a "Generic" alternative ? [DeviceList_Gen.NTamd64] ; For XP and later %AMPCIECR_GEN% = DriverInstall_Gen, PCI\VEN_105b&DEV_0ef6 This does point to something totally different online 105b:0ef6 points to some Realtek HD Audio device... --- ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-12-31 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131231) Package: linux (not installed) Tags: trusty Uname: Linux 3.13.0-031300-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6 InstallationDate: Installed on 2013-12-31 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131231) MachineType: ASUSTeK COMPUTER INC. UX302LG Package: linux (not installed) ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-4-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi= nomodeset plymouth:debug vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 RelatedPackageVersions: linux-restricted-modules-3.13.0-4-generic N/A linux-backports-modules-3.13.0-4-generic N/A linux-firmware1.121 Tags: trusty Uname: Linux 3.13.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270676/+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 1718159] Re: linux: 3.13.0-133.182 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 3.13.0-133.182 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger (juergh) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger (juergh) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger (juergh) -- 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/1718159 Title: linux: 3.13.0-133.182 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718161 derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718159/+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 1700606] Re: POWER9: CAPI2 enablement - Fixes
** Changed in: ubuntu-power-systems Status: In Progress => 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/1700606 Title: POWER9: CAPI2 enablement - Fixes Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: = Comment: #2 - Christophe Lombard - 2017-06-26 11:15:53 == Here are new cxl patches we would like to include on Zesty kernel. These patches bring fixes for the CXL device driver for CAPI and CAPI2. They apply on top of https://bugzilla.linux.ibm.com/show_bug.cgi?id=153737 commit ids: ea9a26d117cf0637c71d3e0076f4a124bf5859df cxl: Force context lock during EEH flow 4f58f0bf155e87dda31a3088b1e107fa9dd79f0e cxl: Route eeh events to all drivers in cxl_pci_error_detected() a715626a8e904e7226915d1bc4885317ea9da141 cxl: Mask slice error interrupts after first occurrence b3aa20ba2ba8072b73bd799605b8c98927b7056c cxl: Avoid double free_irq() for psl,slice interrupts cec422c11caeeccae709e9942058b6b644ce434c cxl: Fix error path on bad ioctl 797625deaedd9a0621376817db2813244b3246e3 cxl: Fixes for Coherent Accelerator Interface Architecture 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1700606/+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 1700606] Comment bridged from LTC Bugzilla
--- Comment From bren...@br.ibm.com 2017-09-19 08:14 EDT--- Canonical, We are *not* pursuing this feature for 16.04.3 anymore. We can catch up on the next release (no backports required in that case). We can close this bug. -- 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/1700606 Title: POWER9: CAPI2 enablement - Fixes Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: = Comment: #2 - Christophe Lombard - 2017-06-26 11:15:53 == Here are new cxl patches we would like to include on Zesty kernel. These patches bring fixes for the CXL device driver for CAPI and CAPI2. They apply on top of https://bugzilla.linux.ibm.com/show_bug.cgi?id=153737 commit ids: ea9a26d117cf0637c71d3e0076f4a124bf5859df cxl: Force context lock during EEH flow 4f58f0bf155e87dda31a3088b1e107fa9dd79f0e cxl: Route eeh events to all drivers in cxl_pci_error_detected() a715626a8e904e7226915d1bc4885317ea9da141 cxl: Mask slice error interrupts after first occurrence b3aa20ba2ba8072b73bd799605b8c98927b7056c cxl: Avoid double free_irq() for psl,slice interrupts cec422c11caeeccae709e9942058b6b644ce434c cxl: Fix error path on bad ioctl 797625deaedd9a0621376817db2813244b3246e3 cxl: Fixes for Coherent Accelerator Interface Architecture 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1700606/+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 1718143] Re: linux: 4.10.0-36.40 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718145,1718146 derivatives: 1718147 + kernel-stable-phase-changed:Tuesday, 19. September 2017 12:32 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718145,1718146 derivatives: 1718147 kernel-stable-phase-changed:Tuesday, 19. September 2017 12:32 UTC kernel-stable-phase:Uploaded + + -- swm properties -- + phase: Uploaded -- 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/1718143 Title: linux: 4.10.0-36.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718145,1718146 derivatives: 1718147 kernel-stable-phase-changed:Tuesday, 19. September 2017 12:32 UTC kernel-stable-phase:Uploaded -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718143/+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 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1670634 Title: blk-mq: possible deadlock on CPU hot(un)plug Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: New Bug description: == Comment: #0 - Carsten Jacobi - 2017-03-07 03:35:31 == I'm evaluating Ubuntu-Xenial on z for development purposes, the test system is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all pathes are configured). The system hangs regularly when I make packages with "pdebuild" using the pbuilder packaging suit. The local Linux development team helped me out with a pre-analysis that I can post here (thanks a lot for that): With the default settings and under a certain workload, blk_mq seems to get into a presumed "deadlock". Possibly this happens on CPU hot(un)plug. After the I/O stalled, a dump was pulled manually. The following information is from the crash dump pre-analysis. $ zgetdump -i dump.0 General dump info: Dump format: elf Version: 1 UTS node name..: mclint UTS kernel release.: 4.4.0-65-generic UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 System arch: s390x (64 bit) CPU count (online).: 2 Dump memory range..: 8192 MB Memory map: - 0001b831afff (7043 MB) 0001b831b000 - 0001 (1149 MB) Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1. KERNEL: vmlinux.full DUMPFILE: dump.0 CPUS: 2 DATE: Fri Mar 3 14:31:07 2017 UPTIME: 02:11:20 LOAD AVERAGE: 13.00, 12.92, 11.37 TASKS: 411 NODENAME: mclint RELEASE: 4.4.0-65-generic VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 MACHINE: s390x (unknown Mhz) MEMORY: 7.8 GB PANIC: "" PID: 0 COMMAND: "swapper/0" TASK: bad528 (1 of 2) [THREAD_INFO: b78000] CPU: 0 STATE: TASK_RUNNING (ACTIVE) INFO: no panic task found crash> dev -d MAJOR GENDISKNAME REQUEST_QUEUE TOTAL ASYNC SYNC DRV ... 8 1e1d6d800 sda1e1d51210 0 23151 4294944145 N/A(MQ) 8 1e4e06800 sdc2081b180 23148 4294944148 N/A(MQ) 8 1f07800sdb20c75680 23195 4294944101 N/A(MQ) 8 1e4e06000 sdd1e4e31210 0 23099 4294944197 N/A(MQ) 252 1e1d6c800 dm-0 1e1d51b18 9 1 8 N/A(MQ) ... So both dm-mpath and sd have requests pending in their block multiqueue. The large numbers of sd look strange and seem to be the unsigned formatting of the values shown for async multiplied by -1. [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49) [0.798262] setup: Linux is running natively in 64-bit mode [0.798290] setup: Max memory size: 8192MB [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel (System RAM: 7996MB) [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0 [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 seconds. [ 5281.179437] Not tainted 4.4.0-65-generic #86-Ubuntu [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 5281.179440] xfsaild/dm-11 D 007bcf52 0 1604 2 0x [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 0001e6f9b9d8 0001e15795f0 0001e6f9b988 00ce8c00 0001ea805c70 0001ea805c00 00ba5ed0 0001e931c1d0 0001e1579b20 0001ea805c00 0001e15795f0 0001ea805c00 007d3978 007bc9f8 0001e6f9b9d8 0001e6f9ba40 [ 5281.179454] Call Trace: [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810) [ 5281.179462] [<007bcf52>] schedule+0x4a/0xb0 [ 5281.179465] [<007c02aa>] schedule_timeout+0x232/0x2a8 [ 5281.179466] [<007bde50>] wait_for_common+0x110/0x1c8 [ 5281.179472] [<0017b602>] flush_work+0x42/0x58 [ 5281.179564] [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs] [ 5281.179589] [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs] [ 5281.179615] [<03ff805df114>] xfs_log_force+0x44/0x100 [xfs] [ 5281.179640] [<03ff805ec668>] xfsaild+0x
[Kernel-packages] [Bug 1718193] [NEW] NEW RYZEN 7 SYSTEM WAKEUP
You have been subscribed to a public bug: after waking up - the kernel throws 22 stack traces ... ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- NEW RYZEN 7 SYSTEM WAKEUP https://bugs.launchpad.net/bugs/1718193 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1718193] [NEW] NEW RYZEN 7 SYSTEM WAKEUP
Public bug reported: after waking up - the kernel throws 22 stack traces ... ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "the dmesg output" https://bugs.launchpad.net/bugs/1718193/+attachment/4952806/+files/bug.txt ** Project changed: launchpad => kernel ** Description changed: - after waking up - the kernel throws 16 stack traces ... + after waking up - the kernel throws 22 stack traces ... ** Project changed: kernel => 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/1718193 Title: NEW RYZEN 7 SYSTEM WAKEUP Status in linux package in Ubuntu: New Bug description: after waking up - the kernel throws 22 stack traces ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718193/+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 1718195] [NEW] Xenial update to 4.4.88 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.88 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.88 stable release shall be applied: * usb: quirks: add delay init quirk for Corsair Strafe RGB keyboard * USB: serial: option: add support for D-Link DWM-157 C1 * usb: Add device quirk for Logitech HD Pro Webcam C920-C * usb:xhci:Fix regression when ATI chipsets detected * USB: core: Avoid race of async_completed() w/ usbdev_release() * staging/rts5208: fix incorrect shift to extract upper nybble * driver core: bus: Fix a potential double free * intel_th: pci: Add Cannon Lake PCH-H support * intel_th: pci: Add Cannon Lake PCH-LP support * ath10k: fix memory leak in rx ring buffer allocation * rtlwifi: rtl_pci_probe: Fix fail path of _rtl_pci_find_adapter * Bluetooth: Add support of 13d3:3494 RTL8723BE device * dlm: avoid double-free on error path in dlm_device_{register,unregister} * mwifiex: correct channel stat buffer overflows * drm/nouveau/pci/msi: disable MSI on big-endian platforms by default * workqueue: Fix flag collision * cs5536: add support for IDE controller variant * scsi: sg: protect against races between mmap() and SG_SET_RESERVED_SIZE * scsi: sg: recheck MMAP_IO request length with lock held * drm: adv7511: really enable interrupts for EDID detection * drm/bridge: adv7511: Fix mutex deadlock when interrupts are disabled * drm/bridge: adv7511: Use work_struct to defer hotplug handing to out of irq context * drm/bridge: adv7511: Switch to using drm_kms_helper_hotplug_event() * drm/bridge: adv7511: Re-write the i2c address before EDID probing * btrfs: resume qgroup rescan on rw remount * locktorture: Fix potential memory leak with rw lock test * ALSA: msnd: Optimize / harden DSP and MIDI loops * ARM: 8692/1: mm: abort uaccess retries upon fatal signal * NFS: Fix 2 use after free issues in the I/O code * xfs: XFS_IS_REALTIME_INODE() should be false if no rt device present * Linux 4.4.88 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (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/1718195 Title: Xenial update to 4.4.88 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.88 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.88 stable release shall be applied: * usb: quirks: add delay init quirk for Corsair Strafe RGB keyboard * USB: serial: option: add support for D-Link DWM-157 C1 * usb: Add device quirk for Logitech HD Pro Webcam C920-C * usb:xhci:Fix regression when ATI chipsets detected * USB: core: Avoid race of async_completed() w/ usbdev_release() * staging/rts5208: fix incorrect shift to extract upper nybble * driver core: bus: Fix a potential double free * intel_th: pci: Add Cannon Lake PCH-H support * intel_th: pci: Add Cannon Lake PCH-LP support * ath10k: fix memory leak in rx ring buffer allocation * rtlwifi: rtl_pci_probe: Fix fail path of _rtl_pci_find_adapter * Bluetooth: Add support of 13d3:3494 RTL8723BE device * dlm: avoid double-free on error path in dlm_device_{register,unregister} * mwifiex: correct channel stat buffer overflows * drm/nouveau/pci/msi: disable MSI on big-endian platforms by default * workqueue: Fix flag collision * cs5536: add
[Kernel-packages] [Bug 1718195] Re: Xenial update to 4.4.88 stable release
Patch "Input: trackpoint - assume 3 buttons when buttons detection fails" is already applied for bug #1715271. Patch "Bluetooth: Properly check L2CAP config option output buffer length" is already applied for CVE-2017-1000251. ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The 4.4.88 upstream stable + patch set is now available. It should be included in the Ubuntu + kernel as well. - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The 4.4.88 upstream stable -patch set is now available. It should be included in the Ubuntu -kernel as well. + git://git.kernel.org/ -git://git.kernel.org/ + TEST CASE: TBD - TEST CASE: TBD - -The following patches from the 4.4.88 stable release shall be - applied: + The following patches from the 4.4.88 stable release shall be applied: + * usb: quirks: add delay init quirk for Corsair Strafe RGB keyboard + * USB: serial: option: add support for D-Link DWM-157 C1 + * usb: Add device quirk for Logitech HD Pro Webcam C920-C + * usb:xhci:Fix regression when ATI chipsets detected + * USB: core: Avoid race of async_completed() w/ usbdev_release() + * staging/rts5208: fix incorrect shift to extract upper nybble + * driver core: bus: Fix a potential double free + * intel_th: pci: Add Cannon Lake PCH-H support + * intel_th: pci: Add Cannon Lake PCH-LP support + * ath10k: fix memory leak in rx ring buffer allocation + * rtlwifi: rtl_pci_probe: Fix fail path of _rtl_pci_find_adapter + * Bluetooth: Add support of 13d3:3494 RTL8723BE device + * dlm: avoid double-free on error path in dlm_device_{register,unregister} + * mwifiex: correct channel stat buffer overflows + * drm/nouveau/pci/msi: disable MSI on big-endian platforms by default + * workqueue: Fix flag collision + * cs5536: add support for IDE controller variant + * scsi: sg: protect against races between mmap() and SG_SET_RESERVED_SIZE + * scsi: sg: recheck MMAP_IO request length with lock held + * drm: adv7511: really enable interrupts for EDID detection + * drm/bridge: adv7511: Fix mutex deadlock when interrupts are disabled + * drm/bridge: adv7511: Use work_struct to defer hotplug handing to out of irq + context + * drm/bridge: adv7511: Switch to using drm_kms_helper_hotplug_event() + * drm/bridge: adv7511: Re-write the i2c address before EDID probing + * btrfs: resume qgroup rescan on rw remount + * locktorture: Fix potential memory leak with rw lock test + * ALSA: msnd: Optimize / harden DSP and MIDI loops + * ARM: 8692/1: mm: abort uaccess retries upon fatal signal + * NFS: Fix 2 use after free issues in the I/O code + * xfs: XFS_IS_REALTIME_INODE() should be false if no rt device present + * Linux 4.4.88 ** CVE added: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2017-1000251 -- 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/1718195 Title: Xenial update to 4.4.88 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.88 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.88 stable release shall be applied: * usb: quirks: add delay init quirk for Corsair Strafe RGB keyboard * USB: serial: option: add support for D-Link DWM-157 C1 * usb: Add device quirk for Logitech HD Pro Webcam C920-C * usb:xhci:Fix regression when ATI chipsets detected * USB: core: Avoid race of async_completed() w/ usbdev_release() * staging/rts5208: fix incorrect shift to extract upper nybble * driver core: bus: Fix a potential double free * intel_th: pci: Add Cannon Lake PCH-H support * intel_th: pci: Add Cannon Lake PCH-LP support * ath10k: fix memory leak in rx ring buffer all
[Kernel-packages] [Bug 1718193] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1718193 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => 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/1718193 Title: NEW RYZEN 7 SYSTEM WAKEUP Status in linux package in Ubuntu: Incomplete Bug description: after waking up - the kernel throws 22 stack traces ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718193/+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 1709282] Re: Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81
Thanks! Apparently it works! can we include this in the mainstream kernel update? -- 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/1709282 Title: Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81 Status in linux package in Ubuntu: Confirmed Bug description: Very similar to this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763 == the Problem == Listening to sound on a vmware machine, hosted by Ubuntu, the devices freezes, and cannot listen to sound anymore, i have to connect/disconnect the device. After i disconnect i get the logs: Aug 8 13:52:05 tim-lap-143 kernel: [112278.344893] usb 1-1: 1:1: cannot get freq at ep 0x81 Aug 8 13:52:05 tim-lap-143 kernel: [112278.347094] usb 1-1: 2:1: cannot get freq at ep 0x1 Aug 8 13:52:05 tim-lap-143 kernel: [112278.358786] usb 1-1: Warning! Unlikely big volume range (=8192), cval->res is probably wrong. Aug 8 13:52:05 tim-lap-143 kernel: [112278.358787] usb 1-1: [11] FU [Sidetone Playback Volume] ch = 1, val = 0/8192/1 Aug 8 13:52:05 tim-lap-143 kernel: [112278.641980] input: Plantronics Plantronics C520-M as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.3/0003:047F:C036.000F/input/input32 Aug 8 13:52:05 tim-lap-143 kernel: [112278.702298] plantronics 0003:047F:C036.000F: input,hiddev0,hidraw2: USB HID v1.11 Device [Plantronics Plantronics C520-M] on usb-:00:14.0-1/input3 Aug 8 13:52:05 tim-lap-143 kernel: [112278.747708] usb 1-1: 2:1: cannot get freq at ep 0x1 Aug 8 13:52:16 tim-lap-143 kernel: [112289.406154] usb 1-1: reset full-speed USB device number 19 using xhci_hcd Aug 8 13:52:16 tim-lap-143 kernel: [112289.906146] usb 1-1: reset full-speed USB device number 19 using xhci_hcd = The solution == It is simple, add this USB ID to the sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function. version signature: Ubuntu 4.10.0-28.32-generic 4.10.17 Thanks! --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: mihai.cin...@3pillar.corp 2208 F...m pulseaudio /dev/snd/controlC0: mihai.cin...@3pillar.corp 2208 F pulseaudio DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=d363a75c-d8a4-467d-a576-a46b3c317861 InstallationDate: Installed on 2017-06-22 (47 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Precision 3510 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_guc_loading=1 i915.enable_guc_submission=1 intel_pstate=skylake_hwp i915.enable_psr=1 i915.disable_power_well=0 i915.enable_rc6=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-28-generic N/A linux-backports-modules-4.10.0-28-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-07-21 (18 days ago) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.4 dmi.board.name: 00D283 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.4:bd05/12/2017:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn00D283:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 3510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282/+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 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure
** Changed in: crash (Ubuntu) Status: Fix Released => Fix Committed ** Changed in: crash (Ubuntu Xenial) Importance: Undecided => High ** Changed in: crash (Ubuntu Xenial) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1712867 Title: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure Status in crash package in Ubuntu: Fix Committed Status in kexec-tools package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Committed Status in crash source package in Xenial: Fix Released Status in kexec-tools source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Committed Bug description: [Impact] Currently it's not possible to use the kdump functionality in xenial when running the linux-azure kernel. The problem is actually caused by several factors: 1. kexec fails to parse /proc/kcore and thus fails to load the crash kernel. That's similar to bug #1713940 and it's related to 4.10+ kernels. 2. When the crash kernel boots, a bug in KASLR causes it to crash in a very early stage. For the user, it seems the system just rebooted after the crash. 3. Currently in azure, crashkernel=128G is not enough to boot and run the dump procedure with 4.11+ kernels. That value needs to be increased in order to kdump to succeed. 4. After the vmcore is dumped, the current version of crash in xenial is not able to parse it. All the necessary fixes are already upstream and can be backported. [Test Case] 1. Install the linux-azure kernel in an azure instance (although it's possible to run linux-azure in bare metal or kvm, the KASLR issue only is triggered in azure). 2. Follow the instructions in https://help.ubuntu.com/lts/serverguide /kernel-crash-dump.html to setup kdump and manually trigger a crash using /proc/sysrq-trigger. The vmcore must be generated and it should be possible to inspect it using crash. 3. Perform these same tests for the linux-generic kernel, on each supported architecture. [Regression Potential] Since both kexec-tools and crash are being changed to support 4.10+ kernels, it's very important that they continue to handle 4.4 kernels properly. The same steps above can be used to test linux-generic for regressions. [Other Info] Original description: --8<-- Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the following error: kdump-tools[1436]: ELF core (kcore) parse failed Perhaps the artful kexec-tools should be backported? --8<-- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1712867/+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 1718107] Re: brk_near_huge test will hang on IBM s390x zKVM / zVM
** Also affects: ubuntu-z-systems Importance: Undecided Status: New -- 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/1718107 Title: brk_near_huge test will hang on IBM s390x zKVM / zVM Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Incomplete Bug description: This issue does not exist on other amd64 / i386 / arm64 boxes. Steps: 1. Clone git://kernel.ubuntu.com/ubuntu/autotest-client-tests 2. Untar libhugetlbfs/libhugetlbfs-2.20.tar.gz 3. Run `sudo BUILDTYPE=NATIVEONLY make check` in the extracted libhugetlbfs-2.20 directory 4. Hit Ctrl + C to terminate it From the output you will see it get stuck: truncate_above_4GB (1024K: 64): PASS brk_near_huge (1024K: 64):brk_near_huge: malloc.c:2427: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed. task-size-overrun (1024K: 64): From the syslog you can see brk_near_huge has crashed: Sep 19 07:28:25 s2lp6g004 rsyslogd-2007: action 'action 10' suspended, next retry is Tue Sep 19 07:29:55 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Application brk_near_huge, PID 10474 crashed Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Writing core files to ['/home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.brk_near_huge.10474'] Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Could not determine from which application core file /home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.brk_near_huge.10474/core is from After hitting Ctrl + C to interrupt, kernel trace could be found in syslog: Sep 19 07:30:02 s2lp6g004 kernel: [11224.325504] report_user_fault: 35 callbacks suppressed Sep 19 07:30:02 s2lp6g004 kernel: [11224.325507] User process fault: interruption code 0010 ilc:3 in stack_grow_into_huge[12f88+4000] Sep 19 07:30:02 s2lp6g004 kernel: [11224.325520] Failing address: 03ffe72fe000 TEID: 03ffe72fe400 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325521] Fault in primary space mode while using user ASCE. Sep 19 07:30:02 s2lp6g004 kernel: [11224.325523] AS:551701c7 R3:48d88007 S:0020 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325527] CPU: 0 PID: 10481 Comm: stack_grow_into Tainted: P DO4.13.0-11-generic #12-Ubuntu Sep 19 07:30:02 s2lp6g004 kernel: [11224.325527] Hardware name: IBM 2964 N63 400 (KVM/Linux) Sep 19 07:30:02 s2lp6g004 kernel: [11224.325528] task: 6245 task.stack: 62b3c000 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325529] User PSW : 070530018000 00012f8819a8 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325530]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:3 PM:0 RI:0 EA:3 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325531] User GPRS: 02001c51e2f8 f000 0004 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325531]03fff72fe5c0 0003 000157806000 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325532]fff0 0010 03fff700 03fff72fe520 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325532]02001c426000 0003 00012f8819a2 03ffe72fe518 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540] User Code: 00012f881996: e548b0a80001mvghi 168(%r11),1 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f88199c: c0e5fc86brasl %r14,12f8812a8 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540] #00012f8819a2: c2f41008slgfi %r15,268435464 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540] >00012f8819a8: e54cf0a1mvhi160(%r15),1 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819ae: 4110f0a0la %r1,160(%r15) Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819b2: ec1afff8a065clgrj %r1,%r10,10,12f8819a2 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819b8: b24f0010ear %r1,%a0 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819bc: eb11002dsllg%r1,%r1,32 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325549] Last Breaking-Event-Address: Sep 19 07:30:02 s2lp6g004 kernel: [11224.325552] [<02001c7f26e8>] 0x2001c7f26e8 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325562] Process 10481(stack_grow_into) has RLIMIT_CORE set to 1 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325563] Aborting core Please find attachment for a more detailed syslog and core dump file. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-11-gen
[Kernel-packages] [Bug 1702910] Re: System freeze after in6_dev_finish_destroy errors
There's a discussion here possibly about the same problem: https://patchwork.ozlabs.org/patch/801533/ And they referred to this patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable.git/commit/?id=242d3a49a2a1a71d8eb9f953db1bcaa9d698ce00 The changes look like they line up with the call trace order, but I could be wrong. -- 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/1702910 Title: System freeze after in6_dev_finish_destroy errors Status in linux package in Ubuntu: Incomplete Bug description: After the upgrade to the `4.4.0-83-generic #106~14.04.1-Ubuntu` kernel we are seeing system hangs with the following logs. Prior to this upgrade there were no crashes or kernel traces of this sort. We have ruled out physical hardware issues by moving the VM to another physical host. In the logs there's reference to docker instances on the host. This results in veth devices being brought up and torn down frequently, which is likely related. As a possible workaround we have disabled IPv6 for now. ``` kernel: [337352.274907] vethf317e0d: renamed from eth0 kernel: [337352.386446] docker0: port 1(veth160ed4a) entered disabled state kernel: [337352.393444] docker0: port 1(veth160ed4a) entered disabled state kernel: [337352.395408] device veth160ed4a left promiscuous mode kernel: [337352.395417] docker0: port 1(veth160ed4a) entered disabled state kernel: [337359.301576] vethee2599d: renamed from eth0 kernel: [337359.339582] docker0: port 2(veth3100aab) entered disabled state kernel: [337359.343059] docker0: port 2(veth3100aab) entered disabled state kernel: [337359.344987] device veth3100aab left promiscuous mode kernel: [337359.344997] docker0: port 2(veth3100aab) entered disabled state kernel: [337475.398358] [ cut here ] kernel: [337475.398370] WARNING: CPU: 3 PID: 23671 at /build/linux-lts-xenial-ep3zLI/linux-lts-xenial-4.4.0/net/ipv6/addrconf_core.c:159 in6_dev_f kernel: [337475.398372] Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c veth ip6table_filter ip6_tab comment ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_fil filter bridge stp llc aufs tcp_diag inet_diag coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel ppdev aes_x86_64 lrw gf128mul input_leds serio_raw drm_kms_helper parport_pc drm lp fb_sys_fops syscopyarea sysfillrect sysimgblt vmw_vmci parport shpchp 8250_fintek i2c_piix4 kernel: [337475.398416] CPU: 3 PID: 23671 Comm: kworker/u8:0 Not tainted 4.4.0-83-generic #106~14.04.1-Ubuntu kernel: [337475.398418] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/17/2015 kernel: [337475.398423] Workqueue: netns cleanup_net kernel: [337475.398424] 8801b197fbb8 813ddefc kernel: [337475.398427] 81d7aa10 8801b197fbf0 8107ea36 88016f97d400 kernel: [337475.398428] 88016f97e800 0006 8801b197fcc0 kernel: [337475.398430] Call Trace: kernel: [337475.398435] [] dump_stack+0x63/0x87 kernel: [337475.398440] [] warn_slowpath_common+0x86/0xc0 kernel: [337475.398442] [] warn_slowpath_null+0x1a/0x20 kernel: [337475.398444] [] in6_dev_finish_destroy+0x6b/0xb0 kernel: [337475.398447] [] ip6_route_dev_notify+0x110/0x130 kernel: [337475.398450] [] notifier_call_chain+0x49/0x70 kernel: [337475.398452] [] raw_notifier_call_chain+0x16/0x20 kernel: [337475.398455] [] call_netdevice_notifiers_info+0x35/0x60 kernel: [337475.398458] [] netdev_run_todo+0x157/0x300 kernel: [337475.398461] [] ? rollback_registered_many+0x22e/0x2e0 kernel: [337475.398463] [] rtnl_unlock+0xe/0x10 kernel: [337475.398464] [] default_device_exit_batch+0x138/0x150 kernel: [337475.398468] [] ? __wake_up_sync+0x20/0x20 kernel: [337475.398470] [] ops_exit_list.isra.4+0x52/0x60 kernel: [337475.398472] [] cleanup_net+0x1b3/0x280 kernel: [337475.398476] [] process_one_work+0x150/0x3f0 kernel: [337475.398478] [] worker_thread+0x11a/0x470 kernel: [337475.398481] [] ? __schedule+0x359/0x980 kernel: [337475.398483] [] ? rescuer_thread+0x310/0x310 kernel: [337475.398484] [] kthread+0xd6/0xf0 kernel: [337475.398486] [] ? kthread_park+0x60/0x60 kernel: [337475.398488] [] ret_from_fork+0x3f/0x70 kernel: [337475.398490] [] ? kthread_park+0x60/0x60 kernel: [337475.398491] ---[ end trace 6d63274dc9a3dbec ]--- kernel: [337475.398492] [ cut here ] ``` ProblemType: Bug ApportVersion: 2.14.1-0ubuntu3.24 Architecture: amd64 Date: Fri Jul 7 13:59:36 2017 Dependencies: adduser 3.113+nmu3ubuntu3 apt-utils 1.0.1ubunt
[Kernel-packages] [Bug 1718107] Re: brk_near_huge test will hang on IBM s390x zKVM / zVM
** Changed in: ubuntu-z-systems Assignee: (unassigned) => bugproxy (bugproxy) -- 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/1718107 Title: brk_near_huge test will hang on IBM s390x zKVM / zVM Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Incomplete Bug description: This issue does not exist on other amd64 / i386 / arm64 boxes. Steps: 1. Clone git://kernel.ubuntu.com/ubuntu/autotest-client-tests 2. Untar libhugetlbfs/libhugetlbfs-2.20.tar.gz 3. Run `sudo BUILDTYPE=NATIVEONLY make check` in the extracted libhugetlbfs-2.20 directory 4. Hit Ctrl + C to terminate it From the output you will see it get stuck: truncate_above_4GB (1024K: 64): PASS brk_near_huge (1024K: 64):brk_near_huge: malloc.c:2427: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed. task-size-overrun (1024K: 64): From the syslog you can see brk_near_huge has crashed: Sep 19 07:28:25 s2lp6g004 rsyslogd-2007: action 'action 10' suspended, next retry is Tue Sep 19 07:29:55 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Application brk_near_huge, PID 10474 crashed Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Writing core files to ['/home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.brk_near_huge.10474'] Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Could not determine from which application core file /home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.brk_near_huge.10474/core is from After hitting Ctrl + C to interrupt, kernel trace could be found in syslog: Sep 19 07:30:02 s2lp6g004 kernel: [11224.325504] report_user_fault: 35 callbacks suppressed Sep 19 07:30:02 s2lp6g004 kernel: [11224.325507] User process fault: interruption code 0010 ilc:3 in stack_grow_into_huge[12f88+4000] Sep 19 07:30:02 s2lp6g004 kernel: [11224.325520] Failing address: 03ffe72fe000 TEID: 03ffe72fe400 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325521] Fault in primary space mode while using user ASCE. Sep 19 07:30:02 s2lp6g004 kernel: [11224.325523] AS:551701c7 R3:48d88007 S:0020 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325527] CPU: 0 PID: 10481 Comm: stack_grow_into Tainted: P DO4.13.0-11-generic #12-Ubuntu Sep 19 07:30:02 s2lp6g004 kernel: [11224.325527] Hardware name: IBM 2964 N63 400 (KVM/Linux) Sep 19 07:30:02 s2lp6g004 kernel: [11224.325528] task: 6245 task.stack: 62b3c000 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325529] User PSW : 070530018000 00012f8819a8 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325530]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:3 PM:0 RI:0 EA:3 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325531] User GPRS: 02001c51e2f8 f000 0004 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325531]03fff72fe5c0 0003 000157806000 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325532]fff0 0010 03fff700 03fff72fe520 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325532]02001c426000 0003 00012f8819a2 03ffe72fe518 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540] User Code: 00012f881996: e548b0a80001mvghi 168(%r11),1 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f88199c: c0e5fc86brasl %r14,12f8812a8 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540] #00012f8819a2: c2f41008slgfi %r15,268435464 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540] >00012f8819a8: e54cf0a1mvhi160(%r15),1 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819ae: 4110f0a0la %r1,160(%r15) Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819b2: ec1afff8a065clgrj %r1,%r10,10,12f8819a2 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819b8: b24f0010ear %r1,%a0 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819bc: eb11002dsllg%r1,%r1,32 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325549] Last Breaking-Event-Address: Sep 19 07:30:02 s2lp6g004 kernel: [11224.325552] [<02001c7f26e8>] 0x2001c7f26e8 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325562] Process 10481(stack_grow_into) has RLIMIT_CORE set to 1 Sep 19 07:30:02 s2lp6g004 kernel: [11224.325563] Aborting core Please find attachment for a more detailed syslog and core dump file. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-1
[Kernel-packages] [Bug 1718149] Re: linux: 4.4.0-97.120 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.4.0-97.120 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1718149 Title: linux: 4.4.0-97.120 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718150,1718151 derivatives: 1718153,1718154,1718155,1718156,1718157 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718149/+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 1718161] Re: linux-lts-trusty: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1718159 + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Tuesday, 19. September 2017 16:02 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1718159 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Tuesday, 19. September 2017 16:02 UTC + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1718161 Title: linux-lts-trusty: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1718159 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718161/+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 1718159] Re: linux: 3.13.0-133.182 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718161 derivatives: + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Tuesday, 19. September 2017 16:02 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718161 derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 19. September 2017 16:02 UTC + + -- swm properties -- + phase: Uploaded -- 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/1718159 Title: linux: 3.13.0-133.182 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718161 derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 19. September 2017 16:02 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718159/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
** Also affects: nss-pam-ldapd (Ubuntu) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu) Importance: Undecided Status: New ** Also affects: openvpn (Ubuntu) Importance: Undecided Status: New ** Also affects: postfix (Ubuntu) Importance: Undecided Status: New ** Also affects: quicktun (Ubuntu) Importance: Undecided Status: New ** Also affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Also affects: sendmail (Ubuntu) Importance: Undecided Status: New ** Also affects: shorewall-init (Ubuntu) Importance: Undecided Status: New ** Also affects: sidedoor (Ubuntu) Importance: Undecided Status: New ** Also affects: slrn (Ubuntu) Importance: Undecided Status: New ** Also affects: tinc (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu) Importance: Undecided Status: New ** Also affects: ucarp (Ubuntu) Importance: Undecided Status: New ** Also affects: uml-utilities (Ubuntu) Importance: Undecided Status: New ** Also affects: uruk (Ubuntu) Importance: Undecided Status: New ** Also affects: vlan (Ubuntu) Importance: Undecided Status: New ** Also affects: vzctl (Ubuntu) Importance: Undecided Status: New ** Also affects: wide-dhcpv6 (Ubuntu) Importance: Undecided Status: New ** Also affects: wpa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1718227 Title: replacement of ifupdown with netplan needs integration for /etc/network/if{up,down}.d scripts Status in aiccu package in Ubuntu: Invalid Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: New Status in bind9 package in Ubuntu: New Status in chrony package in Ubuntu: New Status in clamav package in Ubuntu: New Status in controlaula package in Ubuntu: New Status in epoptes package in Ubuntu: New Status in ethtool package in Ubuntu: New Status in guidedog package in Ubuntu: New Status in htpdate package in Ubuntu: New Status in ifenslave package in Ubuntu: New Status in ifmetric package in Ubuntu: New Status in ifupdown-multi package in Ubuntu: New Status in ifupdown-scripts-zg2 package in Ubuntu: New Status in isatapd package in Ubuntu: New Status in lprng package in Ubuntu: New Status in miredo package in Ubuntu: New Status in mythtv package in Ubuntu: New Status in nplan package in Ubuntu: New Status in nss-pam-ldapd package in Ubuntu: New Status in ntp package in Ubuntu: New Status in openntpd package in Ubuntu: New Status in openresolv package in Ubuntu: New Status in openssh package in Ubuntu: New Status in openvpn package in Ubuntu: New Status in postfix package in Ubuntu: New Status in quicktun package in Ubuntu: New Status in resolvconf package in Ubuntu: New Status in sendmail package in Ubuntu: New Status in shorewall-init package in Ubuntu: New Status in sidedoor package in Ubuntu: New Status in slrn package in Ubuntu: New Status in tinc package in Ubuntu: New Status in ubuntu-fan package in Ubuntu: New Status in ucarp package in Ubuntu: New Status in uml-utilities package in Ubuntu: New Status in uruk package in Ubuntu: New Status in vlan package in Ubuntu: New Status in vzctl package in Ubuntu: New Status in wide-dhcpv6 package in Ubuntu: New Status in wpa package in Ubuntu: New Bug description: when network is configured with ifupdown, scripts in /etc/network/ifup.d/ were called on network being brought up and /etc/network/ifdown.d were called on network being brought down. Any packages that shipped these hooks need to be verified to have the same functionality under a netplan configured system. # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u) # for i in $binpkgs; do src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }'); [ -z "$src" ] && src="$i"; echo $src; done | sort -u aiccu aoetools avahi bind9 chrony clamav controlaula epoptes ethtool guidedog htpdate ifenslave ifmetric ifupdown-extra ifupdown-multi ifupdown-scripts-zg2 isatapd lprng miredo mythtv-backend nss-pam-ldapd ntp openntpd openresolv openssh openvpn postfix quicktun resolvconf sendmail shorewall-init sidedoor slrn tinc ubuntu-fan ucarp uml-utilities uruk vlan vzctl wide-dhcpv6 wpa Related bugs: * bug 1718227: replacement of ifupdown with netplan needs integration for /etc/network/if{up,down}.d scripts * bug 1713803: replacement of resolvconf with systemd needs integration * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration ProblemTyp
[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- 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/1670634 Title: blk-mq: possible deadlock on CPU hot(un)plug Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Fix Committed Bug description: == Comment: #0 - Carsten Jacobi - 2017-03-07 03:35:31 == I'm evaluating Ubuntu-Xenial on z for development purposes, the test system is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all pathes are configured). The system hangs regularly when I make packages with "pdebuild" using the pbuilder packaging suit. The local Linux development team helped me out with a pre-analysis that I can post here (thanks a lot for that): With the default settings and under a certain workload, blk_mq seems to get into a presumed "deadlock". Possibly this happens on CPU hot(un)plug. After the I/O stalled, a dump was pulled manually. The following information is from the crash dump pre-analysis. $ zgetdump -i dump.0 General dump info: Dump format: elf Version: 1 UTS node name..: mclint UTS kernel release.: 4.4.0-65-generic UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 System arch: s390x (64 bit) CPU count (online).: 2 Dump memory range..: 8192 MB Memory map: - 0001b831afff (7043 MB) 0001b831b000 - 0001 (1149 MB) Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1. KERNEL: vmlinux.full DUMPFILE: dump.0 CPUS: 2 DATE: Fri Mar 3 14:31:07 2017 UPTIME: 02:11:20 LOAD AVERAGE: 13.00, 12.92, 11.37 TASKS: 411 NODENAME: mclint RELEASE: 4.4.0-65-generic VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 MACHINE: s390x (unknown Mhz) MEMORY: 7.8 GB PANIC: "" PID: 0 COMMAND: "swapper/0" TASK: bad528 (1 of 2) [THREAD_INFO: b78000] CPU: 0 STATE: TASK_RUNNING (ACTIVE) INFO: no panic task found crash> dev -d MAJOR GENDISKNAME REQUEST_QUEUE TOTAL ASYNC SYNC DRV ... 8 1e1d6d800 sda1e1d51210 0 23151 4294944145 N/A(MQ) 8 1e4e06800 sdc2081b180 23148 4294944148 N/A(MQ) 8 1f07800sdb20c75680 23195 4294944101 N/A(MQ) 8 1e4e06000 sdd1e4e31210 0 23099 4294944197 N/A(MQ) 252 1e1d6c800 dm-0 1e1d51b18 9 1 8 N/A(MQ) ... So both dm-mpath and sd have requests pending in their block multiqueue. The large numbers of sd look strange and seem to be the unsigned formatting of the values shown for async multiplied by -1. [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49) [0.798262] setup: Linux is running natively in 64-bit mode [0.798290] setup: Max memory size: 8192MB [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel (System RAM: 7996MB) [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0 [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 seconds. [ 5281.179437] Not tainted 4.4.0-65-generic #86-Ubuntu [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 5281.179440] xfsaild/dm-11 D 007bcf52 0 1604 2 0x [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 0001e6f9b9d8 0001e15795f0 0001e6f9b988 00ce8c00 0001ea805c70 0001ea805c00 00ba5ed0 0001e931c1d0 0001e1579b20 0001ea805c00 0001e15795f0 0001ea805c00 007d3978 007bc9f8 0001e6f9b9d8 0001e6f9ba40 [ 5281.179454] Call Trace: [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810) [ 5281.179462] [<007bcf52>] schedule+0x4a/0xb0 [ 5281.179465] [<007c02aa>] schedule_timeout+0x232/0x2a8 [ 5281.179466] [<007bde50>] wait_for_common+0x110/0x1c8 [ 5281.179472] [<0017b602>] flush_work+0x42/0x58 [ 5281.179564] [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs] [ 5281.179589] [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs] [ 5281.179615] [<03ff805df114>] xfs_log_force+0x44/0x100 [xfs] [ 5281.179640] [<03ff805ec668>] xfsaild+0x
[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
** Description changed: when network is configured with ifupdown, scripts in /etc/network/ifup.d/ were called on network being brought up and /etc/network/ifdown.d were called on network being brought down. Any packages that shipped these hooks need to be verified to have the same functionality under a netplan configured system. + # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u) + # for i in $binpkgs; do + src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }'); + [ -z "$src" ] && src="$i"; echo $src; done | sort -u - $ apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u aiccu aoetools - avahi-autoipd - avahi-daemon + avahi bind9 chrony - clamav-freshclam + clamav controlaula - epoptes-client + epoptes ethtool guidedog htpdate ifenslave ifmetric ifupdown-extra ifupdown-multi ifupdown-scripts-zg2 isatapd lprng miredo mythtv-backend - nslcd - ntpdate + nss-pam-ldapd + ntp openntpd openresolv - openssh-server + openssh openvpn postfix quicktun resolvconf - sendmail-base + sendmail shorewall-init sidedoor slrn - slrnpull tinc ubuntu-fan ucarp uml-utilities uruk vlan vzctl - wide-dhcpv6-client - wpasupplicant + wide-dhcpv6 + wpa + + + Related bugs: + * bug 1718227: replacement of ifupdown with netplan needs integration for /etc/network/if{up,down}.d scripts + * bug 1713803: replacement of resolvconf with systemd needs integration + * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration + ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: netplan (not installed) ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 19 10:53:08 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: plan UpgradeStatus: No upgrade log present (probably fresh install) ** Tags added: netplan-transition -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1718227 Title: replacement of ifupdown with netplan needs integration for /etc/network/if{up,down}.d scripts Status in aiccu package in Ubuntu: Invalid Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: New Status in bind9 package in Ubuntu: New Status in chrony package in Ubuntu: New Status in clamav package in Ubuntu: New Status in controlaula package in Ubuntu: New Status in epoptes package in Ubuntu: New Status in ethtool package in Ubuntu: New Status in guidedog package in Ubuntu: New Status in htpdate package in Ubuntu: New Status in ifenslave package in Ubuntu: New Status in ifmetric package in Ubuntu: New Status in ifupdown-multi package in Ubuntu: New Status in ifupdown-scripts-zg2 package in Ubuntu: New Status in isatapd package in Ubuntu: New Status in lprng package in Ubuntu: New Status in miredo package in Ubuntu: New Status in mythtv package in Ubuntu: New Status in nplan package in Ubuntu: New Status in nss-pam-ldapd package in Ubuntu: New Status in ntp package in Ubuntu: New Status in openntpd package in Ubuntu: New Status in openresolv package in Ubuntu: New Status in openssh package in Ubuntu: New Status in openvpn package in Ubuntu: New Status in postfix package in Ubuntu: New Status in quicktun package in Ubuntu: New Status in resolvconf package in Ubuntu: New Status in sendmail package in Ubuntu: New Status in shorewall-init package in Ubuntu: New Status in sidedoor package in Ubuntu: New Status in slrn package in Ubuntu: New Status in tinc package in Ubuntu: New Status in ubuntu-fan package in Ubuntu: New Status in ucarp package in Ubuntu: New Status in uml-utilities package in Ubuntu: New Status in uruk package in Ubuntu: New Status in vlan package in Ubuntu: New Status in vzctl package in Ubuntu: New Status in wide-dhcpv6 package in Ubuntu: New Status in wpa package in Ubuntu: New Bug description: when network is configured with ifupdown, scripts in /etc/network/ifup.d/ were called on network being brought up and /etc/network/ifdown.d were called on network being brought down. Any packages that shipped these hooks need to be verified to have the same functionality under a netplan configured system. # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u) # for i in $binpkgs; do src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[Kernel-packages] [Bug 1711104] Re: [P9][Ubuntu 16.04.03] Additional PMU fixes for P9
Yes, that commit is in the test kernel posted at: http://kernel.ubuntu.com/~jsalisbury/lp1711104/ -- 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/1711104 Title: [P9][Ubuntu 16.04.03] Additional PMU fixes for P9 Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Status in perforate source package in Zesty: New Bug description: == Comment: #0 - Shriya R. Kulkarni - 2017-08-16 04:07:45 == Please integrate the following PMU fixes for P9. 93fc5ca9a0048c ('powerpc/perf: Cleanup of PM_BR_CMPL vs. PM_BRU_CMPL in Power9 event list') 91e0bd1e62519b ('powerpc/perf: Add PM_LD_MISS_L1 and PM_BR_2PATH to power9 event list') 70a7e720998d5b ('powerpc/perf: Factor out PPMU_ONLY_COUNT_RUN check code from power8') 7aa345d84245a7 ('powerpc/perf: Update default sdar_mode value for power9') 101dd590a7fa37 ('powerpc/perf: Avoid spurious PMU interrupts after idle') bdd21ddb919d28 ('powerpc/perf: Avoid spurious PMU interrupts after idle on Power9') 3f0bd8dad0db73 ('powerpc/perf: Add POWER9 alternate PM_RUN_CYC and PM_RUN_INST_CMPL events') 20dd4c624d2515 ('powerpc/perf: Fix SDAR_MODE value for continous sampling on Power9') 24bedcb7c81137 ('powerpc/perf: Fix branch event code for power9') 8c218578fcbbbd ('powerpc/perf: Fix Power9 test_adder fields') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711104/+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 1700606] Re: POWER9: CAPI2 enablement - Fixes
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Zesty) Status: In Progress => 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/1700606 Title: POWER9: CAPI2 enablement - Fixes Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: Invalid Bug description: = Comment: #2 - Christophe Lombard - 2017-06-26 11:15:53 == Here are new cxl patches we would like to include on Zesty kernel. These patches bring fixes for the CXL device driver for CAPI and CAPI2. They apply on top of https://bugzilla.linux.ibm.com/show_bug.cgi?id=153737 commit ids: ea9a26d117cf0637c71d3e0076f4a124bf5859df cxl: Force context lock during EEH flow 4f58f0bf155e87dda31a3088b1e107fa9dd79f0e cxl: Route eeh events to all drivers in cxl_pci_error_detected() a715626a8e904e7226915d1bc4885317ea9da141 cxl: Mask slice error interrupts after first occurrence b3aa20ba2ba8072b73bd799605b8c98927b7056c cxl: Avoid double free_irq() for psl,slice interrupts cec422c11caeeccae709e9942058b6b644ce434c cxl: Fix error path on bad ioctl 797625deaedd9a0621376817db2813244b3246e3 cxl: Fixes for Coherent Accelerator Interface Architecture 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1700606/+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 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services
Thanks for the clarification. Since there are two issues, we should probably focus on one at a time. The test kernel posted in comment #36 sounds like it fixes the first issue, so lets handle that one first. I'll ping the upstream patch author for that commit and get some feedback. Before doing that, can you test 4.14-rc1 to be sure this issue is not already fixed in mainline? It can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc1/ -- 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/1701222 Title: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: In Progress Bug description: Issue description: Hyper-V daemons fail to start after disable/re- enable VM integration services. Platform: host independent Affected daemons - KVP, FCOPY and VSS. Distribution name and release: Ubuntu 16.04, Ubuntu 17.04 Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 4.10.0-19-generic (for Ubuntu 17.04) Repro rate: 100% Steps to reproduce: 1.Start VM with Guest Services enabled (FCopy daemon starts automatically) 2.Go to File > Settings > Integration Services, uncheck Guest Services and apply (FCopy daemon will stop at this point) 3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running). This is the issue. systemd monitors for the service and if we have the hook for the Guest Service, it tries to start the daemon again. systemd attempt to start any of the LIS daemons will fail, but manually executing the daemon binary, it will start the daemon. Additional Info: - the steps above can be repro'd with KVP / Data Exchange integration service as well. - Manually starting hv_fcopy_daemon works fine. - other distros (RHEL) does not have this behavior, the LIS daemons are started automatically by systemd once we re-enable the integration service. On the upstream kernel and the upstream hv daemons, these messages are recorded in syslog, once we re-enable the Guest service: HV_FCOPY: pread failed: Bad file descriptor systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: hv-fcopy-daemon.service: Unit entered failed state. systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701222/+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 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug
** Changed in: linux (Ubuntu) Status: Triaged => Fix Committed ** Changed in: ubuntu-z-systems Status: Triaged => Fix Committed -- 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/1670634 Title: blk-mq: possible deadlock on CPU hot(un)plug Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: == Comment: #0 - Carsten Jacobi - 2017-03-07 03:35:31 == I'm evaluating Ubuntu-Xenial on z for development purposes, the test system is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all pathes are configured). The system hangs regularly when I make packages with "pdebuild" using the pbuilder packaging suit. The local Linux development team helped me out with a pre-analysis that I can post here (thanks a lot for that): With the default settings and under a certain workload, blk_mq seems to get into a presumed "deadlock". Possibly this happens on CPU hot(un)plug. After the I/O stalled, a dump was pulled manually. The following information is from the crash dump pre-analysis. $ zgetdump -i dump.0 General dump info: Dump format: elf Version: 1 UTS node name..: mclint UTS kernel release.: 4.4.0-65-generic UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 System arch: s390x (64 bit) CPU count (online).: 2 Dump memory range..: 8192 MB Memory map: - 0001b831afff (7043 MB) 0001b831b000 - 0001 (1149 MB) Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1. KERNEL: vmlinux.full DUMPFILE: dump.0 CPUS: 2 DATE: Fri Mar 3 14:31:07 2017 UPTIME: 02:11:20 LOAD AVERAGE: 13.00, 12.92, 11.37 TASKS: 411 NODENAME: mclint RELEASE: 4.4.0-65-generic VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 MACHINE: s390x (unknown Mhz) MEMORY: 7.8 GB PANIC: "" PID: 0 COMMAND: "swapper/0" TASK: bad528 (1 of 2) [THREAD_INFO: b78000] CPU: 0 STATE: TASK_RUNNING (ACTIVE) INFO: no panic task found crash> dev -d MAJOR GENDISKNAME REQUEST_QUEUE TOTAL ASYNC SYNC DRV ... 8 1e1d6d800 sda1e1d51210 0 23151 4294944145 N/A(MQ) 8 1e4e06800 sdc2081b180 23148 4294944148 N/A(MQ) 8 1f07800sdb20c75680 23195 4294944101 N/A(MQ) 8 1e4e06000 sdd1e4e31210 0 23099 4294944197 N/A(MQ) 252 1e1d6c800 dm-0 1e1d51b18 9 1 8 N/A(MQ) ... So both dm-mpath and sd have requests pending in their block multiqueue. The large numbers of sd look strange and seem to be the unsigned formatting of the values shown for async multiplied by -1. [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49) [0.798262] setup: Linux is running natively in 64-bit mode [0.798290] setup: Max memory size: 8192MB [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel (System RAM: 7996MB) [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0 [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 seconds. [ 5281.179437] Not tainted 4.4.0-65-generic #86-Ubuntu [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 5281.179440] xfsaild/dm-11 D 007bcf52 0 1604 2 0x [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 0001e6f9b9d8 0001e15795f0 0001e6f9b988 00ce8c00 0001ea805c70 0001ea805c00 00ba5ed0 0001e931c1d0 0001e1579b20 0001ea805c00 0001e15795f0 0001ea805c00 007d3978 007bc9f8 0001e6f9b9d8 0001e6f9ba40 [ 5281.179454] Call Trace: [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810) [ 5281.179462] [<007bcf52>] schedule+0x4a/0xb0 [ 5281.179465] [<007c02aa>] schedule_timeout+0x232/0x2a8 [ 5281.179466] [<007bde50>] wait_for_common+0x110/0x1c8 [ 5281.179472] [<0017b602>] flush_work+0x42/0x58 [ 5281.179564] [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs] [ 5281.179589] [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs] [ 5281.179615] [<03ff805df114>
[Kernel-packages] [Bug 1717581] Re: linux 4.13.0-11.12 ADT test failure with linux 4.13.0-11.12
Bisected to f1dd2cd13c4b "mm, memory_hotplug: do not associate hotadded memory to zones until online." Reported upstream. -- 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/1717581 Title: linux 4.13.0-11.12 ADT test failure with linux 4.13.0-11.12 Status in linux package in Ubuntu: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20170914_153408_2e966@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1717581/+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 1707695] Re: radeon 0000:03:00.0: ring 0 stalled for more than 10000msec
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- 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/1707695 Title: radeon :03:00.0: ring 0 stalled for more than 1msec Status in linux package in Ubuntu: Confirmed Bug description: My system intermittently locks up every few days. It does not seem to correspond to a particular program or action. When that happens, the screen goes to black, then returns after a few seconds. At that point, the time on the clock is static and indicates that the screen is frozen, but audio continues to play for 30 seconds to a minute. The keyboard and mouse do not affect what's being displayed, but I can Alt - SysRq - REISUB to restart. Every time (7 crashes and counting), /var/log/kern.log indicates that kernel: [353692.378886] radeon :03:00.0: ring 0 stalled for more than 10280msec kernel: [353692.378896] radeon :03:00.0: GPU lockup (current fence id 0x006e96e5 last fence id 0x006e96e9 on ring 0) just before the system locks. Different ring numbers are reported as stalling at different times. As per the instructions, I posted a question about this issue at: https://askubuntu.com/questions/937792/system-lockup-radeon-ring- stalled-for-more-than-10280msec?noredirect=1#comment1486875_937792 but I have not received many responses. I'm running 16.04 LTS. :~$ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 According to the Software Center, I am running Ubuntu Software 3.20.1. I have a Radeon HD graphics card. :~$ lspci | grep VGA 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] :~$ lspci -v -s 03:00.0 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Cedar [Radeon HD 5000/6000/7350/8350 Series] Flags: bus master, fast devsel, latency 0, IRQ 53 Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d3d2 (64-bit, non-prefetchable) [size=128K] I/O ports at 7000 [size=256] Expansion ROM at d3d0 [disabled] [size=128K] Capabilities: Kernel driver in use: radeon Kernel modules: radeon Please let me know if additional information would be useful, and I will be glad to provide it. Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-87-generic 4.4.0-87.110 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: clapp 3889 F pulseaudio /dev/snd/controlC2: clapp 3889 F pulseaudio /dev/snd/controlC1: clapp 3889 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 31 14:02:27 2017 HibernationDevice: RESUME=UUID=1b30dad6-8c48-42cf-ae26-66ab8b0eb446 InstallationDate: Installed on 2013-09-04 (1425 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Dell Inc. Precision T7600 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic root=UUID=33722f76-37fd-4289-b071-d7f48b65dd32 ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-87-generic N/A linux-backports-modules-4.4.0-87-generic N/A linux-firmware1.157.11 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 082WXT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/03/2013:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T7600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707695/+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 1707695] Re: radeon 0000:03:00.0: ring 0 stalled for more than 10000msec
The problem reoccurred while running what was the most recent mainline kernel when I downloaded it (v4.13/ 2017-09-03 22:30). The log file is attached. Thanks for your help, jsalisbury. ** Attachment added: "Kernel Log of Latest Crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707695/+attachment/4952992/+files/kern.log -- 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/1707695 Title: radeon :03:00.0: ring 0 stalled for more than 1msec Status in linux package in Ubuntu: Confirmed Bug description: My system intermittently locks up every few days. It does not seem to correspond to a particular program or action. When that happens, the screen goes to black, then returns after a few seconds. At that point, the time on the clock is static and indicates that the screen is frozen, but audio continues to play for 30 seconds to a minute. The keyboard and mouse do not affect what's being displayed, but I can Alt - SysRq - REISUB to restart. Every time (7 crashes and counting), /var/log/kern.log indicates that kernel: [353692.378886] radeon :03:00.0: ring 0 stalled for more than 10280msec kernel: [353692.378896] radeon :03:00.0: GPU lockup (current fence id 0x006e96e5 last fence id 0x006e96e9 on ring 0) just before the system locks. Different ring numbers are reported as stalling at different times. As per the instructions, I posted a question about this issue at: https://askubuntu.com/questions/937792/system-lockup-radeon-ring- stalled-for-more-than-10280msec?noredirect=1#comment1486875_937792 but I have not received many responses. I'm running 16.04 LTS. :~$ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 According to the Software Center, I am running Ubuntu Software 3.20.1. I have a Radeon HD graphics card. :~$ lspci | grep VGA 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] :~$ lspci -v -s 03:00.0 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Cedar [Radeon HD 5000/6000/7350/8350 Series] Flags: bus master, fast devsel, latency 0, IRQ 53 Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d3d2 (64-bit, non-prefetchable) [size=128K] I/O ports at 7000 [size=256] Expansion ROM at d3d0 [disabled] [size=128K] Capabilities: Kernel driver in use: radeon Kernel modules: radeon Please let me know if additional information would be useful, and I will be glad to provide it. Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-87-generic 4.4.0-87.110 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: clapp 3889 F pulseaudio /dev/snd/controlC2: clapp 3889 F pulseaudio /dev/snd/controlC1: clapp 3889 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 31 14:02:27 2017 HibernationDevice: RESUME=UUID=1b30dad6-8c48-42cf-ae26-66ab8b0eb446 InstallationDate: Installed on 2013-09-04 (1425 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Dell Inc. Precision T7600 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic root=UUID=33722f76-37fd-4289-b071-d7f48b65dd32 ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-87-generic N/A linux-backports-modules-4.4.0-87-generic N/A linux-firmware1.157.11 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 082WXT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/03/2013:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T7600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707695/+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 1718150] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1718149 + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Tuesday, 19. September 2017 18:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1718149 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Tuesday, 19. September 2017 18:01 UTC + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1718150 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1718149 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718150/+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 1718149] Re: linux: 4.4.0-97.120 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718150,1718151 derivatives: 1718153,1718154,1718155,1718156,1718157 + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Tuesday, 19. September 2017 18:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718150,1718151 derivatives: 1718153,1718154,1718155,1718156,1718157 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 19. September 2017 18:01 UTC + + -- swm properties -- + phase: Uploaded -- 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/1718149 Title: linux: 4.4.0-97.120 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718150,1718151 derivatives: 1718153,1718154,1718155,1718156,1718157 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 19. September 2017 18:01 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718149/+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 1718155] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1718149 + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Tuesday, 19. September 2017 18:02 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1718149 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Tuesday, 19. September 2017 18:02 UTC + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1718155 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1718149 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718155/+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 1713575] Re: Vlun resize request could fail with cxlflash driver
** Tags added: bugnameltc-158076 severity-high -- 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/1713575 Title: Vlun resize request could fail with cxlflash driver Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: == Comment: #0 - UMA KRISHNAN - 2017-08-28 12:14:12 == ---Problem Description--- Recently a regression in cxlflash driver was identified and a fix has been upstreamed to kernel.org. We would like to get that included in Xenial 16.04.3 SRU (HWE v4.10 kernel). Even though regression patch is the very last one, I have also listed the missing patches in-between, that are minor and will be easier for further cxlflash updates to Xenial. eeac8cda2c957e156093933b860eec09e488fe15 scsi: cxlflash: return -EFAULT if copy_from_user() fails 9ff870417e56b1fb7b15b2cda74de639d3cd8559 scsi: cxlflash: Fix an error handling path in 'cxlflash_disk_attach()' 48a17ad5931c3832eec68411620bc3527021c193 scsi: cxlflash: Remove unnecessary existence check 1a9e394154e34728f58c1f697b993aaaf89a4db2 scsi: cxlflash: Avoid double mutex unlock 07a191f762a7b8d0db13c38036380927116e29bb scsi: cxlflash: Fix vlun resize failure in the shrink path ---Steps to Reproduce--- Vlun resize request could fail after updating to a kernel that includes Commit 565180723294 ("scsi: cxlflash: SISlite updates to support 4 ports") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1713575/+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 1685899] dmesg
Default Comment by Bridge ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1685899/+attachment/4953005/+files/dmesg_jfs -- 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/1685899 Title: [Ubuntu 17.04] - JFS related call traces and system enters xmon when rebooted after installation Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Issue: JFS related call traces and system enters xmon when rebooted after installation Steps to reproduce: - 1 - Install Ubuntu 17.04 the system with - prepboot - /root [JFS filesystem] - swap space 2 -After installation when rebooted it gives out call traces like as below: [3.895246] Unable to handle kernel paging request for data at address 0x [3.895278] Faulting instruction address: 0xd4c5df1c [3.895284] Oops: Kernel access of bad area, sig: 11 [#1] [3.895287] SMP NR_CPUS=2048 [3.895288] NUMA [3.895290] pSeries [3.895292] Modules linked in: ip_tables x_tables autofs4 jfs ibmvscsi crc32c_vpmsum [3.895301] CPU: 30 PID: 923 Comm: ureadahead Not tainted 4.9.0-15-generic #16-Ubuntu [3.895304] task: c00381d3c800 task.stack: c00381fd [3.895307] NIP: d4c5df1c LR: d4c5deb0 CTR: c01279d0 [3.895310] REGS: c00381fd3500 TRAP: 0300 Not tainted (4.9.0-15-generic) [3.895313] MSR: 8280b033 [ 3.895322] CR: 48008804 XER: 0001 [3.895324] CFAR: c0008a60 DAR: DSISR: 4000 SOFTE: 1 GPR00: d4c5deb0 c00381fd3780 d4c78c28 c003802f40f0 GPR04: d4c6f6f0 d4c72b58 0563 d4c78c28 GPR08: 00180e97 d4c6a608 GPR12: c01279d0 cfb90e00 GPR16: GPR20: GPR24: 1000 d4c72b38 GPR28: 00180e97 f0e1d5c0 c003812af240 c003802f40b0 NIP [d4c5df1c] __get_metapage+0x204/0x6f0 [jfs] [3.895372] LR [d4c5deb0] __get_metapage+0x198/0x6f0 [jfs] [3.895374] Call Trace: [3.895378] [c00381fd3780] [d4c5de6c] __get_metapage+0x154/0x6f0 [jfs] (unreliable) [3.895384] [c00381fd3870] [d4c4c368] diRead+0x130/0x260 [jfs] [3.895388] [c00381fd3920] [d4c424f4] jfs_iget+0x6c/0x1e0 [jfs] [3.895393] [c00381fd3950] [d4c43adc] jfs_lookup+0xe4/0x100 [jfs] [3.895398] [c00381fd3a80] [c032a120] lookup_slow+0xe0/0x240 [3.895402] [c00381fd3b00] [c032e8a8] walk_component+0x2d8/0x3f0 [3.895406] [c00381fd3b70] [c032eb94] link_path_walk+0x1d4/0x600 [3.895409] [c00381fd3c00] [c0330c1c] path_openat+0xbc/0x480 [3.895413] [c00381fd3c80] [c03328ac] do_filp_open+0xec/0x160 [3.895417] [c00381fd3db0] [c031863c] do_sys_open+0x1cc/0x380 [3.895421] [c00381fd3e30] [c000bd84] system_call+0x38/0xe0 [3.895424] Instruction dump: [3.895426] 7909f00e 7fc9f214 3921 f93f0028 fbdf0030 e93d 71280800 41820460 [3.895433] ebdd0030 41920034 e91d0008 e93f0038 811e 80e70090 39080001 [3.895441] ---[ end trace c2aa9ba09ea05eac ]--- [3.895443] [4.088560] systemd-journald[925]: Received request to flush runtime journal from PID 1 [4.362062] crypto_register_alg 'aes' = 0 [4.362112] crypto_register_alg 'cbc(aes)' = 0 [4.362150] crypto_register_alg 'ctr(aes)' = 0 [4.362191] crypto_register_alg 'xts(aes)' = 0 [4.366949] pseries_rng: Registering IBM pSeries RNG driver When I first connected to the LPAR, it was unresponsive so I restarted it from the HMC and surprisingly it came up to the login prompt and I logged into the shell. I proceeded to install the matching linux- image-4.10.0-15-generic-dbgsym_4.10.0-15.17_ppc64el.ddeb. However, the installation of the matching dbgsym wasn't as helpful as I wanted it to be. objdump, crash tool, or addr2line wouldn't give me the source line correspond to the NIP address. I then restarted the LPAR with xmon enabled and it would drop to xmon immediately after attempting to remount / and at the same location as before at __get_metapage+0x204/0x6f0 [jfs] and again with a dereference of 0x0 as the cause of the data exception 0xd649df54 <__get_metapage+508>:ld r8,8(r29) 0xd649df58 <__get_metapage+512>:ld r9,56(r31) 0xd649df5c <__ge
[Kernel-packages] [Bug 1685899] xmon log data
Default Comment by Bridge ** Attachment added: "xmon log data" https://bugs.launchpad.net/bugs/1685899/+attachment/4953004/+files/xmonlogs -- 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/1685899 Title: [Ubuntu 17.04] - JFS related call traces and system enters xmon when rebooted after installation Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Issue: JFS related call traces and system enters xmon when rebooted after installation Steps to reproduce: - 1 - Install Ubuntu 17.04 the system with - prepboot - /root [JFS filesystem] - swap space 2 -After installation when rebooted it gives out call traces like as below: [3.895246] Unable to handle kernel paging request for data at address 0x [3.895278] Faulting instruction address: 0xd4c5df1c [3.895284] Oops: Kernel access of bad area, sig: 11 [#1] [3.895287] SMP NR_CPUS=2048 [3.895288] NUMA [3.895290] pSeries [3.895292] Modules linked in: ip_tables x_tables autofs4 jfs ibmvscsi crc32c_vpmsum [3.895301] CPU: 30 PID: 923 Comm: ureadahead Not tainted 4.9.0-15-generic #16-Ubuntu [3.895304] task: c00381d3c800 task.stack: c00381fd [3.895307] NIP: d4c5df1c LR: d4c5deb0 CTR: c01279d0 [3.895310] REGS: c00381fd3500 TRAP: 0300 Not tainted (4.9.0-15-generic) [3.895313] MSR: 8280b033 [ 3.895322] CR: 48008804 XER: 0001 [3.895324] CFAR: c0008a60 DAR: DSISR: 4000 SOFTE: 1 GPR00: d4c5deb0 c00381fd3780 d4c78c28 c003802f40f0 GPR04: d4c6f6f0 d4c72b58 0563 d4c78c28 GPR08: 00180e97 d4c6a608 GPR12: c01279d0 cfb90e00 GPR16: GPR20: GPR24: 1000 d4c72b38 GPR28: 00180e97 f0e1d5c0 c003812af240 c003802f40b0 NIP [d4c5df1c] __get_metapage+0x204/0x6f0 [jfs] [3.895372] LR [d4c5deb0] __get_metapage+0x198/0x6f0 [jfs] [3.895374] Call Trace: [3.895378] [c00381fd3780] [d4c5de6c] __get_metapage+0x154/0x6f0 [jfs] (unreliable) [3.895384] [c00381fd3870] [d4c4c368] diRead+0x130/0x260 [jfs] [3.895388] [c00381fd3920] [d4c424f4] jfs_iget+0x6c/0x1e0 [jfs] [3.895393] [c00381fd3950] [d4c43adc] jfs_lookup+0xe4/0x100 [jfs] [3.895398] [c00381fd3a80] [c032a120] lookup_slow+0xe0/0x240 [3.895402] [c00381fd3b00] [c032e8a8] walk_component+0x2d8/0x3f0 [3.895406] [c00381fd3b70] [c032eb94] link_path_walk+0x1d4/0x600 [3.895409] [c00381fd3c00] [c0330c1c] path_openat+0xbc/0x480 [3.895413] [c00381fd3c80] [c03328ac] do_filp_open+0xec/0x160 [3.895417] [c00381fd3db0] [c031863c] do_sys_open+0x1cc/0x380 [3.895421] [c00381fd3e30] [c000bd84] system_call+0x38/0xe0 [3.895424] Instruction dump: [3.895426] 7909f00e 7fc9f214 3921 f93f0028 fbdf0030 e93d 71280800 41820460 [3.895433] ebdd0030 41920034 e91d0008 e93f0038 811e 80e70090 39080001 [3.895441] ---[ end trace c2aa9ba09ea05eac ]--- [3.895443] [4.088560] systemd-journald[925]: Received request to flush runtime journal from PID 1 [4.362062] crypto_register_alg 'aes' = 0 [4.362112] crypto_register_alg 'cbc(aes)' = 0 [4.362150] crypto_register_alg 'ctr(aes)' = 0 [4.362191] crypto_register_alg 'xts(aes)' = 0 [4.366949] pseries_rng: Registering IBM pSeries RNG driver When I first connected to the LPAR, it was unresponsive so I restarted it from the HMC and surprisingly it came up to the login prompt and I logged into the shell. I proceeded to install the matching linux- image-4.10.0-15-generic-dbgsym_4.10.0-15.17_ppc64el.ddeb. However, the installation of the matching dbgsym wasn't as helpful as I wanted it to be. objdump, crash tool, or addr2line wouldn't give me the source line correspond to the NIP address. I then restarted the LPAR with xmon enabled and it would drop to xmon immediately after attempting to remount / and at the same location as before at __get_metapage+0x204/0x6f0 [jfs] and again with a dereference of 0x0 as the cause of the data exception 0xd649df54 <__get_metapage+508>:ld r8,8(r29) 0xd649df58 <__get_metapage+512>:ld r9,56(r31) 0xd649df5
[Kernel-packages] [Bug 1685899] kernel log buffer from xmon with debug jfs
Default Comment by Bridge ** Attachment added: "kernel log buffer from xmon with debug jfs" https://bugs.launchpad.net/bugs/1685899/+attachment/4953006/+files/jfs.log -- 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/1685899 Title: [Ubuntu 17.04] - JFS related call traces and system enters xmon when rebooted after installation Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Issue: JFS related call traces and system enters xmon when rebooted after installation Steps to reproduce: - 1 - Install Ubuntu 17.04 the system with - prepboot - /root [JFS filesystem] - swap space 2 -After installation when rebooted it gives out call traces like as below: [3.895246] Unable to handle kernel paging request for data at address 0x [3.895278] Faulting instruction address: 0xd4c5df1c [3.895284] Oops: Kernel access of bad area, sig: 11 [#1] [3.895287] SMP NR_CPUS=2048 [3.895288] NUMA [3.895290] pSeries [3.895292] Modules linked in: ip_tables x_tables autofs4 jfs ibmvscsi crc32c_vpmsum [3.895301] CPU: 30 PID: 923 Comm: ureadahead Not tainted 4.9.0-15-generic #16-Ubuntu [3.895304] task: c00381d3c800 task.stack: c00381fd [3.895307] NIP: d4c5df1c LR: d4c5deb0 CTR: c01279d0 [3.895310] REGS: c00381fd3500 TRAP: 0300 Not tainted (4.9.0-15-generic) [3.895313] MSR: 8280b033 [ 3.895322] CR: 48008804 XER: 0001 [3.895324] CFAR: c0008a60 DAR: DSISR: 4000 SOFTE: 1 GPR00: d4c5deb0 c00381fd3780 d4c78c28 c003802f40f0 GPR04: d4c6f6f0 d4c72b58 0563 d4c78c28 GPR08: 00180e97 d4c6a608 GPR12: c01279d0 cfb90e00 GPR16: GPR20: GPR24: 1000 d4c72b38 GPR28: 00180e97 f0e1d5c0 c003812af240 c003802f40b0 NIP [d4c5df1c] __get_metapage+0x204/0x6f0 [jfs] [3.895372] LR [d4c5deb0] __get_metapage+0x198/0x6f0 [jfs] [3.895374] Call Trace: [3.895378] [c00381fd3780] [d4c5de6c] __get_metapage+0x154/0x6f0 [jfs] (unreliable) [3.895384] [c00381fd3870] [d4c4c368] diRead+0x130/0x260 [jfs] [3.895388] [c00381fd3920] [d4c424f4] jfs_iget+0x6c/0x1e0 [jfs] [3.895393] [c00381fd3950] [d4c43adc] jfs_lookup+0xe4/0x100 [jfs] [3.895398] [c00381fd3a80] [c032a120] lookup_slow+0xe0/0x240 [3.895402] [c00381fd3b00] [c032e8a8] walk_component+0x2d8/0x3f0 [3.895406] [c00381fd3b70] [c032eb94] link_path_walk+0x1d4/0x600 [3.895409] [c00381fd3c00] [c0330c1c] path_openat+0xbc/0x480 [3.895413] [c00381fd3c80] [c03328ac] do_filp_open+0xec/0x160 [3.895417] [c00381fd3db0] [c031863c] do_sys_open+0x1cc/0x380 [3.895421] [c00381fd3e30] [c000bd84] system_call+0x38/0xe0 [3.895424] Instruction dump: [3.895426] 7909f00e 7fc9f214 3921 f93f0028 fbdf0030 e93d 71280800 41820460 [3.895433] ebdd0030 41920034 e91d0008 e93f0038 811e 80e70090 39080001 [3.895441] ---[ end trace c2aa9ba09ea05eac ]--- [3.895443] [4.088560] systemd-journald[925]: Received request to flush runtime journal from PID 1 [4.362062] crypto_register_alg 'aes' = 0 [4.362112] crypto_register_alg 'cbc(aes)' = 0 [4.362150] crypto_register_alg 'ctr(aes)' = 0 [4.362191] crypto_register_alg 'xts(aes)' = 0 [4.366949] pseries_rng: Registering IBM pSeries RNG driver When I first connected to the LPAR, it was unresponsive so I restarted it from the HMC and surprisingly it came up to the login prompt and I logged into the shell. I proceeded to install the matching linux- image-4.10.0-15-generic-dbgsym_4.10.0-15.17_ppc64el.ddeb. However, the installation of the matching dbgsym wasn't as helpful as I wanted it to be. objdump, crash tool, or addr2line wouldn't give me the source line correspond to the NIP address. I then restarted the LPAR with xmon enabled and it would drop to xmon immediately after attempting to remount / and at the same location as before at __get_metapage+0x204/0x6f0 [jfs] and again with a dereference of 0x0 as the cause of the data exception 0xd649df54 <__get_metapage+508>:ld r8,8(r29) 0xd649df58 <__get_metapage+512>:ld r9
[Kernel-packages] [Bug 1718276] [NEW] package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Trying to install ubuntu from bootable usb with ubuntu on it, and new HDD in my laptop. I already tried installing ubuntu on it this same way but while it was connected by SATA cable to my PC, as external HDD. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4 AptOrdering: dkms:amd64: Install bcmwl-kernel-source:amd64: Install iucode-tool:amd64: Install intel-microcode:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Sep 19 19:30:05 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1718276 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bcmwl package in Ubuntu: New Bug description: Trying to install ubuntu from bootable usb with ubuntu on it, and new HDD in my laptop. I already tried installing ubuntu on it this same way but while it was connected by SATA cable to my PC, as external HDD. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4 AptOrdering: dkms:amd64: Install bcmwl-kernel-source:amd64: Install iucode-tool:amd64: Install intel-microcode:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Sep 19 19:30:05 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1718276/+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 1696049] Re: xfstest sanity checks on seek operations fails
A ppc kernel is now available at: http://kernel.ubuntu.com/~jsalisbury/lp1696049/ -- 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/1696049 Title: xfstest sanity checks on seek operations fails Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: In Progress Status in linux source package in Artful: Fix Released Bug description: == Comment: #0 - Harish Sriram Issue: -- xfstest fails with sanity checks on seek operations # uname -a Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Create a loop device with xfs filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.config for running with created loop device 5. Run xfstests-dev test : ./check tests/generic/285 or ./check tests/generic/436 The test 285 fails with following ... ... 07. Test file with unwritten extents, only have dirty pages 07.01 SEEK_HOLE expected 0 or 45056, got 0. succ 07.02 SEEK_HOLE expected 1 or 45056, got 1. succ 07.03 SEEK_DATA expected 40960 or 40960, got -1. FAIL 07.04 SEEK_DATA expected 40960 or 40960, got -1. FAIL 08. Test file with unwritten extents, only have unwritten pages 08.01 SEEK_HOLE expected 0 or 45056, got 0. succ 08.02 SEEK_HOLE expected 1 or 45056, got 1. succ 08.03 SEEK_DATA expected 40960 or 40960, got -1. FAIL 08.04 SEEK_DATA expected 40960 or 40960, got -1. FAIL The test 436 fails with ... ... 14. Test file with unwritten extents, small hole after pagevec dirty pages 14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016. FAIL 14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016. FAIL 14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ 14.04 SEEK_DATA expected 0 or 0, got 0. succ 14.05 SEEK_DATA expected 1 or 1, got 1. succ 14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ seek sanity check failed! Full log is attached. == Comment: #6 - Harish Sriram commit 5375023ae1266553a7baa0845e82917d8803f48c Author: Jan Kara Date: Thu May 18 16:36:22 2017 -0700 xfs: Fix missed holes in SEEK_HOLE implementation XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as can be seen by the following command: xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k" -c "seek -h 0" file wrote 57344/57344 bytes at offset 0 56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec) wrote 8192/8192 bytes at offset 131072 8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec) Whence Result HOLE139264 Where we can see that hole at offset 56k was just ignored by SEEK_HOLE implementation. The bug is in xfs_find_get_desired_pgoff() which does not properly detect the case when pages are not contiguous. Fix the problem by properly detecting when found page has larger offset than expected. CC: sta...@vger.kernel.org Fixes: d126d43f631f996daeee5006714fed914be32368 Signed-off-by: Jan Kara Reviewed-by: Brian Foster Reviewed-by: Darrick J. Wong Signed-off-by: Darrick J. Wong The above commit fixes the generic/436 test, but generic/285 still FAILS. The generic/285 failure is reproducible on most P8/P9 systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696049/+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 1718276] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1718276 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bcmwl package in Ubuntu: New Bug description: Trying to install ubuntu from bootable usb with ubuntu on it, and new HDD in my laptop. I already tried installing ubuntu on it this same way but while it was connected by SATA cable to my PC, as external HDD. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4 AptOrdering: dkms:amd64: Install bcmwl-kernel-source:amd64: Install iucode-tool:amd64: Install intel-microcode:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Sep 19 19:30:05 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1718276/+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 1718284] [NEW] package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: recurring failure to install. likely to be local issue ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 3521 F pulseaudio /dev/snd/controlC0: alex 3521 F pulseaudio Date: Mon Sep 18 17:29:36 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=53248f42-e64e-45c2-a19c-ea82c55b9eb5 InstallationDate: Installed on 2016-11-16 (307 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed root=UUID=520bf0a3-9021-4268-b355-10efda7b0177 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2163 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.24 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/26/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08961030410620100:rvnHewlett-Packard:rn2163:rvr29.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 08961030410620100 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package zesty -- 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/1718284 Title: package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: recurring failure to install. likely to be local issue ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 3521 F pulseaudio /dev/snd/controlC0: alex 3521 F pulseaudio Date: Mon Sep 18 17:29:36 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=53248f42-e64e-45c2-a19c-ea82c55b9eb5 InstallationDate: Installed on 2016-11-16 (307 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed root=UUID=520bf0a3-9021-4268-b355-10efda7b0177 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2163 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.24 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/26/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08961030410620100:rvnHewlett-Packard:rn2163:rvr29.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 08961030410620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718284/+subscriptions -- Mailing list: ht
[Kernel-packages] [Bug 1718284] Re: package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- 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/1718284 Title: package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: recurring failure to install. likely to be local issue ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 3521 F pulseaudio /dev/snd/controlC0: alex 3521 F pulseaudio Date: Mon Sep 18 17:29:36 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=53248f42-e64e-45c2-a19c-ea82c55b9eb5 InstallationDate: Installed on 2016-11-16 (307 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed root=UUID=520bf0a3-9021-4268-b355-10efda7b0177 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2163 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.24 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/26/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08961030410620100:rvnHewlett-Packard:rn2163:rvr29.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 08961030410620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718284/+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 1718284] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1718284 Title: package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: recurring failure to install. likely to be local issue ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 3521 F pulseaudio /dev/snd/controlC0: alex 3521 F pulseaudio Date: Mon Sep 18 17:29:36 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=53248f42-e64e-45c2-a19c-ea82c55b9eb5 InstallationDate: Installed on 2016-11-16 (307 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed root=UUID=520bf0a3-9021-4268-b355-10efda7b0177 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2163 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.24 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/26/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08961030410620100:rvnHewlett-Packard:rn2163:rvr29.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 08961030410620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718284/+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 1718292] [NEW] POWER9: NX842 module changes
You have been subscribed to a public bug: This feature request will be used to submit NX842 changes needed to support on p9 - Using VAS interfaces instead of icswx to communicate with VAS (on PowerNV), modification of HCALL interface (on PowerVM, if needed) and other format changes. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64 bugnameltc-139352 severity-high targetmilestone-inin1710 -- POWER9: NX842 module changes https://bugs.launchpad.net/bugs/1718292 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1718293] [NEW] [Ubuntu 17.10] POWER9 - Base - Integrate P9 VAS (Virtual Accelerator Switchboard) support in kernel
You have been subscribed to a public bug: This feature request is used to submit kernel changes needed for adding VAS (Virtual Accelerator Switchboard) support. VAS interface allows kernel or user space to communicate with any accelerator (Ex: NX). kernel changes will be to open a window/ channel with accelerator and communicate with copy / paste facility. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-140093 severity-high targetmilestone-inin1710 -- [Ubuntu 17.10] POWER9 - Base - Integrate P9 VAS (Virtual Accelerator Switchboard) support in kernel https://bugs.launchpad.net/bugs/1718293 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1718293] [NEW] [Ubuntu 17.10] POWER9 - Base - Integrate P9 VAS (Virtual Accelerator Switchboard) support in kernel
Public bug reported: This feature request is used to submit kernel changes needed for adding VAS (Virtual Accelerator Switchboard) support. VAS interface allows kernel or user space to communicate with any accelerator (Ex: NX). kernel changes will be to open a window/ channel with accelerator and communicate with copy / paste facility. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-140093 severity-high targetmilestone-inin1710 ** Tags added: architecture-ppc64le bugnameltc-140093 severity-high targetmilestone-inin1710 ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** 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/1718293 Title: [Ubuntu 17.10] POWER9 - Base - Integrate P9 VAS (Virtual Accelerator Switchboard) support in kernel Status in linux package in Ubuntu: New Bug description: This feature request is used to submit kernel changes needed for adding VAS (Virtual Accelerator Switchboard) support. VAS interface allows kernel or user space to communicate with any accelerator (Ex: NX). kernel changes will be to open a window/ channel with accelerator and communicate with copy / paste facility. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718293/+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 1718292] [NEW] POWER9: NX842 module changes
Public bug reported: This feature request will be used to submit NX842 changes needed to support on p9 - Using VAS interfaces instead of icswx to communicate with VAS (on PowerNV), modification of HCALL interface (on PowerVM, if needed) and other format changes. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64 bugnameltc-139352 severity-high targetmilestone-inin1710 ** Tags added: architecture-ppc64 bugnameltc-139352 severity-high targetmilestone-inin1710 ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** 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/1718292 Title: POWER9: NX842 module changes Status in linux package in Ubuntu: New Bug description: This feature request will be used to submit NX842 changes needed to support on p9 - Using VAS interfaces instead of icswx to communicate with VAS (on PowerNV), modification of HCALL interface (on PowerVM, if needed) and other format changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718292/+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 1709784] Comment bridged from LTC Bugzilla
--- Comment From furma...@us.ibm.com 2017-09-19 16:53 EDT--- I've tested the new kernel 4.4.0-96 and it fixes this issue. Thank you! -- 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/1709784 Title: KVM on 16.04.3 throws an error Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in qemu package in Ubuntu: Won't Fix Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: Invalid Bug description: Problem Description KVM on Ubuntu 16.04.3 throws an error when used ---uname output--- Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8348-21C Habanero ---Steps to Reproduce--- Install 16.04.3 install KVM like: apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils then exit and log back in so virsh will work without sudo then run my spawn script $ cat spawn.sh #!/bin/bash img=$1 qemu-system-ppc64 \ -machine pseries,accel=kvm,usb=off -cpu host -m 512 \ -display none -nographic \ -net nic -net user \ -drive "file=$img" with a freshly downloaded ubuntu cloud image sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img And I get nothing on the output. and errors in dmesg ubuntu@bastion-1:~$ [ 340.180295] Facility 'TM' unavailable, exception at 0xd000148b7f10, MSR=90009033 [ 340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1] [ 340.180513] SMP NR_CPUS=2048 NUMA PowerNV [ 340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c [ 340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 4.4.0-89-generic #112-Ubuntu [ 340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: c01e34ce4000 [ 340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: d000148b7e40 [ 340.181475] REGS: c01e34ce77b0 TRAP: 0f60 Not tainted (4.4.0-89-generic) [ 340.181519] MSR: 90009033 CR: 22024848 XER: [ 340.181629] CFAR: d000148b7ea4 SOFTE: 1 GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc GPR04: c01db9ac c01e34ce7bc0 GPR08: 0001 c01e34c30b50 0001 d000148278f8 GPR12: d000148b7e40 cfb5b500 001f GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 GPR24: 3fffc91fe990 3fff91c10028 c01e37bc GPR28: c01db9ac c01e37bc c01db9ac [ 340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv] [ 340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182394] Call Trace: [ 340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 (unreliable) [ 340.182468] [c01e34ce7b70] [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182522] [c01e34ce7ba0] [d0001481f674] kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm] [ 340.182581] [c01e34ce7be0] [d00014813918] kvm_vcpu_ioctl+0x528/0x7b0 [kvm] [ 340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0 [ 340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0 [ 340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb4 [ 340.182766] Instruction dump: [ 340.182788] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 e9290108 [ 340.182863] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 e92d02a0 7d4122a6 [ 340.182938] ---[ end trace bc5080cb7d18f102 ]--- [ 340.276202] This was with the latest ubuntu cloud image. I get the same thing when trying to use virt-install with an ISO i
[Kernel-packages] [Bug 1693369] Re: 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2 5u84
Sorry for the delay. I'll submit an SRU request for this bug. -- 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/1693369 Title: 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2 5u84 Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: In Progress Bug description: This is a request to add the following upstream commit to both Ubuntu 16.04.1 and 16.04.2: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=9373eba6cfae48911b977d14323032cd5d161aae Without this patch, the symlink in sysfs which binds a SAS device to an enclosure slot does not get created. This makes disk hotplug near impossible on large JBOD disk drawers. You should be able to do: ls /sys/block/sdb/device/ | grep enclosure and see something like: enclosure_device:1 If you cd to this directory, you can then access the SES controls for that slot to flash the LED to assist in locating the disk to replace a failed disk. Currently with 16.04.1 and 16.04.2, these symlinks are not getting created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1693369/+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 1707695] Re: radeon 0000:03:00.0: ring 0 stalled for more than 10000msec
Please file a bug report at https://bugs.freedesktop.org/ -- 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/1707695 Title: radeon :03:00.0: ring 0 stalled for more than 1msec Status in linux package in Ubuntu: Confirmed Bug description: My system intermittently locks up every few days. It does not seem to correspond to a particular program or action. When that happens, the screen goes to black, then returns after a few seconds. At that point, the time on the clock is static and indicates that the screen is frozen, but audio continues to play for 30 seconds to a minute. The keyboard and mouse do not affect what's being displayed, but I can Alt - SysRq - REISUB to restart. Every time (7 crashes and counting), /var/log/kern.log indicates that kernel: [353692.378886] radeon :03:00.0: ring 0 stalled for more than 10280msec kernel: [353692.378896] radeon :03:00.0: GPU lockup (current fence id 0x006e96e5 last fence id 0x006e96e9 on ring 0) just before the system locks. Different ring numbers are reported as stalling at different times. As per the instructions, I posted a question about this issue at: https://askubuntu.com/questions/937792/system-lockup-radeon-ring- stalled-for-more-than-10280msec?noredirect=1#comment1486875_937792 but I have not received many responses. I'm running 16.04 LTS. :~$ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 According to the Software Center, I am running Ubuntu Software 3.20.1. I have a Radeon HD graphics card. :~$ lspci | grep VGA 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] :~$ lspci -v -s 03:00.0 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Cedar [Radeon HD 5000/6000/7350/8350 Series] Flags: bus master, fast devsel, latency 0, IRQ 53 Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d3d2 (64-bit, non-prefetchable) [size=128K] I/O ports at 7000 [size=256] Expansion ROM at d3d0 [disabled] [size=128K] Capabilities: Kernel driver in use: radeon Kernel modules: radeon Please let me know if additional information would be useful, and I will be glad to provide it. Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-87-generic 4.4.0-87.110 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: clapp 3889 F pulseaudio /dev/snd/controlC2: clapp 3889 F pulseaudio /dev/snd/controlC1: clapp 3889 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 31 14:02:27 2017 HibernationDevice: RESUME=UUID=1b30dad6-8c48-42cf-ae26-66ab8b0eb446 InstallationDate: Installed on 2013-09-04 (1425 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Dell Inc. Precision T7600 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic root=UUID=33722f76-37fd-4289-b071-d7f48b65dd32 ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-87-generic N/A linux-backports-modules-4.4.0-87-generic N/A linux-firmware1.157.11 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 082WXT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/03/2013:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T7600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707695/+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 1709784] Re: KVM on 16.04.3 throws an error
@furmanek, Thanks for testing. @Breno, Commit e47057151 was not applied to Xenial. It did not apply cleanly because the following commit is already in Xenial as of 4.4.0-96(As Xenial SHA1 25e0720): 17d381054b1d6f4adc3db623b2066fff41b4dc1a ("KVM: PPC: Book3S HV: Reload HTM registers explicitly") Commit 17d381054 came in from the 4.4.80 updates and does what commit e47057151 does and more. Per comment #18, it sounds like it fixes this bug. It would be great if others affected by this bug could also test -proposed. -- 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/1709784 Title: KVM on 16.04.3 throws an error Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in qemu package in Ubuntu: Won't Fix Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: Invalid Bug description: Problem Description KVM on Ubuntu 16.04.3 throws an error when used ---uname output--- Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8348-21C Habanero ---Steps to Reproduce--- Install 16.04.3 install KVM like: apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils then exit and log back in so virsh will work without sudo then run my spawn script $ cat spawn.sh #!/bin/bash img=$1 qemu-system-ppc64 \ -machine pseries,accel=kvm,usb=off -cpu host -m 512 \ -display none -nographic \ -net nic -net user \ -drive "file=$img" with a freshly downloaded ubuntu cloud image sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img And I get nothing on the output. and errors in dmesg ubuntu@bastion-1:~$ [ 340.180295] Facility 'TM' unavailable, exception at 0xd000148b7f10, MSR=90009033 [ 340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1] [ 340.180513] SMP NR_CPUS=2048 NUMA PowerNV [ 340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c [ 340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 4.4.0-89-generic #112-Ubuntu [ 340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: c01e34ce4000 [ 340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: d000148b7e40 [ 340.181475] REGS: c01e34ce77b0 TRAP: 0f60 Not tainted (4.4.0-89-generic) [ 340.181519] MSR: 90009033 CR: 22024848 XER: [ 340.181629] CFAR: d000148b7ea4 SOFTE: 1 GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc GPR04: c01db9ac c01e34ce7bc0 GPR08: 0001 c01e34c30b50 0001 d000148278f8 GPR12: d000148b7e40 cfb5b500 001f GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 GPR24: 3fffc91fe990 3fff91c10028 c01e37bc GPR28: c01db9ac c01e37bc c01db9ac [ 340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv] [ 340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182394] Call Trace: [ 340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 (unreliable) [ 340.182468] [c01e34ce7b70] [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182522] [c01e34ce7ba0] [d0001481f674] kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm] [ 340.182581] [c01e34ce7be0] [d00014813918] kvm_vcpu_ioctl+0x528/0x7b0 [kvm] [ 340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0 [ 340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0 [ 340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb4 [ 340.182766] Instruc
[Kernel-packages] [Bug 1718159] Re: linux: 3.13.0-133.182 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718161 derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 19. September 2017 16:02 UTC -- swm properties -- + boot-testing-requested: true phase: Uploaded -- 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/1718159 Title: linux: 3.13.0-133.182 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718161 derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 19. September 2017 16:02 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718159/+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 1713575] Comment bridged from LTC Bugzilla
--- Comment From ukri...@us.ibm.com 2017-09-19 19:08 EDT--- I was able to test the issue that this patch resolves. The kernel in the given link solves the issue. Linux tul83p1 4.10.0-33-generic #37~lp1713575 SMP Wed Sep 6 15:45:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Thanks !! Sorry for the delay in giving the feedback. -- 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/1713575 Title: Vlun resize request could fail with cxlflash driver Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: == Comment: #0 - UMA KRISHNAN - 2017-08-28 12:14:12 == ---Problem Description--- Recently a regression in cxlflash driver was identified and a fix has been upstreamed to kernel.org. We would like to get that included in Xenial 16.04.3 SRU (HWE v4.10 kernel). Even though regression patch is the very last one, I have also listed the missing patches in-between, that are minor and will be easier for further cxlflash updates to Xenial. eeac8cda2c957e156093933b860eec09e488fe15 scsi: cxlflash: return -EFAULT if copy_from_user() fails 9ff870417e56b1fb7b15b2cda74de639d3cd8559 scsi: cxlflash: Fix an error handling path in 'cxlflash_disk_attach()' 48a17ad5931c3832eec68411620bc3527021c193 scsi: cxlflash: Remove unnecessary existence check 1a9e394154e34728f58c1f697b993aaaf89a4db2 scsi: cxlflash: Avoid double mutex unlock 07a191f762a7b8d0db13c38036380927116e29bb scsi: cxlflash: Fix vlun resize failure in the shrink path ---Steps to Reproduce--- Vlun resize request could fail after updating to a kernel that includes Commit 565180723294 ("scsi: cxlflash: SISlite updates to support 4 ports") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1713575/+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 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps
SCMP_ACT_LOG test for libseccomp. ** Description changed: A requirement for snappy is that a snap may be placed in developer mode which will put the security sandbox in complain mode such that violations against policy are logged, but permitted. In this manner learning tools can be written to parse the logs, etc and make developing on snappy easier. Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we can set complain mode to permit all calls, they are not logged at this time. I've discussed this with upstream and we are working together on the approach. This may require a kernel patch and an update to libseccomp, to filing this bug for now as a placeholder and we'll add other tasks as necessary. UPDATE: ubuntu-core-launcher now supports the '@complain' directive that is a synonym for '@unrestricted' so people can at least turn on developer mode and not be blocked by seccomp. Proper complain mode for seccomp needs to still be implemented (this bug). + + [Impact] + + Snapd needs a way to log seccomp actions without blocking any syscalls + in order to have a more useful complain mode. Such functionality has + been acked upstream and patches are on their way into the Linux 4.14 + kernel (backported to 4.12.0-13.14 in artful). + + The corresponding libseccomp changes are still undergoing review + (https://github.com/seccomp/libseccomp/pull/92). The pull request adds a + number of new symbols and probably isn't appropriate to backport until + upstream has acked the pull request. However, only a small part of that + larger pull request is needed by snapd and that change can be safely + backported since the only added symbol, the SCMP_ACT_LOG macro, must + match the SECCOMP_RET_LOG macro that has already been approved and + merged in the upstream Linux kernel. + + [Test Case] + + A large number of tests are ran as part of the libseccomp build. + However, the "live" tests which test libseccomp with actual kernel + enforcement are not ran at that time. They can be manually exercised to + help catch any regressions. Note that on Artful, there's an existing + test failure (20-live-basic_die%%002-1): + + $ sudo apt build-dep -y libseccomp + $ sudo apt install -y cython + $ apt source libseccomp + $ autoreconf -ivf && ./configure --enable-python && make check-build + $ (cd tests && ./regression -T live) + ... + Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP rc=159 + ... + Regression Test Summary + tests run: 12 + tests skipped: 0 + tests passed: 11 + tests failed: 1 + tests errored: 0 + + + Now we can build and run a small test program to test the SCMP_ACT_LOG + action in the way that snapd wants to use it for developer mode: + + $ sudo apt install -y libseccomp-dev + $ gcc -o lp1567597-test lp1567597-test.c -lseccomp + $ ./lp1567597-test + + You should have an entry in the system log that looks like this: + + audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000 + ses=2 pid=18451 comm="lp1567597-test" exe="/home/tyhicks/lp1567597-test" + sig=0 arch=c03e syscall=2 compat=0 ip=0x7f547352c5c0 code=0x7ffc + + [Regression Potential] + + Relatively small since the core logic is in the kernel and we're only + exposing the new action through libseccomp. The changes include smarts + to query the kernel to see if the action is available in the kernel. + Calling applications will not be able to use the action on older kernels + that don't support it. ** Summary changed: - implement 'complain mode' in seccomp for developer mode with snaps + [FFe] implement 'complain mode' in seccomp for developer mode with snaps ** Attachment added: "lp1567597-test.c" https://bugs.launchpad.net/snappy/+bug/1567597/+attachment/4953120/+files/lp1567597-test.c ** Description changed: A requirement for snappy is that a snap may be placed in developer mode which will put the security sandbox in complain mode such that violations against policy are logged, but permitted. In this manner learning tools can be written to parse the logs, etc and make developing on snappy easier. Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we can set complain mode to permit all calls, they are not logged at this time. I've discussed this with upstream and we are working together on the approach. This may require a kernel patch and an update to libseccomp, to filing this bug for now as a placeholder and we'll add other tasks as necessary. UPDATE: ubuntu-core-launcher now supports the '@complain' directive that is a synonym for '@unrestricted' so people can at least turn on developer mode and not be blocked by seccomp. Proper complain mode for seccomp needs to still be implemented (this bug). [Impact] Snapd needs a way to log seccomp actions without blocking any syscalls in order to have a more useful c
[Kernel-packages] [Bug 1567597] Re: [FFe] implement 'complain mode' in seccomp for developer mode with snaps
Clean Artful amd64 build log. ** Attachment added: "libseccomp_2.3.1-2.1ubuntu2_amd64.build" https://bugs.launchpad.net/snappy/+bug/1567597/+attachment/4953122/+files/libseccomp_2.3.1-2.1ubuntu2_amd64.build ** Changed in: libseccomp (Ubuntu) Status: Confirmed => In Progress ** Changed in: snappy Status: In Progress => Confirmed -- 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/1567597 Title: [FFe] implement 'complain mode' in seccomp for developer mode with snaps Status in Snappy: Confirmed Status in libseccomp package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Bug description: A requirement for snappy is that a snap may be placed in developer mode which will put the security sandbox in complain mode such that violations against policy are logged, but permitted. In this manner learning tools can be written to parse the logs, etc and make developing on snappy easier. Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we can set complain mode to permit all calls, they are not logged at this time. I've discussed this with upstream and we are working together on the approach. This may require a kernel patch and an update to libseccomp, to filing this bug for now as a placeholder and we'll add other tasks as necessary. UPDATE: ubuntu-core-launcher now supports the '@complain' directive that is a synonym for '@unrestricted' so people can at least turn on developer mode and not be blocked by seccomp. Proper complain mode for seccomp needs to still be implemented (this bug). [Impact] Snapd needs a way to log seccomp actions without blocking any syscalls in order to have a more useful complain mode. Such functionality has been acked upstream and patches are on their way into the Linux 4.14 kernel (backported to 4.12.0-13.14 in artful). The corresponding libseccomp changes are still undergoing review (https://github.com/seccomp/libseccomp/pull/92). The pull request adds a number of new symbols and probably isn't appropriate to backport until upstream has acked the pull request. However, only a small part of that larger pull request is needed by snapd and that change can be safely backported since the only added symbol, the SCMP_ACT_LOG macro, must match the SECCOMP_RET_LOG macro that has already been approved and merged in the upstream Linux kernel. [Test Case] A large number of tests are ran as part of the libseccomp build. However, the "live" tests which test libseccomp with actual kernel enforcement are not ran at that time. They can be manually exercised to help catch any regressions. Note that on Artful, there's an existing test failure (20-live-basic_die%%002-1): $ sudo apt build-dep -y libseccomp $ sudo apt install -y cython $ apt source libseccomp $ autoreconf -ivf && ./configure --enable-python && make check-build $ (cd tests && ./regression -T live) ... Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP rc=159 ... Regression Test Summary tests run: 12 tests skipped: 0 tests passed: 11 tests failed: 1 tests errored: 0 Now we can build and run a small test program to test the SCMP_ACT_LOG action in the way that snapd wants to use it for developer mode: $ sudo apt install -y libseccomp-dev $ gcc -o lp1567597-test lp1567597-test.c -lseccomp $ ./lp1567597-test The exit code should be 0 and you should have an entry in the system log that looks like this: audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000 ses=2 pid=18451 comm="lp1567597-test" exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2 compat=0 ip=0x7f547352c5c0 code=0x7ffc [Regression Potential] Relatively small since the core logic is in the kernel and we're only exposing the new action through libseccomp. The changes include smarts to query the kernel to see if the action is available in the kernel. Calling applications will not be able to use the action on older kernels that don't support it. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1567597/+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 1567597] Re: [FFe] implement 'complain mode' in seccomp for developer mode with snaps
Debdiff to consider for Artful FFe. (I don't need sponsorship) ** Patch added: "libseccomp_2.3.1-2.1ubuntu2.debdiff" https://bugs.launchpad.net/snappy/+bug/1567597/+attachment/4953121/+files/libseccomp_2.3.1-2.1ubuntu2.debdiff -- 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/1567597 Title: [FFe] implement 'complain mode' in seccomp for developer mode with snaps Status in Snappy: Confirmed Status in libseccomp package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Bug description: A requirement for snappy is that a snap may be placed in developer mode which will put the security sandbox in complain mode such that violations against policy are logged, but permitted. In this manner learning tools can be written to parse the logs, etc and make developing on snappy easier. Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we can set complain mode to permit all calls, they are not logged at this time. I've discussed this with upstream and we are working together on the approach. This may require a kernel patch and an update to libseccomp, to filing this bug for now as a placeholder and we'll add other tasks as necessary. UPDATE: ubuntu-core-launcher now supports the '@complain' directive that is a synonym for '@unrestricted' so people can at least turn on developer mode and not be blocked by seccomp. Proper complain mode for seccomp needs to still be implemented (this bug). [Impact] Snapd needs a way to log seccomp actions without blocking any syscalls in order to have a more useful complain mode. Such functionality has been acked upstream and patches are on their way into the Linux 4.14 kernel (backported to 4.12.0-13.14 in artful). The corresponding libseccomp changes are still undergoing review (https://github.com/seccomp/libseccomp/pull/92). The pull request adds a number of new symbols and probably isn't appropriate to backport until upstream has acked the pull request. However, only a small part of that larger pull request is needed by snapd and that change can be safely backported since the only added symbol, the SCMP_ACT_LOG macro, must match the SECCOMP_RET_LOG macro that has already been approved and merged in the upstream Linux kernel. [Test Case] A large number of tests are ran as part of the libseccomp build. However, the "live" tests which test libseccomp with actual kernel enforcement are not ran at that time. They can be manually exercised to help catch any regressions. Note that on Artful, there's an existing test failure (20-live-basic_die%%002-1): $ sudo apt build-dep -y libseccomp $ sudo apt install -y cython $ apt source libseccomp $ autoreconf -ivf && ./configure --enable-python && make check-build $ (cd tests && ./regression -T live) ... Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP rc=159 ... Regression Test Summary tests run: 12 tests skipped: 0 tests passed: 11 tests failed: 1 tests errored: 0 Now we can build and run a small test program to test the SCMP_ACT_LOG action in the way that snapd wants to use it for developer mode: $ sudo apt install -y libseccomp-dev $ gcc -o lp1567597-test lp1567597-test.c -lseccomp $ ./lp1567597-test The exit code should be 0 and you should have an entry in the system log that looks like this: audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000 ses=2 pid=18451 comm="lp1567597-test" exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2 compat=0 ip=0x7f547352c5c0 code=0x7ffc [Regression Potential] Relatively small since the core logic is in the kernel and we're only exposing the new action through libseccomp. The changes include smarts to query the kernel to see if the action is available in the kernel. Calling applications will not be able to use the action on older kernels that don't support it. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1567597/+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 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure
This bug was fixed in the package linux-azure - 4.11.0-1011.11 --- linux-azure (4.11.0-1011.11) xenial; urgency=low * linux-azure: 4.11.0-1011.11 -proposed tracker (LP: #1718265) * KVP scripts location for linux-azure image (LP: #1718264) - SAUCE: azure: hv_kvp_daemon: search for HV scripts in /usr/sbin/ * [linux-azure] RTC options not present in kernel config (LP: #1718262) - [Config] azure: Enable RTC linux-azure (4.11.0-1010.10) xenial; urgency=low * linux-azure: 4.11.0-1010.10 -proposed tracker (LP: #1717616) * linux-azure: persistent memory is not working (LP: #1715755) - ext4: fix fault handling when mounted with -o dax,ro - [Config] azure: CONFIG_ND_BLK=y - [Config] azure: CONFIG_ACPI_NFIT=y * [Hyper-V] 16.04 kexec-tools doesn't match linux-azure (LP: #1712867) - x86/KASLR: Fix kexec kernel boot crash when KASLR randomization fails -- Marcelo Henrique Cerri Tue, 19 Sep 2017 15:47:22 -0300 ** Changed in: linux-azure (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1712867 Title: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure Status in crash package in Ubuntu: Fix Committed Status in kexec-tools package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Committed Status in crash source package in Xenial: Fix Released Status in kexec-tools source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Bug description: [Impact] Currently it's not possible to use the kdump functionality in xenial when running the linux-azure kernel. The problem is actually caused by several factors: 1. kexec fails to parse /proc/kcore and thus fails to load the crash kernel. That's similar to bug #1713940 and it's related to 4.10+ kernels. 2. When the crash kernel boots, a bug in KASLR causes it to crash in a very early stage. For the user, it seems the system just rebooted after the crash. 3. Currently in azure, crashkernel=128G is not enough to boot and run the dump procedure with 4.11+ kernels. That value needs to be increased in order to kdump to succeed. 4. After the vmcore is dumped, the current version of crash in xenial is not able to parse it. All the necessary fixes are already upstream and can be backported. [Test Case] 1. Install the linux-azure kernel in an azure instance (although it's possible to run linux-azure in bare metal or kvm, the KASLR issue only is triggered in azure). 2. Follow the instructions in https://help.ubuntu.com/lts/serverguide /kernel-crash-dump.html to setup kdump and manually trigger a crash using /proc/sysrq-trigger. The vmcore must be generated and it should be possible to inspect it using crash. 3. Perform these same tests for the linux-generic kernel, on each supported architecture. [Regression Potential] Since both kexec-tools and crash are being changed to support 4.10+ kernels, it's very important that they continue to handle 4.4 kernels properly. The same steps above can be used to test linux-generic for regressions. [Other Info] Original description: --8<-- Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the following error: kdump-tools[1436]: ELF core (kcore) parse failed Perhaps the artful kexec-tools should be backported? --8<-- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1712867/+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 1709282] Re: Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81
https://lkml.org/lkml/2017/9/19/824 -- 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/1709282 Title: Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81 Status in linux package in Ubuntu: Confirmed Bug description: Very similar to this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763 == the Problem == Listening to sound on a vmware machine, hosted by Ubuntu, the devices freezes, and cannot listen to sound anymore, i have to connect/disconnect the device. After i disconnect i get the logs: Aug 8 13:52:05 tim-lap-143 kernel: [112278.344893] usb 1-1: 1:1: cannot get freq at ep 0x81 Aug 8 13:52:05 tim-lap-143 kernel: [112278.347094] usb 1-1: 2:1: cannot get freq at ep 0x1 Aug 8 13:52:05 tim-lap-143 kernel: [112278.358786] usb 1-1: Warning! Unlikely big volume range (=8192), cval->res is probably wrong. Aug 8 13:52:05 tim-lap-143 kernel: [112278.358787] usb 1-1: [11] FU [Sidetone Playback Volume] ch = 1, val = 0/8192/1 Aug 8 13:52:05 tim-lap-143 kernel: [112278.641980] input: Plantronics Plantronics C520-M as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.3/0003:047F:C036.000F/input/input32 Aug 8 13:52:05 tim-lap-143 kernel: [112278.702298] plantronics 0003:047F:C036.000F: input,hiddev0,hidraw2: USB HID v1.11 Device [Plantronics Plantronics C520-M] on usb-:00:14.0-1/input3 Aug 8 13:52:05 tim-lap-143 kernel: [112278.747708] usb 1-1: 2:1: cannot get freq at ep 0x1 Aug 8 13:52:16 tim-lap-143 kernel: [112289.406154] usb 1-1: reset full-speed USB device number 19 using xhci_hcd Aug 8 13:52:16 tim-lap-143 kernel: [112289.906146] usb 1-1: reset full-speed USB device number 19 using xhci_hcd = The solution == It is simple, add this USB ID to the sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function. version signature: Ubuntu 4.10.0-28.32-generic 4.10.17 Thanks! --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: mihai.cin...@3pillar.corp 2208 F...m pulseaudio /dev/snd/controlC0: mihai.cin...@3pillar.corp 2208 F pulseaudio DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=d363a75c-d8a4-467d-a576-a46b3c317861 InstallationDate: Installed on 2017-06-22 (47 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Precision 3510 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_guc_loading=1 i915.enable_guc_submission=1 intel_pstate=skylake_hwp i915.enable_psr=1 i915.disable_power_well=0 i915.enable_rc6=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-28-generic N/A linux-backports-modules-4.10.0-28-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-07-21 (18 days ago) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.4 dmi.board.name: 00D283 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.4:bd05/12/2017:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn00D283:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 3510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282/+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 1708499] Re: usb 3-1: 2:1: cannot get freq at ep 0x1
https://lkml.org/lkml/2017/9/19/824 -- 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/1708499 Title: usb 3-1: 2:1: cannot get freq at ep 0x1 Status in linux package in Ubuntu: Incomplete Bug description: Hello, dmesg: [ 74.344674] usb 3-1: 2:1: cannot get freq at ep 0x1 [ 138.403001] usb 3-1: 2:1: cannot get freq at ep 0x1 [ 247.864869] usb 3-1: 2:1: cannot get freq at ep 0x1 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: caravena 1452 F pulseaudio /dev/snd/controlC0: caravena 1452 F pulseaudio CurrentDesktop: GNOME Date: Thu Aug 3 13:18:46 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2017-07-05 (28 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-07-05 (28 days ago) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708499/+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 1705633] Re: [8087:0a2b] Failed to load bluetooth firmware(might affect some other Intel bt devices)
** Changed in: hwe-next Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) Status: Fix Committed => 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/1705633 Title: [8087:0a2b] Failed to load bluetooth firmware(might affect some other Intel bt devices) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: [Impact] After this linux-firmware bug[1] update the firmware files, it removes intel/ibt-11-16.{ddc,sfi} and add intel/ibt-12-16.{ddc,sfi}, but in btusb driver, it hardcoded the hw_variant as 11. So we got this kind of error after the linux-firmware package updated and lost the bt functions. [5.516003] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.516181] bluetooth hci0: Direct firmware load for intel/ibt-11-16.sfi failed with error -2 [5.516183] Bluetooth: hci0: Failed to load Intel firmware file (-2) [Fix] This patch uses a hw_variant variable to replace the hardcoded 11. [Test Case] Verified on the machine has this issue, and confirm this patch works. [Regression Potential] The hw_variant variable has shown up since kernel 3.10 in this commit dffd30e Bluetooth: Add support for Intel Bluetooth device [8087:07dc] So, we don't have to worry about old chips don't contains this info, since it exists and be used for a very long time. 1. https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1686815 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1705633/+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 1717942] Re: No rule to make target linux_osl.o kernel 4.12.13
Dis regard, builds fine with the latest patch for 4.12 kernels. ** Changed in: bcmwl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1717942 Title: No rule to make target linux_osl.o kernel 4.12.13 Status in bcmwl package in Ubuntu: Fix Released Bug description: Description:Ubuntu 16.04.3 LTS Release:16.04 Kernel 4.12.13-041213-generic #201709132217 SMP Thu Sep 14 02:19:19 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux error when trying to compile the updated bcmwl drivers (kernel 4.12 patch) /bcmwl-6.30.223.271+bdcom$ make KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd` make[1]: Entering directory '/usr/src/linux-headers-4.12.13-041213-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API LD /home/xbmc/zzz/drivers/bcmwl-6.30.223.271+bdcom/built-in.o make[2]: *** No rule to make target '/home/xbmc/zzz/drivers/bcmwl-6.30.223.271+bdcom/src/shared/linux_osl.o', needed by '/home/xbmc/zzz/drivers/bcmwl-6.30.223.271+bdcom/wl.o'. Stop. Makefile:1515: recipe for target '_module_/home/xbmc/zzz/drivers/bcmwl-6.30.223.271+bdcom' failed make[1]: *** [_module_/home/xbmc/zzz/drivers/bcmwl-6.30.223.271+bdcom] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-4.12.13-041213-generic' Makefile:140: recipe for target 'all' failed make: *** [all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1717942/+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 1718143] Re: linux: 4.10.0-36.40 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-zesty ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718145,1718146 derivatives: 1718147 kernel-stable-phase-changed:Tuesday, 19. September 2017 12:32 UTC kernel-stable-phase:Uploaded -- swm properties -- + boot-testing-requested: true phase: Uploaded -- 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/1718143 Title: linux: 4.10.0-36.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718145,1718146 derivatives: 1718147 kernel-stable-phase-changed:Tuesday, 19. September 2017 12:32 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718143/+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 1718149] Re: linux: 4.4.0-97.120 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718150,1718151 derivatives: 1718153,1718154,1718155,1718156,1718157 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 19. September 2017 18:01 UTC -- swm properties -- + boot-testing-requested: true phase: Uploaded -- 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/1718149 Title: linux: 4.4.0-97.120 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1718150,1718151 derivatives: 1718153,1718154,1718155,1718156,1718157 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 19. September 2017 18:01 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718149/+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 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
That's because disks need to be stopped before chipsets/CPU goes to suspend. So the internal messages are flushed *after* disk wakeup - disk is not available at the end the suspend process. -- 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/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state Status in linux package in Ubuntu: In Progress Bug description: Originally thought my issue was same as this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 but requested to report as separate bug System becomes unusable at seemingly random times but especially after resume from suspend due to disk 'disappearing' becoming inaccessible, with hundreds of I/O errors logged. After viewing the above bug report yesterday as a quick temporary fix I added kernel param, updated grub, etc with: GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0" System appears to have been stable for the last day, but is presumably using more power than it should. System, drive details below: M2 nvme drive: Samsung SSD 960 EVO 500GB Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 M/B Asus Prime B350m-A Ryzen 1600 cpu Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffdf800 flags=0x0a00] Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 callbacks suppressed Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to change power state, currently in D3 Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe failure status: -19 Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change from 500107862016 to 0 Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, dev nvme0n1, sector 0 nvme list /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB / 500.11 GB 512 B + 0 B 2B7QCXE7 sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S3EUNX0J305518L mn : Samsung SSD 960 EVO 500GB fr : 2B7QCXE7 rab : 2 ieee : 002538 cmic : 0 mdts : 9 cntlid : 2 ver : 10200 rtd3r : 7a120 rtd3e : 4c4b40 oaes : 0 oacs : 0x7 acl : 7 aerl : 3 frmw : 0x16 lpa : 0x3 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 350 cctemp : 352 mtfa : 0 hmpre : 0 hmmin : 0 tnvmcap : 500107862016 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0x5 vwc : 0x1 awun : 255 awupf : 0 nvscc : 1 acwu : 0 sgls : 0 ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: drgrumpy 2192 F pulseaudio /dev/snd/pcmC1D0p: drgrumpy 2192 F...m pulseaudio /dev/snd/controlC1: drgrumpy 2192 F pulseaudio DistroRelease: Linux 18.2 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec InstallationDate: Installed on 2017-07-06 (15 days ago) InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628 IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.default_ps_max_latency_us=0 ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.157.11 RfKill: Tags: sonya Uname: Linux 4.10.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) User
[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Raised the issue to Samsung: http://lists.infradead.org/pipermail/linux-nvme/2017-September/012892.html ** Changed in: linux (Ubuntu) Status: In Progress => Triaged -- 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/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state Status in linux package in Ubuntu: Triaged Bug description: Originally thought my issue was same as this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 but requested to report as separate bug System becomes unusable at seemingly random times but especially after resume from suspend due to disk 'disappearing' becoming inaccessible, with hundreds of I/O errors logged. After viewing the above bug report yesterday as a quick temporary fix I added kernel param, updated grub, etc with: GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0" System appears to have been stable for the last day, but is presumably using more power than it should. System, drive details below: M2 nvme drive: Samsung SSD 960 EVO 500GB Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 M/B Asus Prime B350m-A Ryzen 1600 cpu Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffdf800 flags=0x0a00] Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 callbacks suppressed Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to change power state, currently in D3 Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe failure status: -19 Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change from 500107862016 to 0 Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, dev nvme0n1, sector 0 nvme list /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB / 500.11 GB 512 B + 0 B 2B7QCXE7 sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S3EUNX0J305518L mn : Samsung SSD 960 EVO 500GB fr : 2B7QCXE7 rab : 2 ieee : 002538 cmic : 0 mdts : 9 cntlid : 2 ver : 10200 rtd3r : 7a120 rtd3e : 4c4b40 oaes : 0 oacs : 0x7 acl : 7 aerl : 3 frmw : 0x16 lpa : 0x3 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 350 cctemp : 352 mtfa : 0 hmpre : 0 hmmin : 0 tnvmcap : 500107862016 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0x5 vwc : 0x1 awun : 255 awupf : 0 nvscc : 1 acwu : 0 sgls : 0 ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: drgrumpy 2192 F pulseaudio /dev/snd/pcmC1D0p: drgrumpy 2192 F...m pulseaudio /dev/snd/controlC1: drgrumpy 2192 F pulseaudio DistroRelease: Linux 18.2 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec InstallationDate: Installed on 2017-07-06 (15 days ago) InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628 IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.default_ps_max_latency_us=0 ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.157.11 RfKill: Tags: sonya Uname: Linux 4.10.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkFo
[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation
The bug didn't happened on kernel 3.19.0-93. Test step: 1. PXE install Ubuntu 16.04.3. 2. Downgrade kernel to 3.19.0-93. 3. The screen goes normally after a reboot. -- 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/1646277 Title: Xenial server 16.04.x will have a black screen after PXE installation Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in debian-installer source package in Xenial: Confirmed Status in linux source package in Xenial: Confirmed Bug description: The display will keep black screen after install 16.04.x via PXE(need use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode screen) Quanta team is installing Xenial server using PXE boot. After the installation, the console will show a black screen. Hitting ctl- alt-f1 displays the text mode screen OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+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 1686268] Re: Backlight brightness level not restored after reboot
** Changed in: linux (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- 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/1686268 Title: Backlight brightness level not restored after reboot Status in linux package in Ubuntu: Confirmed Bug description: I am not sure if this is the right place to report this, so feel free to move it elsewhere. It looks like the systemd-backlight service (/lib/systemd/system /systemd-backlight@.service) does not restore the brightness level (although it saves it before shut-down). However the following command does restore the saved brightness: sudo /lib/systemd/systemd-backlight load backlight:intel_backlight As a temporary solution to automate it at boot I am using the following line added to the root cron: @reboot /lib/systemd/systemd-backlight load backlight:intel_backlight - Ubuntu 4.10.0-20.22-generic 4.10.8 - Gnome 3.24 Please, let me know if you need more info. Thanks. --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dd 1540 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-12 (13 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170411) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=/dev/mapper/nvme-ubuntu_gnome ro systemd.restore_state=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/29/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686268/+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 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
** Changed in: linux (Ubuntu) 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/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Committed Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477/+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 1482390] Re: ASUS UX305LA - Battery state not detected correctly
Will the battery state ever be charging? -- 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/1482390 Title: ASUS UX305LA - Battery state not detected correctly Status in linux package in Ubuntu: Triaged Bug description: Whether the AC adapter is connected or not, the battery is always detected as discharging: When AC adapter is present: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0% AC adapter : online $ sudo acpitool -B Battery #1 : present Remaining capacity : 54027 mWh, 100.0% Design capacity: 56041 mWh Last full capacity : 53507 mWh, 95.48% of design capacity Capacity loss : 4.522% Present rate : 0 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS When AC adapter is not present: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0%, 04:19:49 AC adapter : off-line $ sudo acpitool -B Battery #1 : present Remaining capacity : 54005 mWh, 100.0%, 04:28:31 Design capacity: 56041 mWh Last full capacity : 53507 mWh, 95.48% of design capacity Capacity loss : 4.522% Present rate : 12067 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS System information: $ sudo dmidecode # dmidecode 2.12 # SMBIOS entry point at 0xace2a898 SMBIOS 2.8 present. 27 structures occupying 2154 bytes. Table at 0xAC7C6000. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: UX305LA.202 Release Date: 04/16/2015 Address: 0xF Runtime Size: 64 kB ROM Size: 6464 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.6 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX305LA Version: 1.0 Serial Number: xxx UUID: xxx Wake-up Type: Power Switch SKU Number: ASUS-NotebookSKU Family: UX Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX305LA Version: 1.0 Serial Number: xxx Asset Tag: xxx Features: Board is a hosting board Board is replaceable Location In Chassis: MIDDLE Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 25 bytes Chassis Information Manufacturer: ASUSTeK COMPUTER INC. Type: Notebook Lock: Not Present Version: 1.0 Serial Number: xxx Asset Tag: xxx Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 1 (0) SKU Number: To be filled by O.E.M. Handle 0x0004, DMI type 10, 26 bytes On Board Device 1 Information Type: Video Status: Enabled Description: VGA On Board Device 2 Information Type: Ethernet Status: Enabled Description: GLAN On Board Device 3 Information Type: Ethernet Status: Enabled Description: WLAN On Board Device 4 Information Type: Sound Status: Enabled Description: Audio CODEC On Board Device 5 Information Type: SATA Controller Status: Enabled Description: SATA Controller On Board Device 6 Information Type: Other Status: Enabled Description: USB 2.0 Controller On Board Device 7 Information Type: Other Status: Enabled Description: USB 3.0 Controller On Board Device 8 Information Type: Other Status: Enabled Description: SMBus Controller On Board Device 9 Information Type: Other Status: Enabled Description: Card Reader On Board Device 10 Information Type: Other Status: Enabled Description: Cmos Camera On Board Device 11 Information Type: Other Status: Enabled Description: Bluetooth Handle 0x0005, DMI type 11, 5 bytes OEM Strings String 1: String 2: String 3: String 4: 90NB08T5-M00230 String 5: String 6: String 7: String 8: String 9: String 10: Handle 0x000C, DMI type 32,
[Kernel-packages] [Bug 1705592] Re: package linux-image-4.10.0-28-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1705592 Title: package linux-image-4.10.0-28-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Expired Bug description: Several packages have failed installing lately. Should be checked better before they are made public. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-28-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rasmus 1996 F pulseaudio Date: Fri Jul 21 01:17:26 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=af7e72c8-6005-404a-bef3-9630b22b6bb6 InstallationDate: Installed on 2016-06-24 (391 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 3570R/370R/470R/450R/510R/4450RV ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=53e647d1-9a1f-49e3-b64d-66c1cb9bfa34 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-28-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: Upgraded to zesty on 2017-05-05 (76 days ago) dmi.bios.date: 04/29/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P15RAN.208.140429.ZW dmi.board.asset.tag: No Asset Tag dmi.board.name: NP370R5E-S08SE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP15RAN.208.140429.ZW:bd04/29/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn3570R/370R/470R/450R/510R/4450RV:pvrP15RAN:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370R5E-S08SE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 3570R/370R/470R/450R/510R/4450RV dmi.product.version: P15RAN dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705592/+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 1705751] Re: package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1705751 Title: package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Expired Bug description: some quicken up and down of the light as soon as it goes on ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic 4.10.0-26.30 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: claudio1655 F pulseaudio /dev/snd/controlC0: claudio1655 F pulseaudio Date: Sat Jul 1 21:12:35 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=456d0c64-38cc-4acf-8908-98abe5912fa7 InstallationDate: Installed on 2017-06-06 (45 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Acer Aspire 7560 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=91252ade-604e-4138-8ef6-05bcb9a5eaca ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.1 SourcePackage: linux Title: package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE70-SB dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnAcer:bvrV1.07:bd11/06/2012:svnAcer:pnAspire7560:pvrV1.07:rvnAcer:rnJE70-SB:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.07: dmi.product.name: Aspire 7560 dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705751/+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 1718293] Re: [Ubuntu 17.10] POWER9 - Base - Integrate P9 VAS (Virtual Accelerator Switchboard) support in kernel
Looks like patches are needed, please point to the public commits/links ... ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Server Team (canonical-server) -- 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/1718293 Title: [Ubuntu 17.10] POWER9 - Base - Integrate P9 VAS (Virtual Accelerator Switchboard) support in kernel Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: This feature request is used to submit kernel changes needed for adding VAS (Virtual Accelerator Switchboard) support. VAS interface allows kernel or user space to communicate with any accelerator (Ex: NX). kernel changes will be to open a window/ channel with accelerator and communicate with copy / paste facility. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1718293/+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 1718292] Re: POWER9: NX842 module changes
Looks like patches are needed, please point to the public commits/links ... ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/1718292 Title: POWER9: NX842 module changes Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: This feature request will be used to submit NX842 changes needed to support on p9 - Using VAS interfaces instead of icswx to communicate with VAS (on PowerNV), modification of HCALL interface (on PowerVM, if needed) and other format changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1718292/+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 1683587] Re: LSI Harpoon support in megaraid_sas module
Hi even though I'm late to the party, I could offer to test the modified kernel with H330, H710 and H730. If you send me all the necessary things and provide a list of what things to look out for, then I could test these. -- 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/1683587 Title: LSI Harpoon support in megaraid_sas module Status in linux package in Ubuntu: Confirmed Bug description: The Dell PERC H740 series RAID controllers, codename "Harpoon", are not supported in standard Ubuntu kernels. There is a series of kernel patches required to support these: http://www.mail-archive.com/linux- ker...@vger.kernel.org/msg1307314.html There is also a relevant follow-up series: https://www.spinics.net/lists/linux-scsi/msg104667.html especially patches 1 and 12. The relevant PCI IDs from the PCI database (http://pciids.sourceforge.net/v2.2/pci.ids) are: 0016 MegaRAID Tri-Mode SAS3508 1028 1fc9 PERC H840 Adapter 1028 1fcb PERC H740P Adapter 1028 1fcd PERC H740P Mini 1028 1fcf PERC H740P Mini They should be supported from Xenial onwards. The upstream commit is going in for 4.11, so this will need to be backported to v4.4 and v4.10. I am working on SRU patches for this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683587/+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 1718161] Re: linux-lts-trusty: 3.13.0-133.182~precise1 -proposed tracker
** Summary changed: - linux-lts-trusty: -proposed tracker + linux-lts-trusty: 3.13.0-133.182~precise1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger (juergh) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger (juergh) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1718161 Title: linux-lts-trusty: 3.13.0-133.182~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1718159 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718161/+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