[Kernel-packages] [Bug 1636719] [NEW] Asus X556U touchpad recognized as a mouse on ubuntu 16.04
Public bug reported: Hello, Asus X556U the touch pad is recognized as a PS/2 mouse, so so touchpad options or features. Also the sensitivity is horrible, causing the click to activate constantly when typing. Bug report using guidelines on: https://wiki.ubuntu.com/DebuggingTouchpadDetection uname -a Linux adnanasus 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux adnan@adnanasus:~$ cat xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ FTE1001:00 0B05:0101 id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Button id=8[slave keyboard (3)] ↳ USB Cameraid=11 [slave keyboard (3)] ↳ Asus WMI hotkeys id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] adnan@adnanasus:~$ cat devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=046d Product=c52f Version=0111 N: Name="Logitech USB Receiver" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C52F.0001/input/input5 U: Uniq= H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=143 B: MSC=10 I: Bus=0003 Vendor=046d Product=c52f Version=0111 N: Name="Logitech USB Receiver" P: Phys=usb-:00:14.0-1/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C52F.0002/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=1f B: KEY=3007f 0 0 48317aff32d bf56 1 130f938b17c000 677bfad9415fed 9ed6804400 1002 B: REL=40 B: ABS=1 B: MSC=10 I: Bus=0003 Vendor=0bda Product=57b5 Version=0012 N: Name="USB Camera" P: Phys=usb-:00:14.0-6/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0019 Vendor= Product= Version= N: Name="Asus WMI hotkeys" P: Phys=asus-nb-wmi/input0 S: Sysfs=/devices/platform/asus-nb-wmi/input/input12 U: Uniq= H: Handlers=rfkill kbd event12 B: PROP=0 B: EV=100013 B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0 B: MSC=10 I: Bus=0018 Vendor=0b05 Product=0101 Version=0100 N: Name="FTE1001:00 0B05:0101" P:
[Kernel-packages] [Bug 1636719] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1636719 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/1636719 Title: Asus X556U touchpad recognized as a mouse on ubuntu 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Hello, Asus X556U the touch pad is recognized as a PS/2 mouse, so so touchpad options or features. Also the sensitivity is horrible, causing the click to activate constantly when typing. Bug report using guidelines on: https://wiki.ubuntu.com/DebuggingTouchpadDetection uname -a Linux adnanasus 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux adnan@adnanasus:~$ cat xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ FTE1001:00 0B05:0101 id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Button id=8[slave keyboard (3)] ↳ USB Cameraid=11 [slave keyboard (3)] ↳ Asus WMI hotkeys id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] adnan@adnanasus:~$ cat devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=046d Product=c52f Version=0111 N: Name="Logitech USB Receiver" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C52F.0001/input/input5 U: Uniq= H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=143 B: MSC=10 I: Bus=0003 Vendor=046d Product=c52f Version=0111 N: Name="Logitech USB Receiver" P: Phys=usb-:00:14.0-1/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C52F.0002/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=1f B: KEY=3007f 0 0 48317aff32d bf56 1 130f938b17c000 677bfad9415fed 9ed6804400 1002 B: REL=40 B: ABS=1 B: MSC=10 I: Bus=0003 Vendor=0bda Product=57b5 Version=0012 N: Name="USB Camera" P: Phys=usb-:00:14.0-6/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Versi
[Kernel-packages] [Bug 1636719] Re: Asus X556U touchpad recognized as a mouse on ubuntu 16.04
*** This bug is a duplicate of bug 1620811 *** https://bugs.launchpad.net/bugs/1620811 ** This bug has been marked a duplicate of bug 1620811 [Asus K501UW] FTE1001 touchpad detected as mouse -- 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/1636719 Title: Asus X556U touchpad recognized as a mouse on ubuntu 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Hello, Asus X556U the touch pad is recognized as a PS/2 mouse, so so touchpad options or features. Also the sensitivity is horrible, causing the click to activate constantly when typing. Bug report using guidelines on: https://wiki.ubuntu.com/DebuggingTouchpadDetection uname -a Linux adnanasus 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux adnan@adnanasus:~$ cat xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ FTE1001:00 0B05:0101 id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Button id=8[slave keyboard (3)] ↳ USB Cameraid=11 [slave keyboard (3)] ↳ Asus WMI hotkeys id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] adnan@adnanasus:~$ cat devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=046d Product=c52f Version=0111 N: Name="Logitech USB Receiver" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C52F.0001/input/input5 U: Uniq= H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=143 B: MSC=10 I: Bus=0003 Vendor=046d Product=c52f Version=0111 N: Name="Logitech USB Receiver" P: Phys=usb-:00:14.0-1/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C52F.0002/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=1f B: KEY=3007f 0 0 48317aff32d bf56 1 130f938b17c000 677bfad9415fed 9ed6804400 1002 B: REL=40 B: ABS=1 B: MSC=10 I: Bus=0003 Vendor=0bda Product=57b5 Version=0012 N: Name="USB Camera" P: Phys=usb-:00:14.0-6/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/de
[Kernel-packages] [Bug 1635437] Re: linux-lts-trusty: 3.13.0-101.148~precise1 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/precise/3.13.0-101.148~precise1/precise-3.13-proposed- frozen.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => 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/1635437 Title: linux-lts-trusty: 3.13.0-101.148~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: Fix Released 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: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the 3.13.0-101.148~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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1635430 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635437/+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 1636541] Re: linux-armadaxp: 3.2.0-1677.104 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) => Ike Panhc (ikepanhc) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the 3.2.0-1677.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 -- swm properties -- derivative-trackers-created: true kernel-stable-master-bug: 1636537 phase: Uploaded + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Wednesday, 26. October 2016 07:47 UTC ** Description changed: This bug is for tracking the 3.2.0-1677.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 -- swm properties -- + boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1636537 phase: Uploaded - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Wednesday, 26. October 2016 07:47 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1636541 Title: linux-armadaxp: 3.2.0-1677.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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1677.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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1636537 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1636541/+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 1635428] onza (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-78.101~14.04.1/onza__3.16.0-78.101~14.04.1__2016-10-26_07-43-00/results-index.html -- 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/1635428 Title: linux-lts-vivid: 3.19.0-74.82~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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed 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-74.82~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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1635424 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635428/+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 1636656] Re: [Hyper-V] netvsc: fix incorrect receive checksum offloading
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1636656 Title: [Hyper-V] netvsc: fix incorrect receive checksum offloading Status in linux package in Ubuntu: Confirmed Bug description: The Hyper-V netvsc driver was looking at the incorrect status bits in the checksum info. It was setting the receive checksum unnecessary flag based on the IP header checksum being correct. The checksum flag is skb is about TCP and UDP checksum status. Because of this bug, any packet received with bad TCP checksum would be passed up the stack and to the application causing data corruption. The problem is reproducible via netcat and netem. This had a side effect of not doing receive checksum offload on IPv6. The driver was also also always doing checksum offload independent of the checksum setting done via ethtool. Signed-off-by: Stephen Hemminger https://patchwork.ozlabs.org/patch/685660/ When this patch is committed I will include the commit ID in this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636656/+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 1635428] onza (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-78.101~14.04.1/onza__3.16.0-78.101~14.04.1__2016-10-26_08-09-00/results-index.html -- 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/1635428 Title: linux-lts-vivid: 3.19.0-74.82~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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed 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-74.82~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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1635424 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635428/+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 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
I've the same or similar issue with 16.04, When i turn on my Headset and connect via Bluetooth, it starts with different Profiles depending on the previous status: If I've previously used A2DP it will starts with off If I've used HSP or switched back to it before turning the headset off, it starts with HSP Workaround: If It starts with Off, i can't select A2DP it always jumps back, but if I select HSP manually, turn the Headset off and on again it will now start with Profile HSP and I'm now able to select A2DP, if I switch back to the HSP Profile, before turning my Headset off / disconnecting it, it will also work the next start, if I stay on the A2DP Profile before turning off / disconnecting, I've to redo the Workaround steps from beginning. It looks like the driver (or whatever) can't handle to start with A2DP Profile. It was really painfull until I've read about the workaround in another forum, it is still annoying but at least i don't need to restart any services or make a reboot -- 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/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+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 1635242] s2lp6g001 (s390x.zKVM) - tests ran: 10, failed: 1
tests ran: 10, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-46.67/s2lp6g001__4.4.0-46.67__2016-10-26_08-37-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/1635242 Title: linux: 4.4.0-46.67 -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: In Progress 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-46.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635242/+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 1634892] Re: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error
It worked for me too. -- 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/1634892 Title: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on the 3.13.0-96-generic kernel and below worked fine using the following: $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128 128 As of 3.13.0-97-generic, though, it no longer works as expected: $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128 error: "Invalid argument" setting key "net.ipv4.neigh.default.gc_thresh1" There are two potentially related revisions in the -97 release - http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts- backport-trusty&id=563cf19389d8e999e69d6c94995966aeaf7c3a08 and http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts- backport-trusty&id=7b82096b0ebc9bf487b390fe970d66ffa5a5774e. The expected behavior is that changing neighbor table settings works using 'sysctl -w' with the same values as before the -97 kernel. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-98-generic 3.13.0-98.145~precise1 ProcVersionSignature: Ubuntu 3.13.0-98.145~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-98-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-98-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory CurrentDmesg: [4.586115] NET: Registered protocol family 40 Date: Wed Oct 19 06:13:36 2016 HibernationDevice: RESUME=UUID=d32abfeb-623f-4c11-ae4a-a7babe8c2139 InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140806.1) IwConfig: Error: [Errno 2] No such file or directory MachineType: VMware, Inc. VMware Virtual Platform MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic root=UUID=febea164-78c3-4d3a-a0ce-0f09990df608 ro find_preseed=/preseed.cfg noprompt quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-98-generic N/A linux-backports-modules-3.13.0-98-generic N/A linux-firmware 1.79.16 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634892/+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 1636751] [NEW] Bluetooth
Public bug reported: IDK ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trobsh 3863 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 26 12:18:40 2016 HibernationDevice: RESUME=UUID=190a1533-ad6e-4aa7-a2b3-1717390d6d3f InstallationDate: Installed on 2014-06-02 (876 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. X502CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=207dc037-478e-42ac-a064-df62c28a3464 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X502CA.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X502CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX502CA.209:bd06/09/2013:svnASUSTeKCOMPUTERINC.:pnX502CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX502CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X502CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER 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/1636751 Title: Bluetooth Status in linux package in Ubuntu: Confirmed Bug description: IDK ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trobsh 3863 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 26 12:18:40 2016 HibernationDevice: RESUME=UUID=190a1533-ad6e-4aa7-a2b3-1717390d6d3f InstallationDate: Installed on 2014-06-02 (876 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. X502CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=207dc037-478e-42ac-a064-df62c28a3464 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X502CA.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X502CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX502CA.209:bd06/09/2013:svnASUSTeKCOMPUTERINC.:pnX502CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX502CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X502CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636751/+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 1636751] 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/1636751 Title: Bluetooth Status in linux package in Ubuntu: Confirmed Bug description: IDK ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trobsh 3863 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 26 12:18:40 2016 HibernationDevice: RESUME=UUID=190a1533-ad6e-4aa7-a2b3-1717390d6d3f InstallationDate: Installed on 2014-06-02 (876 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. X502CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=207dc037-478e-42ac-a064-df62c28a3464 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X502CA.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X502CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX502CA.209:bd06/09/2013:svnASUSTeKCOMPUTERINC.:pnX502CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX502CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X502CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636751/+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 1635242] s2lp6g001 (s390x.zKVM) - tests ran: 33, failed: 0
tests ran: 33, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-46.67/s2lp6g001__4.4.0-46.67__2016-10-26_09-04-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/1635242 Title: linux: 4.4.0-46.67 -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: In Progress 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-46.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635242/+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 1635428] modoc (ppc64el) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-78.101~14.04.1/modoc__3.16.0-78.101~14.04.1__2016-10-26_09-54-00/results-index.html -- 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/1635428 Title: linux-lts-vivid: 3.19.0-74.82~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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed 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-74.82~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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1635424 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635428/+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 1611081] Re: [HP Pavilion x2 - 12-b003nf (ENERGY STAR)] Synaptics touchpad not configured by HID RMI
Hi! I also tried kernels up to 4.8.4 but without any improvement. Do I still need to apply this patch manually? -- 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/1611081 Title: [HP Pavilion x2 - 12-b003nf (ENERGY STAR)] Synaptics touchpad not configured by HID RMI Status in linux package in Ubuntu: Triaged Bug description: Hello, The touchpad on the HP Pavilion X2 is not configured properly by hid_rmi and therefore is not detected at all later on by Xorg. The following can be seen in kern.log: Aug 8 20:11:45 X2 kernel: [4.201783] hid-rmi 0003:06CB:7D29.0001: Scanning PDT... Aug 8 20:11:45 X2 kernel: [4.203792] hid-rmi 0003:06CB:7D29.0001: Found F34 on page 0x00 Aug 8 20:11:45 X2 kernel: [4.211498] hid-rmi 0003:06CB:7D29.0001: Found F01 on page 0x00 Aug 8 20:11:45 X2 kernel: [4.213905] hid-rmi 0003:06CB:7D29.0001: Found F12 on page 0x00 Aug 8 20:11:45 X2 kernel: [4.218779] hid-rmi 0003:06CB:7D29.0001: Found F54 on page 0x01 Aug 8 20:11:45 X2 kernel: [4.224524] hid-rmi 0003:06CB:7D29.0001: Found F30 on page 0x02 Aug 8 20:11:45 X2 kernel: [4.229785] hid-rmi 0003:06CB:7D29.0001: Found F55 on page 0x03 Aug 8 20:11:45 X2 kernel: [4.235778] hid-rmi 0003:06CB:7D29.0001: Found F51 on page 0x04 Aug 8 20:11:45 X2 kernel: [4.240853] hid-rmi 0003:06CB:7D29.0001: rmi_scan_pdt: Done with PDT scan. Aug 8 20:11:45 X2 kernel: [4.254044] hid-rmi 0003:06CB:7D29.0001: No 2D sensor found, giving up. Aug 8 20:11:45 X2 kernel: [4.254052] hid-rmi 0003:06CB:7D29.0001: Error while initializing F11 (-19). Aug 8 20:11:45 X2 kernel: [4.260475] hid-rmi 0003:06CB:7D29.0001: hiddev0,hidraw2: USB HID v1.11 Mouse [SYNAPTICS Synaptics HIDUSB TouchPad V03] on usb-:00:14.0-2.1/input0 Aug 8 20:11:45 X2 kernel: [4.260482] hid-rmi 0003:06CB:7D29.0001: Device failed to be properly configured I'll attach dmesg, devices & xOrg log to this bug. Workaround: touchpad can be detected by hid_generic if blacklisting hid_rmi but is then lacking scrolling/multi-touch functionalities. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greenskol 3454 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=bd8f9fbe-28b6-433f-9543-894034b9586d InstallationDate: Installed on 2016-08-02 (6 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Pavilion x2 Detachable Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=8455b162-d9c3-4f18-92b8-7b88707ecbba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 Tags: xenial Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8181 dmi.board.vendor: HP dmi.board.version: 42.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.04:bd11/27/2015:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611081/+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 1636771] [NEW] UbuntuKVM:Ubuntu16.10:makekdumpfile fails during kdump reboot
You have been subscribed to a public bug: Problem Description: === makedumpfile Fails during kdump reboot Steps to re-create: == - Install abakvm with 4.8.0-26 - Edit /etc/default/grub.cfg file with crashkernel as in the following: Logs: root@abakvm:~# cat /proc/cmdline root=UUID=0ed530b3-0f14-45b8-93a8-7502ee36d45f ro splash quiet crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M root@abakvm:~# uname -r 4.8.0-26-generic root@abakvm:~# ls -lh /var/lib/kdump total 31M drwxr-xr-x 5 root root 4.0K Oct 17 03:10 initramfs-tools lrwxrwxrwx 1 root root 42 Oct 24 05:07 initrd.img -> /var/lib/kdump/initrd.img-4.8.0-26-generic -rw-r--r-- 1 root root 16M Oct 17 05:09 initrd.img-4.8.0-22-generic -rw-r--r-- 1 root root 16M Oct 24 04:56 initrd.img-4.8.0-26-generic lrwxrwxrwx 1 root root 30 Oct 24 05:07 vmlinuz -> /boot/vmlinux-4.8.0-26-generic root@abakvm:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-26-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-26-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=0ed530b3-0f14-45b8-93a8-7502ee36d45f ro splash quiet irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@abakvm:~# dmesg | grep Reser [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System RAM: 131072MB) [0.00] cma: Reserved 6560 MiB at 0x001e5600 root@abakvm:~# - Initiate crash, and when checked in console logs the follwoing makekdumpfile is failing Logs: Starting Kernel crash dump capture service... Starting LSB: Start NTP daemon... [ 255.138066] kdump-tools[6019]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201610240645/dump-incomplete [ 255.218513] kdump-tools[6019]: get_mem_map: Can't distinguish the memory type. [ 255.218832] kdump-tools[6019]: The kernel version is not supported. [ 255.219086] kdump-tools[6019]: The makedumpfile operation may be incomplete. [ 255.219385] kdump-tools[6019]: makedumpfile Failed. [ 255.219559] kdump-tools[6019]: * kdump-tools: makedumpfile failed, falling back to 'cp' == Comment: #1 - Vaishnavi Bhat - 2016-10-26 06:05:26 == The makedumpfile.h defines the latest kernel version as 4.5.3 where as the uname output gives a higher kernel version (4.8.0 ), Hence we are seeing this message in the dmesg. #define OLDEST_VERSION KERNEL_VERSION(2, 6, 15)/* linux-2.6.15 */ #define LATEST_VERSION KERNEL_VERSION(4, 5, 3)/* linux-4.5.3 */ ** Affects: makedumpfile (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le bugnameltc-147804 severity-high targetmilestone-inin--- -- UbuntuKVM:Ubuntu16.10:makekdumpfile fails during kdump reboot https://bugs.launchpad.net/bugs/1636771 You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636771] Re: UbuntuKVM:Ubuntu16.10:makekdumpfile fails during kdump reboot
*** This bug is a duplicate of bug 1626269 *** https://bugs.launchpad.net/bugs/1626269 ** This bug has been marked a duplicate of bug 1626269 Ubuntu 16.10: kdump is not working in 4.8 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1636771 Title: UbuntuKVM:Ubuntu16.10:makekdumpfile fails during kdump reboot Status in makedumpfile package in Ubuntu: New Bug description: Problem Description: === makedumpfile Fails during kdump reboot Steps to re-create: == - Install abakvm with 4.8.0-26 - Edit /etc/default/grub.cfg file with crashkernel as in the following: Logs: root@abakvm:~# cat /proc/cmdline root=UUID=0ed530b3-0f14-45b8-93a8-7502ee36d45f ro splash quiet crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M root@abakvm:~# uname -r 4.8.0-26-generic root@abakvm:~# ls -lh /var/lib/kdump total 31M drwxr-xr-x 5 root root 4.0K Oct 17 03:10 initramfs-tools lrwxrwxrwx 1 root root 42 Oct 24 05:07 initrd.img -> /var/lib/kdump/initrd.img-4.8.0-26-generic -rw-r--r-- 1 root root 16M Oct 17 05:09 initrd.img-4.8.0-22-generic -rw-r--r-- 1 root root 16M Oct 24 04:56 initrd.img-4.8.0-26-generic lrwxrwxrwx 1 root root 30 Oct 24 05:07 vmlinuz -> /boot/vmlinux-4.8.0-26-generic root@abakvm:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-26-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-26-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=0ed530b3-0f14-45b8-93a8-7502ee36d45f ro splash quiet irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@abakvm:~# dmesg | grep Reser [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System RAM: 131072MB) [0.00] cma: Reserved 6560 MiB at 0x001e5600 root@abakvm:~# - Initiate crash, and when checked in console logs the follwoing makekdumpfile is failing Logs: Starting Kernel crash dump capture service... Starting LSB: Start NTP daemon... [ 255.138066] kdump-tools[6019]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201610240645/dump-incomplete [ 255.218513] kdump-tools[6019]: get_mem_map: Can't distinguish the memory type. [ 255.218832] kdump-tools[6019]: The kernel version is not supported. [ 255.219086] kdump-tools[6019]: The makedumpfile operation may be incomplete. [ 255.219385] kdump-tools[6019]: makedumpfile Failed. [ 255.219559] kdump-tools[6019]: * kdump-tools: makedumpfile failed, falling back to 'cp' == Comment: #1 - Vaishnavi Bhat - 2016-10-26 06:05:26 == The makedumpfile.h defines the latest kernel version as 4.5.3 where as the uname output gives a higher kernel version (4.8.0 ), Hence we are seeing this message in the dmesg. #define OLDEST_VERSION KERNEL_VERSION(2, 6, 15)/* linux-2.6.15 */ #define LATEST_VERSION KERNEL_VERSION(4, 5, 3)/* linux-4.5.3 */ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1636771/+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 1636771] [NEW] UbuntuKVM:Ubuntu16.10:makekdumpfile fails during kdump reboot
*** This bug is a duplicate of bug 1626269 *** https://bugs.launchpad.net/bugs/1626269 Public bug reported: Problem Description: === makedumpfile Fails during kdump reboot Steps to re-create: == - Install abakvm with 4.8.0-26 - Edit /etc/default/grub.cfg file with crashkernel as in the following: Logs: root@abakvm:~# cat /proc/cmdline root=UUID=0ed530b3-0f14-45b8-93a8-7502ee36d45f ro splash quiet crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M root@abakvm:~# uname -r 4.8.0-26-generic root@abakvm:~# ls -lh /var/lib/kdump total 31M drwxr-xr-x 5 root root 4.0K Oct 17 03:10 initramfs-tools lrwxrwxrwx 1 root root 42 Oct 24 05:07 initrd.img -> /var/lib/kdump/initrd.img-4.8.0-26-generic -rw-r--r-- 1 root root 16M Oct 17 05:09 initrd.img-4.8.0-22-generic -rw-r--r-- 1 root root 16M Oct 24 04:56 initrd.img-4.8.0-26-generic lrwxrwxrwx 1 root root 30 Oct 24 05:07 vmlinuz -> /boot/vmlinux-4.8.0-26-generic root@abakvm:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-26-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-26-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=0ed530b3-0f14-45b8-93a8-7502ee36d45f ro splash quiet irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@abakvm:~# dmesg | grep Reser [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System RAM: 131072MB) [0.00] cma: Reserved 6560 MiB at 0x001e5600 root@abakvm:~# - Initiate crash, and when checked in console logs the follwoing makekdumpfile is failing Logs: Starting Kernel crash dump capture service... Starting LSB: Start NTP daemon... [ 255.138066] kdump-tools[6019]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201610240645/dump-incomplete [ 255.218513] kdump-tools[6019]: get_mem_map: Can't distinguish the memory type. [ 255.218832] kdump-tools[6019]: The kernel version is not supported. [ 255.219086] kdump-tools[6019]: The makedumpfile operation may be incomplete. [ 255.219385] kdump-tools[6019]: makedumpfile Failed. [ 255.219559] kdump-tools[6019]: * kdump-tools: makedumpfile failed, falling back to 'cp' == Comment: #1 - Vaishnavi Bhat - 2016-10-26 06:05:26 == The makedumpfile.h defines the latest kernel version as 4.5.3 where as the uname output gives a higher kernel version (4.8.0 ), Hence we are seeing this message in the dmesg. #define OLDEST_VERSION KERNEL_VERSION(2, 6, 15)/* linux-2.6.15 */ #define LATEST_VERSION KERNEL_VERSION(4, 5, 3)/* linux-4.5.3 */ ** Affects: makedumpfile (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le bugnameltc-147804 severity-high targetmilestone-inin--- ** Tags added: architecture-ppc64le bugnameltc-147804 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Taco Screen team (taco-screen-team) ** Package changed: ubuntu => makedumpfile (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1636771 Title: UbuntuKVM:Ubuntu16.10:makekdumpfile fails during kdump reboot Status in makedumpfile package in Ubuntu: New Bug description: Problem Description: === makedumpfile Fails during kdump reboot Steps to re-create: == - Install abakvm with 4.8.0-26 - Edit /etc/default/grub.cfg file with crashkernel as in the following: Logs: root@abakvm:~# cat /proc/cmdline root=UUID=0ed530b3-0f14-45b8-93a8-7502ee36d45f ro splash quiet crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M root@abakvm:~# uname -r 4.8.0-26-generic root@abakvm:~# ls -lh /var/lib/kdump total 31M drwxr-xr-x 5 root root 4.0K Oct 17 03:10 initramfs-tools lrwxrwxrwx 1 root root 42 Oct 24 05:07 initrd.img -> /var/lib/kdump/initrd.img-4.8.0-26-generic -rw-r--r-- 1 root root 16M Oct 17 05:09 initrd.img-4.8.0-22-generic -rw-r--r-- 1 root root 16M Oct 24 04:56 initrd.img-4.8.0-26-generic lrwxrwxrwx 1 root root 30 Oct 24 05:07 vmlinuz -> /boot/vmlinux-4.8.0-26-generic root@abakvm:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-26-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-26-generic current state:ready to kdump kexec
[Kernel-packages] [Bug 1635377] s2lp4 (s390x.LPAR) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_10-23-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1616214] Re: Macbook Air resumes immediately after suspend
I have the same problem on a Macbook pro retina. It works sometimes after a reboot, but always fails again after the first suspend. Ketil -- 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/1616214 Title: Macbook Air resumes immediately after suspend Status in linux package in Ubuntu: Incomplete Bug description: Based on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311724 I am opening this bug to tackle the issue of a Macbook Air that resumes immediately after suspending. I have the exact same symptoms as those described in the first bug. The first suspend on battery power works without any issues. After that, even trying the 2x pm-suspend method doesn't work. Here's an excerpt from dmesg showing the suspend: [11363.316508] PM: Syncing filesystems ... done. [11363.683228] PM: Preparing system for sleep (mem) [11363.683388] Freezing user space processes ... (elapsed 0.002 seconds) done. [11363.685415] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [11363.686602] PM: Suspending system (mem) [11363.686629] Suspending console(s) (use no_console_suspend to debug) [11363.686839] sd 1:0:0:0: [sda] Synchronizing SCSI cache [11363.686890] sd 1:0:0:0: [sda] Stopping disk [11363.689056] R8188EU: INFO indicate disassoc [11364.057112] PM: suspend of devices complete after 370.364 msecs [11364.079232] PM: late suspend of devices complete after 22.117 msecs [11364.079400] thunderbolt :07:00.0: suspending... [11364.079620] thunderbolt :07:00.0: stopping RX ring 0 [11364.079623] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 12 (0x1001 -> 0x1) [11364.079628] thunderbolt :07:00.0: stopping TX ring 0 [11364.079631] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 0 (0x1 -> 0x0) [11364.079633] thunderbolt :07:00.0: control channel stopped [11364.079634] thunderbolt :07:00.0: suspend finished [11364.080060] xhci_hcd :00:14.0: System wakeup enabled by ACPI [11364.095334] pcieport :05:00.0: quirk: cutting power to thunderbolt controller... [11364.506336] mba6x_bl: Invalid response at reg: 0x1 (len: 24) [11364.733532] mba6x_bl: failed to set brightness [11364.733583] PM: noirq suspend of devices complete after 654.350 msecs [11364.733853] ACPI: Preparing to enter system sleep state S3 [11364.763238] ACPI : EC: EC stopped [11364.763238] PM: Saving platform NVS memory [11364.763240] Disabling non-boot CPUs ... [11364.763530] Broke affinity for irq 49 [11364.764553] smpboot: CPU 1 is now offline [11364.776286] Broke affinity for irq 18 [11364.776293] Broke affinity for irq 44 [11364.776299] Broke affinity for irq 46 [11364.776305] Broke affinity for irq 48 [11364.776309] Broke affinity for irq 49 [11364.777347] smpboot: CPU 2 is now offline [11364.787918] Broke affinity for irq 8 [11364.787921] Broke affinity for irq 9 [11364.787924] Broke affinity for irq 16 [11364.787927] Broke affinity for irq 18 [11364.787930] Broke affinity for irq 44 [11364.787933] Broke affinity for irq 45 [11364.787935] Broke affinity for irq 46 [11364.787937] Broke affinity for irq 47 [11364.787940] Broke affinity for irq 48 [11364.787942] Broke affinity for irq 49 [11364.787945] Broke affinity for irq 54 [11364.788969] smpboot: CPU 3 is now offline [11364.805918] ACPI: Low-level resume complete [11364.806002] ACPI : EC: EC started [11364.806004] PM: Restoring platform NVS memory [11364.806415] Enabling non-boot CPUs ... [11364.826307] x86: Booting SMP configuration: [11364.826309] smpboot: Booting Node 0 Processor 1 APIC 0x2 [11364.837869] cache: parent cpu1 should not be sleeping [11364.838662] CPU1 is up [11365.018821] smpboot: Booting Node 0 Processor 2 APIC 0x1 [11365.074966] cache: parent cpu2 should not be sleeping [11365.075057] CPU2 is up [11365.273364] smpboot: Booting Node 0 Processor 3 APIC 0x3 [11365.325736] cache: parent cpu3 should not be sleeping [11365.350542] CPU3 is up [11365.354192] ACPI: Waking up from system sleep state S3 [11365.430255] xhci_hcd :00:14.0: System wakeup disabled by ACPI [11365.431123] pcieport :06:03.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [11365.431125] pcieport :06:04.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [11365.431219] pcieport :06:05.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [11365.431309] pcieport :06:06.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [11365.446161] thunderbolt :07:00.0: resuming... [11365.446162] thunderbolt :07:00.0: control channel starting... [11365.446165] thunderbolt :07:00.0: starting TX ring 0 [11365.446171] thunderbolt :07:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1)
[Kernel-packages] [Bug 1581326] Re: Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.
Joseph/John, The above mentioned patches(https://marc.info/?l=linux-block&m=147731657127810&w=2 and https://lkml.org/lkml/2016/10/25/326) are posted to upstream by us only. So please consider V2 patch (https://lkml.org/lkml/2016/10/25/326) and let us know. -- 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/1581326 Title: Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS. Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver- v12.100.00.00, Successfully discovered HBA and the devices connected to HBA. >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). volume successfully created and listed from SAS3IRCU utility. >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU utility. Kernel crashed here while creating second volume. >>tried with all possible combinations of RAID volumes. Please find the attached kernel crash logs. >>cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 HBA used : LSI SAS3(Fury) Issue : Kernel gets crashed , when tried creating 2nd RAID volume. Expected : One should be able to create MAX 2 RAID volumes at any point of time successfully , without any kernel crash. --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2 InstallationDate: Installed on 2016-05-11 (1 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: enp5s0f0 no wireless extensions. enp5s0f1 no wireless extensions. lono wireless extensions. MachineType: Supermicro X9DRH-7TF/7F/iTF/iF Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DRH-7TF/7F/iTF/iF dmi.board.vendor: Supermicro dmi.board.version: 1234567890 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Supermicro dmi.chassis.version: 1234567890 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890: dmi.product.name: X9DRH-7TF/7F/iTF/iF dmi.product.version: 1234567890 dmi.sys.vendor: Supermicro --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2 InstallationDate: Installed on 2016-05-11 (1 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: enp5s0f0 no wireless extensions. enp5s0f1 no wireless extensions. lono wireless extensions. MachineType: Supermicro X9DRH-7TF/7F/iTF/iF Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N
[Kernel-packages] [Bug 1626269] Re: Ubuntu 16.10: kdump is not working in 4.8 kernel.
Hello, Here is an update on the situation. I completed a kernel bisection between 4.7.8 and 4.8-rc1 (15 kernel builds) and identified the kernel commit that causes the problem : commit 021182e52fe01c1f7b126f97fd6ba048dc4234fd Author: Thomas Garnier Date: Tue Jun 21 17:47:03 2016 -0700 x86/mm: Enable KASLR for physical mapping memory regions Add the physical mapping in the list of randomized memory regions. The physical memory mapping holds most allocations from boot and heap allocators. Knowing the base address and physical memory size, an attacker can deduce the PDE virtual address for the vDSO memory page. This attack was demonstrated at CanSecWest 2016, in the following presentation: "Getting Physical: Extreme Abuse of Intel Based Paged Systems": https://github.com/n3k/CansecWest2016_Getting_Physical_Extreme_Abuse_of_Intel_Based_Paging_Systems/blob/master/Presentation/CanSec2016_Presentation.pdf (See second part of the presentation). The exploits used against Linux worked successfully against 4.6+ but fail with KASLR memory enabled: https://github.com/n3k/CansecWest2016_Getting_Physical_Extreme_Abuse_of_Intel_Based_Paging_Systems/tree/master/Demos/Linux/exploits Similar research was done at Google leading to this patch proposal. Variants exists to overwrite /proc or /sys objects ACLs leading to elevation of privileges. These variants were tested against 4.6+. The page offset used by the compressed kernel retains the static value since it is not yet randomized during this boot stage. Signed-off-by: Thomas Garnier Signed-off-by: Kees Cook As you can see, this modification is specific to the x86 architecture which is why you don't see the issue. In parallel to that, a patch to fix this situation has been published yesterday to the makedumpfile mailing list and is currently under review by the main developper : https://www.mail-archive.com/kexec@lists.infradead.org/msg16628.html There is a debian bug opened for this issue : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842019 While I understand your concern, I cannot push a modification that will trigger makedumpfile to generate dozen of error messages and a potentially unusable vmcore to all of the x86 world in order to satisfy only one architecture. It is important to remember that, while makedumpfile fails, the kernel dump capture mechanism reverts to using 'cp' to copy /proc/vmcore uncompressed so this vmcore file is still usable for analysis. Hopefully, we should get an ACK for the upstream bug soon, so I can push a new package to Debian. I will then proceed with the synchronization to Zesty and SRU to the other stable releases. I hope that this clarifies the situation. Kind regards ** Bug watch added: Debian Bug tracker #842019 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842019 ** Changed in: makedumpfile (Ubuntu) Status: Confirmed => In Progress ** Changed in: makedumpfile (Ubuntu) Importance: High => Medium ** Changed in: makedumpfile (Ubuntu Yakkety) Importance: High => Medium ** Changed in: makedumpfile (Ubuntu Trusty) Status: New => Confirmed ** Changed in: makedumpfile (Ubuntu Xenial) Status: New => Confirmed ** Changed in: makedumpfile (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: makedumpfile (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1626269 Title: Ubuntu 16.10: kdump is not working in 4.8 kernel. Status in makedumpfile package in Ubuntu: In Progress Status in makedumpfile source package in Trusty: Confirmed Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Yakkety: Confirmed Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2016-09-21 00:50:22 == ---Problem Description--- Ubuntu 16.10: kdump is not working in 4.8 kernel. ---Steps to Reproduce--- 1) apt-get install linux-crashdump 2) increase crashdump size: sudo vim /etc/default/grub.d/kexec-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M" 3) sudo update-grub ; reboot the machine 4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools 5) kdump-config show 6) echo "c" > /proc/sysrq-trigger Logs root@ubuntu:/home/ubuntu# uname -a Linux ubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@ubuntu:/home/ubuntu# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4
[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth
The problem is not so much the `phone but the car. I went to BMW yesterday because mine did connect OK initially but now won`t do it. They were able to get "Connected" on the screen but there was no signal. They then went into the database of the car and found BQ were not on the list. I have an Apple 3 which connects instantly. BQ need to issue the software to car manufacturers otherwise a lot of fed up people will dump the `phone. -- 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/1435040 Title: Ubuntu Phone does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1636625] Re: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile
apport information ** Tags added: apport-collected ** Description changed: Recommended change: remove incorrect extra ) character root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile 615c615 < -fstack-protector not supported by compiler) --- > -fstack-protector not supported by compiler)) This bug causes driver builds to fail like this make[1]: Entering directory `/usr/src/linux-headers-3.13.0-100-generic' /usr/src/linux-headers-3.13.0-100-generic/arch/x86/Makefile:111: CONFIG_X86_X32 enabled but no binutils support Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR: -fstack-protector not supported by compiler Makefile:614: *** missing separator. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-100-generic' make: *** [all] Error 2 + --- + ApportVersion: 2.14.1-0ubuntu3.18 + Architecture: amd64 + 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 + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=93497dab-63bb-4998-9e07-583b6fbd6493 + InstallationDate: Installed on 2014-09-03 (784 days ago) + InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) + IwConfig: + bond0 no wireless extensions. + + eth0 no wireless extensions. + + lono wireless extensions. + MachineType: HP ProLiant ML110 G5 + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic root=UUID=2083fcba-62cb-427d-abb2-cacc50e14374 ro text nomdmonddf nomdmonisw + ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.13.0-100-generic N/A + linux-backports-modules-3.13.0-100-generic N/A + linux-firmware 1.127.22 + RfKill: + + Tags: trusty + Uname: Linux 3.13.0-100-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 10/25/2010 + dmi.bios.vendor: HP + dmi.bios.version: O15 + dmi.board.asset.tag: No Asset Tag + dmi.board.name: ProLiant ML110 G5 + dmi.board.vendor: Wistron Corporation + dmi.board.version: NA + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 7 + dmi.chassis.vendor: HP + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnHP:bvrO15:bd10/25/2010:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnProLiantML110G5:rvrNA:cvnHP:ct7:cvrN/A: + dmi.product.name: ProLiant ML110 G5 + dmi.product.version: NA + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1636625/+attachment/4767516/+files/AlsaInfo.txt -- 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/1636625 Title: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile Status in linux package in Ubuntu: Incomplete Bug description: Recommended change: remove incorrect extra ) character root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile 615c615 < -fstack-protector not supported by compiler) --- > -fstack-protector not supported by compiler)) This bug causes driver builds to fail like this make[1]: Entering directory `/usr/src/linux-headers-3.13.0-100-generic' /usr/src/linux-headers-3.13.0-100-generic/arch/x86/Makefile:111: CONFIG_X86_X32 enabled but no binutils support Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR: -fstack-protector not supported by compiler Makefile:614: *** missing separator. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-100-generic' make: *** [all] Error 2 --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 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 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=93497dab-63bb-4998-9e07-583b6fbd6493 InstallationDate: Installed on 2014-09-03 (784 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: bond0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G5 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic root=UUID=2
[Kernel-packages] [Bug 1636625] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1636625/+attachment/4767520/+files/Lsusb.txt -- 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/1636625 Title: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile Status in linux package in Ubuntu: Incomplete Bug description: Recommended change: remove incorrect extra ) character root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile 615c615 < -fstack-protector not supported by compiler) --- > -fstack-protector not supported by compiler)) This bug causes driver builds to fail like this make[1]: Entering directory `/usr/src/linux-headers-3.13.0-100-generic' /usr/src/linux-headers-3.13.0-100-generic/arch/x86/Makefile:111: CONFIG_X86_X32 enabled but no binutils support Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR: -fstack-protector not supported by compiler Makefile:614: *** missing separator. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-100-generic' make: *** [all] Error 2 --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 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 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=93497dab-63bb-4998-9e07-583b6fbd6493 InstallationDate: Installed on 2014-09-03 (784 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: bond0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G5 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic root=UUID=2083fcba-62cb-427d-abb2-cacc50e14374 ro text nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-100-generic N/A linux-backports-modules-3.13.0-100-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-100-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/25/2010 dmi.bios.vendor: HP dmi.bios.version: O15 dmi.board.asset.tag: No Asset Tag dmi.board.name: ProLiant ML110 G5 dmi.board.vendor: Wistron Corporation dmi.board.version: NA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.chassis.version: N/A dmi.modalias: dmi:bvnHP:bvrO15:bd10/25/2010:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnProLiantML110G5:rvrNA:cvnHP:ct7:cvrN/A: dmi.product.name: ProLiant ML110 G5 dmi.product.version: NA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636625/+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 1636625] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1636625/+attachment/4767524/+files/UdevDb.txt -- 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/1636625 Title: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile Status in linux package in Ubuntu: Incomplete Bug description: Recommended change: remove incorrect extra ) character root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile 615c615 < -fstack-protector not supported by compiler) --- > -fstack-protector not supported by compiler)) This bug causes driver builds to fail like this make[1]: Entering directory `/usr/src/linux-headers-3.13.0-100-generic' /usr/src/linux-headers-3.13.0-100-generic/arch/x86/Makefile:111: CONFIG_X86_X32 enabled but no binutils support Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR: -fstack-protector not supported by compiler Makefile:614: *** missing separator. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-100-generic' make: *** [all] Error 2 --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 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 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=93497dab-63bb-4998-9e07-583b6fbd6493 InstallationDate: Installed on 2014-09-03 (784 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: bond0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G5 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic root=UUID=2083fcba-62cb-427d-abb2-cacc50e14374 ro text nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-100-generic N/A linux-backports-modules-3.13.0-100-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-100-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/25/2010 dmi.bios.vendor: HP dmi.bios.version: O15 dmi.board.asset.tag: No Asset Tag dmi.board.name: ProLiant ML110 G5 dmi.board.vendor: Wistron Corporation dmi.board.version: NA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.chassis.version: N/A dmi.modalias: dmi:bvnHP:bvrO15:bd10/25/2010:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnProLiantML110G5:rvrNA:cvnHP:ct7:cvrN/A: dmi.product.name: ProLiant ML110 G5 dmi.product.version: NA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636625/+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 1636625] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1636625/+attachment/4767519/+files/Lspci.txt -- 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/1636625 Title: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile Status in linux package in Ubuntu: Incomplete Bug description: Recommended change: remove incorrect extra ) character root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile 615c615 < -fstack-protector not supported by compiler) --- > -fstack-protector not supported by compiler)) This bug causes driver builds to fail like this make[1]: Entering directory `/usr/src/linux-headers-3.13.0-100-generic' /usr/src/linux-headers-3.13.0-100-generic/arch/x86/Makefile:111: CONFIG_X86_X32 enabled but no binutils support Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR: -fstack-protector not supported by compiler Makefile:614: *** missing separator. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-100-generic' make: *** [all] Error 2 --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 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 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=93497dab-63bb-4998-9e07-583b6fbd6493 InstallationDate: Installed on 2014-09-03 (784 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: bond0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G5 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic root=UUID=2083fcba-62cb-427d-abb2-cacc50e14374 ro text nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-100-generic N/A linux-backports-modules-3.13.0-100-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-100-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/25/2010 dmi.bios.vendor: HP dmi.bios.version: O15 dmi.board.asset.tag: No Asset Tag dmi.board.name: ProLiant ML110 G5 dmi.board.vendor: Wistron Corporation dmi.board.version: NA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.chassis.version: N/A dmi.modalias: dmi:bvnHP:bvrO15:bd10/25/2010:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnProLiantML110G5:rvrNA:cvnHP:ct7:cvrN/A: dmi.product.name: ProLiant ML110 G5 dmi.product.version: NA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636625/+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 1636625] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1636625/+attachment/4767522/+files/ProcInterrupts.txt -- 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/1636625 Title: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile Status in linux package in Ubuntu: Incomplete Bug description: Recommended change: remove incorrect extra ) character root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile 615c615 < -fstack-protector not supported by compiler) --- > -fstack-protector not supported by compiler)) This bug causes driver builds to fail like this make[1]: Entering directory `/usr/src/linux-headers-3.13.0-100-generic' /usr/src/linux-headers-3.13.0-100-generic/arch/x86/Makefile:111: CONFIG_X86_X32 enabled but no binutils support Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR: -fstack-protector not supported by compiler Makefile:614: *** missing separator. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-100-generic' make: *** [all] Error 2 --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 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 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=93497dab-63bb-4998-9e07-583b6fbd6493 InstallationDate: Installed on 2014-09-03 (784 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: bond0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G5 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic root=UUID=2083fcba-62cb-427d-abb2-cacc50e14374 ro text nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-100-generic N/A linux-backports-modules-3.13.0-100-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-100-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/25/2010 dmi.bios.vendor: HP dmi.bios.version: O15 dmi.board.asset.tag: No Asset Tag dmi.board.name: ProLiant ML110 G5 dmi.board.vendor: Wistron Corporation dmi.board.version: NA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.chassis.version: N/A dmi.modalias: dmi:bvnHP:bvrO15:bd10/25/2010:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnProLiantML110G5:rvrNA:cvnHP:ct7:cvrN/A: dmi.product.name: ProLiant ML110 G5 dmi.product.version: NA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636625/+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 1636625] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1636625/+attachment/4767518/+files/CurrentDmesg.txt -- 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/1636625 Title: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile Status in linux package in Ubuntu: Incomplete Bug description: Recommended change: remove incorrect extra ) character root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile 615c615 < -fstack-protector not supported by compiler) --- > -fstack-protector not supported by compiler)) This bug causes driver builds to fail like this make[1]: Entering directory `/usr/src/linux-headers-3.13.0-100-generic' /usr/src/linux-headers-3.13.0-100-generic/arch/x86/Makefile:111: CONFIG_X86_X32 enabled but no binutils support Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR: -fstack-protector not supported by compiler Makefile:614: *** missing separator. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-100-generic' make: *** [all] Error 2 --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 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 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=93497dab-63bb-4998-9e07-583b6fbd6493 InstallationDate: Installed on 2014-09-03 (784 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: bond0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G5 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic root=UUID=2083fcba-62cb-427d-abb2-cacc50e14374 ro text nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-100-generic N/A linux-backports-modules-3.13.0-100-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-100-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/25/2010 dmi.bios.vendor: HP dmi.bios.version: O15 dmi.board.asset.tag: No Asset Tag dmi.board.name: ProLiant ML110 G5 dmi.board.vendor: Wistron Corporation dmi.board.version: NA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.chassis.version: N/A dmi.modalias: dmi:bvnHP:bvrO15:bd10/25/2010:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnProLiantML110G5:rvrNA:cvnHP:ct7:cvrN/A: dmi.product.name: ProLiant ML110 G5 dmi.product.version: NA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636625/+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 1636625] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1636625/+attachment/4767523/+files/ProcModules.txt -- 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/1636625 Title: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile Status in linux package in Ubuntu: Incomplete Bug description: Recommended change: remove incorrect extra ) character root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile 615c615 < -fstack-protector not supported by compiler) --- > -fstack-protector not supported by compiler)) This bug causes driver builds to fail like this make[1]: Entering directory `/usr/src/linux-headers-3.13.0-100-generic' /usr/src/linux-headers-3.13.0-100-generic/arch/x86/Makefile:111: CONFIG_X86_X32 enabled but no binutils support Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR: -fstack-protector not supported by compiler Makefile:614: *** missing separator. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-100-generic' make: *** [all] Error 2 --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 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 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=93497dab-63bb-4998-9e07-583b6fbd6493 InstallationDate: Installed on 2014-09-03 (784 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: bond0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G5 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic root=UUID=2083fcba-62cb-427d-abb2-cacc50e14374 ro text nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-100-generic N/A linux-backports-modules-3.13.0-100-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-100-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/25/2010 dmi.bios.vendor: HP dmi.bios.version: O15 dmi.board.asset.tag: No Asset Tag dmi.board.name: ProLiant ML110 G5 dmi.board.vendor: Wistron Corporation dmi.board.version: NA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.chassis.version: N/A dmi.modalias: dmi:bvnHP:bvrO15:bd10/25/2010:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnProLiantML110G5:rvrNA:cvnHP:ct7:cvrN/A: dmi.product.name: ProLiant ML110 G5 dmi.product.version: NA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636625/+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 1636625] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1636625/+attachment/4767521/+files/ProcCpuinfo.txt -- 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/1636625 Title: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile Status in linux package in Ubuntu: Incomplete Bug description: Recommended change: remove incorrect extra ) character root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile 615c615 < -fstack-protector not supported by compiler) --- > -fstack-protector not supported by compiler)) This bug causes driver builds to fail like this make[1]: Entering directory `/usr/src/linux-headers-3.13.0-100-generic' /usr/src/linux-headers-3.13.0-100-generic/arch/x86/Makefile:111: CONFIG_X86_X32 enabled but no binutils support Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR: -fstack-protector not supported by compiler Makefile:614: *** missing separator. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-100-generic' make: *** [all] Error 2 --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 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 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=93497dab-63bb-4998-9e07-583b6fbd6493 InstallationDate: Installed on 2014-09-03 (784 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: bond0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G5 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic root=UUID=2083fcba-62cb-427d-abb2-cacc50e14374 ro text nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-100-generic N/A linux-backports-modules-3.13.0-100-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-100-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/25/2010 dmi.bios.vendor: HP dmi.bios.version: O15 dmi.board.asset.tag: No Asset Tag dmi.board.name: ProLiant ML110 G5 dmi.board.vendor: Wistron Corporation dmi.board.version: NA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.chassis.version: N/A dmi.modalias: dmi:bvnHP:bvrO15:bd10/25/2010:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnProLiantML110G5:rvrNA:cvnHP:ct7:cvrN/A: dmi.product.name: ProLiant ML110 G5 dmi.product.version: NA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636625/+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 1636625] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1636625/+attachment/4767517/+files/BootDmesg.txt -- 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/1636625 Title: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile Status in linux package in Ubuntu: Incomplete Bug description: Recommended change: remove incorrect extra ) character root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile 615c615 < -fstack-protector not supported by compiler) --- > -fstack-protector not supported by compiler)) This bug causes driver builds to fail like this make[1]: Entering directory `/usr/src/linux-headers-3.13.0-100-generic' /usr/src/linux-headers-3.13.0-100-generic/arch/x86/Makefile:111: CONFIG_X86_X32 enabled but no binutils support Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR: -fstack-protector not supported by compiler Makefile:614: *** missing separator. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-100-generic' make: *** [all] Error 2 --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 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 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=93497dab-63bb-4998-9e07-583b6fbd6493 InstallationDate: Installed on 2014-09-03 (784 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: bond0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G5 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic root=UUID=2083fcba-62cb-427d-abb2-cacc50e14374 ro text nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-100-generic N/A linux-backports-modules-3.13.0-100-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-100-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/25/2010 dmi.bios.vendor: HP dmi.bios.version: O15 dmi.board.asset.tag: No Asset Tag dmi.board.name: ProLiant ML110 G5 dmi.board.vendor: Wistron Corporation dmi.board.version: NA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.chassis.version: N/A dmi.modalias: dmi:bvnHP:bvrO15:bd10/25/2010:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnProLiantML110G5:rvrNA:cvnHP:ct7:cvrN/A: dmi.product.name: ProLiant ML110 G5 dmi.product.version: NA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636625/+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 1636625] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1636625/+attachment/4767525/+files/UdevLog.txt -- 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/1636625 Title: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile Status in linux package in Ubuntu: Incomplete Bug description: Recommended change: remove incorrect extra ) character root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile 615c615 < -fstack-protector not supported by compiler) --- > -fstack-protector not supported by compiler)) This bug causes driver builds to fail like this make[1]: Entering directory `/usr/src/linux-headers-3.13.0-100-generic' /usr/src/linux-headers-3.13.0-100-generic/arch/x86/Makefile:111: CONFIG_X86_X32 enabled but no binutils support Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR: -fstack-protector not supported by compiler Makefile:614: *** missing separator. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-100-generic' make: *** [all] Error 2 --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 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 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=93497dab-63bb-4998-9e07-583b6fbd6493 InstallationDate: Installed on 2014-09-03 (784 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: bond0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G5 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic root=UUID=2083fcba-62cb-427d-abb2-cacc50e14374 ro text nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-100-generic N/A linux-backports-modules-3.13.0-100-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-100-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/25/2010 dmi.bios.vendor: HP dmi.bios.version: O15 dmi.board.asset.tag: No Asset Tag dmi.board.name: ProLiant ML110 G5 dmi.board.vendor: Wistron Corporation dmi.board.version: NA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.chassis.version: N/A dmi.modalias: dmi:bvnHP:bvrO15:bd10/25/2010:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnProLiantML110G5:rvrNA:cvnHP:ct7:cvrN/A: dmi.product.name: ProLiant ML110 G5 dmi.product.version: NA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636625/+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 1635377] s2lp4 (s390x.LPAR) - tests ran: 10, failed: 2
tests ran: 10, failed: 2; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_10-24-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
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/1636517
Title:
zfs: importing zpool with vdev on zvol hangs kernel
Status in linux package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
New
Bug description:
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev_ioctl+0x44b/0x4e0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x71
[] 0x
I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (merged
in 4.4.0-6.21), which added a second parameter to lookup_bdev without
patching the zfs module (which needs to special case the vdev-on-zvol
case, and uses this exact method only in this special casing code
path).
attached you can find the output of "zfs send -R" ing such a zvol
("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
by "zpool import" should reproduce the hang.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-45-generic 4.4.0-45.66
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 15:46 seq
crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Oct 25 15:49:51 2016
HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
InstallationDate: Installed on 2016-10-25 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic
root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-45-generic N/A
linux-backports-modules-4.4.0-45-generic N/A
linux-firmware1.157.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.7
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.7
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636517/+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 1635430] modoc (ppc64el) - tests ran: 141, failed: 0
tests ran: 141, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-101.148/modoc__3.13.0-101.148__2016-10-26_10-23-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/1635430 Title: linux: 3.13.0-101.148 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-101.148 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635430/+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 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel
Thanks Hajo, I was working the fix last night with a detection of the
two different lookup_bdev calls and been regression testing during the
night for Zesty, Yakkety and Xenial. I've got my fix already prepared...
So the way this kind of fix works with Ubuntu is as follows:
1. Change goes into zfsutils-linux
2. Sync the delta into the kernel package
I've put the zfsutils updates in ppa:
https://launchpad.net/~colin-king/+archive/ubuntu/zfs-lp-1636517
sudo add-apt-repository ppa:colin-king/zfs-lp-1636517
sudo apt-get update && sudo apt-get upgrade
And the fix in some test kernels:
http://kernel.ubuntu.com/~cking/zfs-lp-163651
These have been tested against our internal zfs regression tests and
pass.
@Fabian can you test these and if they are OK I'll SRU these. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1636517
Title:
zfs: importing zpool with vdev on zvol hangs kernel
Status in linux package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
New
Bug description:
[SRU Request][Xenial][Yakkety]
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev_ioctl+0x44b/0x4e0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x71
[] 0x
[Fix]
Zesty:
https://launchpadlibrarian.net/290907232/zfs-linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz
Yakkety, likewise
Xenial, likewise
[Regression Potential]
Minimal. This just touched one line in the zfs module
module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h
Tested and passes with the ubuntu kernel team autotest client zfs
regression tests.
=
I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged
in 4.4.0-6.21), which added a second parameter to lookup_bdev without
patching the zfs module (which needs to special case the vdev-on-zvol
case, and uses this exact method only in this special casing code
path).
attached you can find the output of "zfs send -R" ing such a zvol
("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
by "zpool import" should reproduce the hang.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-45-generic 4.4.0-45.66
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 15:46 seq
crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Oct 25 15:49:51 2016
HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
InstallationDate: Installed on 2016-10-25 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic
root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-45-generic N/A
linux-backports-modules-4.4.0-45-generic N/A
linux-firmware1.157.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.7
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.7
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636517/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Po
[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel
** Description changed:
+ [SRU Request][Xenial][Yakkety]
+
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev_ioctl+0x44b/0x4e0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x71
[] 0x
- I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (merged
- in 4.4.0-6.21), which added a second parameter to lookup_bdev without
+ [Fix]
+ Zesty:
https://launchpadlibrarian.net/290907232/zfs-linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz
+
+ Yakkety, likewise
+ Xenial, likewise
+
+ [Regression Potential]
+
+ Minimal. This just touched one line in the zfs module
+ module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h
+
+ Tested and passes with the ubuntu kernel team autotest client zfs
+ regression tests.
+
+
+ =
+
+ I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged in
+ 4.4.0-6.21), which added a second parameter to lookup_bdev without
patching the zfs module (which needs to special case the vdev-on-zvol
case, and uses this exact method only in this special casing code path).
attached you can find the output of "zfs send -R" ing such a zvol
("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed by
"zpool import" should reproduce the hang.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-45-generic 4.4.0-45.66
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices:
- total 0
- crw-rw 1 root audio 116, 1 Oct 25 15:46 seq
- crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
+ total 0
+ crw-rw 1 root audio 116, 1 Oct 25 15:46 seq
+ crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Oct 25 15:49:51 2016
HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
InstallationDate: Installed on 2016-10-25 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
-
+
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic
root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
- linux-restricted-modules-4.4.0-45-generic N/A
- linux-backports-modules-4.4.0-45-generic N/A
- linux-firmware1.157.4
+ linux-restricted-modules-4.4.0-45-generic N/A
+ linux-backports-modules-4.4.0-45-generic N/A
+ linux-firmware1.157.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.7
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.7
dmi.sys.vendor: QEMU
--
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/1636517
Title:
zfs: importing zpool with vdev on zvol hangs kernel
Status in linux package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
New
Bug description:
[SRU Request][Xenial][Yakkety]
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev
[Kernel-packages] [Bug 1635242] Re: linux: 4.4.0-46.67 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-46.67 /xenial-proposed-frozen.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635242 Title: linux: 4.4.0-46.67 -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: Fix Released 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-46.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635242/+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 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel
Bah, typo:
test kernels at:
http://kernel.ubuntu.com/~cking/zfs-lp-1636517
** Description changed:
[SRU Request][Xenial][Yakkety]
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev_ioctl+0x44b/0x4e0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x71
[] 0x
[Fix]
- Zesty:
https://launchpadlibrarian.net/290907232/zfs-linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz
+ zfsutils-linux:
+
+ Zesty: https://launchpadlibrarian.net/290907232/zfs-
+ linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz
Yakkety, likewise
Xenial, likewise
+
+ Sync'd fixes into kernel repos, patches in:
+ http://kernel.ubuntu.com/~cking/zfs-lp-1636517
[Regression Potential]
Minimal. This just touched one line in the zfs module
module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h
Tested and passes with the ubuntu kernel team autotest client zfs
regression tests.
-
=
I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged in
4.4.0-6.21), which added a second parameter to lookup_bdev without
patching the zfs module (which needs to special case the vdev-on-zvol
case, and uses this exact method only in this special casing code path).
attached you can find the output of "zfs send -R" ing such a zvol
("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed by
"zpool import" should reproduce the hang.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-45-generic 4.4.0-45.66
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 15:46 seq
crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Oct 25 15:49:51 2016
HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
InstallationDate: Installed on 2016-10-25 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic
root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-45-generic N/A
linux-backports-modules-4.4.0-45-generic N/A
linux-firmware1.157.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.7
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.7
dmi.sys.vendor: QEMU
--
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/1636517
Title:
zfs: importing zpool with vdev on zvol hangs kernel
Status in linux package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
New
Bug description:
[SRU Request][Xenial][Yakkety]
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev_ioctl+0x44b/0x4e0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16
[Kernel-packages] [Bug 1635377] s2lp4 (s390x.LPAR) - tests ran: 18, failed: 0
tests ran: 18, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_11-03-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1635242] s2lp3 (s390x.LPAR) - tests ran: 33, failed: 0
tests ran: 33, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-46.67/s2lp3__4.4.0-46.67__2016-10-26_10-50-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/1635242 Title: linux: 4.4.0-46.67 -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: Fix Released 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-46.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635242/+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 1635428] modoc (ppc64el) - tests ran: 10, failed: 0
tests ran: 10, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-78.101~14.04.1/modoc__3.16.0-78.101~14.04.1__2016-10-26_12-19-00/results-index.html -- 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/1635428 Title: linux-lts-vivid: 3.19.0-74.82~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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed 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-74.82~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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1635424 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635428/+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 1636847] [NEW] unexpectedly large memory usage of mounted snaps
Public bug reported: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker ** Affects: snappy Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: New Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+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 1635377] s2lp4 (s390x.LPAR) - tests ran: 5, failed: 3
tests ran: 5, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_11-34-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1635377] onza (amd64) - tests ran: 19, failed: 0
tests ran: 19, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-27.29/onza__4.8.0-27.29__2016-10-26_12-16-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1625232] Re: xgene i2c slimpro driver fails to load
** Summary changed: - [SRU] [xenial] xgene i2c slimpro driver fails to load + xgene i2c slimpro driver fails to load -- 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/1625232 Title: xgene i2c slimpro driver fails to load Status in linux package in Ubuntu: In Progress Bug description: [Impact] The X-Gene I2C slimpro driver fails to load, which is needed for ipmitool to communicate with the bmc, locally. [Test Case] Ensure the slimpro driver loads and that ipmitool can communicate with the bmc. [Regression Risk] The slimpro driver is a standalone, xgene driver, so any issues with it will only affect that platform. The patches were specified by APM as needed for local bmc access to work. Outside of the driver causing a crash, a regression in the driver itself would leave us in the same state we currently are, the driver not loading or no access to the bmc locally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625232/+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 1636847] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1636847 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/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+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 1635377] s2lp4 (s390x.LPAR) - tests ran: 19, failed: 7
tests ran: 19, failed: 7; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_13-20-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1636847] Re: unexpectedly large memory usage of mounted snaps
Marking as 'confirmed' so the bot doesn't auto-close it. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Confirmed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+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 1635377] s2lp4 (s390x.LPAR) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_13-54-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1635377] s2lp4 (s390x.LPAR) - tests ran: 141, failed: 28
tests ran: 141, failed: 28; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_13-33-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1591618] Re: [Feature] KBL - New device ID for Kabypoint(KbP)
https://lists.ubuntu.com/archives/kernel-team/2016-October/080575.html ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => In Progress ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591618 Title: [Feature] KBL - New device ID for Kabypoint(KbP) Status in intel: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: identify what new device IDs are required for Kabypoint (KBP): HS- UART,SPI, I2C, SMBUS,SPI-NOR,NPK,xHCI,usb device, SD Platform: Kabylake-S with Kabypoint PCH upstream schedule: 4.9 X-HWE-Bug: Bug #1622469 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591618/+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 1591618] Re: [Feature] KBL - New device ID for Kabypoint(KbP)
https://lists.ubuntu.com/archives/kernel-team/2016-October/080576.html ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Zesty) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591618 Title: [Feature] KBL - New device ID for Kabypoint(KbP) Status in intel: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: identify what new device IDs are required for Kabypoint (KBP): HS- UART,SPI, I2C, SMBUS,SPI-NOR,NPK,xHCI,usb device, SD Platform: Kabylake-S with Kabypoint PCH upstream schedule: 4.9 X-HWE-Bug: Bug #1622469 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591618/+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 1635377] s2lp4 (s390x.LPAR) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_13-56-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1635594] Re: [yakkety] hio driver missing
** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Fix Committed ** Also affects: linux (Ubuntu Zesty) Importance: Critical Assignee: Andy Whitcroft (apw) Status: In Progress -- 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/1635594 Title: [yakkety] hio driver missing Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: In Progress Bug description: == SRU Justification == Huawei servers, including Huawei PCIe SSD's require the hio driver which is currently not included in our kernels. We would like to carry this driver in our kernels for Xenial and newer in order to support platforms with these drives. This was original ported to Xenial and is now missing in Yakkety creating a regression in that release. == Source == http://support.huawei.com/enterprisesearch/ebgSearch#sp.keyword=HUAWEI%20ES3000%20V2%20Driver%20SRC == Testing == The reporter has hardware to test these kernels. == Regression potential == The driver does not exist currently, so no regression potential exists in Yakkety. Upgrades from Xenial are currently regressing and will need to be tested. --- The hio ubuntu driver in Xenial seems to be MIA in yakkety. Reported to us by Elmo. --- Kernel-Description: hio Ubuntu sauce driver needs porting to 4.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635594/+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 1635177] Re: mfd: intel-lpss: Add default I2C device properties for Apollo Lake
** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Ying-Chun Liu (paulliu) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Ying-Chun Liu (paulliu) ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Yakkety) Status: New => In Progress -- 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/1635177 Title: mfd: intel-lpss: Add default I2C device properties for Apollo Lake Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: We need this patch for all Apollo Lake platforms for enabling the touchpad. This patch was cherry-picked from c50cdd62dda3f885c1e6ca8b3d5a0851c911ec54. And later backported to 4.4 kernel. It is because for Apollo Lake, the default freq/falling-time is incorrect. So it makes the i2c acts weird. Please consider SRU this commit. Impact: All touchpad on Apollo Lake work unstable on i2c mode. Sometimes it will fallback to PS/2 mode and lost some functionality. Fix: touchpad works good on i2c mode. Tested: The patch is tested on many Dell ApolloLake laptops and works good. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1635177/+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 1636847] Re: unexpectedly large memory usage of mounted snaps
Evidence suggests this is triggered by the parallel decompressor. Will spin a kernel with that switched out: CONFIG_SQUASHFS_DECOMP_SINGLE=y -- 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/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Confirmed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+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 1636330] Re: guest experiencing Transmit Timeouts on CX4
Was the attached patch accepted upstream? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636330 Title: guest experiencing Transmit Timeouts on CX4 Status in linux package in Ubuntu: New Bug description: This patch fixes a race condition that was reintroduced in the 4.8 kernel, as part of the P9 changes, after having been originally fixed in 3.19. The effect of the race condition is that a secondary thread can start trying to execute code from the guest while the thread is still in hypervisor mode, so it can cause many different symptoms, one of which seems to be the timebase corruption that leads to the lockup in ktime_get_ts64. It could cause other problems such as CPU cores locking up hard or memory corruption. This patch is only needed on the host. It should be applied to any 4.8 kernel being used as a host, including the Ubuntu 16.10 kernel. Hi Paul I built a kernel with your patch and put at the host and in the guest. I can still see some ktime_get_ts64 at the host. The guest dmesg is clean. This patch fixes another race condition I found in the fastsleep code. Please apply this patch as well and test. Sure will do and provide feedback. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636330/+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 1635428] modoc (ppc64el) - tests ran: 141, failed: 0
tests ran: 141, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-78.101~14.04.1/modoc__3.16.0-78.101~14.04.1__2016-10-26_14-13-00/results-index.html -- 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/1635428 Title: linux-lts-vivid: 3.19.0-74.82~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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed 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-74.82~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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1635424 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635428/+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 1634705] Re: Add ipvlan module to 16.04 kernel
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Yakkety) 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/1634705 Title: Add ipvlan module to 16.04 kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: Currently, ipvlan is included in the linux-image-extra package however users have requested that it be included as a module in the primary kernel package. Users running docker with mesos require ipvlan for container networking to function (and likely other container use cases). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634705/+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 1634753] Re: srcname from mount rule corrupted under load
** Changed in: linux (Ubuntu Trusty)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1634753
Title:
srcname from mount rule corrupted under load
Status in AppArmor:
In Progress
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Precise:
Invalid
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Yakkety:
Invalid
Bug description:
This came up in snapd spread tests but can be reproduced with:
In an i386 up to date 16.04 VM:
1. in one terminal, run this:
$ cat reproducer.sh
#!/bin/sh
set -e
sudo sysctl -w kernel.printk_ratelimit=0
sudo snap install hello-world || true
count=0
while /bin/true ; do
count=$((count+1))
if [ `echo "$count % 100" | bc` -eq 0 ]; then
echo "$count runs"
fi
hello-world > /dev/null || {
tail -100 /var/log/syslog | grep DEN && exit
}
sudo cat /run/snapd/ns/hello-world.mnt 2>/dev/null || sudo
/usr/lib/snapd/snap-discard-ns hello-world
done
2. in another terminal run:
$ while do /bin/true ; sudo apparmor_parser -r /etc/apparmor.d/* >/dev/null
2>&1 ; done
3. In another terminal:
$ tail -f /var/log/syslog|grep DEN
This is not limited to i386.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1634753/+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 1636847] Re: unexpectedly large memory usage of mounted snaps
Ok test kernels at the URL below, please report testing results back here: people.canonical.com/~apw/lp1636847-xenial/ Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Confirmed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+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 1559194] Re: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Yakkety) 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/1559194 Title: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - Dmitry Gorbachev - 2016-03-17 08:52:41 == An error occurs when running zEDC compression/decompression and hotplugging PCI devices. There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled. Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in process genwqe_gunzip pfn:3c275 Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 count:-1 mapcount:0 mapping: (null) index:0x0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0() Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero _count Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) dasd_eckd_mod(E) dasd_mod(E) Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: genwqe_gunzip Tainted: GW E 4.4.0-8-generic #23-Ubuntu Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 20917788 0002 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 209177a0 209177a0 00114182 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 0092345a 03d1000a 000a Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 20917788 20914000 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 00114182 20917788 209177e8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace: Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] show_trace+0xf6/0x148) Mar 14 23:59:01 s8330018 kernel: [ 4972.486929] [<00114136>] show_stack+0x76/0xe8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486934] [<00518c26>] dump_stack+0x6e/0x90 Mar 14 23:59:01 s8330018 kernel: [ 4972.486937] [<0027c376>] bad_page+0xe6/0x148 Mar 14 23:59:01 s8330018 kernel: [ 4972.486938] [<00280516>] get_page_from_freelist+0x49e/0xba8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486940] [<00280ede>] __alloc_pages_nodemask+0x166/0xb00 Mar 14 23:59:01 s8330018 kernel: [ 4972.486941] [<0015635a>] s390_dma_alloc+0x82/0x1a0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486944] [<03ff805ea142>] __genwqe_alloc_consistent+0x7a/0x90 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486947] [<03ff805ea344>] genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486950] [<03ff805e52da>] do_execute_ddcb+0x1da/0x348 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486952] [<03ff805e5964>] genwqe_ioctl+0x51c/0xc20 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486953] [<003145ee>] do_vfs_ioctl+0x3b6/0x518 Mar 14 23:59:01 s8330018 kernel: [ 4972.486955] [<003147f4>] SyS_ioctl+0xa4/0xb8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486956] [<007ad1be>] system_call+0xd6/0x264 Mar 14 23:59:01 s8330018 kernel: [ 4972.486957] [<03ffa9df2492>] 0x3ffa9df2492 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1559194/+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 1620979] Re: Hotkey doesn't work on HP x360
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1620979 Title: Hotkey doesn't work on HP x360 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Committed Bug description: [Impact] When pinctrl-cherryview probing gpio device it clear interrupt mask and status, and in the later procedures the interrupt mask isn't set back correctly, leads to hotkeys fail. [Fix] Upstream fixes this in 4.8-rc3 by not clearing interrupt masks: commit bcb48cca23ec9852739e4a464307fa29515bbe48 Author: Mika Westerberg Date: Mon Aug 22 14:42:52 2016 +0300 pinctrl: cherryview: Do not mask all interrupts in probe To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1620979/+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 1634271] Re: arm64: kprobes disabled
** Changed in: linux (Ubuntu Yakkety) 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/1634271 Title: arm64: kprobes disabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: [Impact] kprobes is currently enabled for all Ubuntu architectures except arm64. This excludes a useful debug feature, which is required by certain userspace provided by Ubuntu, such as perf's probe command. I failed to notice this in my yakkety config review because it is a new feature in v4.8. [Test Case] = Failure case = ubuntu@arm64:~$ sudo perf probe schedule kprobe_events file does not exist - please rebuild kernel with CONFIG_KPROBE_EVENTS. Error: Failed to add events. = Success case = ubuntu@arm64:~$ sudo perf probe schedule Added new event: probe:schedule (on schedule) You can now use it in all perf tools, such as: perf record -e probe:schedule -aR sleep 1 ubuntu@arm64:~$ sudo perf record -e probe:schedule -aR sleep 1 [ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 0.185 MB perf.data (61 samples) ] [Regression Risk] The proposed fix enables a config for an already-upstream feature, so regressions will have upstream support. The config change mostly results in building new code vs. modifying existing code. The notable exception is that arm64's notify_page_fault() will now get code to call kprobe_fault_handler() - but only in the case that this newly enabled feature is being used (if kprobe_running()). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634271/+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 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
** 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/1633128
Title:
ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
In Progress
Bug description:
== Comment: #0 - Chanh H. Nguyen - 2016-06-02 14:22:00
==
There are a huge iommu_alloc failure on the dmesg log during our ST run on
the nvme card.
root@br502lp2:~# uname -r
4.4.0-22-generic
root@br502lp2:~# free -g
totalusedfree shared buff/cache
available
Mem:376 1 101 0 273
373
Swap:10 0 10
root@br502lp2:~# dmesg |grep "iommu_alloc"
[ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c351 npages 16
[ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c026 npages 16
[ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c35b npages 16
[ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c35b npages 16
[ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c02a6450 npages 16
[ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c02a6450 npages 16
[ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c03b80d1 npages 16
[ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c0290391 npages 16
[ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
root@br502lp2:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic
root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash
quiet crashkernel=384M-:128M
root@br502lp2:~# lsmcode
Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079)
(p) FW840.20 (SC840_100) (b)
Version of PFW is 14492016042881CF0681
== Comment: #4 - Mauricio Faria De Oliveira -
2016-10-13 10:16:40 ==
Hi Canonical,
This patch series that resolves this problem made linux mainline in the 4.9
merge window:
("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute")
Can you please apply it on 16.04.x?
Thanks!
Links/commits
---
[1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a
[2] "powerpc: implement the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723
[3] "nvme: use the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+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 1632844] Re: linux: 3.13.0-99.146 -proposed tracker
*** This bug is a duplicate of bug 1635430 *** https://bugs.launchpad.net/bugs/1635430 ** This bug has been marked a duplicate of bug 1635430 linux: 3.13.0-101.148 -proposed tracker -- 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/1632844 Title: linux: 3.13.0-99.146 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-99.146 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+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 1632368] Re: linux: 3.19.0-72.80 -proposed tracker
*** This bug is a duplicate of bug 1635424 *** https://bugs.launchpad.net/bugs/1635424 ** This bug has been marked a duplicate of bug 1635424 linux: 3.19.0-74.82 -proposed tracker -- 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/1632368 Title: linux: 3.19.0-72.80 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed 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-72.80 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632368/+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 1635377] dwalin (amd64) - tests ran: 6, failed: 3
tests ran: 6, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-27.29/dwalin__4.8.0-27.29__2016-10-26_14-28-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1635377] kernel02 (s390x.zVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_16-07-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1621088] Re: Fix bugs under virtual scsi server driver for Power
** Changed in: linux (Ubuntu Yakkety) 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/1621088 Title: Fix bugs under virtual scsi server driver for Power Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - BRYANT G. LY - 2016-09-06 12:16:14 == All three of these have been accepted into the 4.9/scsi-queue and scsi tree under misc ibmvscsis: Properly deregister target sessions - http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=712db3eb2c35e79986268bcd694ba8075445737d ibmvscsis: Code cleanup of print statements - http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=812902159d4174df9a82948c0445becb865dabec ibmvscsis: Fixed a bug reported by Dan Carpenter - http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=f6dbe38edf1ef4929847c90e244204ef4c6b3ce7 Still pending Review in target-devel mailing list: target/user: Return TCMU-generated sense data to fabric module - Is still under review under scsi and target-devel mailing list. http://www.spinics.net/lists/target-devel/msg13449.html TCM-User fixes and cleanups - http://www.spinics.net/lists/target-devel/msg13444.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1621088/+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 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...
Currently blocked on a grub SRU in xenial-proposed that isn't completely verified. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1527727 Title: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/... Status in grub: Unknown Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in grub2 source package in Xenial: In Progress Status in grub2-signed source package in Xenial: In Progress Status in zfs-linux source package in Xenial: Confirmed Bug description: [Impact] Installs over ZFS where a ZFS disk is expected to be used as a root device. [Test case] - Run update-grub on a system with a ZFS root filesystem. [Regression Potential] Installs relying on the current broken behavior to avoid listing other operating systems in grub menu may find that new entries are added. --- update-grub runs /usr/sbin/grub-probe Without libzfslinux support compiled in, /usr/sbin/grub-probe runs ["zpool", "status", poolname] to find out ZFS info. zpool responds with device names as used at (I think!) pool creation time. Often, this is /dev/disk/by-id/... names, without the path. grub-probe then parses the output, and takes the names of devices, and if they do not start with a "/", it prepends "/dev/". It then tests the existence of the path name of the device. it fails. grub-probe then returns something like /usr/sbin/grub-probe: error: failed to get canonical path of `/dev /ata-ST31000333AS_-part1'. The actual path is of course /dev/disk/by- id/ST31000333AS_-part1 It can prepend smarter than "/dev" or it can understand ZFS natively, to fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1527727/+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 1636847] Re: unexpectedly large memory usage of mounted snaps
After using the CONFING_SQUASHFS_DECOMP_SINGLE=y option in an experimental kernel the memory usage dropped significantly. The traces below are for -45 and the experimental -46 kernel. The 1 and 4 are the number of CPUs on the system. A single CPU system used to consumer 131MB per mounted snap, this is now reduced to just 4MB/snap. A four-CPU system has less dramatic improvement where the numbers are 7MB -> 4MB. This suggests some kind of bug in the CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU option perhaps + echo Ubuntu 16.04 Ubuntu 16.04 + ./analyze.py ubuntu 16.04 4.4.0-45-generic 1 size-1m.squashfs.xz.heavy # num-mounted extra-memory delta 0: 142.60MB 1: 274.71MB (delta: 132.11MB) 2: 406.55MB (delta: 131.84MB) 3: 538.36MB (delta: 131.81MB) 4: 670.19MB (delta: 131.82MB) + ./analyze.py ubuntu 16.04 4.4.0-46-generic 1 size-1m.squashfs.xz.heavy # num-mounted extra-memory delta 0: 62.28MB 1: 66.99MB (delta: 4.71MB) 2: 71.05MB (delta: 4.07MB) 3: 75.12MB (delta: 4.06MB) 4: 79.19MB (delta: 4.07MB) + ./analyze.py ubuntu 16.04 4.4.0-45-generic 4 size-1m.squashfs.xz.heavy # num-mounted extra-memory delta 0: 235.43MB 1: 242.38MB (delta: 6.96MB) 2: 249.38MB (delta: 7.00MB) 3: 256.45MB (delta: 7.06MB) 4: 263.42MB (delta: 6.97MB) + ./analyze.py ubuntu 16.04 4.4.0-46-generic 4 size-1m.squashfs.xz.heavy # num-mounted extra-memory delta 0: 72.79MB 1: 75.90MB (delta: 3.11MB) 2: 79.96MB (delta: 4.06MB) 3: 83.93MB (delta: 3.97MB) 4: 88.00MB (delta: 4.07MB) -- 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/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Confirmed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+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 1588479] Re: dkms_packages.py supported kernel check is not working
Done for xenial: [ 9:26AM 17170 ] [ bdmurray@impulse:~ ] $ sudo apt-get install dkms Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-34 linux-headers-4.4.0-34-generic linux-image-4.4.0-34-generic linux-image-extra-4.4.0-34-generic linux-tools-4.4.0-34 linux-tools-4.4.0-34-generic python3-requests-oauthlib Use 'sudo apt autoremove' to remove them. The following packages will be upgraded: dkms 1 upgraded, 0 newly installed, 0 to remove and 190 not upgraded. Need to get 66.1 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 dkms all 2.2.0.3-2ubuntu11.3 [66.1 kB] Fetched 66.1 kB in 0s (104 kB/s) Sorry, your system lacks support for the snapshot feature Reading changelogs... Done (Reading database ... 918737 files and directories currently installed.) Preparing to unpack .../dkms_2.2.0.3-2ubuntu11.3_all.deb ... Unpacking dkms (2.2.0.3-2ubuntu11.3) over (2.2.0.3-2ubuntu11.2) ... Processing triggers for man-db (2.7.5-1) ... Setting up dkms (2.2.0.3-2ubuntu11.3) ... [ 9:26AM 17171 ] [ bdmurray@impulse:~ ] $ python3 /usr/share/apport/package-hooks/dkms_packages.py -m bbswitch -v 0.8 -k 4.6.1-01234-lowlatency ERROR (dkms apport): kernel package linux-headers-4.6.1-01234-lowlatency is not supported -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1588479 Title: dkms_packages.py supported kernel check is not working Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Trusty: Fix Committed Status in dkms source package in Xenial: Fix Committed Status in dkms source package in Yakkety: Fix Released Bug description: Test Case - 1) Look for some dkms package in /usr/src e.g. bbswitch-0.8 2) Run python3 /usr/share/apport/package-hooks/dkms_packages.py -m bbswitch -v 0.8 -k 4.6.1-01234-lowlatency 3) Observe a crash report dialog from apport for bbswitch With the version of apport from -proposed you will instead receive: ERROR (dkms apport): kernel package linux- headers-4.6.1-01234-lowlatency is not supported The apport package hook for dkms packages seems to have an error in its supported kernel check. If the kernel is an unsupported one, the hook should exit with a return code of 1. However, in the Ubuntu Error Tracker we can see some crashes with unsupported kernel versions e.g.: https://errors.ubuntu.com/oops/2733d742-284e-11e6-a745-fa163e839e11 DKMSKernelVersion: 4.6.1-040601-lowlatency https://errors.ubuntu.com/oops/0a1afefc-253c-11e6-9082-fa163e192766 DKMSKernelVersion: 4.6.0-040600-lowlatency If the intent really is to block creation of these reports, then let's do that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1588479/+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 1588479] Re: dkms_packages.py supported kernel check is not working
Verified for Trusty too: Setting up dkms (2.2.0.3-1.1ubuntu5.14.04.9) ... bdmurray@upgrade-trusty-amd64:~$ python3 /usr/share/apport/package-hooks/dkms_packages.py -m bbswitch -v 0.7 -k 4.6.1-01234-lowlatency ERROR (dkms apport): kernel package linux-headers-4.6.1-01234-lowlatency is not supported ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1588479 Title: dkms_packages.py supported kernel check is not working Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Trusty: Fix Committed Status in dkms source package in Xenial: Fix Committed Status in dkms source package in Yakkety: Fix Released Bug description: Test Case - 1) Look for some dkms package in /usr/src e.g. bbswitch-0.8 2) Run python3 /usr/share/apport/package-hooks/dkms_packages.py -m bbswitch -v 0.8 -k 4.6.1-01234-lowlatency 3) Observe a crash report dialog from apport for bbswitch With the version of apport from -proposed you will instead receive: ERROR (dkms apport): kernel package linux- headers-4.6.1-01234-lowlatency is not supported The apport package hook for dkms packages seems to have an error in its supported kernel check. If the kernel is an unsupported one, the hook should exit with a return code of 1. However, in the Ubuntu Error Tracker we can see some crashes with unsupported kernel versions e.g.: https://errors.ubuntu.com/oops/2733d742-284e-11e6-a745-fa163e839e11 DKMSKernelVersion: 4.6.1-040601-lowlatency https://errors.ubuntu.com/oops/0a1afefc-253c-11e6-9082-fa163e192766 DKMSKernelVersion: 4.6.0-040600-lowlatency If the intent really is to block creation of these reports, then let's do that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1588479/+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 1636847] Re: unexpectedly large memory usage of mounted snaps
** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Andy Whitcroft (apw) -- 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/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+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 1632786] Re: [Hyper-V] do not lose pending heartbeat vmbus packets
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Precise)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Yakkety)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Yakkety)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Precise)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
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/1632786
Title:
[Hyper-V] do not lose pending heartbeat vmbus packets
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Precise:
In Progress
Status in linux source package in Trusty:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Yakkety:
In Progress
Bug description:
Hyper-V hosts can continue sending heartbeat packets to guests
independent of whether earlier packets have responses, which led to a
potential issue of these packets being dropped when responses took too
long to process. Lost heartbeats will lead to the host diagnosing that
the guest is dead and should be shut down and restarted.
The following patch was submitted upstream but has not yet been
accepted. I will add the upstream commit ID once the patch goes into
linux-next:
From: Long Li
The host keeps sending heartbeat packets independent of the
guest responding to them. Even though we respond to the heartbeat messages at
interrupt level, we can have situations where there maybe multiple heartbeat
messages pending that have not been responded to. For instance this occurs
when the
VM is paused and the host continues to send the heartbeat messages.
Address this issue by draining and responding to all
the heartbeat messages that maybe pending.
Signed-off-by: Long Li
Signed-off-by: K. Y. Srinivasan
CC: Stable
---
V2: Submit the patch to stable as well - Joshua R. Poulson
drivers/hv/hv_util.c | 10 +++---
1 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/hv/hv_util.c b/drivers/hv/hv_util.c
index 4aa3cb6..bcd0630 100644
--- a/drivers/hv/hv_util.c
+++ b/drivers/hv/hv_util.c
@@ -314,10 +314,14 @@ static void heartbeat_onchannelcallback(void *context)
u8 *hbeat_txf_buf = util_heartbeat.recv_buffer;
struct icmsg_negotiate *negop = NULL;
- vmbus_recvpacket(channel, hbeat_txf_buf,
-PAGE_SIZE, &recvlen, &requestid);
+ while (1) {
+
+ vmbus_recvpacket(channel, hbeat_txf_buf,
+PAGE_SIZE, &recvlen, &requestid);
+
+ if (!recvlen)
+ break;
- if (recvlen > 0) {
icmsghdrp = (struct icmsg_hdr *)&hbeat_txf_buf[
sizeof(struct vmbuspipe_hdr)];
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632786/+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 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915
@bitgandtter Intel added driver support for hardware that is not released yet, so there are no available firmware. The only affect it has on any actual system is these warnings, it's nothing to worry about. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1611124 Title: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 Status in xen: Unknown Status in linux-firmware package in Ubuntu: Invalid Bug description: $sudo dpkg -i linux-image-4.8.0-040800rc1-lowlatency [...] update-initramfs: Generating /boot/initrd.img-4.8.0-040800rc1-lowlatency W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-firmware 1.159 Uname: Linux 4.8.0-040800rc1-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 Date: Mon Aug 8 17:50:38 2016 Dependencies: InstallationDate: Installed on 2015-07-26 (379 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xen/+bug/1611124/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
Can you give 4.5-rc1 a test? It is available from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc1-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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1613925] Re: System locks up after issuing a sas3ircu storage management command during RAID rebuild
Broadcom found root cause and proposed the following fix: https://marc.info/?l=linux-block&m=147731657127810&w=2 -- 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/1613925 Title: System locks up after issuing a sas3ircu storage management command during RAID rebuild Status in linux package in Ubuntu: Incomplete Bug description: We have a PPC system on Ubuntu 16.04.1 LTS that will lock up if we issue a display or status command to the RAID controller during RAID rebuild process. The HDDs where the Operating system resides will change to RO (Read Only) once we trigger the problem. This will only occur if the Operating System's HDDs are also connected to the RAID controller. We've tried this problem with the OS residing on a USB and this problem does not occur. Apport is not writing or reporting anything in the "/etc/apport/" directory "ubuntu-bug" is not accessible after the crash. Ubuntu 16.04.1 LTS 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le PPC64EL (Power8) RAID Controller: LSI SAS3008 - Driver: mpt3sas - Driver version: 12.100.00.00 HDDs: - 2x WD Re SATA WD5003ABYZ-011FA0 (RAID0 / OS resides) - 2x Seagate ST6000NM0034 (FW: E001) (RAID1) 1.) Ubuntu 16.04.1 LTS 2.) 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le 3.) A driver update to prevent this from crashing the system. 4.) The system crashed. Please read the first paragraph above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udisks2 (not installed) ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic ppc64le ApportVersion: 2.20.1-0ubuntu2.1 Architecture: ppc64el Date: Tue Aug 16 18:23:32 2016 InstallationDate: Installed on 2016-08-16 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release ppc64el (20160719) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcLoadAvg: 0.00 0.01 0.00 1/1117 9416 ProcLocks: 1: FLOCK ADVISORY WRITE 7727 00:17:5 0 EOF 2: FLOCK ADVISORY WRITE 7723 00:14:631 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/sda3 partition394321280 -1 ProcVersion: Linux version 4.4.0-31-generic (buildd@bos01-ppc64el-028) (gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613925/+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 1559194] linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb
--- Comment on attachment From geral...@de.ibm.com 2016-09-06 10:25 EDT--- Debian kernel package with genwqe-bad-page.patch applied. ** Attachment added: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/bugs/1559194/+attachment/4767763/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb -- 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/1559194 Title: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - Dmitry Gorbachev - 2016-03-17 08:52:41 == An error occurs when running zEDC compression/decompression and hotplugging PCI devices. There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled. Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in process genwqe_gunzip pfn:3c275 Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 count:-1 mapcount:0 mapping: (null) index:0x0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0() Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero _count Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) dasd_eckd_mod(E) dasd_mod(E) Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: genwqe_gunzip Tainted: GW E 4.4.0-8-generic #23-Ubuntu Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 20917788 0002 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 209177a0 209177a0 00114182 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 0092345a 03d1000a 000a Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 20917788 20914000 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 00114182 20917788 209177e8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace: Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] show_trace+0xf6/0x148) Mar 14 23:59:01 s8330018 kernel: [ 4972.486929] [<00114136>] show_stack+0x76/0xe8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486934] [<00518c26>] dump_stack+0x6e/0x90 Mar 14 23:59:01 s8330018 kernel: [ 4972.486937] [<0027c376>] bad_page+0xe6/0x148 Mar 14 23:59:01 s8330018 kernel: [ 4972.486938] [<00280516>] get_page_from_freelist+0x49e/0xba8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486940] [<00280ede>] __alloc_pages_nodemask+0x166/0xb00 Mar 14 23:59:01 s8330018 kernel: [ 4972.486941] [<0015635a>] s390_dma_alloc+0x82/0x1a0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486944] [<03ff805ea142>] __genwqe_alloc_consistent+0x7a/0x90 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486947] [<03ff805ea344>] genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486950] [<03ff805e52da>] do_execute_ddcb+0x1da/0x348 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486952] [<03ff805e5964>] genwqe_ioctl+0x51c/0xc20 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486953] [<003145ee>] do_vfs_ioctl+0x3b6/0x518 Mar 14 23:59:01 s8330018 kernel: [ 4972.486955] [<003147f4>] SyS_ioctl+0xa4/0xb8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486956] [<007ad1be>] system_call+0xd6/0x264 Mar 14 23:59:01 s8330018 kernel: [ 4972.486957] [<03ffa9df2492>] 0x3ffa9df2492 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1559194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel
[Kernel-packages] [Bug 1636847] Re: unexpectedly large memory usage of mounted snaps
** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Yakkety) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: linux (Ubuntu Zesty) Importance: Medium Assignee: Colin Ian King (colin-king) Status: 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/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+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 1635377] kernel02 (s390x.zVM) - tests ran: 10, failed: 2
tests ran: 10, failed: 2; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_16-17-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1562778] Re: I2C touchscreen init failed on HP X360
** Changed in: linux (Ubuntu Wily) Assignee: Phidias (phidias-chiang) => (unassigned) ** Changed in: linux (Ubuntu Wily) Status: In Progress => Won't Fix ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1562778 Title: I2C touchscreen init failed on HP X360 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Won't Fix Status in linux source package in Xenial: Fix Released Bug description: [Impact] As title, after upgrading to latest Vivid kernel the touchscreen failed. After bisecting shows this revert cause the regression: commit 95df597989f6f297db63dd8669656d10f5f48eb1 Author: Andy Shevchenko Date: Fri Dec 4 23:49:18 2015 +0200 Revert "ACPI / LPSS: allow to use specific PM domain during ->probe()" [Fix] The reverted patch has had a revised version upstreamed: commit de16d55206c5ce82ad44590b01718fbe2323853c Author: Andy Shevchenko Date: Fri Dec 4 23:49:19 2015 +0200 ACPI / LPSS: allow to use specific PM domain during ->probe() For Vivid it depends on a patch to device core for adding BUS_NOTIFY_DRIVER_NOT_BOUND notification, both are clean cherry-pick. For Xenial the touchscreen still works because the original patch is not reverted, and with the patch reverted the I2C touchscreen still works fine, so I'll skip Xenial for this patch. For Wily it also contains the revert patch as Vivid, but the I2C on X360 still works. [Test] 3.19.0-56 -> Failed 3.19.0-56 + patches -> OK (Including suspend) 4.2.0-34 (with revert patch already) -> OK 4.4.0-15 -> OK 4.4.0-15 + revert patch -> OK 4.4.0-15 + patches -> N/A To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1562778/+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 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
** Changed in: linux (Ubuntu Yakkety)
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/1633128
Title:
ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Bug description:
== Comment: #0 - Chanh H. Nguyen - 2016-06-02 14:22:00
==
There are a huge iommu_alloc failure on the dmesg log during our ST run on
the nvme card.
root@br502lp2:~# uname -r
4.4.0-22-generic
root@br502lp2:~# free -g
totalusedfree shared buff/cache
available
Mem:376 1 101 0 273
373
Swap:10 0 10
root@br502lp2:~# dmesg |grep "iommu_alloc"
[ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c351 npages 16
[ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c026 npages 16
[ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c35b npages 16
[ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c35b npages 16
[ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c02a6450 npages 16
[ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c02a6450 npages 16
[ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c03b80d1 npages 16
[ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c0290391 npages 16
[ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
root@br502lp2:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic
root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash
quiet crashkernel=384M-:128M
root@br502lp2:~# lsmcode
Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079)
(p) FW840.20 (SC840_100) (b)
Version of PFW is 14492016042881CF0681
== Comment: #4 - Mauricio Faria De Oliveira -
2016-10-13 10:16:40 ==
Hi Canonical,
This patch series that resolves this problem made linux mainline in the 4.9
merge window:
("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute")
Can you please apply it on 16.04.x?
Thanks!
Links/commits
---
[1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a
[2] "powerpc: implement the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723
[3] "nvme: use the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+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 1635377] kernel02 (s390x.zVM) - tests ran: 18, failed: 1
tests ran: 18, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_17-06-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1636941] [NEW] linux: 4.4.0-47.68 -proposed tracker
Public bug reported: This bug is for tracking the 4.4.0-47.68 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: block-proposed-xenial kernel-release-tracking-bug xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-xenial ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-p
[Kernel-packages] [Bug 1636940] [NEW] linux: 4.4.0-46.67 -proposed tracker
Public bug reported: This bug is for tracking the 4.4.0-46.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed-xenial kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-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/1636940 Title: linux: 4.4.0-46.67 -proposed tracker Status in linux package in Ubuntu: New Bug description: This bug is for tracking the 4.4.0-46.67 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636940/+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 1635377] kernel02 (s390x.zVM) - tests ran: 5, failed: 3
tests ran: 5, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_17-38-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1636941] Re: linux: 4.4.0-47.68 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-signed 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/1636941 Title: linux: 4.4.0-47.68 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-47.68 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-phase:Packaging kernel-stable-phase-changed:Wednesday, 26. October 2016 18:02 UTC -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1636941/+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 1608236] Re: Regression: S-video output does not work
It does not have the 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/1608236 Title: Regression: S-video output does not work Status in linux package in Ubuntu: Confirmed Bug description: Regression. S-video output can not be used. It works by 4.4.0-22-generic. xrandr tells on 4.4.0-31-generic: TV1 unknown connection (normal left inverted right x axis y axis) 848x480 50.00 + 640x480 50.00 + 1024x768 50.00 800x600 50.00 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1573 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 31 17:15:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (94 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1636941] Packages available
Derivative packages from packages here can be worked on, the following tracking bugs were opened for them: linux-raspi2 - bug 1636946 linux-snapdragon - bug 1636948 Backport packages from packages here can be worked on, the following tracking bugs were opened for them: linux-lts-xenial (14.04.1) - bug 1636951 ** Description changed: This bug is for tracking the 4.4.0-47.68 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-phase:Packaging + kernel-stable-phase-changed:Wednesday, 26. October 2016 18:02 UTC ** Description changed: This bug is for tracking the 4.4.0-47.68 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-phase:Packaging kernel-stable-phase-changed:Wednesday, 26. October 2016 18:02 UTC + + -- swm properties -- + derivative-trackers-created: true + phase: Packaging -- 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/1636941 Title: linux: 4.4.0-47.68 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-47.68 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-phase:Packaging kernel-stable-phase-changed:Wednesday, 26. October 2016 18:02 UTC -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1636941/+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 1626436] Re: [4.8 regression] boot has become very slow
I built the another test kernel, up to the same commit: 7afd16f882887c9adc69cd1794f5e5723217 This kernel also has the two patches. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1626436 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/1626436 Title: [4.8 regression] boot has become very slow Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: With yakkety's recent update from linux 4.4 to 4.8 booting has become a lot slower. It's not one service in particular, but without "quiet" and "splash" you can now easily read every single line instead of that whole wall of text zipping by. It now takes over 20s instead of ~10 seconds to boot. This is even more dramatic when factoring out the recent boot hang of NetworkManager (bug 1622893) and disabling lightdm: sudo systemctl mask NetworkManager NetworkManager-wait-online lightdm then booting with 4.4 takes 1.5s and with 4.8 19.5s (!). Some excerps from systemd-analyze blame: 4.4: 474ms postfix@-.service 395ms lxd-containers.service 305ms networking.service 4.8: 4.578s postfix@-.service 7.300s lxd-containers.service 6.285s networking.service I attach the full outputs of critical-chain and analyze for 4.4 and 4.8 for reference. This is much less noticeable in the running system. There is no immediate feeling of sluggishness (although my system is by and large idle). I compared the time of sbuilding colord under similar circumstances (-j4, building on tmpfs, thus no hard disk delays; running with fully pre-loaded apt-cacher-ng thus no random network delays), and with 4.4 it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit slower, but much less dramatically than during boot, so this is either happening when a lot of processes run in parallel, or is perhaps related to setting up cgroups. One thing I noticed that during sbuild in 4.8 "top" shows ridiculous loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that doesn't reflect in actual sluggishness, so this might be just an unrelated bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-11-generic 4.8.0-11.12 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: martin 3049 F...m pulseaudio /dev/snd/pcmC0D0p: martin 3049 F...m pulseaudio /dev/snd/controlC0: martin 3049 F pulseaudio Date: Thu Sep 22 09:42:56 2016 EcryptfsInUse: Yes MachineType: LENOVO 2324CTO ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ systemd.debug-shell RelatedPackageVersions: linux-restricted-modules-4.8.0-11-generic N/A linux-backports-modules-4.8.0-11-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324CTO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 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:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2324CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436/+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 1635377] kernel02 (s390x.zVM) - tests ran: 33, failed: 1
tests ran: 33, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_17-50-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1630063] Re: specific USB devices disconnect and don't reconnect
I also run into this "HcDoneHead not written back; disabled" problem with the latest self compiled kernel 4.8.4 on debian 8. And the disappearing device is an "Eaton 5S 700" ups. It works with the last 4.7.10 without problems. So for the moment i will stick to 4.7.10. -- 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/1630063 Title: specific USB devices disconnect and don't reconnect Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: 2 USB ports randomly disconnect and don't reconnect (it's always the same two), and in dmesg all I get is " [ 1276.916458] ohci-pci :00:12.0: HcDoneHead not written back; disabled [ 1276.916467] ohci-pci :00:12.0: HC died; cleaning up [ 1276.916553] usb 3-1: USB disconnect, device number 2 [ 1277.017302] usb 3-2: USB disconnect, device number 3 " This only started happening when Yakkety went to the 4.8 branch, with 4.7 branch this doesn't occur, hence the bug report since it's unlikely that a hardware failure will only stick to one OS and one branch of the kernel for that OS. (these USB ports don't randomly die on Windows or BSD, I've tested that in the past couple of days) kernel version: 4.8.0.17.27 Ubuntu version Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: c_smith2213 F pulseaudio /dev/snd/controlC0: c_smith2213 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1a29baaa-55ea-4817-ba45-8c618f65ec4b InstallationDate: Installed on 2016-10-03 (0 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161002) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic root=/dev/mapper/Linux-root ro nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-generic N/A linux-backports-modules-4.8.0-17-generic N/A linux-firmware1.161 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: GA-78LMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630063/+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 1634892] Re: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error
I built another Trusty test kernel. However, this kernel is with a cherry pick of commit 9ecf07a1d8f7 and without the reverts. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1634892/ Can you test this kernel and see if it resolves this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634892 Title: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on the 3.13.0-96-generic kernel and below worked fine using the following: $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128 128 As of 3.13.0-97-generic, though, it no longer works as expected: $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128 error: "Invalid argument" setting key "net.ipv4.neigh.default.gc_thresh1" There are two potentially related revisions in the -97 release - http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts- backport-trusty&id=563cf19389d8e999e69d6c94995966aeaf7c3a08 and http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts- backport-trusty&id=7b82096b0ebc9bf487b390fe970d66ffa5a5774e. The expected behavior is that changing neighbor table settings works using 'sysctl -w' with the same values as before the -97 kernel. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-98-generic 3.13.0-98.145~precise1 ProcVersionSignature: Ubuntu 3.13.0-98.145~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-98-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-98-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory CurrentDmesg: [4.586115] NET: Registered protocol family 40 Date: Wed Oct 19 06:13:36 2016 HibernationDevice: RESUME=UUID=d32abfeb-623f-4c11-ae4a-a7babe8c2139 InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140806.1) IwConfig: Error: [Errno 2] No such file or directory MachineType: VMware, Inc. VMware Virtual Platform MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic root=UUID=febea164-78c3-4d3a-a0ce-0f09990df608 ro find_preseed=/preseed.cfg noprompt quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-98-generic N/A linux-backports-modules-3.13.0-98-generic N/A linux-firmware 1.79.16 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634892/+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 1635377] kernel02 (s390x.zVM) - tests ran: 19, failed: 8
tests ran: 19, failed: 8; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_18-47-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+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 1636656] Re: [Hyper-V] netvsc: fix incorrect receive checksum offloading
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Medium Status: Triaged ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Triaged ** No longer affects: linux (Ubuntu Zesty) ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Vivid) Status: New => Triaged ** Changed in: linux (Ubuntu Trusty) Status: New => Triaged ** Changed in: linux (Ubuntu Precise) Status: New => Triaged ** Changed in: linux (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Medium ** Tags added: kernel-da-key kernel-hyper-v ** Tags added: bot-stop-nagging precise trusty vivid xenial yakkety -- 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/1636656 Title: [Hyper-V] netvsc: fix incorrect receive checksum offloading Status in linux package in Ubuntu: Triaged Status in linux source package in Precise: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Vivid: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Bug description: The Hyper-V netvsc driver was looking at the incorrect status bits in the checksum info. It was setting the receive checksum unnecessary flag based on the IP header checksum being correct. The checksum flag is skb is about TCP and UDP checksum status. Because of this bug, any packet received with bad TCP checksum would be passed up the stack and to the application causing data corruption. The problem is reproducible via netcat and netem. This had a side effect of not doing receive checksum offload on IPv6. The driver was also also always doing checksum offload independent of the checksum setting done via ethtool. Signed-off-by: Stephen Hemminger https://patchwork.ozlabs.org/patch/685660/ When this patch is committed I will include the commit ID in this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636656/+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
