[Kernel-packages] [Bug 1551880] [NEW] [Dell XPS 13 9343] Audio broken with I2S mode in Ubuntu 16.04
Public bug reported: I wanted to try Linux again on this machine and the tons of troubleshooting since release got a bit better, but the sound is still a bit strange. So after changing distributions I installed Xubuntu 16.04 Beta 1 today with kernel 4.4.0-8 and sound isn't working because the 3,5 mm device is completely missing. PulseAudio is only showing the HDMI output. I got the sound working by downloading kernel 4.3.6 from the Ubuntu kernel archives, although then it looks like it is running in HDA mode instead of I2S (which I don't like because Dual Boot). Let me know if there is anything else I can do to track down the problem. $ dmesg -t | egrep "(audio|snd|INT3438)" DMAR: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0 snd_hda_intel :00:03.0: enabling device ( -> 0002) sst-acpi INT3438:00: DesignWare DMA Controller, 8 channels haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered $ cat /proc/asound/cards 0 [HDMI ]: HDA-Intel - HDA Intel HDMI HDA Intel HDMI at 0xf7218000 irq 50 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-8-generic 4.4.0-8.23 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sysop 1266 F pulseaudio CurrentDesktop: XFCE Date: Tue Mar 1 18:48:05 2016 HibernationDevice: RESUME=UUID=338a51e1-7748-466e-ba21-4210b34c4189 InstallationDate: Installed on 2016-03-01 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic.efi.signed root=UUID=347e6152-7230-486c-b801-8eb0811c8c8d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-8-generic N/A linux-backports-modules-4.4.0-8-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0WF2C3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0WF2C3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- 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/1551880 Title: [Dell XPS 13 9343] Audio broken with I2S mode in Ubuntu 16.04 Status in linux package in Ubuntu: Confirmed Bug description: I wanted to try Linux again on this machine and the tons of troubleshooting since release got a bit better, but the sound is still a bit strange. So after changing distributions I installed Xubuntu 16.04 Beta 1 today with kernel 4.4.0-8 and sound isn't working because the 3,5 mm device is completely missing. PulseAudio is only showing the HDMI output. I got the sound working by downloading kernel 4.3.6 from the Ubuntu kernel archives, although then it looks like it is running in HDA mode instead of I2S (which I don't like because Dual Boot). Let me know if there is anything else I can do to track down the problem. $ dmesg -t | egrep "(audio|snd|INT3438)" DMAR: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0 snd_hda_intel :00:03.0: enabling device ( -> 0002) sst-acpi INT3438:00: DesignWare DMA Controller, 8 channels haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version:
[Kernel-packages] [Bug 1551854] Re: LXD bootstrap issues on xenial
Also cannot reproduce in a clean VM, so I have to assume juju is tweaking something. Can you show output of 'lxc config show ' where is the container which fails? -- 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/1551854 Title: LXD bootstrap issues on xenial Status in linux package in Ubuntu: Confirmed Bug description: I'm using lxd with zfs block storage on xenial, and having issues with trusty containers. I've witnessed this problem when trying to bootstrap as well as after rebooting the host and a container failed to start. In the latter case, the container that failed to start was the juju controller: c@mawhrin-skel:~/omnibus-layers$ lxc list [3/3] +-+-++--++---+ |NAME | STATE | IPV4 | IPV6 |TYPE| SNAPSHOTS | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 (eth0) | | PERSISTENT | 0 | | | | 10.0.4.1 (lxcbr0) | || | +-+-++--++---+ I manually started it, but found that no upstart services were started. Remembering this thread, https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I checked /var/log/mountall.log in the machine-0 container, and sure enough: root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat /var/log/upstart/mountall.log mount: permission denied mountall: mount /sys/kernel/debug [187] terminated with status 32 mountall: Filesystem could not be mounted: /sys/kernel/debug The problem persists if I stop and start the container. If I remount /sys/kernel/debug on the host, then stop and start the container, upstart succeeds and the juju controller starts up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-8-generic 4.4.0-8.23 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: c 24562 F pulseaudio CurrentDesktop: MATE Date: Tue Mar 1 10:52:45 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=007cedda-f922-4e4c-89b1-57b31f18292e InstallationDate: Installed on 2016-02-28 (2 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) MachineType:
[Kernel-packages] [Bug 1551880] 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/1551880 Title: [Dell XPS 13 9343] Audio broken with I2S mode in Ubuntu 16.04 Status in linux package in Ubuntu: Confirmed Bug description: I wanted to try Linux again on this machine and the tons of troubleshooting since release got a bit better, but the sound is still a bit strange. So after changing distributions I installed Xubuntu 16.04 Beta 1 today with kernel 4.4.0-8 and sound isn't working because the 3,5 mm device is completely missing. PulseAudio is only showing the HDMI output. I got the sound working by downloading kernel 4.3.6 from the Ubuntu kernel archives, although then it looks like it is running in HDA mode instead of I2S (which I don't like because Dual Boot). Let me know if there is anything else I can do to track down the problem. $ dmesg -t | egrep "(audio|snd|INT3438)" DMAR: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0 snd_hda_intel :00:03.0: enabling device ( -> 0002) sst-acpi INT3438:00: DesignWare DMA Controller, 8 channels haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered $ cat /proc/asound/cards 0 [HDMI ]: HDA-Intel - HDA Intel HDMI HDA Intel HDMI at 0xf7218000 irq 50 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-8-generic 4.4.0-8.23 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sysop 1266 F pulseaudio CurrentDesktop: XFCE Date: Tue Mar 1 18:48:05 2016 HibernationDevice: RESUME=UUID=338a51e1-7748-466e-ba21-4210b34c4189 InstallationDate: Installed on 2016-03-01 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic.efi.signed root=UUID=347e6152-7230-486c-b801-8eb0811c8c8d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-8-generic N/A linux-backports-modules-4.4.0-8-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0WF2C3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0WF2C3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551880/+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 1547619] Re: Intermittent screen blinking with 4k external mini display port with 4.4 kernels
I started a kernel bisect between v4.3 final and v4.4-rc1. The kernel bisect will require testing of about 13 test kernels. I built the first test kernel, up to the following commit: 118c216e16c5ccb028cd03a0dcd56d17a07ff8d7 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1547619 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- 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/1547619 Title: Intermittent screen blinking with 4k external mini display port with 4.4 kernels Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: When using an external 4K monitor plugged into the mini display port on my Dell XPS 13 9343 using both the laptop screen and the external monitor (external monitor is left and laptop screen right), when using all of the following kernels: 4.4.0-2.16-generic 4.4.0-4.19-generic 4.4.0-6.21-generic 4.4.0-7.22-generic the external monitor will sometimes blink off for about a second or two, then back on. What is weird is this seems to only happen when typing into a gnome-terminal as opposed to firefox or evolution. Simply changing to a gnome-terminal and typing into it doesn't cause the blinking, but it might happen immediately or it might take several minutes. 4.3.0-7.18-generic worked fine and I can go hours and hours in a gnome-terminal with no issues. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-6-generic 4.4.0-6.21 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jamie 5882 F pulseaudio /dev/snd/controlC1: jamie 5882 F pulseaudio /dev/snd/controlC0: jamie 5882 F pulseaudio CurrentDesktop: Unity Date: Fri Feb 19 12:09:28 2016 HibernationDevice: RESUME=UUID=27fa6713-c8c2-4eb8-9766-ba6918bc1cfb InstallationDate: Installed on 2015-06-13 (250 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic.efi.signed root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq kaslr quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-6-generic N/A linux-backports-modules-4.4.0-6-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-01-12 (38 days ago) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547619/+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 1550576] Re: linux: 3.19.0-53.59 -proposed tracker
** Tags added: qa-testing-passed -- 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/1550576 Title: linux: 3.19.0-53.59 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-53.59 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 kernel-stable-Prepare-package-start:Friday, 26. February 2016 23:43 UTC kernel-stable-Prepare-package-end:Saturday, 27. February 2016 09:03 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. February 2016 09:03 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 01. March 2016 00:02 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Tuesday, 01. March 2016 02:02 UTC kernel-stable-Verification-testing-start:Tuesday, 01. March 2016 02:02 UTC kernel-stable-Certification-testing-start:Tuesday, 01. March 2016 02:02 UTC kernel-stable-Security-signoff-start:Tuesday, 01. March 2016 02:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 01. March 2016 02:02 UTC kernel-stable-Security-signoff-end:Tuesday, 01. March 2016 10:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1550576/+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 1550605] Re: linux-lts-utopic: 3.16.0-64.84~14.04.1 -proposed tracker
** Tags added: qa-testing-passed ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1550605 Title: linux-lts-utopic: 3.16.0-64.84~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.16.0-64.84~14.04.1 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 kernel-stable-Prepare-package-start:Saturday, 27. February 2016 01:54 UTC kernel-stable-Prepare-package-end:Saturday, 27. February 2016 11:02 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. February 2016 11:02 UTC kernel-stable-Promote-to-proposed-end:Monday, 29. February 2016 15:02 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 29. February 2016 16:03 UTC kernel-stable-Verification-testing-start:Monday, 29. February 2016 16:03 UTC kernel-stable-Certification-testing-start:Monday, 29. February 2016 16:03 UTC kernel-stable-Security-signoff-start:Monday, 29. February 2016 16:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 29. February 2016 16:03 UTC kernel-stable-Security-signoff-end:Tuesday, 01. March 2016 12:01 UTC kernel-stable-Regression-testing-end:Tuesday, 01. March 2016 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1550605/+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 1499203] Re: memory leak in hv_storvsc (3.13.0-63-generic)
Thanks for the update, Oskar. Would you say this bug is now resolved? If so, I can close it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1499203 Title: memory leak in hv_storvsc (3.13.0-63-generic) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: Slab and SUnreclaim values in /proc/meminfo keep increasing. On one servers it reached 85% of physical memory after 14 days - but on most other servers it increases more slowly. I checked /proc/slabinfo and almost all allocations were in kmalloc-512. So I enabled "slub_debug=U,kmalloc-512" on one server, and after only 24h of uptime 11% of the memory was used by kmalloc-512 and unreclaimable. With debugging enabled I could see the following in /sys/kernel/slab/kmalloc-512/alloc_calls: 521294 storvsc_queuecommand+0x359/0x790 [hv_storvsc] age=161922/955116/20882927 pid=1-41545 All other counters were below 2000. In /sys/kernel/slab/kmalloc-512/free_calls I see the following: 516823 age=4315783846 pid=0 The hv_storvsc module is for Hyper-V. We are (unfortunately) running Hyper-V 6.3.9600.16384 with Microsoft System Center 2012 R2 Update rollup 3 for all the servers with this issue. Kernels are stock linux-image-3.13.0-63-generic, 3.13.0-63.103, x86_64, from Ubuntu 14.04 LTS . /proc/version_signature contains: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 No output from lspci -vnvn. The problem described above happens on both single and multicore virtual machines. CPU in hypervisors are E5-2630 v2 @ 2.60GHz. Let me know if you need more info or if I can do more debugging. Regards, Oskar Liljeblad --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 24 00:31 seq crw-rw 1 root audio 116, 33 Sep 24 00:31 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [59081.977909] systemd-udevd[26480]: starting version 204 [59124.051974] init: systemd-logind main process (756) killed by TERM signal DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-09-09 (380 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic.efi.signed root=UUID=f4d228d6-2eee-40fc-bf3f-633e46fa8301 ro slub_debug=U,kmalloc-512 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 RelatedPackageVersions: linux-restricted-modules-3.13.0-63-generic N/A linux-backports-modules-3.13.0-63-generic N/A linux-firmware 1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: Sep 24 02:06:19 adm-backup1 dhclient: message repeated 1447 times: [ DHCPREQUEST of 10.40.128.9 on eth0 to 192.0.2.253 port 67 (xid=0x429dad4)] Sep 24 02:06:37 adm-backup1 dhclient: DHCPREQUEST of 10.40.128.9 on eth0 to 255.255.255.255 port 67 (xid=0x429dad4) Sep 24 02:06:37 adm-backup1 dhclient: DHCPACK of 10.40.128.9 from 192.0.2.253 Sep 24 02:06:37 adm-backup1 dhclient: bound to 10.40.128.9 -- renewal in 44877 seconds. _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6126-4244-1659-0314-3158-3955-44 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to:
[Kernel-packages] [Bug 1551870] 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/1551870 Title: snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024 Status in linux package in Ubuntu: Confirmed Bug description: Occurred right after login, several very similar bug alerts happened, this report is about one of them. pos = 16384 pos = 16386 pos = 16388 ... ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-8-generic 4.4.0-8.23 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic i686 NonfreeKernelModules: nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olle 2146 F pulseaudio /dev/snd/controlC1: olle 2146 F pulseaudio Date: Tue Mar 1 09:44:40 2016 Failure: oops HibernationDevice: RESUME=UUID=03bed9e9-e39b-4107-8cd6-c2612af9a6aa InstallationDate: Installed on 2016-02-28 (1 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160226) MachineType: Hewlett-Packard HP xw8400 Workstation OopsText: snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024 VBoxNetFlt: attached to 'enp31s0' / 00:1a:4b:54:34:1c device enp31s0 entered promiscuous mode ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=2160f8ed-4aa3-4243-b5d6-f87c1967e253 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9 RfKill: SourcePackage: linux Title: snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786D5 v02.37 dmi.board.name: 0A08h dmi.board.vendor: Hewlett-Packard dmi.board.version: NA dmi.chassis.asset.tag: CZC722497N dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786D5v02.37:bd07/09/2009:svnHewlett-Packard:pnHPxw8400Workstation:pvr:rvnHewlett-Packard:rn0A08h:rvrNA:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP xw8400 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551870/+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 1548759] Re: linux-lts-trusty: 3.13.0-80.124~precise1 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-80.124~precise1 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 kernel-stable-Prepare-package-start:Tuesday, 23. February 2016 11:02 UTC kernel-stable-master-bug:1548519 kernel-stable-Prepare-package-end:Wednesday, 24. February 2016 01:03 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 24. February 2016 01:03 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 24. February 2016 21:03 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 24. February 2016 23:02 UTC kernel-stable-Verification-testing-start:Wednesday, 24. February 2016 23:02 UTC kernel-stable-Certification-testing-start:Wednesday, 24. February 2016 23:02 UTC kernel-stable-Security-signoff-start:Wednesday, 24. February 2016 23:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 24. February 2016 23:02 UTC kernel-stable-Security-signoff-end:Thursday, 25. February 2016 09:01 UTC + kernel-stable-Regression-testing-end:Tuesday, 01. March 2016 18:01 UTC -- 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/1548759 Title: linux-lts-trusty: 3.13.0-80.124~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-80.124~precise1 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 kernel-stable-Prepare-package-start:Tuesday, 23. February 2016 11:02 UTC kernel-stable-master-bug:1548519 kernel-stable-Prepare-package-end:Wednesday, 24. February 2016 01:03 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 24. February 2016 01:03 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 24. February 2016 21:03 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 24. February 2016 23:02 UTC kernel-stable-Verification-testing-start:Wednesday, 24. February 2016 23:02 UTC kernel-stable-Certification-testing-start:Wednesday, 24. February 2016 23:02 UTC kernel-stable-Security-signoff-start:Wednesday, 24. February 2016 23:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 24. February 2016 23:02 UTC kernel-stable-Security-signoff-end:Thursday, 25. February 2016 09:01 UTC kernel-stable-Regression-testing-end:Tuesday, 01. March 2016 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1548759/+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 1542188] Re: Adaptive keyboard breaks with sleep/resume
Thanks for the update, Dean. Would you say this bug is now resolved? If so, I can close it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1542188 Title: Adaptive keyboard breaks with sleep/resume Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: I have a Lenovo X1 Carbon Gen2. It as the adaptive row of keys that change from function keys to volume, etc when you toggle the function key. It's always worked fine but with this kernel, after a few sleep/resumes, the entire row will go black. If I reboot it will return to normal. dmesg throws a bunch of these.. [29190.142959] thinkpad_acpi: EC reports that Thermal Table has changed [30910.489925] thinkpad_acpi: unknown possible thermal alarm or keyboard event received [30910.489931] thinkpad_acpi: unhandled HKEY event 0x60c0 [30910.489932] thinkpad_acpi: please report the conditions when this event happened to ibm-acpi-de...@lists.sourceforge.net [30911.439252] thinkpad_acpi: unknown possible thermal alarm or keyboard event received [30911.439258] thinkpad_acpi: unhandled HKEY event 0x60c0 though I'm not sure it's the cause of the failure. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-2-generic 4.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dean 3316 F pulseaudio /dev/snd/controlC0: dean 3316 F pulseaudio CurrentDesktop: Unity Date: Fri Feb 5 08:34:46 2016 HibernationDevice: RESUME=UUID=5ce0185d-e833-4337-9655-9be9fcac3654 InstallationDate: Installed on 2015-11-03 (93 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20A7002QUS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-2-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2015-12-07 (59 days ago) dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7002QUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7002QUS:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7002QUS:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7002QUS dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1542188/+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 1548505] Re: linux-ti-omap4: 3.2.0-1478.104 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Description changed: This bug is for tracking the 3.2.0-1478.104 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 kernel-stable-Prepare-package-start:Monday, 22. February 2016 21:01 UTC kernel-stable-master-bug:1548504 kernel-stable-Certification-testing-end:Wednesday, 24. February 2016 16:00 UTC - kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Saturday, 27. February 2016 09:22 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. February 2016 09:22 UTC - kernel-stable-phase-changed:Saturday, 27. February 2016 09:22 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 01. March 2016 16:01 UTC + kernel-stable-phase:Verification & Testing + kernel-stable-phase-changed:Tuesday, 01. March 2016 18:00 UTC + kernel-stable-Security-signoff-start:Tuesday, 01. March 2016 18:00 UTC + kernel-stable-Regression-testing-start:Tuesday, 01. March 2016 18:00 UTC + proposed-announcement-sent:True + kernel-stable-Verification-testing-start:Tuesday, 01. March 2016 18:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1548505 Title: linux-ti-omap4: 3.2.0-1478.104 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid 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 promote-to-proposed series: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the 3.2.0-1478.104 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 kernel-stable-Prepare-package-start:Monday, 22. February 2016 21:01 UTC kernel-stable-master-bug:1548504 kernel-stable-Certification-testing-end:Wednesday, 24. February 2016 16:00 UTC kernel-stable-Prepare-package-end:Saturday, 27. February 2016 09:22 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. February 2016 09:22 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 01. March 2016 16:01 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Tuesday, 01. March 2016 18:00 UTC kernel-stable-Security-signoff-start:Tuesday, 01. March 2016 18:00 UTC kernel-stable-Regression-testing-start:Tuesday, 01. March 2016 18:00 UTC proposed-announcement-sent:True kernel-stable-Verification-testing-start:Tuesday, 01. March 2016 18:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1548505/+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 1550591] Re: linux-lts-vivid: 3.19.0-53.59~14.04.1 -proposed tracker
** Tags added: qa-testing-passed ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the 3.19.0-53.59~14.04.1 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 kernel-stable-Prepare-package-start:Saturday, 27. February 2016 00:30 UTC kernel-stable-master-bug:1550576 kernel-stable-Prepare-package-end:Saturday, 27. February 2016 10:02 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. February 2016 10:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 01. March 2016 09:02 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Tuesday, 01. March 2016 11:02 UTC kernel-stable-Verification-testing-start:Tuesday, 01. March 2016 11:02 UTC kernel-stable-Certification-testing-start:Tuesday, 01. March 2016 11:02 UTC kernel-stable-Security-signoff-start:Tuesday, 01. March 2016 11:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 01. March 2016 11:03 UTC + kernel-stable-Regression-testing-end:Tuesday, 01. March 2016 18:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1550591 Title: linux-lts-vivid: 3.19.0-53.59~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.19.0-53.59~14.04.1 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 kernel-stable-Prepare-package-start:Saturday, 27. February 2016 00:30 UTC kernel-stable-master-bug:1550576 kernel-stable-Prepare-package-end:Saturday, 27. February 2016 10:02 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. February 2016 10:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 01. March 2016 09:02 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Tuesday, 01. March 2016 11:02 UTC kernel-stable-Verification-testing-start:Tuesday, 01. March 2016 11:02 UTC kernel-stable-Certification-testing-start:Tuesday, 01. March 2016 11:02 UTC kernel-stable-Security-signoff-start:Tuesday, 01. March 2016 11:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 01. March 2016 11:03 UTC kernel-stable-Regression-testing-end:Tuesday, 01. March 2016 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1550591/+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 1550605] Re: linux-lts-utopic: 3.16.0-64.84~14.04.1 -proposed tracker
** Description changed: This bug is for tracking the 3.16.0-64.84~14.04.1 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 kernel-stable-Prepare-package-start:Saturday, 27. February 2016 01:54 UTC kernel-stable-Prepare-package-end:Saturday, 27. February 2016 11:02 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. February 2016 11:02 UTC kernel-stable-Promote-to-proposed-end:Monday, 29. February 2016 15:02 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 29. February 2016 16:03 UTC kernel-stable-Verification-testing-start:Monday, 29. February 2016 16:03 UTC kernel-stable-Certification-testing-start:Monday, 29. February 2016 16:03 UTC kernel-stable-Security-signoff-start:Monday, 29. February 2016 16:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 29. February 2016 16:03 UTC kernel-stable-Security-signoff-end:Tuesday, 01. March 2016 12:01 UTC + kernel-stable-Regression-testing-end:Tuesday, 01. March 2016 18:02 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1550605 Title: linux-lts-utopic: 3.16.0-64.84~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.16.0-64.84~14.04.1 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 kernel-stable-Prepare-package-start:Saturday, 27. February 2016 01:54 UTC kernel-stable-Prepare-package-end:Saturday, 27. February 2016 11:02 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. February 2016 11:02 UTC kernel-stable-Promote-to-proposed-end:Monday, 29. February 2016 15:02 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 29. February 2016 16:03 UTC kernel-stable-Verification-testing-start:Monday, 29. February 2016 16:03 UTC kernel-stable-Certification-testing-start:Monday, 29. February 2016 16:03 UTC kernel-stable-Security-signoff-start:Monday, 29. February 2016 16:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 29. February 2016 16:03 UTC kernel-stable-Security-signoff-end:Tuesday, 01. March 2016 12:01 UTC kernel-stable-Regression-testing-end:Tuesday, 01. March 2016 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1550605/+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 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
@Simon Thanks for picking this up again. Topic 1. Audio A3: I will test this this evening or tomorrow and will give you a feedback. I am very sure that the pin I have entered was correct but I will check this again. Topic 3. Logitec Bluetooth Mouse For both channels (OTA9.1 & rc-proposed (current: 270)) I can now connect the mouse. Output during pairing is: [NEW] Device 00:80:00:00:15:76 Bluetooth Mouse [CHG] Controller 4C:74:03:64:75:ED Discoverable: no [CHG] Controller 4C:74:03:64:75:ED Discoverable: yes [CHG] Device 00:80:00:00:15:76 RSSI: -33 [CHG] Device 00:80:00:00:15:76 RSSI is nil [CHG] Controller 4C:74:03:64:75:ED Discovering: no [CHG] Device 00:80:00:00:15:76 Connected: yes [CHG] Device 00:80:00:00:15:76 Modalias: usb:v099Ap0500d011B [CHG] Device 00:80:00:00:15:76 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 00:80:00:00:15:76 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 00:80:00:00:15:76 Paired: yes [CHG] Device 00:80:00:00:15:76 Trusted: yes I was mistaken myself and therefore also my writing in the past: this in NOT a Logitech mouse. It is LogiLink (looks like Logitech, ...) and the packaging simply states: ID0078. Do you need any more information for topic 2. Jabra headset? Thanks for the work, Matthias -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+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 1551319] Re: linux: 4.4.0-9.24 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package-meta Status: New => Fix Released ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) -- 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/1551319 Title: linux: 4.4.0-9.24 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-9.24 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 kernel-Prepare-package-start:Monday, 29. February 2016 16:22 UTC kernel-phase-changed:Monday, 29. February 2016 16:22 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Monday, 29. February 2016 17:01 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1551319/+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 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5
** Changed in: bluez (Ubuntu) Status: New => In Progress ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1527354 Title: [Jawbone ERA] HFP features not working with Bluez5 Status in Canonical System Image: New Status in bluez package in Ubuntu: In Progress Bug description: While debugging some re-factoring work on the ofono upower plugin, I noticed that I wasn't able to answer or terminate calls using my Jawbone ERA headset. I bought this headset last year, and although it's an older model, it's spec sheet states that it supports HSP 1.1, and HFP 1.5. I can pair the device with my krillin, and it properly auto connects ( note, this seems to work better than my iPhone ). In-call audio works for both incoming and outgoing calls, however I get no ringtone in the headset and as mentioned above, I can't answer or terminate the call. I've verified on my iPhone6, that the headset works. In addition to a ringtone in the earpiece, the headset also announces the incoming phone number. From looking at the ofono debug output, I'm never seeing a new HFP connection occur. I noticed as the upower plugin uses a foreach_atom (HFP) style call to update the battery indicators on all attached HFP devices. I've tested this extensively on krillin, running rc-proposed: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 205 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-12-16 17:53:19 version version: 205 version ubuntu: 20151216 version device: 20151204-2254a36 version custom: 2015--36-46-vivid I've also tested on mako, rc-proposed ( #317 ). For reference here's the versions of bluez, ofono, and PulseAudio on the device: bluez 5.36-0ubuntu2~overlay1 ofono 1.17.bzr6908+15.04.20151203-0ubuntu1~awe3 pulseaudio1:6.0-0ubuntu9.11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+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 1546310] Re: In CAR bluetooth not working
Dear all, I have a new insight which might correlate to this bug or contribute to the understanding. Maybe first of all, I just tested the above scenario with: current build number: 270 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-01 15:29:28 version version: 270 version ubuntu: 20160301 version device: 20160108-efc96d8 version custom: 20160111-926-36—vivid this issue is still the same. But I haven't expected it differently since you seemed to be busy with other stuff. Now the new insight: - I have had a similar issue with OTA9.1 but only in the following circumstance: I start to call (and I establish this call fully) before I start the bluetooth of my car. I have expected that the bluetooth of the car picks this call up and I can continue with it via my car microphone & speaker. But I ended with the same behaviour as described above (but only in this circumstance with OTA9.1!): I can not hear anything via my car speakers only if I turn on the phone speaker (inner & outer speaker) I could hear it via these speakers. I you want to have a look at these logs: start of the call: 26.02.2016 at 18:38 h CET start of the in car bluetooth system: approx. 18:42 h I have verified this on later occasions again, this is a reproducible situation for my phone/car/bluetooth combination. ** Attachment added: "20160226_2117.tar.gz" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+attachment/4585578/+files/20160226_2117.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546310 Title: In CAR bluetooth not working Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+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 1540390] Re: Backport more recent driver for SKL, KBL and BXT graphics
** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Peter Hunt (tigerite) -- 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/1540390 Title: Backport more recent driver for SKL, KBL and BXT graphics Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Bug description: We need to support Skylake (SKL), Kabylake (KBL) and Broxton (BXT) graphics in xenial, but the kernel driver is not fresh enough for proper support. For the kernel the plan is to provide a separate driver module (i915_bpo) like for Skylake/Broadwell/Braswell in vivid. The drm/i915 driver in 4.4 is not recent enough for SKL/KBL/BXT, so pulling the driver from current drm-intel-next branch would provide what'll end up in 4.6. The i915 drivers will be modified so that only i915_bpo loads on SKL/KBL/BXT machines, and only there. The driver will get further updates along the way, and possibly also rebased to a later kernel release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1540390/+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 1550468] Re: s390x: correct restore of high gprs on signal return
New kernel upload has entered xenial-proposed, and is being tested before migrating to release component For full changelog see: https://launchpad.net/ubuntu/+source/linux/4.4.0-9.24 Kernel release process workflow bug for this kernel is at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551319 To see progress of this kernel being released to xenial release component. Highlights from the changelog: * s390x: correct restore of high gprs on signal return (LP: #1550468) - s390/compat: correct restore of high gprs on signal return * Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register (LP: #1548414) - s390/fpu: signals vs. floating point control register * Various failures of kernel_security suite on Xenial kernel on s390x arch (LP: #1531327) - [config] s390x -- CONFIG_DEFAULT_MMAP_MIN_ADDR=65536 -- 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/1550468 Title: s390x: correct restore of high gprs on signal return Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Invalid Status in linux source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux source package in Xenial: Fix Committed Bug description: == Comment: #0 - Hendrik Brueckner - 2016-02-26 11:02:00 == Please backport Linux kernel upstream commit ID: commit 342300cc9cd3428bc6bfe5809bfcc1b9a0f06702 Author: Martin SchwidefskyDate: Fri Feb 19 14:44:14 2016 +0100 s390/compat: correct restore of high gprs on signal return git commit 8070361799ae1e3f4ef347bd10f0a508ac10acfb "s390: add support for vector extension" broke 31-bit compat processes in regard to signal handling. The restore_sigregs_ext32() function is used to restore the additional elements from the user space signal frame. Among the additional elements are the upper registers halves for 64-bit register support for 31-bit processes. The copy_from_user that is used to retrieve the high- gprs array from the user stack uses an incorrect length, 8 bytes instead of 64 bytes. This causes incorrect upper register halves to get loaded. Cc: sta...@vger.kernel.org # 3.8+ Signed-off-by: Martin Schwidefsky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550468/+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 1546092] Re: computer freezes frequently
** Tags removed: kernel-key ** Tags added: kernel-da-key -- 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/1546092 Title: computer freezes frequently Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Running Xenial. Freezes seem to happen every 5 to 45 minutes. I have not been able to create any repro steps, it feels quite random. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-4-generic 4.4.0-4.19 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rick 1780 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 16 08:26:12 2016 HibernationDevice: RESUME=UUID=36268acb-4215-452f-9778-754c015d00d8 InstallationDate: Installed on 2016-02-02 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: TOSHIBA Satellite L15W-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic.efi.signed root=UUID=ed019e52-c90e-48b7-bbe4-ae5d39fea067 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-4-generic N/A linux-backports-modules-4.4.0-4-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.00 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 0670 dmi.board.vendor: FF40 dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.00:bd07/16/2015:svnTOSHIBA:pnSatelliteL15W-B:pvrPSKVUU-00S01U:rvnFF40:rn0670:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Satellite L15W-B dmi.product.version: PSKVUU-00S01U dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546092/+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 1551712] 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/1551712 Title: Belkin Thunderbolt 2 Express Dock HD display port hot plug not supported. Status in linux package in Ubuntu: Confirmed Bug description: There are two problems when using this dock: 1. When booted, connecting the dock only allows USB and Ethernet to work, it does not support HDMI or DisplayPort monitors 2. When booted with the device connected, while the device works fine, reseating the dock causes no adapters to work (No USB, Ethernet, HDMI and DisplayPort) This makes this dock and other Thunderbolt docks unusable, because I can't hotplug it correctly. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-30-generic 4.2.0-30.36 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: graingert 1560 F pulseaudio /dev/snd/controlC0: graingert 1560 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 1 12:42:39 2016 InstallationDate: Installed on 2016-01-05 (55 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic.efi.signed root=UUID=665d68d7-0c44-48e6-9e4c-9496a5c21d21 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-30-generic N/A linux-backports-modules-4.2.0-30-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B15.1510261437 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551712/+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 1545330] Re: [wily][regression] systemtap script compilation broken by new kernels
** 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/1545330 Title: [wily][regression] systemtap script compilation broken by new kernels Status in linux package in Ubuntu: Fix Committed Status in systemtap package in Ubuntu: Confirmed Status in linux source package in Wily: In Progress Status in systemtap source package in Wily: New Status in linux source package in Xenial: Fix Committed Status in systemtap source package in Xenial: Confirmed Status in systemtap package in Fedora: Unknown Bug description: The following errors appear when compiling any systemtap script: In file included from include/linux/mutex.h:15:0, from /tmp/stapbdpxn3/stap_a0ec17f995e8f89d672d8c2eb7fe7c24_1693_src.c:25: include/linux/spinlock_types.h:55:14: error: ‘__ARCH_SPIN_LOCK_UNLOCKED’ undeclared here (not in a function) .raw_lock = __ARCH_SPIN_LOCK_UNLOCKED, \ ^ include/linux/spinlock_types.h:79:15: note: in expansion of macro ‘__RAW_SPIN_LOCK_INITIALIZER’ { { .rlock = __RAW_SPIN_LOCK_INITIALIZER(lockname) } } ^ include/linux/spinlock_types.h:82:16: note: in expansion of macro ‘__SPIN_LOCK_INITIALIZER’ (spinlock_t ) __SPIN_LOCK_INITIALIZER(lockname) ^ include/linux/mutex.h:111:18: note: in expansion of macro ‘__SPIN_LOCK_UNLOCKED’ , .wait_lock = __SPIN_LOCK_UNLOCKED(lockname.wait_lock) \ ^ include/linux/mutex.h:117:27: note: in expansion of macro ‘__MUTEX_INITIALIZER’ struct mutex mutexname = __MUTEX_INITIALIZER(mutexname) Upstream fix: https://www.sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=320e1ecb16427b5769f0f5a097d80823ee1fb765 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1545330/+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 1551319] Re: linux: 4.4.0-9.24 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: New => Fix Released ** Changed in: kernel-development-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) -- 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/1551319 Title: linux: 4.4.0-9.24 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-9.24 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 kernel-Prepare-package-start:Monday, 29. February 2016 16:22 UTC kernel-phase-changed:Monday, 29. February 2016 16:22 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Monday, 29. February 2016 17:01 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1551319/+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 1548505] Re: linux-ti-omap4: 3.2.0-1478.104 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1548505 Title: linux-ti-omap4: 3.2.0-1478.104 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid 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 promote-to-proposed series: Fix Released 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-ti-omap4 package in Ubuntu: Invalid Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the 3.2.0-1478.104 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 kernel-stable-Prepare-package-start:Monday, 22. February 2016 21:01 UTC kernel-stable-master-bug:1548504 kernel-stable-Certification-testing-end:Wednesday, 24. February 2016 16:00 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Saturday, 27. February 2016 09:22 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. February 2016 09:22 UTC kernel-stable-phase-changed:Saturday, 27. February 2016 09:22 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1548505/+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 1547207] Re: skb -> ip_summed == CHECKSUM_NONE creates corrupt packets
** Tags added: verification-done-precise -- 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/1547207 Title: skb -> ip_summed == CHECKSUM_NONE creates corrupt packets Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Canonical, Please apply. Release: all Arch: all Original discussion here: http://www.gossamer- threads.com/lists/linux/kernel/2329960 Signed off patch here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce8c839b74e3017996fad4e1b7ba2e2625ede82f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547207/+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 1540390] Re: Backport more recent driver for SKL, KBL and BXT graphics
** Changed in: initramfs-tools (Ubuntu) Assignee: Peter Hunt (tigerite) => (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/1540390 Title: Backport more recent driver for SKL, KBL and BXT graphics Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Bug description: We need to support Skylake (SKL), Kabylake (KBL) and Broxton (BXT) graphics in xenial, but the kernel driver is not fresh enough for proper support. For the kernel the plan is to provide a separate driver module (i915_bpo) like for Skylake/Broadwell/Braswell in vivid. The drm/i915 driver in 4.4 is not recent enough for SKL/KBL/BXT, so pulling the driver from current drm-intel-next branch would provide what'll end up in 4.6. The i915 drivers will be modified so that only i915_bpo loads on SKL/KBL/BXT machines, and only there. The driver will get further updates along the way, and possibly also rebased to a later kernel release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1540390/+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 1548414] Re: Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register
New kernel upload has entered xenial-proposed, and is being tested before migrating to release component For full changelog see: https://launchpad.net/ubuntu/+source/linux/4.4.0-9.24 Kernel release process workflow bug for this kernel is at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551319 To see progress of this kernel being released to xenial release component. Highlights from the changelog: * s390x: correct restore of high gprs on signal return (LP: #1550468) - s390/compat: correct restore of high gprs on signal return * Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register (LP: #1548414) - s390/fpu: signals vs. floating point control register * Various failures of kernel_security suite on Xenial kernel on s390x arch (LP: #1531327) - [config] s390x -- CONFIG_DEFAULT_MMAP_MIN_ADDR=65536 -- 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/1548414 Title: Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: == Comment: #0 - Alexander Efremkin- 2016-02-17 12:18:14 == With a C program sets FPE handler and triggers an FPE exception, it expects that machine-dependent context data, which is passed to the handler, will contain sensible values. In this scenario, however, FPC register was zero and contained no DXC (Data-Exception Code) indication: #include #include #include void trapFunction() { asm volatile ("lhi %r1,0\n\t" "cit %r1,0,8\n\t"); } static void sigFPE_handler(int signal, siginfo_t *info, void *context) { ucontext_t *uc = context; mcontext_t mc = uc->uc_mcontext; fpregset_t fpregs = mc.fpregs; unsigned int fpc = fpregs.fpc; printf("received signal!\n"); printf("fpc: %08x\n", fpc ); } int main() { struct sigaction action; memset(, '\0', sizeof(action)); printf("registering signal handler\n"); action.sa_flags |= SA_SIGINFO; action.sa_sigaction = sigFPE_handler; if (sigaction(SIGFPE, , NULL)) printf("error calling sigaction\n"); printf("firing trap\n"); trapFunction(); return 0; } This program prints "fpc: ", but the expected output is "fpc: ff00".. The IBM Java team has encountered test failures around the use of trap instructions; Linux on z Distribution Test reproduced the issue on the following system: z13 LPAR Ubuntu 16.04 Kernel 4.4.0-4-generic gcc (Ubuntu 5.3.1-8ubuntu2) 5.3.1 20160205 libc6 2.21-0ubuntu5 Also, similar issue has been found during test of SIMD (vector) instructions, FPC contents was also zero, whereas it expected at least an exception mask and vector-defined DXC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548414/+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 1536810] Re: kernel install failed /bin/cp: cannot stat ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory
Verified fixed in arm64 image for 20160227. I noticed it does still have the bogus 'initrd.img file: $ ls -l $exdir/boot total 20592 drwxr-xr-x 2 root root 4096 Feb 27 14:36 grub -rw-r--r-- 1 root root 21079648 Feb 27 14:38 initrd.img But the initrd.img file does not seem to cause a problem here, and after install we have a symlink to the proper place. $ ls -l $exdir/boot/initrd.img lrwxrwxrwx 1 root root 26 Mar 1 15:13 /tmp/tmp.RGUZJZwhWr/boot/initrd.img -> initrd.img-4.4.0-8-generic I've reverted my workaround change in maas-images at revno 284. -- 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/1536810 Title: kernel install failed /bin/cp: cannot stat ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory Status in linux package in Ubuntu: Fix Released Bug description: Hi, this failure for kernel package installation occured inside a maas image (lp:maas-images) build process. The failure log ends like this: Unpacking linux-generic (4.3.0.7.8) ... Processing triggers for man-db (2.7.5-1) ... Setting up linux-image-4.3.0-7-generic (4.3.0-7.18) ... Running depmod. update-initramfs: deferring update (hook will be called later) /bin/cp: cannot stat '/boot/initrd.img-4.3.0-7-generic': No such file or directory Failed to copy /boot/initrd.img-4.3.0-7-generic to /boot/initrd.img at /var/lib/dpkg/info/linux-image-4.3.0-7-generic.postinst line 745. dpkg: error processing package linux-image-4.3.0-7-generic (--configure): subprocess installed post-installation script returned error exit status 2 Setting up devio (1.2-1build2) ... Setting up linux-base (4.0ubuntu1) ... Setting up flash-kernel (3.0~rc.4ubuntu57) ... Setting up linux-firmware (1.155) ... dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-4.3.0-7-generic; however: Package linux-image-4.3.0-7-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured Setting up linux-headers-4.3.0-7 (4.3.0-7.18) ... Setting up linux-headers-4.3.0-7-generic (4.3.0-7.18) ... Setting up linux-headers-generic (4.3.0.7.8) ... dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 4.3.0.7.8); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: linux-image-4.3.0-7-generic linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) failed install of linux-generic failed chroot and kernel install failed failed to get linux-generic output Related bugs: * bug 1539157: Images built with "link_in_boot = yes" in /etc/kernel-img.conf end up with a broken /boot/initrd.img * bug 1536810 kernel install failed /bin/cp: cannot stat ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536810/+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 1550050] Re: repeating phantom key when bt disconnects
** Changed in: canonical-pocket-desktop Importance: Undecided => Critical ** Changed in: canonical-pocket-desktop Assignee: (unassigned) => kevin gunn (kgunn72) ** Changed in: mir Importance: Undecided => Critical ** Changed in: mir (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1550050 Title: repeating phantom key when bt disconnects Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: New Status in Mir: In Progress Status in bluez package in Ubuntu: Confirmed Status in mir package in Ubuntu: In Progress Bug description: Every now and then when having bt mouse/keyboard connected - you will see when selecting a text box there is a repeating character (there is no specific character, but always repeats) It seems to be related somehow to bt devices disconnecting the only cure is a reboot This was reproduced by turning off the keyboard while holding down a key. We suspect the key up event is never delivered. This mimics the case where the BT connection drops off momentarily or perhaps an event is missed over the BT connection. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+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 1551319] Re: linux: 4.4.0-9.24 -proposed tracker
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-9.24/dwalin__4.4.0-9.24__2016-03-01_16-14-00/results-index.html ** Changed in: kernel-development-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551319 Title: linux: 4.4.0-9.24 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-9.24 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 kernel-Prepare-package-start:Monday, 29. February 2016 16:22 UTC kernel-phase-changed:Monday, 29. February 2016 16:22 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Monday, 29. February 2016 17:01 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1551319/+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 1531327] Re: Various failures of kernel_security suite on Xenial kernel on s390x arch
** Tags added: s390x -- 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/1531327 Title: Various failures of kernel_security suite on Xenial kernel on s390x arch Status in QA Regression Testing: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Partial log: 01/05 13:07:05 ERROR| utils:0153| [stderr] ASLR enabled ... ok 01/05 13:07:05 ERROR| utils:0153| [stderr] test_020_aslr_dapper_stack (__main__.KernelSecurityTest) 01/05 13:07:05 ERROR| utils:0153| [stderr] ASLR of stack ... ok 01/05 13:07:05 ERROR| utils:0153| [stderr] test_021_aslr_dapper_libs (__main__.KernelSecurityTest) 01/05 13:07:05 ERROR| utils:0153| [stderr] ASLR of libs ... FAIL 01/05 13:07:05 ERROR| utils:0153| [stderr] test_021_aslr_dapper_mmap (__main__.KernelSecurityTest) 01/05 13:07:05 ERROR| utils:0153| [stderr] ASLR of mmap ... FAIL 01/05 13:07:05 ERROR| utils:0153| [stderr] test_022_aslr_hardy_text (__main__.KernelSecurityTest) 01/05 13:07:05 ERROR| utils:0153| [stderr] ASLR of text ... FAIL 01/05 13:07:05 ERROR| utils:0153| [stderr] test_022_aslr_hardy_vdso (__main__.KernelSecurityTest) 01/05 13:07:05 ERROR| utils:0153| [stderr] ASLR of vdso ... FAIL 01/05 13:07:05 ERROR| utils:0153| [stderr] test_022_aslr_intrepid_brk (__main__.KernelSecurityTest) 01/05 13:07:05 ERROR| utils:0153| [stderr] ASLR of brk ... FAIL Full log is attached (client.DEBUG.txt). To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1531327/+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 1551319] Re: linux: 4.4.0-9.24 -proposed tracker
** Changed in: kernel-development-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-development-workflow/prepare-package-signed Status: New => Fix Released ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) -- 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/1551319 Title: linux: 4.4.0-9.24 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Confirmed Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-9.24 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 kernel-Prepare-package-start:Monday, 29. February 2016 16:22 UTC kernel-phase-changed:Monday, 29. February 2016 16:22 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Monday, 29. February 2016 17:01 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1551319/+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 1548505] Re: linux-ti-omap4: 3.2.0-1478.104 -proposed tracker
** Description changed: This bug is for tracking the 3.2.0-1478.104 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 kernel-stable-Prepare-package-start:Monday, 22. February 2016 21:01 UTC kernel-stable-master-bug:1548504 kernel-stable-Certification-testing-end:Wednesday, 24. February 2016 16:00 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Saturday, 27. February 2016 09:22 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. February 2016 09:22 UTC kernel-stable-phase-changed:Saturday, 27. February 2016 09:22 UTC + kernel-stable-Promote-to-proposed-end:Tuesday, 01. March 2016 16:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1548505 Title: linux-ti-omap4: 3.2.0-1478.104 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid 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 promote-to-proposed series: Fix Released 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-ti-omap4 package in Ubuntu: Invalid Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the 3.2.0-1478.104 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 kernel-stable-Prepare-package-start:Monday, 22. February 2016 21:01 UTC kernel-stable-master-bug:1548504 kernel-stable-Certification-testing-end:Wednesday, 24. February 2016 16:00 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Saturday, 27. February 2016 09:22 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. February 2016 09:22 UTC kernel-stable-phase-changed:Saturday, 27. February 2016 09:22 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 01. March 2016 16:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1548505/+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 1551787] [NEW] Ubuntu crashed after Laptop is collapsed
You have been subscribed to a public bug: After I collapsed the laptop, disconnected a monitor and took the laptop to another place with a docking station and monitor, Ubuntu 15.10 was not restartable again. It is a Thinkpad T440s. It was possible to change keyboard lights via Fn + Space, but it was not possible to restart the laptop by hitting any button or by hitting the power button. I only could hit the power button for some seconds, so Ubuntu could restart. I have no clue what package caused this. kern.log contains: Mar 1 15:15:22 reichelt-ThinkPad-T440s kernel: [ 26.919927] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Mar 1 15:15:23 reichelt-ThinkPad-T440s kernel: [ 27.499806] Bluetooth: RFCOMM TTY layer initialized Mar 1 15:15:23 reichelt-ThinkPad-T440s kernel: [ 27.499813] Bluetooth: RFCOMM socket layer initialized Mar 1 15:15:23 reichelt-ThinkPad-T440s kernel: [ 27.499818] Bluetooth: RFCOMM ver 1.11 Mar 1 15:15:25 reichelt-ThinkPad-T440s kernel: [ 29.953253] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Mar 1 15:15:30 reichelt-ThinkPad-T440s kernel: [ 34.605776] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Mar 1 15:15:31 reichelt-ThinkPad-T440s gnome-session[1927]: Entering running state Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.577783] wlan0: authenticate with 0c:85:25:68:72:eb Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.584251] wlan0: send auth to 0c:85:25:68:72:eb (try 1/3) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.660589] wlan0: authenticated Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.661279] wlan0: associate with 0c:85:25:68:72:eb (try 1/3) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.667460] wlan0: RX AssocResp from 0c:85:25:68:72:eb (capab=0x11 status=0 aid=10) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.670657] wlan0: associated Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.670693] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673874] cfg80211: Regulatory domain changed to country: DE Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673877] cfg80211: DFS Master region: ETSI Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673878] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673880] cfg80211: (240 KHz - 2483500 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673881] cfg80211: (515 KHz - 525 KHz @ 8 KHz, 20 KHz AUTO), (N/A, 2000 mBm), (N/A) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673883] cfg80211: (525 KHz - 535 KHz @ 8 KHz, 20 KHz AUTO), (N/A, 2000 mBm), (0 s) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673884] cfg80211: (547 KHz - 5725000 KHz @ 16 KHz), (N/A, 2698 mBm), (0 s) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673885] cfg80211: (5700 KHz - 6600 KHz @ 216 KHz), (N/A, 4000 mBm), (N/A) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.764423] wlan0: Limiting TX power to 17 dBm as advertised by 0c:85:25:68:72:eb Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 162.965399] usb 1-3: new low-speed USB device number 5 using xhci_hcd Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.097082] usb 1-3: New USB device found, idVendor=03f0, idProduct=094a Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.097090] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.097094] usb 1-3: Product: HP USB Optical Mouse Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.097097] usb 1-3: Manufacturer: PixArt Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.098197] usb 1-3: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.130256] hidraw: raw HID events driver (C) Jiri Kosina Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.135844] usbcore: registered new interface driver usbhid Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.135847] usbhid: USB HID core driver Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.138802] input: PixArt HP USB Optical Mouse as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:03F0:094A.0001/input/input17 Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.193472] hid-generic 0003:03F0:094A.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt HP USB Optical Mouse] on usb-:00:14.0-3/input0 Mar 1 15:32:44 reichelt-ThinkPad-T440s kernel: [ 1068.664276] usb 1-3: USB disconnect, device number 5 Mar 1 15:32:46 reichelt-ThinkPad-T440s kernel: [ 1070.577753] thinkpad_acpi: EC reports that Thermal Table has changed Mar 1 15:32:56 reichelt-ThinkPad-T440s kernel: [ 1080.720873] thinkpad_acpi: docked into
[Kernel-packages] [Bug 1481357] Re: [LTCTest][Kernel][OP810]Ubuntu14.04.3: kernel call trace while continuously switching between smt on/off and changing subcores
Tim, >From what I understand, it seems a regression from what we have in 14.04.2. Satheesh, is it correct? Is this a regression? -- 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/1481357 Title: [LTCTest][Kernel][OP810]Ubuntu14.04.3: kernel call trace while continuously switching between smt on/off and changing subcores Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Bug description: == Comment: #0 - Satheesh Rajendran- 2015-07-14 02:32:22 == While running the below script, and nothing else was running in the system, host got the kernel call traces after around 15~20 mins #!/bin/bash -x while true; do for i in 1 2 4; do ppc64_cpu --subcores-per-core=$i; ppc64_cpu --info ppc64_cpu --smt=off; ppc64_cpu --info sleep 1; lscpu ppc64_cpu --smt=on; ppc64_cpu --info sleep 1; lscpu done; sleep 1; done Environment: -- $ cat /etc/issue Ubuntu 14.04.2 LTS \n \l $ uname -a Linux tul8fp 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux $ lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):160 On-line CPU(s) list: 0,4,8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,138-159 Off-line CPU(s) list: 1-3,5-7,9-11,13-15,17-19,21-23,25-27,29-31,33-35,37-39,41-43,45-47,49-51,53-55,57-59,61-63,65-67,69-71,73-75,77-79,81-83,85-87,89-91,93-95,97-99,101-103,105-107,109-111,113-115,117-119,121-123,125-127,129-131,133-135,137 Thread(s) per core:2 Core(s) per socket:10 Socket(s): 2 NUMA node(s): 2 Model: 8335-GTA L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 0,4,88,92,96,100,104,108,112,116,120,124,128,132,136,138-159 NUMA node8 CPU(s): 8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84 $ tail -10 /proc/cpuinfo processor : 159 cpu : POWER8 (raw), altivec supported clock : 2693.00MHz revision : 2.0 (pvr 004d 0200) timebase : 51200 platform : PowerNV model : 8335-GTA machine : PowerNV 8335-GTA firmware : OPAL v3 Logs:- - # dmesg [79081.074088] INFO: task irqbalance:1897 blocked for more than 120 seconds. [79081.074333] Not tainted 3.19.0-22-generic #22~14.04.1-Ubuntu [79081.074388] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [79081.074449] irqbalance D 3fff9ac39d3c 0 1897 1 0x0004 [79081.074454] Call Trace: [79081.074470] [c007e8d035f0] [3fff9af5] 0x3fff9af5 (unreliable) [79081.074477] [c007e8d037c0] [c0015934] __switch_to+0x204/0x350 [79081.074482] [c007e8d03820] [c0a11508] __schedule+0x368/0x8d0 [79081.074486] --- interrupt: 1000ba30 at 0xc007e8d039f0 [79081.074486] LR = 0x10026a6c1d0 [79081.074490] [c007e8d03a40] [c0a120a0] schedule_preempt_disabled+0x20/0x30 (unreliable) [79081.074494] [c007e8d03a60] [c0a1420c] __mutex_lock_slowpath+0xfc/0x1f0 [79081.074497] [c007e8d03ae0] [c0a1436c] mutex_lock+0x6c/0x70 [79081.074501] [c007e8d03b10] [c064488c] online_show+0x3c/0x90 [79081.074503] [c007e8d03b90] [c0644fec] dev_attr_show+0x5c/0xc0 [79081.074508] [c007e8d03bd0] [c035b7f4] sysfs_kf_seq_show+0x114/0x200 [79081.074511] [c007e8d03c20] [c03591e4] kernfs_seq_show+0x54/0x70 [79081.074515] [c007e8d03c50] [c02e74fc] seq_read+0xec/0x500 [79081.074519] [c007e8d03cf0] [c035a474] kernfs_fop_read+0x184/0x220 [79081.074523] [c007e8d03d50] [c02b520c] __vfs_read+0x6c/0x120 [79081.074527] [c007e8d03d90] [c02b5364] vfs_read+0xa4/0x1c0 [79081.074530] [c007e8d03de0] [c02b54ec] SyS_read+0x6c/0x110 [79081.074534] [c007e8d03e30] [c0009258] system_call+0x38/0xd0 [79081.074546] INFO: task ppc64_cpu:111047 blocked for more than 120 seconds. [79081.074597] Not tainted 3.19.0-22-generic #22~14.04.1-Ubuntu [79081.074802] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [79081.074865] ppc64_cpu D 3fff82892d08 0 111047 109995 0x0004 [79081.074868] Call Trace: [79081.074871] [c00f1c67f680] [c00f1c67f710] 0xc00f1c67f710 (unreliable) [79081.074875] [c00f1c67f850] [c0015934] __switch_to+0x204/0x350 [79081.074878]
[Kernel-packages] [Bug 1550050] Re: repeating phantom key when bt disconnects
** Changed in: mir Status: New => In Progress ** Changed in: mir Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1550050 Title: repeating phantom key when bt disconnects Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: New Status in Mir: In Progress Status in bluez package in Ubuntu: Confirmed Status in mir package in Ubuntu: In Progress Bug description: Every now and then when having bt mouse/keyboard connected - you will see when selecting a text box there is a repeating character (there is no specific character, but always repeats) It seems to be related somehow to bt devices disconnecting the only cure is a reboot This was reproduced by turning off the keyboard while holding down a key. We suspect the key up event is never delivered. This mimics the case where the BT connection drops off momentarily or perhaps an event is missed over the BT connection. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
verification can be done with this script: #!/bin/bash modprobe nbd qemu-nbd -d /dev/nbd0 truncate /tmp/testfile -s 20G qemu-nbd -c /dev/nbd0 /tmp/testfile for n in $( seq 1 250 ) ; do echo $n ( dd if=/dev/zero of=/dev/nbd0 bs=1 & ) done qemu-nbd -d /dev/nbd0 after running that, on an unpatched system the dmesg will show a large number (~100 or more) of messages like: [ 70.408246] block nbd0: Attempted send on closed socket with a patched kernel, the dmesg will show a ratelimited number (~10) of those messages. This has been verified on trusty 3.13, vivid 3.19, and wily 4.2 ** Tags removed: verification-needed-vivid verification-needed-wily ** Tags added: verification-done-vivid verification-done-wily -- 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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 12:23 seq crw-rw 1 root audio 116, 33 Nov 24 12:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL385 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-36-generic root=UUID=13289ac9-8dc9-4feb-b6bd-ca7db66b21d6 ro console=tty0 console=ttyS1,38400 nosplash crashkernel=384M-:512M nox2apic intremap=off ProcVersionSignature: Ubuntu 3.19.0-36.41~14.04.1hf00090138v20151122b1-generic 3.19.8-ckt9 RelatedPackageVersions: linux-restricted-modules-3.19.0-36-generic N/A linux-backports-modules-3.19.0-36-generic N/A linux-firmware 1.127.18 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.19.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/02/2014 dmi.bios.vendor: HP dmi.bios.version: A18 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrA18:bd02/02/2014:svnHP:pnProLiantDL385G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL385 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1550576] onza (amd64) - tests ran: 197, failed: 0
tests ran: 197, failed: 0; http://kernel.ubuntu.com/testing/3.19.0-53.59/onza__3.19.0-53.59__2016-03-01_06-59-00/results-index.html -- 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/1550576 Title: linux: 3.19.0-53.59 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-53.59 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 kernel-stable-Prepare-package-start:Friday, 26. February 2016 23:43 UTC kernel-stable-Prepare-package-end:Saturday, 27. February 2016 09:03 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. February 2016 09:03 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 01. March 2016 00:02 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Tuesday, 01. March 2016 02:02 UTC kernel-stable-Verification-testing-start:Tuesday, 01. March 2016 02:02 UTC kernel-stable-Certification-testing-start:Tuesday, 01. March 2016 02:02 UTC kernel-stable-Security-signoff-start:Tuesday, 01. March 2016 02:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 01. March 2016 02:02 UTC kernel-stable-Security-signoff-end:Tuesday, 01. March 2016 10:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1550576/+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 1550050] Re: repeating phantom key when bt disconnects
I will start with a small fix to get the repeat to stop on disconnect.. Then there still is a problem with modifier states that might be stuck untill the device is reattached and the key is pressed again.. ** Changed in: mir (Ubuntu) Status: New => Confirmed ** Changed in: mir (Ubuntu) Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny) ** Changed in: mir (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1550050 Title: repeating phantom key when bt disconnects Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: New Status in Mir: New Status in bluez package in Ubuntu: Confirmed Status in mir package in Ubuntu: In Progress Bug description: Every now and then when having bt mouse/keyboard connected - you will see when selecting a text box there is a repeating character (there is no specific character, but always repeats) It seems to be related somehow to bt devices disconnecting the only cure is a reboot This was reproduced by turning off the keyboard while holding down a key. We suspect the key up event is never delivered. This mimics the case where the BT connection drops off momentarily or perhaps an event is missed over the BT connection. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+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 1548505] Re: linux-ti-omap4: 3.2.0-1478.104 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1548505 Title: linux-ti-omap4: 3.2.0-1478.104 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid 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 promote-to-proposed series: In Progress 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-ti-omap4 package in Ubuntu: Invalid Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the 3.2.0-1478.104 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 kernel-stable-Prepare-package-start:Monday, 22. February 2016 21:01 UTC kernel-stable-master-bug:1548504 kernel-stable-Certification-testing-end:Wednesday, 24. February 2016 16:00 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Saturday, 27. February 2016 09:22 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. February 2016 09:22 UTC kernel-stable-phase-changed:Saturday, 27. February 2016 09:22 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1548505/+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 1546145] Re: Surelock-GA2:kernel panic @ cxl_configure_adapter+0x418/0x8b0
** Tags removed: verification-needed-wily ** Tags added: verification-done-wily -- 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/1546145 Title: Surelock-GA2:kernel panic @ cxl_configure_adapter+0x418/0x8b0 Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: == Comment: #18 - Andrew Donnellan - 2016-02-15 20:17:01 == Canonical kernel team - please apply 1bc74f1ccd457832dc515fc1febe6655985fdcd2 from the powerpc-fixes tree. https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=1bc74f1ccd457832dc515fc1febe6655985fdcd2 powerpc/powernv: Fix stale PE primary bus When PCI bus is unplugged during full hotplug for EEH recovery, the platform PE instance (struct pnv_ioda_pe) isn't released and it dereferences the stale PCI bus that has been released. It leads to kernel crash when referring to the stale PCI bus. This fixes the issue by correcting the PE's primary bus when it's oneline at plugging time, in pnv_pci_dma_bus_setup() which is to be called by pcibios_fixup_bus(). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546145/+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 1124250] Re: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth
Hi, Am I still hitting this bug ? root@XX:~# uname -r 3.13.0-77-generic root@XX~# root@~# cat /etc/issue Ubuntu 14.04.4 LTS \n \l root@:~# root@prod-login-west01:~# ls -l /u4/ | head total 9356 drwx--x--x 6 nobody staff4096 Jun 24 2013 aabdul drwx--x--x 75 nobody staff 24576 Feb 12 2015 aadhikar drwxr-xr-x 3 4294967294 daemon 4096 Nov 6 2013 aaggarwa drwx--x--x 27 nobody staff 20480 Jul 22 2012 aalness drwx--x--x 3 4294967294 staff4096 Aug 1 2012 aamehta drwx--x--x 4 nobody staff4096 Dec 10 2012 aamsalem drwx--x--x 4 4294967294 staff4096 Jan 23 2015 aamte drwxr-xr-x 3 4294967294 staff4096 Jul 15 2014 aanand drwx--x--x 2 4294967294 staff4096 Mar 26 2013 aassfalg root@prod-login-west01:~# -- 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/1124250 Title: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Status in nfs-utils package in Debian: Confirmed Status in Fedora: Unknown Bug description: [Impact] * This bug is likely to cause an incorrect UID/GID mapping for NFS shares in case of large numbers of differend UIDs/GIDs or in case of expired UID/GID mappings (stored as keys in the kernel). [Test Case] 1. Setup a nfs4 server exporting /home with a large number of different users and ldap-based authentication. 2. Mount the share on a ldap-connected client machine. 3. List the mounted /home directory. 4. Wait more than 10 minutes (the default key expiration time) and list it again with ls -l. Expected result - all directories are listed with correct UIDs/GIDs. Actual result - some of the directories may be listed with incorrect UID/GID of 4294967294. [Regression Potential] * This issue has been merged upstream in the 3.18 kernel and is also present in Debian's 3.16 kernel. [Other Info] * Original bug description: I'm running a nfs4 server exporting a directory /home (ext4,usrquota). This server is running Ubuntu 12.04 amd64(up-to-date). This directory is handling 662 homedirs for ldap authenticated users. /etc/exports is : /exports 192.168.0.0/24(rw,fsid=0,no_subtree_check) Important lines in /etc/idmapd.conf : domain=my-domain.org [Translation] Method=nsswitch. In /etc/default/nfs-common : NEED_IDMAPD=yes In /etc/default/nfs-kernel-server : RPCNFSDCOUNT=75 RPCMOUNTDOPTS=--manage-gids 2 Clients (rhel6 x86 & Ubuntu 12.04.2 i686) are mounting this nfs4 exported directory with no problems : When doing ls -l /home on this clients, I have : ... drwx-- 4 user100 oldusers 4096 sept. 21 2011 user100 drwx-- 4 user101 oldusers 4096 sept. 21 2011 user101 drwx-- 37 user102 oldusers 4096 oct. 1 19:06 user102 drwx-- 36 user103 users4096 févr. 5 21:08 user103 drwx-- 36 user104 users4096 févr. 8 14:03 user104 drwx-- 30 user105 users4096 févr. 4 18:01 user105 drwx-- 28 user106 oldusers 4096 oct. 5 2011 user106 drwx-- 37 user107 oldusers 4096 janv. 8 14:52 user107 drwx-- 31 user108 users4096 déc. 4 11:52 user108 drwx-- 4 user109 oldusers 4096 sept. 21 2011 user109 drwx--x--x 45 user110 oldusers 4096 janv. 22 15:53 user109 drwx-- 31 user111 users4096 janv. 29 12:03 user110 ... uid/gid mapping works fine, authldap works fine, ... All Clients running Ubuntu 12.10 i686 or Ubuntu 12.10 amd64 are experiencing the same problem : The config files are the same that used in ubuntu 12.04. Auth ldap is correctly configured, user can log in. This is the /etc/fstab entry for /home : 192.168.0.1:/ /home nfs rw,nfsvers=4 0 0 Important lines in /etc/idmapd.conf : domain=my-domain.org [Translation] Method=nsswitch In /etc/default/nfs-common : NEED_IDMAPD=yes /etc/nsswitch.conf is : passwd: files ldap group: files ldap shadow: files ldap When doing ls -l /home there is a strange problem : drwx-- 4 4294967294 oldusers 4096 sept. 21 2011 user100 drwx-- 4 user101oldusers 4096 sept. 21 2011 user101 drwx-- 37 user102oldusers 4096 oct. 1 19:06 user102 drwx-- 36 4294967294 users4096 févr. 5 21:08 user103 drwx-- 36 4294967294 users4096 févr. 8 14:03 user104 drwx-- 30 4294967294 users4096 févr. 4 18:01 user105 drwx-- 28 4294967294 oldusers 4096 oct. 5 2011 user106 drwx-- 37 4294967294 oldusers 4096 janv. 8 14:52 user107 drwx-- 31 4294967294 users4096 déc. 4 11:52 user108 drwx-- 4 user109oldusers
[Kernel-packages] [Bug 1124250] Re: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth
Hi, I'm still seeing this error. root@XX:~# uname -r 3.13.0-77-generic root@XX~# root@~# cat /etc/issue Ubuntu 14.04.4 LTS \n \l root@:~# -- 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/1124250 Title: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Status in nfs-utils package in Debian: Confirmed Status in Fedora: Unknown Bug description: [Impact] * This bug is likely to cause an incorrect UID/GID mapping for NFS shares in case of large numbers of differend UIDs/GIDs or in case of expired UID/GID mappings (stored as keys in the kernel). [Test Case] 1. Setup a nfs4 server exporting /home with a large number of different users and ldap-based authentication. 2. Mount the share on a ldap-connected client machine. 3. List the mounted /home directory. 4. Wait more than 10 minutes (the default key expiration time) and list it again with ls -l. Expected result - all directories are listed with correct UIDs/GIDs. Actual result - some of the directories may be listed with incorrect UID/GID of 4294967294. [Regression Potential] * This issue has been merged upstream in the 3.18 kernel and is also present in Debian's 3.16 kernel. [Other Info] * Original bug description: I'm running a nfs4 server exporting a directory /home (ext4,usrquota). This server is running Ubuntu 12.04 amd64(up-to-date). This directory is handling 662 homedirs for ldap authenticated users. /etc/exports is : /exports 192.168.0.0/24(rw,fsid=0,no_subtree_check) Important lines in /etc/idmapd.conf : domain=my-domain.org [Translation] Method=nsswitch. In /etc/default/nfs-common : NEED_IDMAPD=yes In /etc/default/nfs-kernel-server : RPCNFSDCOUNT=75 RPCMOUNTDOPTS=--manage-gids 2 Clients (rhel6 x86 & Ubuntu 12.04.2 i686) are mounting this nfs4 exported directory with no problems : When doing ls -l /home on this clients, I have : ... drwx-- 4 user100 oldusers 4096 sept. 21 2011 user100 drwx-- 4 user101 oldusers 4096 sept. 21 2011 user101 drwx-- 37 user102 oldusers 4096 oct. 1 19:06 user102 drwx-- 36 user103 users4096 févr. 5 21:08 user103 drwx-- 36 user104 users4096 févr. 8 14:03 user104 drwx-- 30 user105 users4096 févr. 4 18:01 user105 drwx-- 28 user106 oldusers 4096 oct. 5 2011 user106 drwx-- 37 user107 oldusers 4096 janv. 8 14:52 user107 drwx-- 31 user108 users4096 déc. 4 11:52 user108 drwx-- 4 user109 oldusers 4096 sept. 21 2011 user109 drwx--x--x 45 user110 oldusers 4096 janv. 22 15:53 user109 drwx-- 31 user111 users4096 janv. 29 12:03 user110 ... uid/gid mapping works fine, authldap works fine, ... All Clients running Ubuntu 12.10 i686 or Ubuntu 12.10 amd64 are experiencing the same problem : The config files are the same that used in ubuntu 12.04. Auth ldap is correctly configured, user can log in. This is the /etc/fstab entry for /home : 192.168.0.1:/ /home nfs rw,nfsvers=4 0 0 Important lines in /etc/idmapd.conf : domain=my-domain.org [Translation] Method=nsswitch In /etc/default/nfs-common : NEED_IDMAPD=yes /etc/nsswitch.conf is : passwd: files ldap group: files ldap shadow: files ldap When doing ls -l /home there is a strange problem : drwx-- 4 4294967294 oldusers 4096 sept. 21 2011 user100 drwx-- 4 user101oldusers 4096 sept. 21 2011 user101 drwx-- 37 user102oldusers 4096 oct. 1 19:06 user102 drwx-- 36 4294967294 users4096 févr. 5 21:08 user103 drwx-- 36 4294967294 users4096 févr. 8 14:03 user104 drwx-- 30 4294967294 users4096 févr. 4 18:01 user105 drwx-- 28 4294967294 oldusers 4096 oct. 5 2011 user106 drwx-- 37 4294967294 oldusers 4096 janv. 8 14:52 user107 drwx-- 31 4294967294 users4096 déc. 4 11:52 user108 drwx-- 4 user109oldusers 4096 sept. 21 2011 user109 drwx--x--x 45 4294967294 oldusers 4096 janv. 22 15:53 user110 drwx-- 31 4294967294 users4096 janv. 29 12:03 user111 for 571 homedirs (this number varies at each reboot)/662, the owner is the value 4294967294. For the 91 remaining homedirs, the owner is correct. The gidnumber is correctly mapped for all (only 5 differents values used for gidNumber). In /var/log/syslog, I can see : For example : user110 is mapped as 4294967294. but the command "id user110" returns : uid=31124(user110) gid=666(oldusers) groupes=666(oldusers) user110 logs in (auth ldap) from tty1. He runs "ls -l /home/user110/"
[Kernel-packages] [Bug 1481357] Re: [LTCTest][Kernel][OP810]Ubuntu14.04.3: kernel call trace while continuously switching between smt on/off and changing subcores
14.04.2 worked at some point, so what has changed ? The install failure seems unrelated to the original 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/1481357 Title: [LTCTest][Kernel][OP810]Ubuntu14.04.3: kernel call trace while continuously switching between smt on/off and changing subcores Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Bug description: == Comment: #0 - Satheesh Rajendran- 2015-07-14 02:32:22 == While running the below script, and nothing else was running in the system, host got the kernel call traces after around 15~20 mins #!/bin/bash -x while true; do for i in 1 2 4; do ppc64_cpu --subcores-per-core=$i; ppc64_cpu --info ppc64_cpu --smt=off; ppc64_cpu --info sleep 1; lscpu ppc64_cpu --smt=on; ppc64_cpu --info sleep 1; lscpu done; sleep 1; done Environment: -- $ cat /etc/issue Ubuntu 14.04.2 LTS \n \l $ uname -a Linux tul8fp 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux $ lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):160 On-line CPU(s) list: 0,4,8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,138-159 Off-line CPU(s) list: 1-3,5-7,9-11,13-15,17-19,21-23,25-27,29-31,33-35,37-39,41-43,45-47,49-51,53-55,57-59,61-63,65-67,69-71,73-75,77-79,81-83,85-87,89-91,93-95,97-99,101-103,105-107,109-111,113-115,117-119,121-123,125-127,129-131,133-135,137 Thread(s) per core:2 Core(s) per socket:10 Socket(s): 2 NUMA node(s): 2 Model: 8335-GTA L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 0,4,88,92,96,100,104,108,112,116,120,124,128,132,136,138-159 NUMA node8 CPU(s): 8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84 $ tail -10 /proc/cpuinfo processor : 159 cpu : POWER8 (raw), altivec supported clock : 2693.00MHz revision : 2.0 (pvr 004d 0200) timebase : 51200 platform : PowerNV model : 8335-GTA machine : PowerNV 8335-GTA firmware : OPAL v3 Logs:- - # dmesg [79081.074088] INFO: task irqbalance:1897 blocked for more than 120 seconds. [79081.074333] Not tainted 3.19.0-22-generic #22~14.04.1-Ubuntu [79081.074388] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [79081.074449] irqbalance D 3fff9ac39d3c 0 1897 1 0x0004 [79081.074454] Call Trace: [79081.074470] [c007e8d035f0] [3fff9af5] 0x3fff9af5 (unreliable) [79081.074477] [c007e8d037c0] [c0015934] __switch_to+0x204/0x350 [79081.074482] [c007e8d03820] [c0a11508] __schedule+0x368/0x8d0 [79081.074486] --- interrupt: 1000ba30 at 0xc007e8d039f0 [79081.074486] LR = 0x10026a6c1d0 [79081.074490] [c007e8d03a40] [c0a120a0] schedule_preempt_disabled+0x20/0x30 (unreliable) [79081.074494] [c007e8d03a60] [c0a1420c] __mutex_lock_slowpath+0xfc/0x1f0 [79081.074497] [c007e8d03ae0] [c0a1436c] mutex_lock+0x6c/0x70 [79081.074501] [c007e8d03b10] [c064488c] online_show+0x3c/0x90 [79081.074503] [c007e8d03b90] [c0644fec] dev_attr_show+0x5c/0xc0 [79081.074508] [c007e8d03bd0] [c035b7f4] sysfs_kf_seq_show+0x114/0x200 [79081.074511] [c007e8d03c20] [c03591e4] kernfs_seq_show+0x54/0x70 [79081.074515] [c007e8d03c50] [c02e74fc] seq_read+0xec/0x500 [79081.074519] [c007e8d03cf0] [c035a474] kernfs_fop_read+0x184/0x220 [79081.074523] [c007e8d03d50] [c02b520c] __vfs_read+0x6c/0x120 [79081.074527] [c007e8d03d90] [c02b5364] vfs_read+0xa4/0x1c0 [79081.074530] [c007e8d03de0] [c02b54ec] SyS_read+0x6c/0x110 [79081.074534] [c007e8d03e30] [c0009258] system_call+0x38/0xd0 [79081.074546] INFO: task ppc64_cpu:111047 blocked for more than 120 seconds. [79081.074597] Not tainted 3.19.0-22-generic #22~14.04.1-Ubuntu [79081.074802] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [79081.074865] ppc64_cpu D 3fff82892d08 0 111047 109995 0x0004 [79081.074868] Call Trace: [79081.074871] [c00f1c67f680] [c00f1c67f710] 0xc00f1c67f710 (unreliable) [79081.074875] [c00f1c67f850] [c0015934] __switch_to+0x204/0x350 [79081.074878] [c00f1c67f8b0] [c0a11508]
[Kernel-packages] [Bug 1333697] Re: ACER Aspire 5100 laptop Suspend/Resume Failure
Aaron Sosnick, in order to eliminate confusion, it will help immensely if you filed a new report (not reopen this one) with Ubuntu (not Mint) via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs. -- 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/1333697 Title: ACER Aspire 5100 laptop Suspend/Resume Failure Status in linux package in Ubuntu: Invalid Bug description: On this old laptop, Ubunutu 14.04 works fine on boot (after making sure fgrlx drivers are removed). However after a Suspend/Resume the screen flickers/tears so badly as to make the system unusable. Note that the problem does not occur with Hibernate/Resume. In fact if I can get the focus into a terminal while the screen is flickering and do a $ sudo pm_hibernate, the screen will be okay on Resume. Separately the wifi (b43) vanishes after a Resume, but I'll file a separate report on that later. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron 1959 F pulseaudio Date: Tue Jun 24 09:15:25 2014 HibernationDevice: RESUME=UUID=2e389861-74ff-4ad0-a5cc-272eef21f8d6 InstallationDate: Installed on 2014-06-21 (3 days ago) InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530 Lsusb: Bus 001 Device 002: ID 5986:0100 Acer, Inc Orbicam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer Aspire 5100 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=6990d211-9cd7-4c22-9263-2e3c11e9010a ro radeon.runpm=1 splash quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2008 dmi.bios.vendor: Acer dmi.bios.version: V3.13 dmi.board.name: Navarro dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5100:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5100 dmi.product.version: V3.13 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1333697/+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 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
** Bug watch added: Debian Bug tracker #735169 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735169 ** Also affects: os-prober (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735169 Importance: Unknown Status: Unknown -- 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/1374759 Title: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in os-prober package in Ubuntu: Confirmed Status in os-prober package in Debian: Unknown Bug description: [ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536 [ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE]. [ 556.792231] QNX4 filesystem 0.2.3 registered. [ 557.922469] EXT4-fs (sda4): unable to read superblock [ 557.925868] EXT4-fs (sda4): unable to read superblock [ 557.928967] EXT4-fs (sda4): unable to read superblock [ 557.931784] FAT-fs (sda4): bogus number of reserved sectors [ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.946740] XFS (sda4): Invalid superblock magic number [ 557.951904] FAT-fs (sda4): bogus number of reserved sectors [ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.959099] MINIX-fs: unable to read superblock [ 557.965712] attempt to access beyond end of device [ 557.965721] sda4: rw=16, want=3, limit=2 [ 557.965725] hfsplus: unable to find HFS+ superblock [ 557.968487] qnx4: no qnx4 filesystem (no root dir). [ 557.971203] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 557.974459] hfs: can't find a HFS filesystem on dev sda4 [ 564.034208] EXT4-fs (sda4): unable to read superblock [ 564.040322] EXT4-fs (sda4): unable to read superblock [ 564.043485] EXT4-fs (sda4): unable to read superblock [ 564.047076] FAT-fs (sda4): bogus number of reserved sectors [ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.059578] XFS (sda4): Invalid superblock magic number [ 564.064473] FAT-fs (sda4): bogus number of reserved sectors [ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.072080] MINIX-fs: unable to read superblock [ 564.074564] attempt to access beyond end of device [ 564.074571] sda4: rw=16, want=3, limit=2 [ 564.074576] hfsplus: unable to find HFS+ superblock [ 564.076688] qnx4: no qnx4 filesystem (no root dir). [ 564.078847] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 564.080902] hfs: can't find a HFS filesystem on dev sda4 [ 570.554296] EXT4-fs (sda4): unable to read superblock [ 570.557647] EXT4-fs (sda4): unable to read superblock [ 570.560516] EXT4-fs (sda4): unable to read superblock [ 570.563451] FAT-fs (sda4): bogus number of reserved sectors [ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.574953] XFS (sda4): Invalid superblock magic number [ 570.580796] FAT-fs (sda4): bogus number of reserved sectors [ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.588340] MINIX-fs: unable to read superblock [ 570.590983] attempt to access beyond end of device [ 570.590993] sda4: rw=16, want=3, limit=2 [ 570.590999] hfsplus: unable to find HFS+ superblock [ 570.593321] qnx4: no qnx4 filesystem (no root dir). [ 570.595556] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 570.597775] hfs: can't find a HFS filesystem on dev sda4 [ 576.795014] EXT4-fs (sda4): unable to read superblock [ 576.797554] EXT4-fs (sda4): unable to read superblock [ 576.800063] EXT4-fs (sda4): unable to read superblock [ 576.802647] FAT-fs (sda4): bogus number of reserved sectors [ 576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.813305] XFS (sda4): Invalid superblock magic number [ 576.820257] FAT-fs (sda4): bogus number of reserved sectors [ 576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.830945] MINIX-fs: unable to read superblock [ 576.834108] attempt to access beyond end of device [ 576.834119] sda4: rw=16, want=3, limit=2 [ 576.834125] hfsplus: unable to find HFS+ superblock [ 576.837264] qnx4: no qnx4
[Kernel-packages] [Bug 1548759] Re: linux-lts-trusty: 3.13.0-80.124~precise1 -proposed tracker
** Tags added: qa-testing-passed ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released -- 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/1548759 Title: linux-lts-trusty: 3.13.0-80.124~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-80.124~precise1 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 kernel-stable-Prepare-package-start:Tuesday, 23. February 2016 11:02 UTC kernel-stable-master-bug:1548519 kernel-stable-Prepare-package-end:Wednesday, 24. February 2016 01:03 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 24. February 2016 01:03 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 24. February 2016 21:03 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 24. February 2016 23:02 UTC kernel-stable-Verification-testing-start:Wednesday, 24. February 2016 23:02 UTC kernel-stable-Certification-testing-start:Wednesday, 24. February 2016 23:02 UTC kernel-stable-Security-signoff-start:Wednesday, 24. February 2016 23:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 24. February 2016 23:02 UTC kernel-stable-Security-signoff-end:Thursday, 25. February 2016 09:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1548759/+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 1551319] dagmar (amd64) - tests ran: 182, failed: 10
tests ran: 182, failed: 10; http://kernel.ubuntu.com/testing/4.4.0-9.24/dagmar__4.4.0-9.24__2016-03-01_16-14-00/results-index.html -- 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/1551319 Title: linux: 4.4.0-9.24 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-9.24 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 kernel-Prepare-package-start:Monday, 29. February 2016 16:22 UTC kernel-phase-changed:Monday, 29. February 2016 16:22 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Monday, 29. February 2016 17:01 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1551319/+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 1551854] 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/1551854 Title: LXD bootstrap issues on xenial Status in linux package in Ubuntu: Confirmed Bug description: I'm using lxd with zfs block storage on xenial, and having issues with trusty containers. I've witnessed this problem when trying to bootstrap as well as after rebooting the host and a container failed to start. In the latter case, the container that failed to start was the juju controller: c@mawhrin-skel:~/omnibus-layers$ lxc list [3/3] +-+-++--++---+ |NAME | STATE | IPV4 | IPV6 |TYPE| SNAPSHOTS | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 (eth0) | | PERSISTENT | 0 | | | | 10.0.4.1 (lxcbr0) | || | +-+-++--++---+ I manually started it, but found that no upstart services were started. Remembering this thread, https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I checked /var/log/mountall.log in the machine-0 container, and sure enough: root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat /var/log/upstart/mountall.log mount: permission denied mountall: mount /sys/kernel/debug [187] terminated with status 32 mountall: Filesystem could not be mounted: /sys/kernel/debug The problem persists if I stop and start the container. If I remount /sys/kernel/debug on the host, then stop and start the container, upstart succeeds and the juju controller starts up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-8-generic 4.4.0-8.23 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: c 24562 F pulseaudio CurrentDesktop: MATE Date: Tue Mar 1 10:52:45 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=007cedda-f922-4e4c-89b1-57b31f18292e InstallationDate: Installed on 2016-02-28 (2 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1551870] [NEW] snd_au8820 0000:01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024
Public bug reported: Occurred right after login, several very similar bug alerts happened, this report is about one of them. pos = 16384 pos = 16386 pos = 16388 ... ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-8-generic 4.4.0-8.23 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic i686 NonfreeKernelModules: nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olle 2146 F pulseaudio /dev/snd/controlC1: olle 2146 F pulseaudio Date: Tue Mar 1 09:44:40 2016 Failure: oops HibernationDevice: RESUME=UUID=03bed9e9-e39b-4107-8cd6-c2612af9a6aa InstallationDate: Installed on 2016-02-28 (1 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160226) MachineType: Hewlett-Packard HP xw8400 Workstation OopsText: snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024 VBoxNetFlt: attached to 'enp31s0' / 00:1a:4b:54:34:1c device enp31s0 entered promiscuous mode ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=2160f8ed-4aa3-4243-b5d6-f87c1967e253 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9 RfKill: SourcePackage: linux Title: snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786D5 v02.37 dmi.board.name: 0A08h dmi.board.vendor: Hewlett-Packard dmi.board.version: NA dmi.chassis.asset.tag: CZC722497N dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786D5v02.37:bd07/09/2009:svnHewlett-Packard:pnHPxw8400Workstation:pvr:rvnHewlett-Packard:rn0A08h:rvrNA:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP xw8400 Workstation dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 kernel-oops xenial -- 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/1551870 Title: snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024 Status in linux package in Ubuntu: New Bug description: Occurred right after login, several very similar bug alerts happened, this report is about one of them. pos = 16384 pos = 16386 pos = 16388 ... ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-8-generic 4.4.0-8.23 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic i686 NonfreeKernelModules: nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olle 2146 F pulseaudio /dev/snd/controlC1: olle 2146 F pulseaudio Date: Tue Mar 1 09:44:40 2016 Failure: oops HibernationDevice: RESUME=UUID=03bed9e9-e39b-4107-8cd6-c2612af9a6aa InstallationDate: Installed on 2016-02-28 (1 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160226) MachineType: Hewlett-Packard HP xw8400 Workstation OopsText: snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024 VBoxNetFlt: attached to 'enp31s0' / 00:1a:4b:54:34:1c device enp31s0 entered promiscuous mode ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=2160f8ed-4aa3-4243-b5d6-f87c1967e253 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9 RfKill: SourcePackage: linux Title: snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786D5 v02.37 dmi.board.name: 0A08h dmi.board.vendor: Hewlett-Packard dmi.board.version: NA dmi.chassis.asset.tag: CZC722497N dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786D5v02.37:bd07/09/2009:svnHewlett-Packard:pnHPxw8400Workstation:pvr:rvnHewlett-Packard:rn0A08h:rvrNA:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP xw8400 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to:
[Kernel-packages] [Bug 1551319] dwalin (amd64) - tests ran: 66, failed: 0
tests ran: 66, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-9.24/dwalin__4.4.0-9.24__2016-03-01_17-09-00/results-index.html -- 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/1551319 Title: linux: 4.4.0-9.24 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-9.24 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 kernel-Prepare-package-start:Monday, 29. February 2016 16:22 UTC kernel-phase-changed:Monday, 29. February 2016 16:22 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Monday, 29. February 2016 17:01 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1551319/+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 1551319] fozzie (amd64) - tests ran: 182, failed: 10
tests ran: 182, failed: 10; http://kernel.ubuntu.com/testing/4.4.0-9.24/fozzie__4.4.0-9.24__2016-03-01_16-13-00/results-index.html -- 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/1551319 Title: linux: 4.4.0-9.24 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-9.24 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 kernel-Prepare-package-start:Monday, 29. February 2016 16:22 UTC kernel-phase-changed:Monday, 29. February 2016 16:22 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Monday, 29. February 2016 17:01 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1551319/+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 1551854] Re: LXD bootstrap issues on xenial
marking confirmed because two people have reported it, but I cannot reproduce it yet. -- 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/1551854 Title: LXD bootstrap issues on xenial Status in linux package in Ubuntu: Confirmed Bug description: I'm using lxd with zfs block storage on xenial, and having issues with trusty containers. I've witnessed this problem when trying to bootstrap as well as after rebooting the host and a container failed to start. In the latter case, the container that failed to start was the juju controller: c@mawhrin-skel:~/omnibus-layers$ lxc list [3/3] +-+-++--++---+ |NAME | STATE | IPV4 | IPV6 |TYPE| SNAPSHOTS | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 (eth0) | | PERSISTENT | 0 | | | | 10.0.4.1 (lxcbr0) | || | +-+-++--++---+ I manually started it, but found that no upstart services were started. Remembering this thread, https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I checked /var/log/mountall.log in the machine-0 container, and sure enough: root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat /var/log/upstart/mountall.log mount: permission denied mountall: mount /sys/kernel/debug [187] terminated with status 32 mountall: Filesystem could not be mounted: /sys/kernel/debug The problem persists if I stop and start the container. If I remount /sys/kernel/debug on the host, then stop and start the container, upstart succeeds and the juju controller starts up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-8-generic 4.4.0-8.23 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: c 24562 F pulseaudio CurrentDesktop: MATE Date: Tue Mar 1 10:52:45 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=007cedda-f922-4e4c-89b1-57b31f18292e InstallationDate: Installed on 2016-02-28 (2 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1551854] Re: LXD bootstrap issues on xenial
I'm on the same kernel Linux sl 4.4.0-8-generic #23-Ubuntu SMP Wed Feb 24 20:45:30 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux and also have the tracefs mounted 0 ✓ serge@sl ~ $ grep debug /proc/self/mountinfo 74 19 0:7 / /sys/kernel/debug rw,relatime shared:26 - debugfs debugfs rw 44 74 0:9 / /sys/kernel/debug/tracing rw,relatime shared:29 - tracefs tracefs rw but trusty (upstart-based) containers start fine for me, using lxc version 2.0.0~rc4+master~20160229-0647-0ubuntu1~xenial and lxd from git HEAD. Very odd therefore that unmounting and re-mounting debugfs works for you... Will try in a fresh vm. -- 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/1551854 Title: LXD bootstrap issues on xenial Status in linux package in Ubuntu: Confirmed Bug description: I'm using lxd with zfs block storage on xenial, and having issues with trusty containers. I've witnessed this problem when trying to bootstrap as well as after rebooting the host and a container failed to start. In the latter case, the container that failed to start was the juju controller: c@mawhrin-skel:~/omnibus-layers$ lxc list [3/3] +-+-++--++---+ |NAME | STATE | IPV4 | IPV6 |TYPE| SNAPSHOTS | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 (eth0) | | PERSISTENT | 0 | | | | 10.0.4.1 (lxcbr0) | || | +-+-++--++---+ I manually started it, but found that no upstart services were started. Remembering this thread, https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I checked /var/log/mountall.log in the machine-0 container, and sure enough: root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat /var/log/upstart/mountall.log mount: permission denied mountall: mount /sys/kernel/debug [187] terminated with status 32 mountall: Filesystem could not be mounted: /sys/kernel/debug The problem persists if I stop and start the container. If I remount /sys/kernel/debug on the host, then stop and start the container, upstart succeeds and the juju controller starts up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-8-generic 4.4.0-8.23 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion:
[Kernel-packages] [Bug 1550591] Re: linux-lts-vivid: 3.19.0-53.59~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1550591 Title: linux-lts-vivid: 3.19.0-53.59~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.19.0-53.59~14.04.1 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 kernel-stable-Prepare-package-start:Saturday, 27. February 2016 00:30 UTC kernel-stable-master-bug:1550576 kernel-stable-Prepare-package-end:Saturday, 27. February 2016 10:02 UTC kernel-stable-Promote-to-proposed-start:Saturday, 27. February 2016 10:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 01. March 2016 09:02 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Tuesday, 01. March 2016 11:02 UTC kernel-stable-Verification-testing-start:Tuesday, 01. March 2016 11:02 UTC kernel-stable-Certification-testing-start:Tuesday, 01. March 2016 11:02 UTC kernel-stable-Security-signoff-start:Tuesday, 01. March 2016 11:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 01. March 2016 11:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1550591/+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 1551787] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1551787 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/1551787 Title: Ubuntu crashed after Laptop is collapsed Status in linux package in Ubuntu: Incomplete Bug description: After I collapsed the laptop, disconnected a monitor and took the laptop to another place with a docking station and monitor, Ubuntu 15.10 was not restartable again. It is a Thinkpad T440s. It was possible to change keyboard lights via Fn + Space, but it was not possible to restart the laptop by hitting any button or by hitting the power button. I only could hit the power button for some seconds, so Ubuntu could restart. I have no clue what package caused this. kern.log contains: Mar 1 15:15:22 reichelt-ThinkPad-T440s kernel: [ 26.919927] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Mar 1 15:15:23 reichelt-ThinkPad-T440s kernel: [ 27.499806] Bluetooth: RFCOMM TTY layer initialized Mar 1 15:15:23 reichelt-ThinkPad-T440s kernel: [ 27.499813] Bluetooth: RFCOMM socket layer initialized Mar 1 15:15:23 reichelt-ThinkPad-T440s kernel: [ 27.499818] Bluetooth: RFCOMM ver 1.11 Mar 1 15:15:25 reichelt-ThinkPad-T440s kernel: [ 29.953253] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Mar 1 15:15:30 reichelt-ThinkPad-T440s kernel: [ 34.605776] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Mar 1 15:15:31 reichelt-ThinkPad-T440s gnome-session[1927]: Entering running state Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.577783] wlan0: authenticate with 0c:85:25:68:72:eb Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.584251] wlan0: send auth to 0c:85:25:68:72:eb (try 1/3) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.660589] wlan0: authenticated Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.661279] wlan0: associate with 0c:85:25:68:72:eb (try 1/3) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.667460] wlan0: RX AssocResp from 0c:85:25:68:72:eb (capab=0x11 status=0 aid=10) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.670657] wlan0: associated Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.670693] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673874] cfg80211: Regulatory domain changed to country: DE Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673877] cfg80211: DFS Master region: ETSI Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673878] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673880] cfg80211: (240 KHz - 2483500 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673881] cfg80211: (515 KHz - 525 KHz @ 8 KHz, 20 KHz AUTO), (N/A, 2000 mBm), (N/A) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673883] cfg80211: (525 KHz - 535 KHz @ 8 KHz, 20 KHz AUTO), (N/A, 2000 mBm), (0 s) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673884] cfg80211: (547 KHz - 5725000 KHz @ 16 KHz), (N/A, 2698 mBm), (0 s) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673885] cfg80211: (5700 KHz - 6600 KHz @ 216 KHz), (N/A, 4000 mBm), (N/A) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.764423] wlan0: Limiting TX power to 17 dBm as advertised by 0c:85:25:68:72:eb Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 162.965399] usb 1-3: new low-speed USB device number 5 using xhci_hcd Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.097082] usb 1-3: New USB device found, idVendor=03f0, idProduct=094a Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.097090] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.097094] usb 1-3: Product: HP USB Optical Mouse Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.097097] usb 1-3: Manufacturer: PixArt Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.098197] usb 1-3: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.130256] hidraw: raw HID events driver (C) Jiri Kosina Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.135844]
[Kernel-packages] [Bug 1333697] Re: ACER Aspire 5100 laptop Suspend/Resume Failure
This problem happens with or without Mint packages. It is an Ubuntu problem and you are not nice for suggesting otherwise. Please mark "won't fix" not invalid if that's your attitude. I'll give some more recent Ubuntu versions a chance when I can and reopen if it hasn't been fixed. -- 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/1333697 Title: ACER Aspire 5100 laptop Suspend/Resume Failure Status in linux package in Ubuntu: Invalid Bug description: On this old laptop, Ubunutu 14.04 works fine on boot (after making sure fgrlx drivers are removed). However after a Suspend/Resume the screen flickers/tears so badly as to make the system unusable. Note that the problem does not occur with Hibernate/Resume. In fact if I can get the focus into a terminal while the screen is flickering and do a $ sudo pm_hibernate, the screen will be okay on Resume. Separately the wifi (b43) vanishes after a Resume, but I'll file a separate report on that later. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron 1959 F pulseaudio Date: Tue Jun 24 09:15:25 2014 HibernationDevice: RESUME=UUID=2e389861-74ff-4ad0-a5cc-272eef21f8d6 InstallationDate: Installed on 2014-06-21 (3 days ago) InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530 Lsusb: Bus 001 Device 002: ID 5986:0100 Acer, Inc Orbicam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer Aspire 5100 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=6990d211-9cd7-4c22-9263-2e3c11e9010a ro radeon.runpm=1 splash quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2008 dmi.bios.vendor: Acer dmi.bios.version: V3.13 dmi.board.name: Navarro dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5100:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5100 dmi.product.version: V3.13 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1333697/+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 1551854] Re: LXD bootstrap issues on xenial
I also confirmed that the mountall error message was duplicated every time I restarted the machine-0 container -- until remounting on the host. -- 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/1551854 Title: LXD bootstrap issues on xenial Status in linux package in Ubuntu: New Bug description: I'm using lxd with zfs block storage on xenial, and having issues with trusty containers. I've witnessed this problem when trying to bootstrap as well as after rebooting the host and a container failed to start. In the latter case, the container that failed to start was the juju controller: c@mawhrin-skel:~/omnibus-layers$ lxc list [3/3] +-+-++--++---+ |NAME | STATE | IPV4 | IPV6 |TYPE| SNAPSHOTS | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 (eth0) | | PERSISTENT | 0 | | | | 10.0.4.1 (lxcbr0) | || | +-+-++--++---+ I manually started it, but found that no upstart services were started. Remembering this thread, https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I checked /var/log/mountall.log in the machine-0 container, and sure enough: root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat /var/log/upstart/mountall.log mount: permission denied mountall: mount /sys/kernel/debug [187] terminated with status 32 mountall: Filesystem could not be mounted: /sys/kernel/debug The problem persists if I stop and start the container. If I remount /sys/kernel/debug on the host, then stop and start the container, upstart succeeds and the juju controller starts up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-8-generic 4.4.0-8.23 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: c 24562 F pulseaudio CurrentDesktop: MATE Date: Tue Mar 1 10:52:45 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=007cedda-f922-4e4c-89b1-57b31f18292e InstallationDate: Installed on 2016-02-28 (2 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) MachineType: LENOVO 2306CTO ProcFB: 0
[Kernel-packages] [Bug 1551787] Re: Ubuntu crashed after Laptop is collapsed
** 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/1551787 Title: Ubuntu crashed after Laptop is collapsed Status in linux package in Ubuntu: New Bug description: After I collapsed the laptop, disconnected a monitor and took the laptop to another place with a docking station and monitor, Ubuntu 15.10 was not restartable again. It is a Thinkpad T440s. It was possible to change keyboard lights via Fn + Space, but it was not possible to restart the laptop by hitting any button or by hitting the power button. I only could hit the power button for some seconds, so Ubuntu could restart. I have no clue what package caused this. kern.log contains: Mar 1 15:15:22 reichelt-ThinkPad-T440s kernel: [ 26.919927] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Mar 1 15:15:23 reichelt-ThinkPad-T440s kernel: [ 27.499806] Bluetooth: RFCOMM TTY layer initialized Mar 1 15:15:23 reichelt-ThinkPad-T440s kernel: [ 27.499813] Bluetooth: RFCOMM socket layer initialized Mar 1 15:15:23 reichelt-ThinkPad-T440s kernel: [ 27.499818] Bluetooth: RFCOMM ver 1.11 Mar 1 15:15:25 reichelt-ThinkPad-T440s kernel: [ 29.953253] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Mar 1 15:15:30 reichelt-ThinkPad-T440s kernel: [ 34.605776] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Mar 1 15:15:31 reichelt-ThinkPad-T440s gnome-session[1927]: Entering running state Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.577783] wlan0: authenticate with 0c:85:25:68:72:eb Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.584251] wlan0: send auth to 0c:85:25:68:72:eb (try 1/3) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.660589] wlan0: authenticated Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.661279] wlan0: associate with 0c:85:25:68:72:eb (try 1/3) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.667460] wlan0: RX AssocResp from 0c:85:25:68:72:eb (capab=0x11 status=0 aid=10) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.670657] wlan0: associated Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.670693] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673874] cfg80211: Regulatory domain changed to country: DE Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673877] cfg80211: DFS Master region: ETSI Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673878] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673880] cfg80211: (240 KHz - 2483500 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673881] cfg80211: (515 KHz - 525 KHz @ 8 KHz, 20 KHz AUTO), (N/A, 2000 mBm), (N/A) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673883] cfg80211: (525 KHz - 535 KHz @ 8 KHz, 20 KHz AUTO), (N/A, 2000 mBm), (0 s) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673884] cfg80211: (547 KHz - 5725000 KHz @ 16 KHz), (N/A, 2698 mBm), (0 s) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.673885] cfg80211: (5700 KHz - 6600 KHz @ 216 KHz), (N/A, 4000 mBm), (N/A) Mar 1 15:15:33 reichelt-ThinkPad-T440s kernel: [ 37.764423] wlan0: Limiting TX power to 17 dBm as advertised by 0c:85:25:68:72:eb Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 162.965399] usb 1-3: new low-speed USB device number 5 using xhci_hcd Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.097082] usb 1-3: New USB device found, idVendor=03f0, idProduct=094a Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.097090] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.097094] usb 1-3: Product: HP USB Optical Mouse Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.097097] usb 1-3: Manufacturer: PixArt Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.098197] usb 1-3: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.130256] hidraw: raw HID events driver (C) Jiri Kosina Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.135844] usbcore: registered new interface driver usbhid Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.135847] usbhid: USB HID core driver Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.138802] input: PixArt HP USB Optical Mouse as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:03F0:094A.0001/input/input17 Mar 1 15:17:38 reichelt-ThinkPad-T440s kernel: [ 163.193472] hid-generic 0003:03F0:094A.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt HP
[Kernel-packages] [Bug 1534144] Re: [Ubuntu 16.04] CORSA CAPI enabling in PowerVM LPARs
--- Comment From bren...@br.ibm.com 2016-03-01 11:35 EDT--- Deferring this feature to Ubuntu 16.10 ** Tags removed: targetmilestone-inin1604 ** Tags added: targetmilestone-inin1610 -- 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/1534144 Title: [Ubuntu 16.04] CORSA CAPI enabling in PowerVM LPARs Status in linux package in Ubuntu: Incomplete Bug description: Support Corsa CAPI in Ubuntu 16.04 in a PowerVM LPAR. This is a set of kernel patches for CORSA device driver. Firmware: 840 FW update == Comment: #4 - Frederic Barrat- 2016-01-13 14:18:06 == We are still working on developing this feature and are about to submit patches upstream for review. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1534144/+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 1371262] Re: kernel try to mount partition with unknown filesystem
*** This bug is a duplicate of bug 1374759 *** https://bugs.launchpad.net/bugs/1374759 ** This bug has been marked a duplicate of bug 1374759 >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old -- 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/1371262 Title: kernel try to mount partition with unknown filesystem Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have got syslog error that kernel is trying to mount partition with unknown file system: Sep 18 01:03:39 ARIVUBU os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sde1 Sep 18 01:03:39 ARIVUBU kernel: [ 1149.585226] EXT4-fs (sde1): VFS: Can't find ext4 filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.586163] EXT4-fs (sde1): VFS: Can't find ext4 filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.587100] EXT4-fs (sde1): VFS: Can't find ext4 filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.588039] FAT-fs (sde1): invalid media value (0xb5) Sep 18 01:03:39 ARIVUBU kernel: [ 1149.588041] FAT-fs (sde1): Can't find a valid FAT filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.621168] XFS (sde1): Invalid superblock magic number Sep 18 01:03:39 ARIVUBU kernel: [ 1149.628618] FAT-fs (sde1): invalid media value (0xb5) Sep 18 01:03:39 ARIVUBU kernel: [ 1149.628620] FAT-fs (sde1): Can't find a valid FAT filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.631463] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sde1. Sep 18 01:03:39 ARIVUBU kernel: [ 1149.634430] hfsplus: unable to find HFS+ superblock Sep 18 01:03:39 ARIVUBU kernel: [ 1149.635388] qnx4: no qnx4 filesystem (no root dir). Sep 18 01:03:39 ARIVUBU kernel: [ 1149.636181] You didn't specify the type of your ufs filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.636181] Sep 18 01:03:39 ARIVUBU kernel: [ 1149.636181] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... Sep 18 01:03:39 ARIVUBU kernel: [ 1149.636181] Sep 18 01:03:39 ARIVUBU kernel: [ 1149.636181] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old Sep 18 01:03:39 ARIVUBU kernel: [ 1149.636349] ufs_read_super: bad magic number Sep 18 01:03:39 ARIVUBU kernel: [ 1149.637321] hfs: can't find a HFS filesystem on dev sde1 Sep 18 01:03:39 ARIVUBU os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sdf1 Sep 18 01:03:39 ARIVUBU kernel: [ 1149.784640] EXT4-fs (sdf1): VFS: Can't find ext4 filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.785889] EXT4-fs (sdf1): VFS: Can't find ext4 filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.787125] EXT4-fs (sdf1): VFS: Can't find ext4 filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.788280] FAT-fs (sdf1): invalid media value (0x7d) Sep 18 01:03:39 ARIVUBU kernel: [ 1149.788283] FAT-fs (sdf1): Can't find a valid FAT filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.793998] XFS (sdf1): Invalid superblock magic number Sep 18 01:03:39 ARIVUBU kernel: [ 1149.797373] FAT-fs (sdf1): invalid media value (0x7d) Sep 18 01:03:39 ARIVUBU kernel: [ 1149.797375] FAT-fs (sdf1): Can't find a valid FAT filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.801157] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sdf1. Sep 18 01:03:39 ARIVUBU kernel: [ 1149.802872] hfsplus: unable to find HFS+ superblock Sep 18 01:03:39 ARIVUBU kernel: [ 1149.804030] qnx4: no qnx4 filesystem (no root dir). Sep 18 01:03:39 ARIVUBU kernel: [ 1149.804847] You didn't specify the type of your ufs filesystem Sep 18 01:03:39 ARIVUBU kernel: [ 1149.804847] Sep 18 01:03:39 ARIVUBU kernel: [ 1149.804847] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... Sep 18 01:03:39 ARIVUBU kernel: [ 1149.804847] Sep 18 01:03:39 ARIVUBU kernel: [ 1149.804847] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old Sep 18 01:03:39 ARIVUBU kernel: [ 1149.805620] ufs_read_super: bad magic number Sep 18 01:03:39 ARIVUBU kernel: [ 1149.807247] hfs: can't find a HFS filesystem on dev sdf1 The first case: "/dev/sde1" Partition is marked as bios-grub and should not be trying to be mounted by kernel. The second case " /dev/sdf1" is used by truecrypt application . Kernel should not be trying to mount it. uname -a Linux ARIVUBU 3.16.0-14-lowlatency #20-Ubuntu SMP PREEMPT Sun Sep 7 00:05:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy linux-image-3.16.0-14-lowlatency linux-image-3.16.0-14-lowlatency: Installed: 3.16.0-14.20 Candidate: 3.16.0-14.20 Version table: *** 3.16.0-14.20 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status Thank You, Kind Regards, Martin P.S. Is it possible to tell to
[Kernel-packages] [Bug 1551854] [NEW] LXD bootstrap issues on xenial
Public bug reported: I'm using lxd with zfs block storage on xenial, and having issues with trusty containers. I've witnessed this problem when trying to bootstrap as well as after rebooting the host and a container failed to start. In the latter case, the container that failed to start was the juju controller: c@mawhrin-skel:~/omnibus-layers$ lxc list [3/3] +-+-++--++---+ |NAME | STATE | IPV4 | IPV6 |TYPE| SNAPSHOTS | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 (eth0) | | PERSISTENT | 0 | +-+-++--++---+ | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 (eth0) | | PERSISTENT | 0 | | | | 10.0.4.1 (lxcbr0) | || | +-+-++--++---+ I manually started it, but found that no upstart services were started. Remembering this thread, https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I checked /var/log/mountall.log in the machine-0 container, and sure enough: root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat /var/log/upstart/mountall.log mount: permission denied mountall: mount /sys/kernel/debug [187] terminated with status 32 mountall: Filesystem could not be mounted: /sys/kernel/debug The problem persists if I stop and start the container. If I remount /sys/kernel/debug on the host, then stop and start the container, upstart succeeds and the juju controller starts up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-8-generic 4.4.0-8.23 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: c 24562 F pulseaudio CurrentDesktop: MATE Date: Tue Mar 1 10:52:45 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=007cedda-f922-4e4c-89b1-57b31f18292e InstallationDate: Installed on 2016-02-28 (2 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-8-generic.efi.signed root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-8-generic N/A linux-backports-modules-4.4.0-8-generic N/A linux-firmware 1.156 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2014