[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
Logitec Mouse M185 works here again in 16.04 since kernel kernel 4.4.38 maybe one or two versions earlier. I discovered it by chance that it works again. -- 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/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10. Type: XIKeyClass Keycodes supported: 248 Class originated from: 10. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Does anyone have an idea how I can attempt to further debug that issue? Or maybe even a solution? Should I consider this issue a bug? Can I provide more info? --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toby 11625 F pulseaudio /dev/snd/controlC0: toby 11625 F pulseaudio /dev/snd/pcmC1D0p: toby 11625 F...m pulseaudio /dev/snd/controlC1: toby 11625 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5e3a6d2e-05f8-4d01-b80c-a9f200e6 InstallationDate: Installed on 2014-04-24 (749 days ago) InstallationMedia: Ubunt
[Kernel-packages] [Bug 1633321] Re: Fix alps driver for multitouch function.
** Tags added: originate-from-1611588 somerville ** Changed in: hwe-next Assignee: (unassigned) => Ying-Chun Liu (paulliu) -- 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/1633321 Title: Fix alps driver for multitouch function. Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: We need to cherry-pick 9a54cf462d6f3c383a5a4f5fe15c020a03db44e6 for alps touchpads. Otherwise the touchpad will stop working when we put more than 3 fingers on the pad. Please consider SRU this commit. Impact: Alps driver doesn't work when users put more than 3 fingers on it. Fix: Alps touchpad still works good after multitouch for more than 3 fingers. Tested: The patch is tested on new Dell Inspiron laptops and works very good. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1633321/+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 1227996] Re: [Lenovo IdeaPad Yoga 13] ubuntu doesn't know about Yoga screen rotation keycodes: atkbd serio0: Use 'setkeycodes e03e ' to make it known.
This is exactly the behavior I see on my machine. Linux shinobi 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux 66CN55WW 02/28/2013 -- 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/1227996 Title: [Lenovo IdeaPad Yoga 13] ubuntu doesn't know about Yoga screen rotation keycodes: atkbd serio0: Use 'setkeycodes e03e ' to make it known. Status in linux package in Ubuntu: Triaged Bug description: The following spam litters dmesg: [36294.989706] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [36294.995650] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [36294.995661] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [36296.016998] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [36296.017002] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [36296.021894] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [36296.021907] atkbd serio0: Use 'setkeycodes e03e ' to make it known. As can be seen, this occurs frequently. It might be related, but at times, the keyboard freezes for a few seconds and then starts sending a repeating character while no keys are pressed. This behavior is not stopped unless a key (any key) is pressed. The character that is output is a special character, but I don't know what combination it is specifically. This might be related to the fact that this is a lenovo yoga 13 ideapad. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-30-generic 3.8.0-30.44 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: noobermin 1991 F pulseaudio /dev/snd/pcmC0D0p: noobermin 1991 F...m pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Sep 20 02:07:54 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=7d95a03d-5f38-403f-84d9-51ebca691a4b InstallationDate: Installed on 2013-08-31 (19 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 20175 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=UUID=6a1575e6-9b6a-4086-988e-2efda2c80fd3 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-30-generic N/A linux-backports-modules-3.8.0-30-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 66CN52WW dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Yoga 13 dmi.modalias: dmi:bvnLENOVO:bvr66CN52WW:bd11/22/2012:svnLENOVO:pn20175:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13: dmi.product.name: 20175 dmi.product.version: Lenovo IdeaPad Yoga 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1227996/+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 1633321] Re: Fix alps driver for multitouch function.
** Description changed: We need to cherry-pick 9a54cf462d6f3c383a5a4f5fe15c020a03db44e6 for alps touchpads. Otherwise the touchpad will stop working when we put more than 3 fingers on the pad. Please consider SRU this commit. + + Impact: + Alps driver doesn't work when users put more than 3 fingers on it. + + Fix: + Alps touchpad still works good after multitouch for more than 3 fingers. + + Tested: + The patch is tested on new Dell Inspiron laptops and works very good. -- 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/1633321 Title: Fix alps driver for multitouch function. Status in linux package in Ubuntu: Incomplete Bug description: We need to cherry-pick 9a54cf462d6f3c383a5a4f5fe15c020a03db44e6 for alps touchpads. Otherwise the touchpad will stop working when we put more than 3 fingers on the pad. Please consider SRU this commit. Impact: Alps driver doesn't work when users put more than 3 fingers on it. Fix: Alps touchpad still works good after multitouch for more than 3 fingers. Tested: The patch is tested on new Dell Inspiron laptops and works very good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633321/+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 1624540] Re: please have lxd recommend zfs
> The udev event is going to fire before the pool is imported. So how does a pool get imported, what triggers that if it's not block devices appearing? Whatever does that import, couldn't that start zed.service then instead of the udev rule? -- 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/1624540 Title: please have lxd recommend zfs Status in lxd package in Ubuntu: Incomplete Status in zfs-linux package in Ubuntu: Confirmed Bug description: Since ZFS is now in Main (Bug #1532198), LXD should recommend the ZFS userspace package, such that 'sudo lxd init' just works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1624540/+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 1227996] Re: [Lenovo IdeaPad Yoga 13] ubuntu doesn't know about Yoga screen rotation keycodes: atkbd serio0: Use 'setkeycodes e03e ' to make it known.
I am also having this issue. It started happening for me when I was using ArchLinux during July of 2016; I was thinking about going back to Ubuntu, so I re-installed Lubuntu over Arch. Low and Behold, the issue persists. My issue is worse in that usually the key(s) that will trigger this repeated key is the arrow keys, which I frequently use to scroll up and down through man pages, web pages, etc. However, when this occurs, my keyboard no longer responds to input, and my mouse will start "falling" to whichever direction the arrow key corresponds (down arrow repeat will cause my mouse cursor to continuously move to the bottom of the screen). I noticed that my dmesg was being spammed with this error too, and when I (temporarily) set the keycodes to 255, the issue persists, but the error message will go away from dmesg. If my issue seems right for another new bug thread, please let me know. I'll provide what everyone else has been providing -- welcome to provide any information I can in order to address this bug. $ cat /etc/issue Ubuntu 16.04.1 LTS \n \l $ uname -a Linux masq-Lu 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux # dmidecode -s bios-version && dmidecode -s bios-release-date 66CN55WW 02/28/2013 Or if anyone knows generally what might be messed up, I'm pretty experienced using Linux, and I know some C... so I could theoretically fix it myself (I would post any successes I had here). Cheers -- 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/1227996 Title: [Lenovo IdeaPad Yoga 13] ubuntu doesn't know about Yoga screen rotation keycodes: atkbd serio0: Use 'setkeycodes e03e ' to make it known. Status in linux package in Ubuntu: Triaged Bug description: The following spam litters dmesg: [36294.989706] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [36294.995650] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [36294.995661] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [36296.016998] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [36296.017002] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [36296.021894] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [36296.021907] atkbd serio0: Use 'setkeycodes e03e ' to make it known. As can be seen, this occurs frequently. It might be related, but at times, the keyboard freezes for a few seconds and then starts sending a repeating character while no keys are pressed. This behavior is not stopped unless a key (any key) is pressed. The character that is output is a special character, but I don't know what combination it is specifically. This might be related to the fact that this is a lenovo yoga 13 ideapad. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-30-generic 3.8.0-30.44 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: noobermin 1991 F pulseaudio /dev/snd/pcmC0D0p: noobermin 1991 F...m pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Sep 20 02:07:54 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=7d95a03d-5f38-403f-84d9-51ebca691a4b InstallationDate: Installed on 2013-08-31 (19 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 20175 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=UUID=6a1575e6-9b6a-4086-988e-2efda2c80fd3 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-30-generic N/A linux-backports-modules-3.8.0-30-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 66CN52WW dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Yoga 13 dmi.modalias: dmi:bvnLENOVO:bvr66CN52WW:bd11/22/2012:svnLENOVO:pn20175:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13: dmi.product.name: 20175 dmi.product.version: Lenovo IdeaPad Yoga 13 dmi.sys.vendor: L
[Kernel-packages] [Bug 1613158] Re: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0)
I tried to purge nvidia proprietary drivers and boot with nouveau and got exactly the same issue. The only difference is my screen is just black. Same errors in dmesg: fifo: SCHED_ERROR 08 [] I use Nvidia GTX 970. -- 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/1613158 Title: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0) Status in linux package in Ubuntu: Invalid Bug description: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0). I've tried: * Plain yakkety 4.4.0-34-generic * Mainline kernel 4.7 * Mainline kernel 4.8rc1 and only the first one works. Kernels 4.7 and 4.8rc1 freeze with a bright orange screen. Best I can tell, the frozen orange screen coincides with kernel log messages: Aug 15 12:24:23 x51 kernel: [1.761197] fb: switching to nouveaufb from simple Aug 15 12:24:23 x51 kernel: [1.761210] Console: switching to colour dummy device 80x25 ... Aug 15 12:24:26 x51 kernel: [ 11.896160] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.897225] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.898292] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.899358] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.900423] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.901489] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.902555] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.903621] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.904686] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.905753] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.906818] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.907883] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.908949] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.910014] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.911079] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.912145] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.913210] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] ... ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613158/+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 1633321] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1633321 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/1633321 Title: Fix alps driver for multitouch function. Status in linux package in Ubuntu: Incomplete Bug description: We need to cherry-pick 9a54cf462d6f3c383a5a4f5fe15c020a03db44e6 for alps touchpads. Otherwise the touchpad will stop working when we put more than 3 fingers on the pad. Please consider SRU this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633321/+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 1633321] [NEW] Fix alps driver for multitouch function.
Public bug reported: We need to cherry-pick 9a54cf462d6f3c383a5a4f5fe15c020a03db44e6 for alps touchpads. Otherwise the touchpad will stop working when we put more than 3 fingers on the pad. Please consider SRU this commit. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Description changed: We need to cherry-pick 9a54cf462d6f3c383a5a4f5fe15c020a03db44e6 for alps touchpads. Otherwise the touchpad will stop working when we put more than 3 fingers on the pad. + + Please consider SRU this commit. -- 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/1633321 Title: Fix alps driver for multitouch function. Status in linux package in Ubuntu: Incomplete Bug description: We need to cherry-pick 9a54cf462d6f3c383a5a4f5fe15c020a03db44e6 for alps touchpads. Otherwise the touchpad will stop working when we put more than 3 fingers on the pad. Please consider SRU this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633321/+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 1632918] onza (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/onza__4.8.0-25.27__2016-10-14_04-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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1629714] Re: scsi host6: runtime PM trying to activate child device host6 but parent (3-1:1.0) is not active
Here's a kernel bug report on this: https://www.mail-archive.com/kernel-packages@lists.launchpad.net/msg201349.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/1629714 Title: scsi host6: runtime PM trying to activate child device host6 but parent (3-1:1.0) is not active Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: [ 7434.858833] scsi host6: runtime PM trying to activate child device host6 but parent (3-1:1.0) is not active ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19 ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7 Uname: Linux 4.8.0-17-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2140 F...m pulseaudio /dev/snd/controlC0: caravena 2140 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 2 19:32:49 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (434 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-lowlatency N/A linux-backports-modules-4.8.0-17-lowlatency N/A linux-firmware 1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1629714/+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 1629714] Re: scsi host6: runtime PM trying to activate child device host6 but parent (3-1:1.0) is not active
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1629714 Title: scsi host6: runtime PM trying to activate child device host6 but parent (3-1:1.0) is not active Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: [ 7434.858833] scsi host6: runtime PM trying to activate child device host6 but parent (3-1:1.0) is not active ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19 ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7 Uname: Linux 4.8.0-17-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2140 F...m pulseaudio /dev/snd/controlC0: caravena 2140 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 2 19:32:49 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (434 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-lowlatency N/A linux-backports-modules-4.8.0-17-lowlatency N/A linux-firmware 1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1629714/+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 was able to fix the issue by changing the IO_WATCHDOG_DELAY in ohci- hcd.c from 250 msec to 275 msec. I suspect that the new timer wheel based timers in 4.8 have exposed a bug in the ohci driver. Before the io watchdog timer was set to 250 with 20 msecs of slack time. This is more than likely just a hack work around but I'm able to use my usb headphones now. Here's my diff -bpaluch/media/bpaluch/f0c7f0e5-1628-458e-b05c-a92f73e9ed11/builds/ubuntu-yakkety ((e658052...))$ git diff diff --git a/drivers/usb/host/ohci-hcd.c b/drivers/usb/host/ohci-hcd.c index 1700908..86612ac 100644 --- a/drivers/usb/host/ohci-hcd.c +++ b/drivers/usb/host/ohci-hcd.c @@ -72,7 +72,7 @@ static const char hcd_name [] = "ohci_hcd"; #defineSTATECHANGE_DELAY msecs_to_jiffies(300) -#defineIO_WATCHDOG_DELAY msecs_to_jiffies(250) +#defineIO_WATCHDOG_DELAY msecs_to_jiffies(275) #include "ohci.h" #include "pci-quirks.h" -- 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 1630304] Re: Ubuntu 16.10 KVM: Issue doing hotplug detach to SRIOV VF
** Tags removed: severity-critical ** Tags added: severity-high -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630304 Title: Ubuntu 16.10 KVM: Issue doing hotplug detach to SRIOV VF Status in linux package in Ubuntu: New Bug description: ---Problem Description--- I can not get hotplug attach to work in Ubuntu but if I try to detach a CX4 VF from a guest I am getting some issues: Like in this case: [ 474.393308] vfio-pci 0001:01:00.3: No device request channel registered, blocked until released by user [ 474.393543] pci 0001:01: 0.3: [PE# 006] Removing DMA window #0 [ 474.393553] pci 0001:01: 0.3: [PE# 006] Removing DMA window #1 [ 474.393906] mlx5_core 0001:01:00.3: enabling device ( -> 0002) [ 474.393939] mlx5_core 0001:01:00.3: Using 32-bit DMA via iommu [ 474.400360] pci 0001:01: 0.3: [PE# 006] Setting up window#0 0..7fff pg=1000 [ 474.400380] mlx5_core 0001:01:00.3: firmware version: 12.17.226 [ 474.401341] pci 0001:01: 0.3: [PE# 006] Enabling 64-bit DMA bypass [ 474.402284] EEH: Frozen PE#6 on PHB#1 detected [ 474.402475] EEH: PE location: Slot4, PHB location: N/A [ 474.403699] EEH: This PCI device has failed 1 times in the last hour [ 474.403700] EEH: Notify device drivers to shutdown [ 474.403707] mlx5_core 0001:01:00.3: mlx5_pci_err_detected was called [ 474.403711] mlx5_core 0001:01:00.3: 0001:01:00.3:mlx5_enter_error_state:115:(pid 779): start [ 474.403870] mlx5_core 0001:01:00.3: 0001:01:00.3:mlx5_enter_error_state:120:(pid 779): end One time I saw SSep 13 09:41:32 ltc-fire1 kernel: [70437.943722] vfio-pci 0001:01:00.3: No device request channel registered, blocked until released by user Sep 13 09:41:32 ltc-fire1 kernel: [70437.944076] mlx5_core 0001:01:00.3: enabling device ( -> 0002) Sep 13 09:41:32 ltc-fire1 kernel: [70437.944110] mlx5_core 0001:01:00.3: Using 32-bit DMA via iommu Sep 13 09:41:32 ltc-fire1 kernel: [70437.944145] pci 0001:01: 0.3: [PE# 006] Removing DMA window #0 Sep 13 09:41:32 ltc-fire1 kernel: [70437.944152] pci 0001:01: 0.3: [PE# 006] Removing DMA window #1 Sep 13 09:41:32 ltc-fire1 kernel: [70437.944195] mlx5_core 0001:01:00.3: firmware version: 12.17.226 Sep 13 09:41:32 ltc-fire1 kernel: [70437.944260] Unable to handle kernel paging request for data at address 0x Sep 13 09:41:32 ltc-fire1 kernel: [70437.944533] Faulting instruction address: 0xc05b37e0 Sep 13 09:41:32 ltc-fire1 kernel: [70437.944592] Oops: Kernel access of bad area, sig: 11 [#1] Sep 13 09:41:32 ltc-fire1 kernel: [70437.944636] SMP NR_CPUS=2048 NUMA PowerNV Sep 13 09:41:32 ltc-fire1 kernel: [70437.944851] Modules linked in: vfio_pci irqbypass vfio_iommu_spapr_tce vfio_virqfd vfio vfio_spapr_eeh xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp kvm_hv kvm_pr kvm ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) mlx4_en(OE) ib_addr(OE) ib_netlink(OE) mlx4_core(OE) mlx_compat(OE) bridge stp llc joydev input_leds mac_hid ofpart at24 cmdlinepart powernv_flash ipmi_powernv nvmem_core uio_pdrv_genirq opal_prd mtd ipmi_msghandler uio ibmpowernv powernv_rng binfmt_misc dm_multipath knem(OE) ip_tables x_tables autofs4 hid_generic usbhid hid uas usb_storage ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sys imgblt fb_sys_fops drm ahci devlink libahci [last unloaded: mlx4_core] Sep 13 09:41:32 ltc-fire1 kernel: [70437.946007] CPU: 40 PID: 12501 Comm: libvirtd Tainted: G OE 4.7.0unofficial #5 Sep 13 09:41:32 ltc-fire1 kernel: [70437.946074] task: c00ec319a200 ti: c00ec324c000 task.ti: c00ec324c000 Sep 13 09:41:32 ltc-fire1 kernel: [70437.946140] NIP: c05b37e0 LR: c05ad070 CTR: Sep 13 09:41:32 ltc-fire1 kernel: [70437.946208] REGS: c00ec324f100 TRAP: 0300 Tainted: G OE(4.7.0unofficial) Sep 13 09:41:32 ltc-fire1 kernel: [70437.946286] MSR: 90010280b033 CR: 84028844 XER: 2000 Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] CFAR: c0008468 DAR: DSISR: 4000 SOFTE: 0 Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR00: c05d19c8 c00ec324f380 c13bef00 Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR04: Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR08: f3803140 Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR12: 000
[Kernel-packages] [Bug 1632918] onza (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/onza__4.8.0-25.27__2016-10-14_00-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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1632918] modoc (ppc64el) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/modoc__4.8.0-25.27__2016-10-14_00-21-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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1633223] Re: rcu_sched detected stalls with kernel 3.19.0-58, NVIDIA driver, and docker
Did you see #1533043? Check your version of aufs (`modinfo aufs`) -- 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/1633223 Title: rcu_sched detected stalls with kernel 3.19.0-58, NVIDIA driver, and docker Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Seeing occasional rcu_sched detected stalls on 14.04 LTS with kernel 3.19.0-58. The system is running docker containers, and has the NVIDIA GPU driver loaded. We've seen about 4 stalls in the last month, all with the 3.19.0-58 kernel, and with the NVIDIA 352.93 and 361.49 drivers. ---uname output--- Linux dldev1 3.19.0-58-generic #64~14.04.1-Ubuntu SMP Fri Mar 18 19:05:01 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- 2 x NVIDIA K80 GPU adapter: $ lspci | grep NV 0002:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 0002:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 0006:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 0006:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) Machine Type = 8247-42L ---System Hang--- Usual symptom is that the system is unresponsive except maybe for ping and writing the stall-detection messages to the console. Login/getty isn't available either via ssh nor on the console. System must be power cycled to recover. Attached is the kernel log from a stall detection on May 18th. The detection first occurs at: May 18 15:17:55. The system is later rebooted and those messages indicate the kernel (3.19.0-58) and NVIDIA driver version (352.93) that were active at the time. We've suffered 3 or 4 stalls since, all with the same kernel, but some with a newer NVIDIA driver (361.49). Unfortunately, information about the newer stalls wasn't preserved in the various log files (and we're not capturing the console constantly), so we don't have detailed data for those. We'd welcome any suggestions for how to collect additional data for these occurrences. I can't say for sure that we haven't seen the stalls on other systems, but they're occuring fairly frequently on this system, and it's unusual in that it's running both Docker and NVIDIA GPU driver. So maybe aufs or the NVIDIA driver are somehow involved. From the kern.log, The Call trace points to some kind of deadlock in aufs - May 18 15:17:55 dldev1 kernel: [713670.798624] Task dump for CPU 3: May 18 15:17:55 dldev1 kernel: [713670.798628] cc1 R running task0 99183 99173 0x00040004 May 18 15:17:55 dldev1 kernel: [713670.798633] Call Trace: May 18 15:17:55 dldev1 kernel: [713670.798643] [c00fa64673a0] [c00cf004] wake_up_worker+0x44/0x60 (unreliable) May 18 15:17:55 dldev1 kernel: [713670.798671] [c00fa6467570] [c00fa64675d0] 0xc00fa64675d0 May 18 15:17:55 dldev1 kernel: [713670.798676] [c00fa64675d0] [c0a1b050] __schedule+0x370/0x900 May 18 15:17:55 dldev1 kernel: [713670.798679] [c00fa64677f0] [c00fa6467850] 0xc00fa6467850 May 18 15:17:55 dldev1 kernel: [713670.798682] Task dump for CPU 75: May 18 15:17:55 dldev1 kernel: [713670.798684] cc1 D 105d9410 0 99427 99405 0x00040004 May 18 15:17:55 dldev1 kernel: [713670.798688] Call Trace: May 18 15:17:55 dldev1 kernel: [713670.798691] [c017efdd3460] [c017efdd34a0] 0xc017efdd34a0 (unreliable) May 18 15:17:55 dldev1 kernel: [713670.798695] [c017efdd3630] [c017efdd3690] 0xc017efdd3690 May 18 15:17:55 dldev1 kernel: [713670.798698] [c017efdd3690] [c0a1b050] __schedule+0x370/0x900 May 18 15:17:55 dldev1 kernel: [713670.798702] [c017efdd38b0] [c0a1f128] rwsem_down_write_failed+0x288/0x400 May 18 15:17:55 dldev1 kernel: [713670.798706] [c017efdd3940] [c0a1e538] down_write+0x88/0x90 May 18 15:17:55 dldev1 kernel: [713670.798716] [c017efdd3970] [d0001ead562c] do_ii_write_lock+0x8c/0xd0 [aufs] May 18 15:17:55 dldev1 kernel: [713670.798724] [c017efdd39a0] [d0001eac0e98] aufs_read_lock+0xb8/0xd0 [aufs] May 18 15:17:55 dldev1 kernel: [713670.798733] [c017efdd39e0] [d0001ead8208] aufs_d_revalidate+0x98/0x7a0 [aufs] May 18 15:17:55 dldev1 kernel: [713670.798737] [c017efdd3aa0] [c02c88f8] lookup_fast+0x368/0x3b0 May 18 15:17:55 dldev1 kernel: [713670.798740] [c017efdd3b10] [c02cb620] path_lookupat+0x180/0x970 May 18 15:17:55 dldev1 kernel: [713670.798743] [c017efdd3be0] [c02cbe68] filename_lookup+0x58/0x140 May 18 15:17:55 dldev1 kernel: [713670.798746] [c017efdd3c30] [c02cde04] user_path_at_empty+0x84/0xe0 May 18 15:17:55 dldev1 kernel: [713670.798749] [c017efdd3d20] [c02be744] vfs_fstatat+0x84/0x140 M
[Kernel-packages] [Bug 1633267] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1633267/+attachment/4760666/+files/WifiSyslog.txt ** 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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1633267] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1633267/+attachment/4760665/+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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
I was able to backport the two patches to Trusty. It required quite a few prerequisite commits. The following commits were backported to a Trusty test kernel: f9cc88d lp1470250: patch from faulpeltz 6f3e8a2 Drivers: hv: utils: Continue to poll VSS channel after handling requests. 725a85d Drivers: hv: utils: fix a race on userspace daemons registration a0c12c6 Drivers: hv: kvp: fix IP Failover 51fea7d Drivers: hv: utils: Invoke the poll function after handshake 42fb309 Drivers: hv: utils: run polling callback always in interrupt context 505de58 Drivers: hv: fcopy: full handshake support 2ec9789 Drivers: hv: vss: full handshake support e12c519 Tools: hv: vss: use misc char device to communicate with kernel 1f3abc0 Drivers: hv: kvp: convert to hv_utils_transport d789589 Drivers: hv: fcopy: convert to hv_utils_transport 51ed5da Drivers: hv: vss: convert to hv_utils_transport edbff5d Drivers: hv: util: introduce hv_utils_transport abstraction 056fbb5 Drivers: hv: fcopy: switch to using the hvutil_device_state state machine 5eb0af4 Drivers: hv: vss: switch to using the hvutil_device_state state machine a170e78 Drivers: hv: kvp: switch to using the hvutil_device_state state machine a539598 Drivers: hv: fcopy: rename fcopy_work -> fcopy_timeout_work 7894b35 Drivers: hv: kvp: rename kvp_work -> kvp_timeout_work d3fc031 Drivers: hv: kvp,vss: Fast propagation of userspace communication failure ee85362 Drivers: hv: vss: Introduce timeout for communication with userspace d714c5a Tools: hv: vssdaemon: ignore the EBUSY on multiple freezing the same partition b957545 connector: add portid to unicast in addition to broadcasting The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1470250/AlexFaulpeltzPatch/trusty/ Can this kernel be tested to see if it resolves this bug? Note, that both the linux-image and linux-image-extra .deb packages need to be installed. -- 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/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: 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: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here).As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~ker
[Kernel-packages] [Bug 1633267] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1633267/+attachment/4760664/+files/RfKill.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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1633267] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1633267/+attachment/4760662/+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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1633267] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1633267/+attachment/4760661/+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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1633267] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1633267/+attachment/4760663/+files/PulseList.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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1633267] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1633267/+attachment/4760656/+files/IwConfig.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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1633267] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1633267/+attachment/4760659/+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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1633267] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1633267/+attachment/4760653/+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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1633267] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1633267/+attachment/4760655/+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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1633267] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1633267/+attachment/4760660/+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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1633267] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1633267/+attachment/4760654/+files/CRDA.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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1633267] Re: Wifi, sound not detected when booting on 4.4.0-43
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+attachment/4760652/+files/version.log ** Tags added: apport-collected ** Description changed: - I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to - 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or - sound hardware: there was no Wifi icon or ability to connect to a - network, and the only output on the sound menu was "Dummy Output." - Rebooting into 4.4.0-42 solved the issue. + I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. + --- + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: matt 3400 F pulseaudio + /dev/snd/controlC1: matt 3400 F pulseaudio + CurrentDesktop: GNOME + DistroRelease: Ubuntu 16.04 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 + InstallationDate: Installed on 2015-08-23 (417 days ago) + InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) + MachineType: LENOVO 20ANCTO1WW + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-42-generic N/A + linux-backports-modules-4.4.0-42-generic N/A + linux-firmware1.157.4 + Tags: xenial + Uname: Linux 4.4.0-42-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/18/2016 + dmi.bios.vendor: LENOVO + dmi.bios.version: GLET84WW (2.38 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20ANCTO1WW + dmi.board.vendor: LENOVO + dmi.board.version: 0B98405 STD + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.name: 20ANCTO1WW + dmi.product.version: ThinkPad T440p + dmi.sys.vendor: LENOVO -- 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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.ch
[Kernel-packages] [Bug 1633267] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1633267/+attachment/4760657/+files/JournalErrors.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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1633267] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1633267/+attachment/4760658/+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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1633267] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1633267 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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 3400 F pulseaudio /dev/snd/controlC1: matt 3400 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423 InstallationDate: Installed on 2015-08-23 (417 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20ANCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic.efi.signed root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET84WW (2.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1632918] kernel02 (s390x.zVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-21.23/kernel02__4.8.0-21.23__2016-10-13_23-49-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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-21.23/s2lp6g002__4.8.0-21.23__2016-10-13_23-49-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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1633267] [NEW] Wifi, sound not detected when booting on 4.4.0-43
Public bug reported: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: kernel-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/1633267 Title: Wifi, sound not detected when booting on 4.4.0-43 Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or sound hardware: there was no Wifi icon or ability to connect to a network, and the only output on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633267/+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 1633172] Re: Linux 4.8 as in 16.10 hangs during boot
Same thing here in a VMWare virtual machine. It sometimes starts into X11 (xfce) and hangs after a view seconds. -- 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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Confirmed Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1627496] Re: radeon broken with kernel 4.6.0+
** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627496 Title: radeon broken with kernel 4.6.0+ Status in linux package in Ubuntu: Confirmed Bug description: Hello Guys, I'm currently running an up-to-date Xenial system on amd64 (PC) platform. Whenever I launch the OS with stock kernel (4.4.X) all seems good. Whenever I launch the OS with let's say a mainline-PPA kernel whose version is above 4.6.0 inclusive (4.5.X are functional), or stock yakkety kernel nowadays (4.8.X), kernel fails to setup my graphics card, whose description is appended in a few text files I joined to this message. In hope this helps, Sincelely, Vécu P.S. : I very suspect this is a mainstream bug ; for any complimentary info. please don't hesitate to post and ask for more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 25 15:23:08 2016 DistUpgraded: 2016-04-23 10:48:41,985 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Radeon HD 7670M [1179:fb41] InstallationDate: Installed on 2015-05-01 (512 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: TOSHIBA SATELLITE L875-10G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-16-generic root=UUID=fb0648bd-7019-4cb2-b5b3-382141e3716a ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-23 (155 days ago) dmi.bios.date: 3/25/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.50:bd3/25/2013:svnTOSHIBA:pnSATELLITEL875-10G:pvrPSKBLE-003006FR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE L875-10G dmi.product.version: PSKBLE-003006FR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs 1.0 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Sep 25 15:10:31 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627496/+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 1631126] Re: package linux-image-extra-4.4.0-38-generic (not installed) failed to install/upgrade: no hay instalado ningún paquete llamado `linux-image-extra-4.4.0-38-generic',
** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1631126 Title: package linux-image-extra-4.4.0-38-generic (not installed) failed to install/upgrade: no hay instalado ningún paquete llamado `linux-image- extra-4.4.0-38-generic', no se puede configurar Status in linux package in Ubuntu: Confirmed Bug description: Al actualizar mi ubuntu al linux-image-extra-4.4.0-38 no reconoce a mis tarjetas de red, video o sonido pero al hacer un lspci se listan los dispositivos. actualmente estoy trabajando con el linux-image-extra-4.4.0-36 que si puedo trabajar con ello pero con eso no puedo actualizar el sistema. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-38-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1915 F pulseaudio boris 2340 F pulseaudio Date: Thu Oct 6 15:01:24 2016 DpkgHistoryLog: Start-Date: 2016-10-06 15:01:09 Commandline: apt-get -f install Requested-By: boris (1000) Install: linux-image-extra-4.4.0-38-generic:amd64 (4.4.0-38.57, automatic) DpkgTerminalLog: Preparando para desempaquetar .../linux-image-extra-4.4.0-38-generic_4.4.0-38.57_amd64.deb ... Desempaquetando linux-headers-4.4.0-38 (4.4.0-38.57) sobre (4.4.0-38.57) ... dpkg: error al procesar el paquete linux-image-extra-4.4.0-38-generic (--configure): no hay instalado ningún paquete llamado `linux-image-extra-4.4.0-38-generic', no se puede configurar ErrorMessage: no hay instalado ningún paquete llamado `linux-image-extra-4.4.0-38-generic', no se puede configurar HibernationDevice: RESUME=UUID=ff500f4f-be28-4f2f-9bff-8944ef590901 InstallationDate: Installed on 2016-06-21 (107 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: Hewlett-Packard HP ENVY Sleekbook 4 PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=244e0f86-6a47-47f5-8a60-563bcb8f3258 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-extra-4.4.0-38-generic (not installed) failed to install/upgrade: no hay instalado ningún paquete llamado `linux-image-extra-4.4.0-38-generic', no se puede configurar UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1895 dmi.board.vendor: Hewlett-Packard dmi.board.version: 72.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.16:bd10/17/2012:svnHewlett-Packard:pnHPENVYSleekbook4PC:pvr088511305A0310130:rvnHewlett-Packard:rn1895:rvr72.43:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Sleekbook 4 PC dmi.product.version: 088511305A0310130 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631126/+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 1632902] Re: kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36
** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- 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/1632902 Title: kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36 Status in linux package in Ubuntu: Confirmed Bug description: This occurred after rebooting after running Kubuntu's Update Manager 5.6.2 on 2016-10-12. Unfortunately, I hadn't rebooted after the last update that required me to do so, and thus I don't know if the problem was from that update or this one. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacob 1494 F pulseaudio /dev/snd/controlC0: jacob 1494 F pulseaudio CurrentDesktop: KDE Date: Wed Oct 12 19:54:03 2016 HibernationDevice: RESUME=UUID=c5fdca37-edfe-4f31-928b-970bd6696164 InstallationDate: Installed on 2016-05-25 (140 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=c70ba36b-21e9-48ae-bf12-79060d17dcfc ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/02/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632902/+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 1632081] Re: package linux-headers-4.4.0-42-generic (not installed) failed to install/upgrade: chyba při vytváření adresáře „./usr/src/linux-headers-4.4.0-42-generic/include/con
** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632081 Title: package linux-headers-4.4.0-42-generic (not installed) failed to install/upgrade: chyba při vytváření adresáře „./usr/src/linux- headers-4.4.0-42-generic/include/config/log/buf“: Na zařízení není volné místo Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.4.0-38.57-generic 4.4.19 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-42-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikolas2596 F pulseaudio Date: Mon Oct 10 21:37:45 2016 ErrorMessage: chyba při vytváření adresáře „./usr/src/linux-headers-4.4.0-42-generic/include/config/log/buf“: Na zařízení není volné místo HibernationDevice: RESUME=UUID=4df6ee66-62c6-4d67-b0bc-83f338bc98d3 InstallationDate: Installed on 2016-06-11 (121 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. docker0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=882d7f83-3a5b-4d76-9520-22e6c140aadf ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2 RfKill: SourcePackage: linux Title: package linux-headers-4.4.0-42-generic (not installed) failed to install/upgrade: chyba při vytváření adresáře „./usr/src/linux-headers-4.4.0-42-generic/include/config/log/buf“: Na zařízení není volné místo UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2A-MX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd11/26/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-MX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632081/+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 1629421] Re: package linux-image-4.4.0-41-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1629421 Title: package linux-image-4.4.0-41-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: they had problems basically update the update manager and a fault occurred which indicates the kenel want to know about the possible solution thanks for your attention. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-41-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-39.59-generic 4.4.21 Uname: Linux 4.4.0-39-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hackskull 1866 F pulseaudio Date: Wed Sep 28 18:48:03 2016 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=25b7f84c-56ca-426e-91b5-fe3aede123d8 InstallationDate: Installed on 2016-09-02 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Intel Corporation Intel powered classmate PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-39-generic root=UUID=1780b7ed-bcb2-4097-890a-ceecf3d25822 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.3 SourcePackage: linux Title: package linux-image-4.4.0-41-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2012 dmi.bios.vendor: Phoenix dmi.bios.version: BPPNV20L.86A.0010.2012.0208.1808 dmi.board.asset.tag: PTL Nanjing dmi.board.name: Intel powered classmate PC dmi.board.vendor: Intel Corporation dmi.board.version: BP PV dmi.chassis.type: 10 dmi.chassis.vendor: Intel dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrBPPNV20L.86A.0010.2012.0208.1808:bd02/08/2012:svnIntelCorporation:pnIntelpoweredclassmatePC:pvrBPPVDuoCore:rvnIntelCorporation:rnIntelpoweredclassmatePC:rvrBPPV:cvnIntel:ct10:cvrN/A: dmi.product.name: Intel powered classmate PC dmi.product.version: BP PV Duo Core dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629421/+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 1568865] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe B FIFO underrun
I have an Asus X555UB laptop with Geforce 940M active and this error happens with me when I try to wake up from suspend mode. -- 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/1568865 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe B FIFO underrun Status in linux package in Ubuntu: Confirmed Bug description: Running Gnome-Shell on ubuntu 16.04 on my Dell XPS 15 9550 laptop using Intel graphics (Nvidia card turned off), I get this error in syslog when plugging in an external monitor (HDMI). Apr 11 14:28:38 miaco kernel: [ 2616.604641] [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe B FIFO underrun Meanwhile both screens flash and show corruption. Most of the time this has caused a hang that needs a hard power off to get out of, but occasionally removing the external monitor is enough to get going again and so I've been able to find this message in the logs. Note that when using Nvidia (proprietary) drivers and Unity DE I do not have this problem; so it seems to be related to the intel drivers, or possibly Gnome Shell's use of them. Happy to help if I can (would like to be able to use external monitors!) Rich ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rich 1943 F pulseaudio Date: Mon Apr 11 14:31:26 2016 InstallationDate: Installed on 2016-03-21 (21 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=3f8391d5-e9cc-4768-8efb-8f04d340567c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568865/+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 1615895] Re: apparmor module parameters can be changed after the policy is locked
** Tags added: aa-kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1615895 Title: apparmor module parameters can be changed after the policy is locked Status in AppArmor: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: the policy_lock parameter is a one way switch that prevents policy from being further modified. Unfortunately some of the module parameters can effectively modify policy by turning off enforcement. split policy_admin_capable into a view check and a full admin check, and update the admin check to test the policy_lock parameter. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1615895/+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 1592547] Re: vmalloc failure leads to null ptr dereference in aa_dfa_next
** Tags added: aa-kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1592547 Title: vmalloc failure leads to null ptr dereference in aa_dfa_next Status in AppArmor: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: running stress-ng apparmor stressor with a vmalloc NULL return trips a null ptr dereference in aa_dfa_next: $ uname -a Linux ubuntu 4.4.0-24-generic #43 [ 46.271517] BUG: unable to handle kernel NULL pointer dereference at 0020 [ 46.271641] IP: [] aa_dfa_next+0x6/0x70 [ 46.271743] PGD 39ebd067 PUD 39ebe067 PMD 0 [ 46.271833] Oops: [#1] SMP [ 46.271926] Modules linked in: jitterentropy_rng algif_rng salsa20_generic salsa20_x86_64 camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg ppdev snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm input_leds joydev snd_timer serio_raw snd soundcore i2c_piix4 mac_hid 8250_fintek parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq [ 46.273290] libcrc32c raid1 raid0 multipath linear 8139too crct10dif_pclmul crc32_pclmul qxl aesni_intel aes_x86_64 lrw gf128mul ttm drm_kms_helper glue_helper ablk_helper cryptd syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm floppy 8139cp mii pata_acpi [ 46.274250] CPU: 0 PID: 1349 Comm: stress-ng-appar Not tainted 4.4.0-24-generic #43 [ 46.274436] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 46.274632] task: 8800374be040 ti: 88003746c000 task.ti: 88003746c000 [ 46.274854] RIP: 0010:[] [] aa_dfa_next+0x6/0x70 [ 46.275072] RSP: 0018:88003746fca8 EFLAGS: 00010282 [ 46.275450] RAX: RBX: 0003 RCX: 4a46 [ 46.275934] RDX: 0002 RSI: 0001 RDI: [ 46.276348] RBP: 88003746fd28 R08: 88003fc19f40 R09: 88003e001d00 [ 46.276757] R10: 88003da8e600 R11: 88003e001500 R12: 88003746fd48 [ 46.276979] R13: 88003acc4800 R14: 88003acc4894 R15: 0029 [ 46.277202] FS: 7f7198a0f700() GS:88003fc0() knlGS: [ 46.277500] CS: 0010 DS: ES: CR0: 80050033 [ 46.278006] CR2: 0020 CR3: 39ebc000 CR4: 001406f0 [ 46.278592] Stack: [ 46.278846] 88003746fd28 81383585 [ 46.279271] 3746fd00 c9000268e400 [ 46.279860] 88003746fd40 5833b243 88003746fe28 [ 46.280311] Call Trace: [ 46.280606] [] ? unpack_profile+0x5c5/0x970 [ 46.280854] [] aa_unpack+0xe9/0x450 [ 46.281091] [] aa_replace_profiles+0x77/0xb70 [ 46.281341] [] ? vmalloc+0x6b/0x70 [ 46.281610] [] policy_update+0x9f/0x1f0 [ 46.281887] [] profile_replace+0x13/0x20 [ 46.282169] [] __vfs_write+0x18/0x40 [ 46.282444] [] vfs_write+0xa9/0x1a0 [ 46.282728] [] ? do_sys_open+0x1bf/0x2a0 [ 46.283418] [] SyS_write+0x55/0xc0 [ 46.284188] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 46.284753] Code: 0c 42 39 ce 74 d9 0f b6 02 41 0f b7 34 7b 84 c0 75 d9 eb c3 41 0f b7 34 44 eb 89 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 <48> 8b 47 20 4c 8b 5f 28 4c 8b 57 40 48 89 e5 4c 8b 4f 18 48 8d [ 46.285401] RIP [] aa_dfa_next+0x6/0x70 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1592547/+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 1615890] Re: stacking to unconfined in a child namespace confuses mediation
** Tags added: aa-kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1615890 Title: stacking to unconfined in a child namespace confuses mediation Status in AppArmor: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: when viewing a stack involving unconfined from across a ns boundary the mode is reported as mixed. Eg. lxc-container-default//&:lxdns1://unconfined (mixed) This is because the unconfined profile is in the special unconfined mode. Which will result in a (mixed) mode for any stack with profiles in enforcing or complain mode. This can however lead to confusion as to what mode is being used as mixed is also used for enforcing stacked with complain, and This can also currently messes up mediation of trusted helpers like dbus. Since unconfined doesn't affect the stack just special case it. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1615890/+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 1615881] Re: The label build for onexec when stacking is wrong
** Tags added: aa-kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1615881 Title: The label build for onexec when stacking is wrong Status in AppArmor: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: The label build for onexec when crossing a namespace boundry is not quite correct. The label needs to be built per profile and not based on the whole label because the onexec transition only applies to profiles within the ns. Where merging against the label could include profile that are transitioned via the profile_transition callback and should not be in the final label. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1615881/+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 1615887] Re: profiles from different namespaces can block other namespaces from being able to load a profile
** Tags added: aa-kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1615887 Title: profiles from different namespaces can block other namespaces from being able to load a profile Status in AppArmor: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: If ns1 has a profile A in it. It can cause loading a profile with the name A into ns2, and if it does succeed can result in compound labels crossing namespaces resulting in mediation not from one ns being applied to another. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1615887/+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 1615880] Re: The inherit check for new to old label comparison for domain transitions is wrong
** Tags added: aa-kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1615880 Title: The inherit check for new to old label comparison for domain transitions is wrong Status in AppArmor: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: For the purposes of inherit we should be treating a profile/label transition to its replacement as if the replacement is the profile/label. So make the comparison based off of the label proxy, not the label itself. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1615880/+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 1615893] Re: change_hat is logging failures during expected hat probing
** Tags added: aa-kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1615893 Title: change_hat is logging failures during expected hat probing Status in AppArmor: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: change_hat using probing to find and transition to the first available hat. Hats missing as part of this probe are expected and should not be logged except in complain mode. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1615893/+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 1615889] Re: label vec reductions can result in reference labels instead of direct access to labels
** Tags added: aa-kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1615889 Title: label vec reductions can result in reference labels instead of direct access to labels Status in AppArmor: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: The label vec cleanup/reduction can result in a reference label which while not causing wrong mediation is effectively a reference leak as the label will populate the label tree, consume memory and not be removed, it will only reduce to a reference of replacement vars. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1615889/+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 1615892] Re: deleted files outside of the namespace are not being treated as disconnected
** Tags added: aa-kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1615892 Title: deleted files outside of the namespace are not being treated as disconnected Status in AppArmor: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: Deleted files outside of the namespace should be treated the same as other disconnected files To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1615892/+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 1615878] Re: __label_update proxy comparison test is wrong
** Tags added: aa-kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1615878 Title: __label_update proxy comparison test is wrong Status in AppArmor: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: The comparing the proxy pointer, not the address of the labels proxy pointer. This results in labels that shouldn't entering into the invalidate label update path. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1615878/+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 1615882] Re: dfa is missing a bounds check which can cause an oops
** Tags added: aa-kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1615882 Title: dfa is missing a bounds check which can cause an oops Status in AppArmor: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Incomplete Bug description: A custom crafted or corrupted binary profile can cause an oops when loaded due to a missing bounds check To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1615882/+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 1408833] Re: broken postinst test for uvtool-libvirt
** Tags added: aa-kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1408833 Title: broken postinst test for uvtool-libvirt Status in AppArmor: Confirmed Status in openstack-installer: Confirmed Status in uvtool: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Utopic: Fix Released Bug description: Installing uvtool-libvirt *inside an lxc container* on utopic fails due to a test in the postinst script. It uses socat on the libvirt socket, which fails, despite libvirt being installed correctly. ubuntu@uoi-bootstrap:~$ sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libfreetype6 os-prober Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up uvtool-libvirt (0~bzr92-0ubuntu2) ... 2015/01/08 13:01:34 socat[10184] E read(3, 0x13b2a30, 8192): Permission denied libvirtd does not appear to be listening on "/var/run/libvirt/libvirt-sock". On Ubuntu, libvirtd is managed with the "libvirt-bin" upstart job. Repair libvirtd, then reconfigure uvtool-libvirt with: sudo apt-get -f install dpkg: error processing package uvtool-libvirt (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: uvtool-libvirt E: Sub-process /usr/bin/dpkg returned an error code (1) ubuntu@uoi-bootstrap:~$ ps -ef | grep libvirt libvirt+ 9556 1 0 09:52 ?00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper root 9557 9556 0 09:52 ?00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper root 9854 1 0 10:24 ?00:00:00 /usr/sbin/libvirtd -d ubuntu 10155 10120 0 12:56 pts/000:00:00 grep libvirt ubuntu@uoi-bootstrap:~$ groups ubuntu adm dialout cdrom floppy sudo audio dip video plugdev netdev libvirtd ubuntu@uoi-bootstrap:~$ virsh list IdName State for a little more context, there are notes here: https://gist.github.com/mikemccracken/53c665e6094db21efc03 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1408833/+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 1633223] host 'dlfire5' hang from afternoon of Oct 7th
Default Comment by Bridge ** Attachment added: "host 'dlfire5' hang from afternoon of Oct 7th" https://bugs.launchpad.net/bugs/1633223/+attachment/4760613/+files/dlfire5-oct07-kern.log ** Changed in: ubuntu Assignee: (unassigned) => Taco Screen team (taco-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633223 Title: rcu_sched detected stalls with kernel 3.19.0-58, NVIDIA driver, and docker Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Seeing occasional rcu_sched detected stalls on 14.04 LTS with kernel 3.19.0-58. The system is running docker containers, and has the NVIDIA GPU driver loaded. We've seen about 4 stalls in the last month, all with the 3.19.0-58 kernel, and with the NVIDIA 352.93 and 361.49 drivers. ---uname output--- Linux dldev1 3.19.0-58-generic #64~14.04.1-Ubuntu SMP Fri Mar 18 19:05:01 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- 2 x NVIDIA K80 GPU adapter: $ lspci | grep NV 0002:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 0002:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 0006:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 0006:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) Machine Type = 8247-42L ---System Hang--- Usual symptom is that the system is unresponsive except maybe for ping and writing the stall-detection messages to the console. Login/getty isn't available either via ssh nor on the console. System must be power cycled to recover. Attached is the kernel log from a stall detection on May 18th. The detection first occurs at: May 18 15:17:55. The system is later rebooted and those messages indicate the kernel (3.19.0-58) and NVIDIA driver version (352.93) that were active at the time. We've suffered 3 or 4 stalls since, all with the same kernel, but some with a newer NVIDIA driver (361.49). Unfortunately, information about the newer stalls wasn't preserved in the various log files (and we're not capturing the console constantly), so we don't have detailed data for those. We'd welcome any suggestions for how to collect additional data for these occurrences. I can't say for sure that we haven't seen the stalls on other systems, but they're occuring fairly frequently on this system, and it's unusual in that it's running both Docker and NVIDIA GPU driver. So maybe aufs or the NVIDIA driver are somehow involved. From the kern.log, The Call trace points to some kind of deadlock in aufs - May 18 15:17:55 dldev1 kernel: [713670.798624] Task dump for CPU 3: May 18 15:17:55 dldev1 kernel: [713670.798628] cc1 R running task0 99183 99173 0x00040004 May 18 15:17:55 dldev1 kernel: [713670.798633] Call Trace: May 18 15:17:55 dldev1 kernel: [713670.798643] [c00fa64673a0] [c00cf004] wake_up_worker+0x44/0x60 (unreliable) May 18 15:17:55 dldev1 kernel: [713670.798671] [c00fa6467570] [c00fa64675d0] 0xc00fa64675d0 May 18 15:17:55 dldev1 kernel: [713670.798676] [c00fa64675d0] [c0a1b050] __schedule+0x370/0x900 May 18 15:17:55 dldev1 kernel: [713670.798679] [c00fa64677f0] [c00fa6467850] 0xc00fa6467850 May 18 15:17:55 dldev1 kernel: [713670.798682] Task dump for CPU 75: May 18 15:17:55 dldev1 kernel: [713670.798684] cc1 D 105d9410 0 99427 99405 0x00040004 May 18 15:17:55 dldev1 kernel: [713670.798688] Call Trace: May 18 15:17:55 dldev1 kernel: [713670.798691] [c017efdd3460] [c017efdd34a0] 0xc017efdd34a0 (unreliable) May 18 15:17:55 dldev1 kernel: [713670.798695] [c017efdd3630] [c017efdd3690] 0xc017efdd3690 May 18 15:17:55 dldev1 kernel: [713670.798698] [c017efdd3690] [c0a1b050] __schedule+0x370/0x900 May 18 15:17:55 dldev1 kernel: [713670.798702] [c017efdd38b0] [c0a1f128] rwsem_down_write_failed+0x288/0x400 May 18 15:17:55 dldev1 kernel: [713670.798706] [c017efdd3940] [c0a1e538] down_write+0x88/0x90 May 18 15:17:55 dldev1 kernel: [713670.798716] [c017efdd3970] [d0001ead562c] do_ii_write_lock+0x8c/0xd0 [aufs] May 18 15:17:55 dldev1 kernel: [713670.798724] [c017efdd39a0] [d0001eac0e98] aufs_read_lock+0xb8/0xd0 [aufs] May 18 15:17:55 dldev1 kernel: [713670.798733] [c017efdd39e0] [d0001ead8208] aufs_d_revalidate+0x98/0x7a0 [aufs] May 18 15:17:55 dldev1 kernel: [713670.798737] [c017efdd3aa0] [c02c88f8] lookup_fast+0x368/0x3b0 May 18 15:17:55 dldev1 kernel: [713670.798740] [c017efdd3b10] [c02cb620] path_lookupat+0x180/0x970 May 18 15:17:55 dldev1 kernel: [713670.798743] [c017efdd3be0] [c02cbe68
[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
Thanks @faulpeltz for the info. I sent you a private message with the list of maintainers to send the patch (trying to avoid pasting it here in case spam bots can go through this archive). -- 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/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: 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: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here).As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+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 1633223] [NEW] rcu_sched detected stalls with kernel 3.19.0-58, NVIDIA driver, and docker
You have been subscribed to a public bug: ---Problem Description--- Seeing occasional rcu_sched detected stalls on 14.04 LTS with kernel 3.19.0-58. The system is running docker containers, and has the NVIDIA GPU driver loaded. We've seen about 4 stalls in the last month, all with the 3.19.0-58 kernel, and with the NVIDIA 352.93 and 361.49 drivers. ---uname output--- Linux dldev1 3.19.0-58-generic #64~14.04.1-Ubuntu SMP Fri Mar 18 19:05:01 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- 2 x NVIDIA K80 GPU adapter: $ lspci | grep NV 0002:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 0002:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 0006:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 0006:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) Machine Type = 8247-42L ---System Hang--- Usual symptom is that the system is unresponsive except maybe for ping and writing the stall-detection messages to the console. Login/getty isn't available either via ssh nor on the console. System must be power cycled to recover. Attached is the kernel log from a stall detection on May 18th. The detection first occurs at: May 18 15:17:55. The system is later rebooted and those messages indicate the kernel (3.19.0-58) and NVIDIA driver version (352.93) that were active at the time. We've suffered 3 or 4 stalls since, all with the same kernel, but some with a newer NVIDIA driver (361.49). Unfortunately, information about the newer stalls wasn't preserved in the various log files (and we're not capturing the console constantly), so we don't have detailed data for those. We'd welcome any suggestions for how to collect additional data for these occurrences. I can't say for sure that we haven't seen the stalls on other systems, but they're occuring fairly frequently on this system, and it's unusual in that it's running both Docker and NVIDIA GPU driver. So maybe aufs or the NVIDIA driver are somehow involved. >From the kern.log, The Call trace points to some kind of deadlock in aufs - May 18 15:17:55 dldev1 kernel: [713670.798624] Task dump for CPU 3: May 18 15:17:55 dldev1 kernel: [713670.798628] cc1 R running task 0 99183 99173 0x00040004 May 18 15:17:55 dldev1 kernel: [713670.798633] Call Trace: May 18 15:17:55 dldev1 kernel: [713670.798643] [c00fa64673a0] [c00cf004] wake_up_worker+0x44/0x60 (unreliable) May 18 15:17:55 dldev1 kernel: [713670.798671] [c00fa6467570] [c00fa64675d0] 0xc00fa64675d0 May 18 15:17:55 dldev1 kernel: [713670.798676] [c00fa64675d0] [c0a1b050] __schedule+0x370/0x900 May 18 15:17:55 dldev1 kernel: [713670.798679] [c00fa64677f0] [c00fa6467850] 0xc00fa6467850 May 18 15:17:55 dldev1 kernel: [713670.798682] Task dump for CPU 75: May 18 15:17:55 dldev1 kernel: [713670.798684] cc1 D 105d9410 0 99427 99405 0x00040004 May 18 15:17:55 dldev1 kernel: [713670.798688] Call Trace: May 18 15:17:55 dldev1 kernel: [713670.798691] [c017efdd3460] [c017efdd34a0] 0xc017efdd34a0 (unreliable) May 18 15:17:55 dldev1 kernel: [713670.798695] [c017efdd3630] [c017efdd3690] 0xc017efdd3690 May 18 15:17:55 dldev1 kernel: [713670.798698] [c017efdd3690] [c0a1b050] __schedule+0x370/0x900 May 18 15:17:55 dldev1 kernel: [713670.798702] [c017efdd38b0] [c0a1f128] rwsem_down_write_failed+0x288/0x400 May 18 15:17:55 dldev1 kernel: [713670.798706] [c017efdd3940] [c0a1e538] down_write+0x88/0x90 May 18 15:17:55 dldev1 kernel: [713670.798716] [c017efdd3970] [d0001ead562c] do_ii_write_lock+0x8c/0xd0 [aufs] May 18 15:17:55 dldev1 kernel: [713670.798724] [c017efdd39a0] [d0001eac0e98] aufs_read_lock+0xb8/0xd0 [aufs] May 18 15:17:55 dldev1 kernel: [713670.798733] [c017efdd39e0] [d0001ead8208] aufs_d_revalidate+0x98/0x7a0 [aufs] May 18 15:17:55 dldev1 kernel: [713670.798737] [c017efdd3aa0] [c02c88f8] lookup_fast+0x368/0x3b0 May 18 15:17:55 dldev1 kernel: [713670.798740] [c017efdd3b10] [c02cb620] path_lookupat+0x180/0x970 May 18 15:17:55 dldev1 kernel: [713670.798743] [c017efdd3be0] [c02cbe68] filename_lookup+0x58/0x140 May 18 15:17:55 dldev1 kernel: [713670.798746] [c017efdd3c30] [c02cde04] user_path_at_empty+0x84/0xe0 May 18 15:17:55 dldev1 kernel: [713670.798749] [c017efdd3d20] [c02be744] vfs_fstatat+0x84/0x140 May 18 15:17:55 dldev1 kernel: [713670.798753] [c017efdd3d80] [c02bee14] SyS_newlstat+0x34/0x60 May 18 15:17:55 dldev1 kernel: [713670.798757] [c017efdd3e30] [c0009258] system_call+0x38/0xd0 Other info from the log - May 18 16:00:00 dldev1 kernel: [ 11.802963] nvidia 0002:03:00.0: enabling device (0140 -> 0142) May 18 16:00:00 dldev1 kernel: [ 11.803114] nvidia 0002:04:00.0: enabling device (0140 -> 0142) May 18 16:00
[Kernel-packages] [Bug 1626371] Re: cdc_ether fills kernel log
I'm having the same issue on Debian Sid. Thinkpad X1 4th gen, OneLink+ Dock Linux lines 4.8.1-custom01 #1 SMP Fri Oct 7 17:11:08 PDT 2016 x86_64 GNU/Linux -- 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/1626371 Title: cdc_ether fills kernel log Status in linux package in Ubuntu: Incomplete Bug description: On my Lenovo X1 4th gen with a dock attached: [ 1764.086306] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been dropped [ 1764.150317] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been dropped The USB Ethernet device would warn occasionally under the 4.4 kernel. Under the 4.8 kernel, it spams my kernel log so much that I don't get anything else. $ uname -a Linux aurora 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 20:00:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux joel@aurora ~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626371/+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 1630857] Re: Dell Precision Trackpoint not working after suspend
** Changed in: hwe-next 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/1630857 Title: Dell Precision Trackpoint not working after suspend Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Steps: 1) Install Ubuntu 16.04 2) Enter Desktop. 3) Suspend system. 4) Using the trackpoint. 5) Click the left button with DualPoint stick. 6) Click the right button with DualPoint stick. 7) Click the middle button with DualPoint stick. 8) Double-click the left button with DualPoint stick. Expected results: Trackpoint and DualPoint stick can work after suspend. Actual results: Trackpoing and DualPoint stick not working after suspend. Manufacturer: Dell Inc. ProductName: Precision 7500 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1630857/+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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
@Alex 1) Yes, but I might need some help with that. Which list/maintainer should I submit it to? 2) On our test machine, with both the hyper-v host as well as the guest under heavy i/o load, it was a few hundred ms but with high variance and spiking (quite often) in to the 2-4s range, with some extreme values being 10s and more. I assume that this varies a lot with regards to the test hardware, especially storage. With light load (but not idle) this was well in the <100ms range but with occasional spikes. Another thing I noticed was that the freeze operation often took a lot longer (but not always) when triggered directly by the vss daemon through a host backup and not just from a standalone test program which just called FREEZE/THAW in a loop. -- 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/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: 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: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here).As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+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 1609885] Re: exec transitions to profiles with '.' in name don't work
** Tags added: aa-parser
--
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/1609885
Title:
exec transitions to profiles with '.' in name don't work
Status in AppArmor:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Incomplete
Bug description:
If a child profile has '.' in the name, then the parser fails to compile the
policy:
$ sudo apparmor_parser -r /tmp/profile && aa-exec -p test /tmp/test.sh
AppArmor parser error for /tmp/profile in /tmp/profile at line 14: Found
unexpected character: '.'
If put a child profile with '.' in the name in a variable, the parser
compiles the policy but the exec transition fails:
$ sudo apparmor_parser -r /tmp/profile && aa-exec -p test /tmp/test.sh
/tmp/with.dots: 3: /tmp/with.dots: cat: Permission denied
denial is:
apparmor="DENIED" operation="exec" info="profile transition not found"
error=-13 profile="test" name="/bin/cat" pid=18219 comm="with.dots"
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
$ cat /tmp/test.sh
#!/bin/sh
cat /proc/version
$ cat /tmp/profile
#include
@{TARGET_PROFILE}="with.dots"
profile test {
#include
#include
/tmp/test.sh r,
# parser error:
# AppArmor parser error for /tmp/profile in /tmp/profile at line 14: Found
# unexpected character: '.'
/{,usr/}bin/cat cx -> with.dots,
# fail to transition:
# apparmor="DENIED" operation="exec" info="profile transition not found"
# error=-13 profile="test" name="/bin/cat" pid=18105 comm="with.dots"
# requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
#/{,usr/}bin/cat cx -> @{TARGET_PROFILE},
# ok
#/{,usr/}bin/cat cx -> no_dots,
profile with.dots {
#include
@{PROC}/version r,
/{,usr/}bin/cat r,
}
profile no_dots {
#include
@{PROC}/version r,
/{,usr/}bin/cat r,
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1609885/+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 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count
Oh oops, didn't realize this was the patch with the 751eb6b6042a596b0080967c1a529a9fe98dac1d commit Paul mentionned. Well, if that made it into Ubuntu's kernel before and including 4.4.0-42, it didn't fix it (I still get the bug on many machines & VMs). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title: unregister_netdevice: waiting for lo to become free. Usage count Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Confirmed Status in linux source package in Vivid: Fix Released Bug description: SRU Justification: [Impact] Users of kernels that utilize NFS may see the following messages when shutting down and starting containers: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] Setup multiple containers in parallel to mount and NFS share, create some traffic and shutdown. Eventually you will see the kernel message. Dave's script here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24 [Fix] commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream -- I currently running trusty latest patches and i get on these hardware and software: Ubuntu 3.13.0-43.72-generic 3.13.11.11 processor : 7 vendor_id : GenuineIntel cpu family: 6 model : 77 model name: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz stepping : 8 microcode : 0x11d cpu MHz : 2400.000 cache size: 1024 KB physical id : 0 siblings : 8 core id : 7 cpu cores : 8 apicid: 14 initial apicid: 14 fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 4799.48 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: somehow reproducable the subjected error, and lxc is working still but not more managable until a reboot. managable means every command hangs. I saw there are alot of bugs but they seams to relate to older version and are closed, so i decided to file a new one? I run alot of machine with trusty an lxc containers but only these kind of machines produces these errors, all other don't show these odd behavior. thx in advance meno To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1403152/+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 1632045] Re: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA
https://lists.ubuntu.com/archives/kernel-team/2016-October/080363.html ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632045 Title: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: ---Problem Description--- https://github.com/open-power/supermicro-openpower/issues/59 SW/HW Configuration PNOR image version: 5/3/2016 BMC image version: 0.25 CPLD Version: B2.81.01 Host OS version: Ubuntu 16.04 LTS UbuntuKVM Guest OS version: Ubuntu 14.04.4 LTS HTX version: 394 Processor: 00UL865 * 2 Memory: SK hynix 16GB 2Rx4 PC4-2133P * 16 Summary of Issue Two UbuntuKVM guests are each configured with 8 processors, 64 GB of memory, 1 disk of 128 GB, 1 network interface, and 1 GPU (pass- through'd from the Host OS's K80). The two guests are each put into a Create/Destroy loop, with HTX running on each of the guests (NOT HOST) in between its creation and destruction. The mdt.bu profile is used, and the processors, memory, and the GPU are put under load. The HTX session lasts 9 minutes. While this is running, the amount of available memory (free memory) in the Host OS will slowly decrease, and this can continue until the point wherein there's no more free memory for the Host OS to do anything, including creating the two VM guests. It seems to be that after every cycle, a small portion of the memory that was allocated to the VM guest does not get released back to the Host OS, and eventually, this can and will add up to take up all the available memory in the Host OS. At some point, the VM guest(s) might get disconnected and will display the following error: error: Disconnected from qemu:///system due to I/O error error: One or more references were leaked after disconnect from the hypervisor Then, when the Host OS tries to start the VM guest again, the following error shows up: error: Failed to create domain from guest2_trusty.xml error: internal error: early end of file from monitor, possible problem: Unexpected error in spapr_alloc_htab() at /build/qemu-c3ZrbA/qemu-2.5+dfsg/hw/ppc/spapr.c:1030: 2016-05-23T16:18:16.871549Z qemu-system-ppc64: Failed to allocate HTAB of requested size, try with smaller maxmem The Host OS syslog, as seen HERE, also contains quite some errors. To just list a few: May 13 20:27:44 191-136 kernel: [36827.151228] alloc_contig_range: [3fb800, 3fd8f8) PFNs busy May 13 20:27:44 191-136 kernel: [36827.151291] alloc_contig_range: [3fb800, 3fd8fc) PFNs busy May 13 20:27:44 191-136 libvirtd[19263]: *** Error in `/usr/sbin/libvirtd': realloc(): invalid next size: 0x01000a780400 *** May 13 20:27:44 191-136 libvirtd[19263]: === Backtrace: = May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x8720c)[0x3fffaf6a720c] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x96f70)[0x3fffaf6b6f70] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(realloc+0x16c)[0x3fffaf6b87fc] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virReallocN+0x68)[0x3fffaf90ccc8] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0x8ef6c)[0x3fff9346ef6c] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0xa826c)[0x3fff9348826c] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventPollRunOnce+0x8b4)[0x3fffaf9332b4] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventRunDefaultImpl+0x54)[0x3fffaf931334] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virNetDaemonRun+0x1f0)[0x3fffafad2f70] May 13 20:27:44 191-136 libvirtd[19263]: /usr/sbin/libvirtd(+0x15d74)[0x52e45d74] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x2319c)[0x3fffaf64319c] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0xb8)[0x3fffaf6433b8] May 13 20:27:44 191-136 libvirtd[19263]: === Memory map: May 13 20:27:44 191-136 libvirtd[19263]: 52e3-52eb r-xp 08:02 65540510 /usr/sbin/libvirtd May 13 20:27:44 191-136 libvirtd[19263]: 52ec-52ed r--p 0008 08:02 65540510 /usr/sbin/libvirtd May 13 20:27:44 191-136 libvirtd[1
[Kernel-packages] [Bug 1632045] Re: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA
https://lists.ubuntu.com/archives/kernel-team/2016-October/080362.html ** Also affects: linux (Ubuntu Yakkety) Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Triaged ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Yakkety) Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632045 Title: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: ---Problem Description--- https://github.com/open-power/supermicro-openpower/issues/59 SW/HW Configuration PNOR image version: 5/3/2016 BMC image version: 0.25 CPLD Version: B2.81.01 Host OS version: Ubuntu 16.04 LTS UbuntuKVM Guest OS version: Ubuntu 14.04.4 LTS HTX version: 394 Processor: 00UL865 * 2 Memory: SK hynix 16GB 2Rx4 PC4-2133P * 16 Summary of Issue Two UbuntuKVM guests are each configured with 8 processors, 64 GB of memory, 1 disk of 128 GB, 1 network interface, and 1 GPU (pass- through'd from the Host OS's K80). The two guests are each put into a Create/Destroy loop, with HTX running on each of the guests (NOT HOST) in between its creation and destruction. The mdt.bu profile is used, and the processors, memory, and the GPU are put under load. The HTX session lasts 9 minutes. While this is running, the amount of available memory (free memory) in the Host OS will slowly decrease, and this can continue until the point wherein there's no more free memory for the Host OS to do anything, including creating the two VM guests. It seems to be that after every cycle, a small portion of the memory that was allocated to the VM guest does not get released back to the Host OS, and eventually, this can and will add up to take up all the available memory in the Host OS. At some point, the VM guest(s) might get disconnected and will display the following error: error: Disconnected from qemu:///system due to I/O error error: One or more references were leaked after disconnect from the hypervisor Then, when the Host OS tries to start the VM guest again, the following error shows up: error: Failed to create domain from guest2_trusty.xml error: internal error: early end of file from monitor, possible problem: Unexpected error in spapr_alloc_htab() at /build/qemu-c3ZrbA/qemu-2.5+dfsg/hw/ppc/spapr.c:1030: 2016-05-23T16:18:16.871549Z qemu-system-ppc64: Failed to allocate HTAB of requested size, try with smaller maxmem The Host OS syslog, as seen HERE, also contains quite some errors. To just list a few: May 13 20:27:44 191-136 kernel: [36827.151228] alloc_contig_range: [3fb800, 3fd8f8) PFNs busy May 13 20:27:44 191-136 kernel: [36827.151291] alloc_contig_range: [3fb800, 3fd8fc) PFNs busy May 13 20:27:44 191-136 libvirtd[19263]: *** Error in `/usr/sbin/libvirtd': realloc(): invalid next size: 0x01000a780400 *** May 13 20:27:44 191-136 libvirtd[19263]: === Backtrace: = May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x8720c)[0x3fffaf6a720c] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x96f70)[0x3fffaf6b6f70] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(realloc+0x16c)[0x3fffaf6b87fc] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virReallocN+0x68)[0x3fffaf90ccc8] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0x8ef6c)[0x3fff9346ef6c] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0xa826c)[0x3fff9348826c] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventPollRunOnce+0x8b4)[0x3fffaf9332b4] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventRunDefaultImpl+0x54)[0x3fffaf931334] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virNetDaemonRun+0x1f0)[0x3fffafad2f70] May 13 20:27:44 191-136 libvirtd[19263]: /usr/sbin/libvirtd(+0x15d74)[0x52e45d74] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x2319c)[0x3fffaf64319c] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0xb8)[0x3fffaf6433b8] May 13 20:27:44 191-136 libvirtd[19263]: === Memory map:
[Kernel-packages] [Bug 1633193] Re: Oops on EEH hit during tg3 probe
git describe --contains 1b0ff89852d79354e8a091c81a88df21f5aa9f0a
v4.8~5^2~2
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Assignee: Taco Screen team (taco-screen-team)
Status: New
** Changed in: linux (Ubuntu Yakkety)
Status: New => Fix Released
** Changed in: linux (Ubuntu Yakkety)
Assignee: Taco Screen team (taco-screen-team) => (unassigned)
** 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/1633193
Title:
Oops on EEH hit during tg3 probe
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Status in linux source package in Yakkety:
Fix Released
Bug description:
-- Problem Description --
We observed that when EEH error is hit during tg3 driver probe, we might
trigger a kernel oops due to a memory access to an uninitialized pointer.
The following upstream patch addresses the issue: 1b0ff89852 ("tg3: Avoid
NULL pointer dereference in tg3_io_error_detected()")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1b0ff89852d79354e8a091c81a88df21f5aa9f0a
We want to request Canonical to add this patch to Ubuntu 16.04 kernel if
possible.
Thanks in advance,
Guilherme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633193/+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 1633193] Re: Oops on EEH hit during tg3 probe
https://lists.ubuntu.com/archives/kernel-team/2016-October/080364.html
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1633193
Title:
Oops on EEH hit during tg3 probe
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Status in linux source package in Yakkety:
Fix Released
Bug description:
-- Problem Description --
We observed that when EEH error is hit during tg3 driver probe, we might
trigger a kernel oops due to a memory access to an uninitialized pointer.
The following upstream patch addresses the issue: 1b0ff89852 ("tg3: Avoid
NULL pointer dereference in tg3_io_error_detected()")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1b0ff89852d79354e8a091c81a88df21f5aa9f0a
We want to request Canonical to add this patch to Ubuntu 16.04 kernel if
possible.
Thanks in advance,
Guilherme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633193/+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
892b73dd23e0b5e4cc76c2dcd13ea5ae5caf6bec ('UBUNTU: SAUCE: Return TCMU-
generated sense data to fabric module') was released in Ubuntu-4.8.0-7.8
The other 3 TCM patches are proposed on the list:
https://lists.ubuntu.com/archives/kernel-team/2016-October/080358.html
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Released => 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/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:
In Progress
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 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count
> Apparently the fix is in: > > https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.22 Hopefully the commit does fix things, although Paul's comment above indicated it may not, at least not for everyone. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title: unregister_netdevice: waiting for lo to become free. Usage count Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Confirmed Status in linux source package in Vivid: Fix Released Bug description: SRU Justification: [Impact] Users of kernels that utilize NFS may see the following messages when shutting down and starting containers: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] Setup multiple containers in parallel to mount and NFS share, create some traffic and shutdown. Eventually you will see the kernel message. Dave's script here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24 [Fix] commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream -- I currently running trusty latest patches and i get on these hardware and software: Ubuntu 3.13.0-43.72-generic 3.13.11.11 processor : 7 vendor_id : GenuineIntel cpu family: 6 model : 77 model name: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz stepping : 8 microcode : 0x11d cpu MHz : 2400.000 cache size: 1024 KB physical id : 0 siblings : 8 core id : 7 cpu cores : 8 apicid: 14 initial apicid: 14 fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 4799.48 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: somehow reproducable the subjected error, and lxc is working still but not more managable until a reboot. managable means every command hangs. I saw there are alot of bugs but they seams to relate to older version and are closed, so i decided to file a new one? I run alot of machine with trusty an lxc containers but only these kind of machines produces these errors, all other don't show these odd behavior. thx in advance meno To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1403152/+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 1633193] [NEW] Oops on EEH hit during tg3 probe
Public bug reported:
-- Problem Description --
We observed that when EEH error is hit during tg3 driver probe, we might
trigger a kernel oops due to a memory access to an uninitialized pointer.
The following upstream patch addresses the issue: 1b0ff89852 ("tg3: Avoid NULL
pointer dereference in tg3_io_error_detected()")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1b0ff89852d79354e8a091c81a88df21f5aa9f0a
We want to request Canonical to add this patch to Ubuntu 16.04 kernel if
possible.
Thanks in advance,
Guilherme
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Taco Screen team (taco-screen-team)
Status: New
** Tags: architecture-ppc64le bugnameltc-145728 severity-high
targetmilestone-inin16041
** Tags added: architecture-ppc64le bugnameltc-145728 severity-high
targetmilestone-inin16041
** Changed in: ubuntu
Assignee: (unassigned) => Taco Screen team (taco-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1633193
Title:
Oops on EEH hit during tg3 probe
Status in linux package in Ubuntu:
New
Bug description:
-- Problem Description --
We observed that when EEH error is hit during tg3 driver probe, we might
trigger a kernel oops due to a memory access to an uninitialized pointer.
The following upstream patch addresses the issue: 1b0ff89852 ("tg3: Avoid
NULL pointer dereference in tg3_io_error_detected()")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1b0ff89852d79354e8a091c81a88df21f5aa9f0a
We want to request Canonical to add this patch to Ubuntu 16.04 kernel if
possible.
Thanks in advance,
Guilherme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633193/+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
https://lists.ubuntu.com/archives/kernel-team/2016-October/080349.html
https://lists.ubuntu.com/archives/kernel-team/2016-October/080353.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/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:
In Progress
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 1633193] [NEW] Oops on EEH hit during tg3 probe
You have been subscribed to a public bug:
-- Problem Description --
We observed that when EEH error is hit during tg3 driver probe, we might
trigger a kernel oops due to a memory access to an uninitialized pointer.
The following upstream patch addresses the issue: 1b0ff89852 ("tg3: Avoid NULL
pointer dereference in tg3_io_error_detected()")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1b0ff89852d79354e8a091c81a88df21f5aa9f0a
We want to request Canonical to add this patch to Ubuntu 16.04 kernel if
possible.
Thanks in advance,
Guilherme
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Taco Screen team (taco-screen-team)
Status: New
** Tags: architecture-ppc64le bugnameltc-145728 severity-high
targetmilestone-inin16041
--
Oops on EEH hit during tg3 probe
https://bugs.launchpad.net/bugs/1633193
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632045] Re: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632045 Title: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA Status in linux package in Ubuntu: Triaged Bug description: ---Problem Description--- https://github.com/open-power/supermicro-openpower/issues/59 SW/HW Configuration PNOR image version: 5/3/2016 BMC image version: 0.25 CPLD Version: B2.81.01 Host OS version: Ubuntu 16.04 LTS UbuntuKVM Guest OS version: Ubuntu 14.04.4 LTS HTX version: 394 Processor: 00UL865 * 2 Memory: SK hynix 16GB 2Rx4 PC4-2133P * 16 Summary of Issue Two UbuntuKVM guests are each configured with 8 processors, 64 GB of memory, 1 disk of 128 GB, 1 network interface, and 1 GPU (pass- through'd from the Host OS's K80). The two guests are each put into a Create/Destroy loop, with HTX running on each of the guests (NOT HOST) in between its creation and destruction. The mdt.bu profile is used, and the processors, memory, and the GPU are put under load. The HTX session lasts 9 minutes. While this is running, the amount of available memory (free memory) in the Host OS will slowly decrease, and this can continue until the point wherein there's no more free memory for the Host OS to do anything, including creating the two VM guests. It seems to be that after every cycle, a small portion of the memory that was allocated to the VM guest does not get released back to the Host OS, and eventually, this can and will add up to take up all the available memory in the Host OS. At some point, the VM guest(s) might get disconnected and will display the following error: error: Disconnected from qemu:///system due to I/O error error: One or more references were leaked after disconnect from the hypervisor Then, when the Host OS tries to start the VM guest again, the following error shows up: error: Failed to create domain from guest2_trusty.xml error: internal error: early end of file from monitor, possible problem: Unexpected error in spapr_alloc_htab() at /build/qemu-c3ZrbA/qemu-2.5+dfsg/hw/ppc/spapr.c:1030: 2016-05-23T16:18:16.871549Z qemu-system-ppc64: Failed to allocate HTAB of requested size, try with smaller maxmem The Host OS syslog, as seen HERE, also contains quite some errors. To just list a few: May 13 20:27:44 191-136 kernel: [36827.151228] alloc_contig_range: [3fb800, 3fd8f8) PFNs busy May 13 20:27:44 191-136 kernel: [36827.151291] alloc_contig_range: [3fb800, 3fd8fc) PFNs busy May 13 20:27:44 191-136 libvirtd[19263]: *** Error in `/usr/sbin/libvirtd': realloc(): invalid next size: 0x01000a780400 *** May 13 20:27:44 191-136 libvirtd[19263]: === Backtrace: = May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x8720c)[0x3fffaf6a720c] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x96f70)[0x3fffaf6b6f70] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(realloc+0x16c)[0x3fffaf6b87fc] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virReallocN+0x68)[0x3fffaf90ccc8] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0x8ef6c)[0x3fff9346ef6c] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0xa826c)[0x3fff9348826c] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventPollRunOnce+0x8b4)[0x3fffaf9332b4] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventRunDefaultImpl+0x54)[0x3fffaf931334] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virNetDaemonRun+0x1f0)[0x3fffafad2f70] May 13 20:27:44 191-136 libvirtd[19263]: /usr/sbin/libvirtd(+0x15d74)[0x52e45d74] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x2319c)[0x3fffaf64319c] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0xb8)[0x3fffaf6433b8] May 13 20:27:44 191-136 libvirtd[19263]: === Memory map: May 13 20:27:44 191-136 libvirtd[19263]: 52e3-52eb r-xp 08:02 65540510 /usr/sbin/libvirtd May 13 20:27:44 191-136 libvirtd[19263]: 52ec-52ed r--p 0008 08:02 65540510 /usr/sbin/libvirtd May 13 20:27:44 191-136 libvirtd[19263]: 52ed-52ee rw-p 0009 08:02 65540510 /usr/sbin/libvirtd May 13 20:27:44
[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks
That's correct, that dump_buggy is without stress running. -- 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/1627108 Title: X1Carbon comes to a crawl during high CPU usage tasks Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: My X1Carbon becomes quite laggy, the cursor hangs for a few seconds and then resumes while my system is compiling some code, or lets says PyCharm is indexing things or Android Studio is compiling some code. I was using 4.4 on Xenial a few days ago and everything was working just fine. Installed Yakkety and this issue happens. TEST CASE: `stress -c 4` <-- that results in system slowness. I will downgrade the kernel and see if that mitigates the issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-15-generic 4.8.0-15.16 ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7 Uname: Linux 4.8.0-15-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: om26er 3390 F...m pulseaudio /dev/snd/controlC1: om26er 3390 F pulseaudio /dev/snd/controlC0: om26er 3390 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 23 21:40:34 2016 HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e InstallationDate: Installed on 2016-09-21 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) MachineType: LENOVO 20BSCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-15-generic N/A linux-backports-modules-4.8.0-15-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET32W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627108/+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 1625606] Re: List of available GPS app
Sami problemi for M10 tablet -- 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/1625606 Title: List of available GPS app Status in bluez package in Ubuntu: New Bug description: Aquarius E5 OTA-13: Removed apps will not deleted on list of available GPS apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1625606/+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 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks
>From Upstream: "> Here is the dump before stress is started: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627108/+attachment/4760437/+files/dump_nonbuggy This one is ok. The dump indicates Sched Debug Version: v0.11, 4.8.0-11-generic #12~lp1627108Commit3d30544Reverted so this is without the culprit commit > > Here it is after: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627108/+attachment/4760436/+files/dump_buggy > This one has the exact same odds values for system.slice->tg_load_avg than the 1st dump that you sent yesterday The dump indicates Sched Debug Version: v0.11, 4.8.0-22-generic #24-Ubuntu So this dump has been done with a different kernel than for the dump above. As I can't find any stress task in the dump, i tend to believe that the dump has been done before starting the stress tasks and not after starting them. Can you confirm ? If i'm right, it mean that the problem was already there before starting stress tasks." -- 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/1627108 Title: X1Carbon comes to a crawl during high CPU usage tasks Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: My X1Carbon becomes quite laggy, the cursor hangs for a few seconds and then resumes while my system is compiling some code, or lets says PyCharm is indexing things or Android Studio is compiling some code. I was using 4.4 on Xenial a few days ago and everything was working just fine. Installed Yakkety and this issue happens. TEST CASE: `stress -c 4` <-- that results in system slowness. I will downgrade the kernel and see if that mitigates the issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-15-generic 4.8.0-15.16 ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7 Uname: Linux 4.8.0-15-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: om26er 3390 F...m pulseaudio /dev/snd/controlC1: om26er 3390 F pulseaudio /dev/snd/controlC0: om26er 3390 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 23 21:40:34 2016 HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e InstallationDate: Installed on 2016-09-21 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) MachineType: LENOVO 20BSCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-15-generic N/A linux-backports-modules-4.8.0-15-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET32W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627108/+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 1633172] Re: Linux 4.8 as in 16.10 hangs during boot
** 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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Confirmed Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
Hi @faulpeltz, A few questions/comments about your patch: 1) Can you submit your patch to the upstream kernel? 2) Under load, were you able to measure how long the FIFREEZE operation took before it succeeded? I'm trying to see if we can increase the timeout of the kernel driver before it hits the error condition that you encountered. Thanks, Alex -- 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/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: 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: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here).As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+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 1633172] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1633172/+attachment/4760525/+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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1633172/+attachment/4760522/+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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1633172/+attachment/4760517/+files/JournalErrors.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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1633172/+attachment/4760521/+files/ProcEnviron.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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1633172/+attachment/4760519/+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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1633172/+attachment/4760513/+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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-21.23/s2lp6g002__4.8.0-21.23__2016-10-13_18-10-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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+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 1633172] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1633172/+attachment/4760520/+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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1633172/+attachment/4760518/+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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1633172/+attachment/4760526/+files/WifiSyslog.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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1633172/+attachment/4760523/+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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1633172/+attachment/4760524/+files/PulseList.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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1633172/+attachment/4760515/+files/CRDA.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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1633172/+attachment/4760514/+files/AudioDevicesInUse.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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1633172/+attachment/4760516/+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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] Re: Linux 4.8 as in 16.10 hangs during boot
I will run the command. Do note that this will be done using the 4.4 kernel, not the 4.8 kernel which I could not boot as stated in the bug report. ** Tags added: apport-collected yakkety ** Description changed: - I have just upgraded to 16.10 and restarted my machine. The new 4.8 - kernel seemed to take ages to boot and appears to have hanged. I have - managed to boot the system with the older 4.4 kernels from 16.04 just - fine without any problems from systemd etc.. Please fix this so I can - stop selecting the kernel manually on each boot. + I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. + --- + ApportVersion: 2.20.3-0ubuntu8 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.10 + HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 + InstallationDate: Installed on 2016-02-19 (236 days ago) + InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) + IwConfig: + lono wireless extensions. + + enp4s0no wireless extensions. + + eno1 no wireless extensions. + MachineType: ASUS All Series + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-43-generic N/A + linux-backports-modules-4.4.0-43-generic N/A + linux-firmware1.161 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: yakkety + Uname: Linux 4.4.0-43-generic x86_64 + UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/04/2016 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 3101 + dmi.board.asset.tag: Default string + dmi.board.name: SABERTOOTH X99 + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.name: All Series + dmi.product.version: System Version + dmi.sys.vendor: ASUS -- 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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string
[Kernel-packages] [Bug 1633172] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1633172 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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] Re: Linux 4.8 as in 16.10 hangs during boot
Please let me know if I need to collect any system info etc. since I am using an NVIDIA gpu with a manually installed proprietary driver. -- 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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+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 1633172] [NEW] Linux 4.8 as in 16.10 hangs during boot
Public bug reported: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-collected 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/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages P
[Kernel-packages] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image
Thanks Eric, we will remove our local workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1607920 Title: zfs services fail on firstboot if zfs-utils is integrated into the deployment image Status in sysvinit package in Ubuntu: Won't Fix Status in zfs-linux package in Ubuntu: Fix Released Status in sysvinit source package in Xenial: Won't Fix Status in zfs-linux source package in Xenial: Fix Released Bug description: [Impact] * zfs services fail on firstboot if zfs-utils is integrated into the deployment image. * Output from systemd - sudo systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● zfs-import-scan.service loaded failed failed Import ZFS pools by device scanning ● zfs-mount.service loaded failed failed Mount ZFS filesystems * This is particularly frustrating for users who use automated monitoring as it means virtual machines must always be restarted before showing as clean. * This failure is due to zfs services starting up before /etc/mtab has a chance to be symlinked to /proc/mounts. [Test Case] 1. Grab a stock xenial image, and unpack it and add zfs-utils to it. Repack it. 2. Boot machine 3. Check systemctl --failed. [Regression Potential] * none expected, patch has been intensively tested by the upsteam zfs test script suite. * This is a upstream commit merge in 0.7.0. * A ubuntu package has been tested (including the upstream commit) by a user of the community facing this bug, and confirmed it addresses the problem (see comment #7). [Other Info] * The "reading" is redirected to /proc/self/mounts. The writing to /etc/mtab. Some distros still need that. The current hope is to replace the writing (and maybe reading) with libmount, in a second phase. * Upstream commit : https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680 * Debian bug : https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=839071 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1607920/+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 1513914] Re: Dell E7440 touchpad jumps position
The problem still exists when running E7440, A18 bios, Ubuntu 16.04LTS with Kernel 4.8.1-040801.201610071031. dmidecode -s bios-release-date [sudo] password for martyn: A18 04/28/2016 -- 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/1513914 Title: Dell E7440 touchpad jumps position Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 15.10 - Dell E7440 touchpad works correctly when freshly started each time; but after some time running the mouse pointer starts to randomly jumps position when I try to use the touchpad. If I shut down Ubuntu and re-start after about 10 seconds, the problem is temporarily resolved. Both the USB Mouse and keyboard blue joy-button continue to work correctly while having "jumpy touchpad problem. Running Ubuntu 15.10 installed version (updated from 15.04 new installation) I have previously seen the same same problem with Ubuntu 14.04 and 15.04, both live CD and installed versions. I am new to Linux & forums, so please excuse my lack of knowledge. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: martyn 1217 F pulseaudio /dev/snd/controlC0: martyn 1217 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 6 17:33:42 2015 HibernationDevice: RESUME=UUID=d0cf60ae-c48f-4267-bb58-af4193cc2e5c InstallationDate: Installed on 2015-09-23 (44 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Latitude E7440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=42d901b2-6e43-4fbf-a79f-c6329d47548a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149.1 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (14 days ago) dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 03M26R dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03M26R:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513914/+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
