[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards
I notice that there's no mention of a yakety release. Is that deliberate? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579190 Title: Key 5 automatically pressed on some Logitech wireless keyboards Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: I have a K520 Logitech keyboard and sometimes something starts to keep pressing key 5. It mostly happens when I leave the computer alone for some time, but sometimes also just during regular usage. It seems that this is a Linux specific issue as no one is complaining about this issue under Windows, but a couple of people are complaining for different versions of Ubuntu. It is always 5 and WladyXX3740 claims on the Logitech forum that: "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably kernel related." Here is where most of the people are complaining: https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639 I discovered that this is related to my Logitech keyboard by running this command: xinput test-xi2 --root Here is the device list: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech K520 id=10 [slave pointer (2)] ⎜ ↳ Logitech M310/M310t id=11 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=15 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ DELL Wireless hotkeys id=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] And some extract from the output when this happens: EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 12 (PropertyEvent) property: 308 'Synaptics Off' changed: modified EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 b
[Kernel-packages] [Bug 1382993] Re: Micro-sd card not mounted by internal card reader
Still happening in yakketi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382993 Title: Micro-sd card not mounted by internal card reader Status in linux package in Ubuntu: Confirmed Bug description: This card is inserted in the card reader slot via an sd adapter. I've tried to change several adapters but the card is never mounted (Trusty Tahr). Card is recognized by other card readers and the internal card reader recognizes other micro-sd cards. When I insert the card, I get in dmesg: [ 725.527784] mmc0: error -110 whilst initialising SD card [ 725.531751] sdhci-pci :01:04.1: Will use DMA mode even though HW doesn't fully claim to support it. repeated few times. Card reader in lspci: 01:04.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) Subsystem: Acer Incorporated [ALI] Device 0126 Kernel driver in use: sdhci-pci Current kernel: 3.13.0-37-generic ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cristian 1530 F pulseaudio CRDA: Error: [Errno 2] File o directory non esistente: 'iw' CurrentDesktop: LXDE Date: Sun Oct 19 17:59:55 2014 HibernationDevice: RESUME=UUID=048968cd-73dc-48fc-864f-54335e31460e InstallationDate: Installed on 2014-05-20 (152 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 5986:0102 Acer, Inc Crystal Eye Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer Aspire 7520 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=b9458892-57b3-47d6-9950-ad267560f2e2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/31/2007 dmi.bios.vendor: Acer dmi.bios.version: V1.30 dmi.board.name: Fuquene dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV1.30:bd12/31/2007:svnAcer:pnAspire7520:pvrV1.30:rvnAcer:rnFuquene:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 7520 dmi.product.version: V1.30 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1589379] Re: System frozen after resume, on Ubuntu 16.04 kernel 4.4.0-22
I just tested 4.7-rc6, the bug is reproduced (system frozen on resume). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589379 Title: System frozen after resume, on Ubuntu 16.04 kernel 4.4.0-22 Status in linux package in Ubuntu: Incomplete Bug description: Problem on HP probook 450, with Radeon R7 M260/M265. The last kernel on which resume works is 4.4.3-040403-generic. I have the problem on all kernels above, including v4.6-rc7-wily. ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 Annotation: This occurred during a previous suspend, and prevented the system from resuming properly. ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bastien2164 F pulseaudio Date: Mon Jun 6 07:50:40 2016 DuplicateSignature: suspend/resume:HP HP ProBook 450 G3:N78 Ver. 01.06 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=1888eb9c-89d7-4478-b4bc-1ce90d714377 InstallationDate: Installed on 2016-05-05 (31 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterpreterPath: /usr/bin/python3.5 MachineType: HP HP ProBook 450 G3 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=b919e8bc-92b0-4fcc-b9d3-0d8f38803a2b 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: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux Title: [HP HP ProBook 450 G3] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/18/2015 dmi.bios.vendor: HP dmi.bios.version: N78 Ver. 01.06 dmi.board.name: 8101 dmi.board.vendor: HP dmi.board.version: KBC Version 16.20 dmi.chassis.asset.tag: 5CD6080WDD dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN78Ver.01.06:bd12/18/2015:svnHP:pnHPProBook450G3:pvr:rvnHP:rn8101:rvrKBCVersion16.20:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 450 G3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582075] Re: GPU HANG: ecode 6:0:0x85eefffc
It took a while but the problem reproduced itself even on 4.4.0-28. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582075 Title: GPU HANG: ecode 6:0:0x85eefffc Status in linux package in Ubuntu: Incomplete Bug description: I am using an i3 2100 system with an "Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)". I'm getting these errors after suspend, with the screen showing a little garbled (text appearing in the wrong color or disappearing). [27409.858424] [drm] GPU HANG: ecode 6:0:0x85eefffc, in chrome [9550], reason: Ring hung, action: reset [27409.858425] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [27409.858426] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [27409.858427] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [27409.858428] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [27409.858428] [drm] GPU crash dump saved to /sys/class/drm/card0/error --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haggai 8000 F pulseaudio /dev/snd/controlC0: haggai 8000 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ab5f4eed-4f9d-4097-8a15-cd7bc60070fa InstallationDate: Installed on 2013-01-31 (1200 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic root=UUID=35dc6554-8a90-49e3-852a-4ae844b92802 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-06 (10 days ago) UserGroups: adm cdrom debian-transmission dip docker libvirtd lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67BL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10189-207 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-207:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596631] Re: linux: 3.19.0-65.73 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/vivid/3.19.0-65.73 /vivid-proposed-frozen.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596631 Title: linux: 3.19.0-65.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-65.73 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1596631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1600092] Re: radeon: monitor connected to onboard VGA doesn't work with Xenial
Aaron Peromsik, thank you for reporting this and helping make Ubuntu better. Given you have confirmed the fix commit via testing, and it was CC'ed to stable, I'll go ahead and mark this Triaged. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1600092 Title: radeon: monitor connected to onboard VGA doesn't work with Xenial Status in linux package in Ubuntu: Triaged Bug description: Ubuntu recognizes the VGA monitor it but it does not show anything. Monitor works fine during initial boot/BIOS. dmesg says: [3.311243] [drm] Initialized radeon 2.43.0 20080528 for :00:01.0 on minor 0 [ 16.843630] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage [ 16.843663] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed Fix commit: https://github.com/torvalds/linux/commit/c8213a638f65bf487c10593c216525952cca3690 I built a packaged kernel from xenial git source plus that one commit, and when I boot that kernel, the monitor in the VGA port works fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp1', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Jul 7 23:39:27 2016 HibernationDevice: RESUME=UUID=5012a75e-a79a-46fa-94f7-db367d25b3f0 InstallationDate: Installed on 2011-11-01 (1710 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=d13d1157-b660-43bb-a0af-fa8771808d10 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: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-07-04 (4 days ago) dmi.bios.date: 05/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88X-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/28/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3H: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/1600092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1600092] Re: radeon: monitor connected to onboard VGA doesn't work with Xenial
** Tags added: bios-outdated-f7 cherry-pick ** Description changed: - [In comments on 1579481 I mentioned that I had found and cherry-picked a - fix from upstream. I was asked to file another bug so that my hardware - information could be compared. apport will show kernel version 4.4.0-24 - but the issue is reproducible on 4.4.0-28 as well-- just didn't want to - uninstall my fixed version in order to post my hardware info.] - - I have an AMD based desktop system with onboard/APU graphics. I have a - monitor which had been hooked up via DVI until yesterday. Picked up a - nice refurbished monitor which I plugged in to the onboard DVI port, and - moved the other monitor to the VGA port. Ubuntu recognizes it but it - does not show anything. Monitor works fine during initial boot/BIOS. + Ubuntu recognizes the VGA monitor it but it does not show anything. + Monitor works fine during initial boot/BIOS. dmesg says: - [3.311243] [drm] Initialized radeon 2.43.0 20080528 for :00:01.0 on minor 0 [ 16.843630] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage [ 16.843663] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed - Searching for those errors I found bug 1579481 which says it is fixed - upstream, so I went searching for which commit might have fixed it, and - I found this one: + Fix commit: https://github.com/torvalds/linux/commit/c8213a638f65bf487c10593c216525952cca3690 I built a packaged kernel from xenial git source plus that one commit, and when I boot that kernel, the monitor in the VGA port works fine. - Probably worth adding that commit to the official Xenial kernel since - others stated that the issue is a regression. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp1', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Jul 7 23:39:27 2016 HibernationDevice: RESUME=UUID=5012a75e-a79a-46fa-94f7-db367d25b3f0 InstallationDate: Installed on 2011-11-01 (1710 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=d13d1157-b660-43bb-a0af-fa8771808d10 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: - linux-restricted-modules-4.4.0-24-generic N/A - linux-backports-modules-4.4.0-24-generic N/A - linux-firmware1.157.1 + linux-restricted-modules-4.4.0-24-generic N/A + linux-backports-modules-4.4.0-24-generic N/A + linux-firmware1.157.1 RfKill: - + SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-07-04 (4 days ago) dmi.bios.date: 05/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88X-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/28/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3H: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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1600092 Title: radeon: monitor connected to onboard VGA doesn't work with Xenial Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu recognizes the VGA monitor it but it does not show anything. Monitor works fine during initial boot/BIOS. dmesg says: [3.311243] [drm] Initialized radeon 2.43.0 20080528 for :00:01.0 on minor 0 [ 16.843630] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage [ 16.843663] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed Fix commit: https://github.com/torvalds/linux/commit/c8213a638f65bf487c10593c216525952cca3690
[Kernel-packages] [Bug 1597897] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-30.49/ms10-35-mcdivittB0-kernel__4.4.0-30.49__2016-07-08_04-03-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1597897 Title: linux: 4.4.0-30.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-30.49 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
Does this bug happen for people after a USB drive has spun down and the computer tries to access it? My USB freezing issue goes away if I disable UAS for a particular drive. It works fine with UAS until it spins down but the USB subsystem freezes when it tries to spin it up, requiring me to reboot the PC and power cycle the drive. To disable UAS for the drive, first find its identifier with the lsbusb command. For example mine looks like this, ie with identifier 1058:1230: Bus 002 Device 003: ID 1058:1230 Western Digital Technologies, Inc. My Book Add a file like /etc/modprobe.d/usb_storage.conf with the contents and the appropriate identifier: options usb_storage quirks=1058:1230:u and run "sudo update-initramfs -u -k all" and reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413440 Title: USB stops working after a while (xhci_hcd :00:14.0: Timeout while waiting for setup device command) Status in System76: Triaged Status in linux package in Ubuntu: Triaged Bug description: On my laptop the kernel will sometimes drop the USB hub. After this, the laptop doesn't recognise any device plugged in to the USB ports - plugging and unplugging any device I've tried into any of the USB ports produces no response, not even dmesg entries. Strangely this also applies to bluetooth - it no longer works once USB has dropped (possibly the module is hung of the bus internally). Once this has happened only a reboot fixes it; I've not managed to find any combination of module unload/reload or suspend cycles to reinitialise things correctly. Relevant snippet of dmesg: [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead [48838.079742] xhci_hcd :00:14.0: Abort command ring failed [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079806] sched: RT throttling activated [48838.079981] usb 1-1: USB disconnect, device number 16 [48838.079985] usb 1-1.2: USB disconnect, device number 18 [48838.079987] usb 1-1.2.3: USB disconnect, device number 19 [48838.080285] usb 1-1.2.4: USB disconnect, device number 20 [48838.111892] usb 1-1.4: USB disconnect, device number 17 [48838.191292] usb 1-4: USB disconnect, device number 6 [48838.267550] usb 1-10: USB disconnect, device number 8 [48838.282968] usb 2-1: device not accepting address 8, error -62 [48838.282983] usb 2-1: USB disconnect, device number 8 [48838.282986] usb 2-1.2: USB disconnect, device number 9 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 4255 F pulseaudio /dev/snd/controlC0: chris 4255 F pulseaudio CRDA: country AU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (3, 23), (N/A) (5250 - 5330 @ 40), (3, 23), (0 ms), DFS (5735 - 5835 @ 40), (3, 30), (N/A) CurrentDesktop: Unity Date: Thu Jan 22 12:59:27 2015 InstallationDate: Installed on 2013-08-06 (533 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd break=mount RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.141 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1413440/+subscriptions -- Mailing list: https://l
[Kernel-packages] [Bug 1597109] Re: linux: 3.2.0-106.147 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/precise/3.2.0-106.147 /precise-proposed-frozen.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1597109 Title: linux: 3.2.0-106.147 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug is for tracking the 3.2.0-106.147 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1600092] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1600092 Title: radeon: monitor connected to onboard VGA doesn't work with Xenial Status in linux package in Ubuntu: Confirmed Bug description: [In comments on 1579481 I mentioned that I had found and cherry-picked a fix from upstream. I was asked to file another bug so that my hardware information could be compared. apport will show kernel version 4.4.0-24 but the issue is reproducible on 4.4.0-28 as well-- just didn't want to uninstall my fixed version in order to post my hardware info.] I have an AMD based desktop system with onboard/APU graphics. I have a monitor which had been hooked up via DVI until yesterday. Picked up a nice refurbished monitor which I plugged in to the onboard DVI port, and moved the other monitor to the VGA port. Ubuntu recognizes it but it does not show anything. Monitor works fine during initial boot/BIOS. dmesg says: [3.311243] [drm] Initialized radeon 2.43.0 20080528 for :00:01.0 on minor 0 [ 16.843630] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage [ 16.843663] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed Searching for those errors I found bug 1579481 which says it is fixed upstream, so I went searching for which commit might have fixed it, and I found this one: https://github.com/torvalds/linux/commit/c8213a638f65bf487c10593c216525952cca3690 I built a packaged kernel from xenial git source plus that one commit, and when I boot that kernel, the monitor in the VGA port works fine. Probably worth adding that commit to the official Xenial kernel since others stated that the issue is a regression. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp1', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Jul 7 23:39:27 2016 HibernationDevice: RESUME=UUID=5012a75e-a79a-46fa-94f7-db367d25b3f0 InstallationDate: Installed on 2011-11-01 (1710 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=d13d1157-b660-43bb-a0af-fa8771808d10 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: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-07-04 (4 days ago) dmi.bios.date: 05/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88X-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/28/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3H: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/1600092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1600092] [NEW] radeon: monitor connected to onboard VGA doesn't work with Xenial
Public bug reported: [In comments on 1579481 I mentioned that I had found and cherry-picked a fix from upstream. I was asked to file another bug so that my hardware information could be compared. apport will show kernel version 4.4.0-24 but the issue is reproducible on 4.4.0-28 as well-- just didn't want to uninstall my fixed version in order to post my hardware info.] I have an AMD based desktop system with onboard/APU graphics. I have a monitor which had been hooked up via DVI until yesterday. Picked up a nice refurbished monitor which I plugged in to the onboard DVI port, and moved the other monitor to the VGA port. Ubuntu recognizes it but it does not show anything. Monitor works fine during initial boot/BIOS. dmesg says: [3.311243] [drm] Initialized radeon 2.43.0 20080528 for :00:01.0 on minor 0 [ 16.843630] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage [ 16.843663] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed Searching for those errors I found bug 1579481 which says it is fixed upstream, so I went searching for which commit might have fixed it, and I found this one: https://github.com/torvalds/linux/commit/c8213a638f65bf487c10593c216525952cca3690 I built a packaged kernel from xenial git source plus that one commit, and when I boot that kernel, the monitor in the VGA port works fine. Probably worth adding that commit to the official Xenial kernel since others stated that the issue is a regression. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp1', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Jul 7 23:39:27 2016 HibernationDevice: RESUME=UUID=5012a75e-a79a-46fa-94f7-db367d25b3f0 InstallationDate: Installed on 2011-11-01 (1710 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=d13d1157-b660-43bb-a0af-fa8771808d10 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: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-07-04 (4 days ago) dmi.bios.date: 05/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88X-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/28/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3H: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. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1600092 Title: radeon: monitor connected to onboard VGA doesn't work with Xenial Status in linux package in Ubuntu: Confirmed Bug description: [In comments on 1579481 I mentioned that I had found and cherry-picked a fix from upstream. I was asked to file another bug so that my hardware information could be compared. apport will show kernel version 4.4.0-24 but the issue is reproducible on 4.4.0-28 as well-- just didn't want to uninstall my fixed version in order to post my hardware info.] I have an AMD based desktop system with onboard/APU graphics. I have a monitor which had been hooked up via DVI until yesterday. Picked up a nice refurbished monitor which I plugged in to the onboard DVI port, and moved the other monitor to the VGA port. Ubuntu recognizes it but it does not show anything. Monitor works fine during initial boot/BIOS. dmesg says: [3.311243] [drm] Initialized radeon 2.43.0 20080528 for :00:01.0 on minor 0 [ 16.843630] [drm:rade
[Kernel-packages] [Bug 1597897] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 3, failed: 2
tests ran: 3, failed: 2; http://kernel.ubuntu.com/testing/4.4.0-30.49/ms10-35-mcdivittB0-kernel__4.4.0-30.49__2016-07-08_02-27-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/1597897 Title: linux: 4.4.0-30.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-30.49 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1541392] Re: AR3011 Bluetooth not starting after being stoped (but detected)
With a fresh install of 16.04 on HP 4430s laptop, I have this same issue. BT worked before I setup my wireless network, and then didn't. I also can confirm the workaround above of shutting down the laptop, removing power(battery as well), seems to correct the issue. Fixes tried: 1. uninstalled and reinstalled bluetooth 2. echo "options ath9k btcoex_enable=1" | sudo tee /etc/modprobe.d/ath9k.conf 3. installed mainline kernel 4.6.3-040603-generic via dpkg -i 4. tried workaround above--seemed to correct, but for how long? Steps to reproduce: 1. put laptop into suspended mode 2. Bluetooth icon shows on status bar, but will not reconnect 3. rebooted--> BT still Broken 4. shutdown laptop and removed all power 5. BT corrected Attached BT_Issue_corrected.txt which shows when issue is occrring and when working(working part on bottom: 1. While the issue was occurring created BT_Issue.txt--> hciconfig > BT_Issue.txt, lsmod >> BT_Issue.txt, lsusb, dmesg | grep -i blue, lspci 2. While the issue was corrected created BT_Issue_corrected.txt--> hciconfig > BT_Issue.txt, lsmod >> BT_Issue.txt, lsusb >> BT_Issue.txt, dmesg | grep -i blue >> BT_Issue.txt, lspci >> BT_Issue.txt ** Attachment added: "hciconfig > BT_Issue.txt, lsmod >> BT_Issue.txt, lsusb, dmesg | grep -i blue, lspci" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1541392/+attachment/4697261/+files/BT_Issue_corrected.txt -- 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/1541392 Title: AR3011 Bluetooth not starting after being stoped (but detected) Status in bluez package in Ubuntu: New Bug description: kernel : 4.2.0-27 onboard bluetooth controller : AR3011 The Bluetooth was working great. I deactivated the bluetooth via the indicator, and then, impossible to start it. Neither from the settings bluetooth interface, neither via hciconfig. The service was of course started without problems. The device was well recognized and started, could find which usb port and everything. However hciconfig could not see it: $ hciconfig -a hci0 hci0: Type: BR/EDR Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:12 acl:0 sco:0 commands:4 errors:0 Of course I restarted the system, tried purging all bluetooth related packages, tried installing blueman. Nothing would make it start. Finally I found this thread of arch linux : https://bbs.archlinux.org/viewtopic.php?id=171357 So basically I shut down the computer, waited a while, started the computer and the bluetooth is functional again. I will try reproducing the bug. I tried, but it did not happen again. Maybe it's because I was listening music, lost signal, came back to the pc and closed bluetooth. Any thoughts of what is this caused by? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1541392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579481] Re: 16.04 -> External Monitor not working -> radeon VCE init error (-110)
Aaron Peromsik, so your hardware and issue may be scoped, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579481 Title: 16.04 -> External Monitor not working -> radeon VCE init error (-110) Status in linux package in Ubuntu: Incomplete Bug description: Since I've upgraded 15.10 to 16.04 my external monitor is not working anymore. Whether I plug it directly into the DVI port of my laptop ("HP EliteBook 840 G1") or whether I plug it into the DVI or VGA port of my docking station "HP 2013 UltraSlim-Dockingstation" I get the following error in "/var/log/syslog": ... May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.377223] radeon :03:00.0: VCE init error (-110). May 4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [ 64.811603] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage May 4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [ 64.811619] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed ... I tried as well a fresh 16.04 install but this still did not help. The full log related to plugging in an external monitor is: ... May 4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [ 62.573716] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment May 4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [ 62.578032] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment May 4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [ 62.578106] acpi PNP0501:00: Still not present May 4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [ 62.578184] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.267945] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.267950] [drm] PCIE gen 2 link speeds already enabled May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275081] [drm] PCIE GART of 2048M enabled (table at 0x002E8000). May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275187] radeon :03:00.0: WB enabled May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275190] radeon :03:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x880434a83c00 May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275191] radeon :03:00.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu addr 0x880434a83c04 May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275192] radeon :03:00.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu addr 0x880434a83c08 May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275194] radeon :03:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x880434a83c0c May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275195] radeon :03:00.0: fence driver on ring 4 use gpu addr 0x4c10 and cpu addr 0x880434a83c10 May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.276738] radeon :03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90002835a18 May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.377223] radeon :03:00.0: VCE init error (-110). May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612628] [drm] ring test on 0 succeeded in 1 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612635] [drm] ring test on 1 succeeded in 1 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612640] [drm] ring test on 2 succeeded in 1 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612650] [drm] ring test on 3 succeeded in 5 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612658] [drm] ring test on 4 succeeded in 5 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788345] [drm] ring test on 5 succeeded in 2 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788352] [drm] UVD initialized successfully. May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788388] [drm] ib test on ring 0 succeeded in 0 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788421] [drm] ib test on ring 1 succeeded in 0 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788453] [drm] ib test on ring 2 succeeded in 0 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788483] [drm] ib test on ring 3 succeeded in 0 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788514] [drm] ib test on
[Kernel-packages] [Bug 1573648] Re: 16.04 -> AMD APU via VGA gives blank screen
As I mentioned on 1579481: The commit below (also from upstream) fixes this for me. Hadn't noticed the one mentioned above... I only cherry- picked this one on top of current xenial git source. Would be nice to see this commit find its way into official Xenial kernels. https://github.com/torvalds/linux/commit/c8213a638f65bf487c10593c216525952cca3690 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573648 Title: 16.04 -> AMD APU via VGA gives blank screen Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to 16.04, the system will only show a blank screen when a monitor is connected to the VGA output. The system itself is able to completely start-up (checked via a ssh login). Starting up using an older kernel (in this case 4.2.0) gives a functional graphical system. Possibly related dmesg lines (when booting 4.4.0): kernel: [9.131059] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage kernel: [9.131088] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed It might be related to the following kernel post (but i am not entirely sure): https://lists.freedesktop.org/archives/dri-devel/2016-March/10.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rene 2014 F pulseaudio /dev/snd/controlC0: rene 2014 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 16:29:44 2016 HibernationDevice: RESUME=UUID=98dbb6ee-ff08-4e9f-b01d-55b2f28c6a1e InstallationDate: Installed on 2015-12-29 (114 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic.efi.signed root=/dev/mapper/VGelmo-LVroot ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago) dmi.bios.date: 12/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd12/04/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573648/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579481] Re: 16.04 -> External Monitor not working -> radeon VCE init error (-110)
Confirmed: typing this on my second screen, connected via VGA, after cherry-picking the commit I linked to in #28. Without that commit the second screen was recognized but remained dark while connected to the VGA port of my Kaveri-based desktop. Same monitor had been fine when connected via DVI. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579481 Title: 16.04 -> External Monitor not working -> radeon VCE init error (-110) Status in linux package in Ubuntu: Incomplete Bug description: Since I've upgraded 15.10 to 16.04 my external monitor is not working anymore. Whether I plug it directly into the DVI port of my laptop ("HP EliteBook 840 G1") or whether I plug it into the DVI or VGA port of my docking station "HP 2013 UltraSlim-Dockingstation" I get the following error in "/var/log/syslog": ... May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.377223] radeon :03:00.0: VCE init error (-110). May 4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [ 64.811603] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage May 4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [ 64.811619] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed ... I tried as well a fresh 16.04 install but this still did not help. The full log related to plugging in an external monitor is: ... May 4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [ 62.573716] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment May 4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [ 62.578032] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment May 4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [ 62.578106] acpi PNP0501:00: Still not present May 4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [ 62.578184] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.267945] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.267950] [drm] PCIE gen 2 link speeds already enabled May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275081] [drm] PCIE GART of 2048M enabled (table at 0x002E8000). May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275187] radeon :03:00.0: WB enabled May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275190] radeon :03:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x880434a83c00 May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275191] radeon :03:00.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu addr 0x880434a83c04 May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275192] radeon :03:00.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu addr 0x880434a83c08 May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275194] radeon :03:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x880434a83c0c May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275195] radeon :03:00.0: fence driver on ring 4 use gpu addr 0x4c10 and cpu addr 0x880434a83c10 May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.276738] radeon :03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90002835a18 May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.377223] radeon :03:00.0: VCE init error (-110). May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612628] [drm] ring test on 0 succeeded in 1 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612635] [drm] ring test on 1 succeeded in 1 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612640] [drm] ring test on 2 succeeded in 1 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612650] [drm] ring test on 3 succeeded in 5 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612658] [drm] ring test on 4 succeeded in 5 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788345] [drm] ring test on 5 succeeded in 2 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788352] [drm] UVD initialized successfully. May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788388] [drm] ib test on ring 0 succeeded in 0 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788421] [drm] ib test on ring 1 succeeded in 0 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788453] [drm] ib test on ring 2 succeeded in 0 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788483] [drm] ib test on ring 3 succeeded in 0 usecs May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788514] [drm] ib test on ring 4 succeeded in 0 usecs
[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI
Hello Mathieu, or anyone else affected, Accepted shim-signed into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shim- signed/1.17~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-failed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1574727 Title: [SRU] Enforce using signed kernels and modules on UEFI Status in dkms package in Ubuntu: Fix Released Status in efibootmgr package in Ubuntu: Fix Released Status in efivar package in Ubuntu: Fix Released Status in grub2 package in Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in mokutil package in Ubuntu: Fix Released Status in shim package in Ubuntu: New Status in shim-signed package in Ubuntu: Fix Released Status in dkms source package in Precise: New Status in efibootmgr source package in Precise: Invalid Status in efivar source package in Precise: Fix Released Status in grub2 source package in Precise: Invalid Status in grub2-signed source package in Precise: Invalid Status in mokutil source package in Precise: Fix Released Status in shim source package in Precise: New Status in shim-signed source package in Precise: Fix Committed Status in dkms source package in Trusty: Fix Committed Status in efibootmgr source package in Trusty: Invalid Status in efivar source package in Trusty: Fix Committed Status in grub2 source package in Trusty: Invalid Status in grub2-signed source package in Trusty: Invalid Status in mokutil source package in Trusty: Fix Committed Status in shim source package in Trusty: New Status in shim-signed source package in Trusty: Fix Committed Status in dkms source package in Wily: Fix Committed Status in efibootmgr source package in Wily: Fix Released Status in efivar source package in Wily: Fix Released Status in grub2 source package in Wily: Invalid Status in grub2-signed source package in Wily: Invalid Status in mokutil source package in Wily: Fix Committed Status in shim source package in Wily: New Status in shim-signed source package in Wily: Fix Committed Status in dkms source package in Xenial: Fix Released Status in efibootmgr source package in Xenial: Fix Released Status in efivar source package in Xenial: Fix Released Status in grub2 source package in Xenial: In Progress Status in grub2-signed source package in Xenial: In Progress Status in mokutil source package in Xenial: Fix Released Status in shim source package in Xenial: New Status in shim-signed source package in Xenial: Fix Committed Bug description: [Rationale] Secure Boot is good. We want to be able to validate that as much as possible of the boot process happens with signed binaries; from our shim (the part that is loaded by the EFI firmware itself), down to grub2, the kernel, and even loaded modules. [Impact] All our users booting in UEFI; on all supported releases. [Test cases] https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0 Test cases here are separated by the components that need to be changed: = mokutil = Adding a MOK key: 1) Install system 2) Run 'mokutil --import ' to import a signing certificate. 3) On reboot; validate MOK prompts for new MOK key to add. Toggling Secure Boot state: 1) Install system 2) mokutil --enable-validationormokutil --disable-validation 3) Validate that on reboot MOK prompts to change Secure Boot state. Listing keys: 1) mokutil --list-enrolled -- should list keys previously enrolled, and Microsoft keys on systems that are configured with them for factory Secure Boot. = efivar = libefivar0 gets tested via the use of mokutil. Since it is a library with no directly usable binaries; we rely on mokutil / sbsigntool / efibootmgr to do testing. 1) Run efibootmgr -v ; verify it lists BootEntries. 2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that on reboot; you can get into a boot menu that will list 'ubuntu2', and that picking that boot entry boot
[Kernel-packages] [Bug 1574727] Please test proposed package
Hello Mathieu, or anyone else affected, Accepted shim-signed into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shim- signed/1.17~14.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1574727 Title: [SRU] Enforce using signed kernels and modules on UEFI Status in dkms package in Ubuntu: Fix Released Status in efibootmgr package in Ubuntu: Fix Released Status in efivar package in Ubuntu: Fix Released Status in grub2 package in Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in mokutil package in Ubuntu: Fix Released Status in shim package in Ubuntu: New Status in shim-signed package in Ubuntu: Fix Released Status in dkms source package in Precise: New Status in efibootmgr source package in Precise: Invalid Status in efivar source package in Precise: Fix Released Status in grub2 source package in Precise: Invalid Status in grub2-signed source package in Precise: Invalid Status in mokutil source package in Precise: Fix Released Status in shim source package in Precise: New Status in shim-signed source package in Precise: Fix Committed Status in dkms source package in Trusty: Fix Committed Status in efibootmgr source package in Trusty: Invalid Status in efivar source package in Trusty: Fix Committed Status in grub2 source package in Trusty: Invalid Status in grub2-signed source package in Trusty: Invalid Status in mokutil source package in Trusty: Fix Committed Status in shim source package in Trusty: New Status in shim-signed source package in Trusty: Fix Committed Status in dkms source package in Wily: Fix Committed Status in efibootmgr source package in Wily: Fix Released Status in efivar source package in Wily: Fix Released Status in grub2 source package in Wily: Invalid Status in grub2-signed source package in Wily: Invalid Status in mokutil source package in Wily: Fix Committed Status in shim source package in Wily: New Status in shim-signed source package in Wily: Fix Committed Status in dkms source package in Xenial: Fix Released Status in efibootmgr source package in Xenial: Fix Released Status in efivar source package in Xenial: Fix Released Status in grub2 source package in Xenial: In Progress Status in grub2-signed source package in Xenial: In Progress Status in mokutil source package in Xenial: Fix Released Status in shim source package in Xenial: New Status in shim-signed source package in Xenial: Fix Committed Bug description: [Rationale] Secure Boot is good. We want to be able to validate that as much as possible of the boot process happens with signed binaries; from our shim (the part that is loaded by the EFI firmware itself), down to grub2, the kernel, and even loaded modules. [Impact] All our users booting in UEFI; on all supported releases. [Test cases] https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0 Test cases here are separated by the components that need to be changed: = mokutil = Adding a MOK key: 1) Install system 2) Run 'mokutil --import ' to import a signing certificate. 3) On reboot; validate MOK prompts for new MOK key to add. Toggling Secure Boot state: 1) Install system 2) mokutil --enable-validationormokutil --disable-validation 3) Validate that on reboot MOK prompts to change Secure Boot state. Listing keys: 1) mokutil --list-enrolled -- should list keys previously enrolled, and Microsoft keys on systems that are configured with them for factory Secure Boot. = efivar = libefivar0 gets tested via the use of mokutil. Since it is a library with no directly usable binaries; we rely on mokutil / sbsigntool / efibootmgr to do testing. 1) Run efibootmgr -v ; verify it lists BootEntries. 2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that on reboot; you can get into a boot menu that will list 'ubuntu2', and that picking that boot entry boots into Ubuntu. = shim-signed =
[Kernel-packages] [Bug 1574727] Please test proposed package
Hello Mathieu, or anyone else affected, Accepted shim-signed into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shim- signed/1.17~15.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1574727 Title: [SRU] Enforce using signed kernels and modules on UEFI Status in dkms package in Ubuntu: Fix Released Status in efibootmgr package in Ubuntu: Fix Released Status in efivar package in Ubuntu: Fix Released Status in grub2 package in Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in mokutil package in Ubuntu: Fix Released Status in shim package in Ubuntu: New Status in shim-signed package in Ubuntu: Fix Released Status in dkms source package in Precise: New Status in efibootmgr source package in Precise: Invalid Status in efivar source package in Precise: Fix Released Status in grub2 source package in Precise: Invalid Status in grub2-signed source package in Precise: Invalid Status in mokutil source package in Precise: Fix Released Status in shim source package in Precise: New Status in shim-signed source package in Precise: Fix Committed Status in dkms source package in Trusty: Fix Committed Status in efibootmgr source package in Trusty: Invalid Status in efivar source package in Trusty: Fix Committed Status in grub2 source package in Trusty: Invalid Status in grub2-signed source package in Trusty: Invalid Status in mokutil source package in Trusty: Fix Committed Status in shim source package in Trusty: New Status in shim-signed source package in Trusty: Fix Committed Status in dkms source package in Wily: Fix Committed Status in efibootmgr source package in Wily: Fix Released Status in efivar source package in Wily: Fix Released Status in grub2 source package in Wily: Invalid Status in grub2-signed source package in Wily: Invalid Status in mokutil source package in Wily: Fix Committed Status in shim source package in Wily: New Status in shim-signed source package in Wily: Fix Committed Status in dkms source package in Xenial: Fix Released Status in efibootmgr source package in Xenial: Fix Released Status in efivar source package in Xenial: Fix Released Status in grub2 source package in Xenial: In Progress Status in grub2-signed source package in Xenial: In Progress Status in mokutil source package in Xenial: Fix Released Status in shim source package in Xenial: New Status in shim-signed source package in Xenial: Fix Committed Bug description: [Rationale] Secure Boot is good. We want to be able to validate that as much as possible of the boot process happens with signed binaries; from our shim (the part that is loaded by the EFI firmware itself), down to grub2, the kernel, and even loaded modules. [Impact] All our users booting in UEFI; on all supported releases. [Test cases] https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0 Test cases here are separated by the components that need to be changed: = mokutil = Adding a MOK key: 1) Install system 2) Run 'mokutil --import ' to import a signing certificate. 3) On reboot; validate MOK prompts for new MOK key to add. Toggling Secure Boot state: 1) Install system 2) mokutil --enable-validationormokutil --disable-validation 3) Validate that on reboot MOK prompts to change Secure Boot state. Listing keys: 1) mokutil --list-enrolled -- should list keys previously enrolled, and Microsoft keys on systems that are configured with them for factory Secure Boot. = efivar = libefivar0 gets tested via the use of mokutil. Since it is a library with no directly usable binaries; we rely on mokutil / sbsigntool / efibootmgr to do testing. 1) Run efibootmgr -v ; verify it lists BootEntries. 2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that on reboot; you can get into a boot menu that will list 'ubuntu2', and that picking that boot entry boots into Ubuntu. = shim-signed =
[Kernel-packages] [Bug 1574727] Please test proposed package
Hello Mathieu, or anyone else affected, Accepted shim-signed into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shim- signed/1.17~12.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1574727 Title: [SRU] Enforce using signed kernels and modules on UEFI Status in dkms package in Ubuntu: Fix Released Status in efibootmgr package in Ubuntu: Fix Released Status in efivar package in Ubuntu: Fix Released Status in grub2 package in Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in mokutil package in Ubuntu: Fix Released Status in shim package in Ubuntu: New Status in shim-signed package in Ubuntu: Fix Released Status in dkms source package in Precise: New Status in efibootmgr source package in Precise: Invalid Status in efivar source package in Precise: Fix Released Status in grub2 source package in Precise: Invalid Status in grub2-signed source package in Precise: Invalid Status in mokutil source package in Precise: Fix Released Status in shim source package in Precise: New Status in shim-signed source package in Precise: Fix Committed Status in dkms source package in Trusty: Fix Committed Status in efibootmgr source package in Trusty: Invalid Status in efivar source package in Trusty: Fix Committed Status in grub2 source package in Trusty: Invalid Status in grub2-signed source package in Trusty: Invalid Status in mokutil source package in Trusty: Fix Committed Status in shim source package in Trusty: New Status in shim-signed source package in Trusty: Fix Committed Status in dkms source package in Wily: Fix Committed Status in efibootmgr source package in Wily: Fix Released Status in efivar source package in Wily: Fix Released Status in grub2 source package in Wily: Invalid Status in grub2-signed source package in Wily: Invalid Status in mokutil source package in Wily: Fix Committed Status in shim source package in Wily: New Status in shim-signed source package in Wily: Fix Committed Status in dkms source package in Xenial: Fix Released Status in efibootmgr source package in Xenial: Fix Released Status in efivar source package in Xenial: Fix Released Status in grub2 source package in Xenial: In Progress Status in grub2-signed source package in Xenial: In Progress Status in mokutil source package in Xenial: Fix Released Status in shim source package in Xenial: New Status in shim-signed source package in Xenial: Fix Committed Bug description: [Rationale] Secure Boot is good. We want to be able to validate that as much as possible of the boot process happens with signed binaries; from our shim (the part that is loaded by the EFI firmware itself), down to grub2, the kernel, and even loaded modules. [Impact] All our users booting in UEFI; on all supported releases. [Test cases] https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0 Test cases here are separated by the components that need to be changed: = mokutil = Adding a MOK key: 1) Install system 2) Run 'mokutil --import ' to import a signing certificate. 3) On reboot; validate MOK prompts for new MOK key to add. Toggling Secure Boot state: 1) Install system 2) mokutil --enable-validationormokutil --disable-validation 3) Validate that on reboot MOK prompts to change Secure Boot state. Listing keys: 1) mokutil --list-enrolled -- should list keys previously enrolled, and Microsoft keys on systems that are configured with them for factory Secure Boot. = efivar = libefivar0 gets tested via the use of mokutil. Since it is a library with no directly usable binaries; we rely on mokutil / sbsigntool / efibootmgr to do testing. 1) Run efibootmgr -v ; verify it lists BootEntries. 2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that on reboot; you can get into a boot menu that will list 'ubuntu2', and that picking that boot entry boots into Ubuntu. = shim-signed =
[Kernel-packages] [Bug 1600060] Re: ZFS "partially filled holes lose birth time"
** Description changed: Note: This is different from Launchpad bug #1557151. This is another, similar, bug. - This is a very unfortunate bug because the fix only helps you moving - forward. - Bug description from Matt Ahrens at OpenZFS: "If a ZFS object contains a hole at level one, and then a data block is - created at level 0 underneath that l1 block, l0 holes will be created. - However, these l0 holes do not have the birth time property set; as a - result, incremental sends will not send those holes. + created at level 0 underneath that l1 block, l0 holes will be created. + However, these l0 holes do not have the birth time property set; as a + result, incremental sends will not send those holes. - Fix is to modify the dbuf_read code to fill in birth time data." + Fix is to modify the dbuf_read code to fill in birth time data." -- https://www.illumos.org/issues/6513 From pcd on IRC in #zfsonlinux: "basically, what happens is this: if you zero out an entire l1 indirect - block's worth of data (several megabytes), we save space by storing that - entire indirect block as a single hole in an l2 indirect block with - birth time N. If you then modify some of the data under that, but not - all of it, when the l1 indirect block is filled back in with mostly - holes and some data blocks, the wholes will not have any" + block's worth of data (several megabytes), we save space by storing that + entire indirect block as a single hole in an l2 indirect block with + birth time N. If you then modify some of the data under that, but not + all of it, when the l1 indirect block is filled back in with mostly + holes and some data blocks, the wholes will not have any" Fixed in ZoL here: https://github.com/zfsonlinux/zfs/commit/bc77ba73fec82d37c0b57949ec29edd9aa207677 This has *not* been merged into a ZoL release yet, nor the release branch. + + This is a very unfortunate bug because the fix only helps you moving forward. A separate bug has been opened to propose a fix for that: + https://www.illumos.org/issues/7175 -- 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/1600060 Title: ZFS "partially filled holes lose birth time" Status in zfs-linux package in Ubuntu: New Bug description: Note: This is different from Launchpad bug #1557151. This is another, similar, bug. Bug description from Matt Ahrens at OpenZFS: "If a ZFS object contains a hole at level one, and then a data block is created at level 0 underneath that l1 block, l0 holes will be created. However, these l0 holes do not have the birth time property set; as a result, incremental sends will not send those holes. Fix is to modify the dbuf_read code to fill in birth time data." -- https://www.illumos.org/issues/6513 From pcd on IRC in #zfsonlinux: "basically, what happens is this: if you zero out an entire l1 indirect block's worth of data (several megabytes), we save space by storing that entire indirect block as a single hole in an l2 indirect block with birth time N. If you then modify some of the data under that, but not all of it, when the l1 indirect block is filled back in with mostly holes and some data blocks, the wholes will not have any" Fixed in ZoL here: https://github.com/zfsonlinux/zfs/commit/bc77ba73fec82d37c0b57949ec29edd9aa207677 This has *not* been merged into a ZoL release yet, nor the release branch. This is a very unfortunate bug because the fix only helps you moving forward. A separate bug has been opened to propose a fix for that: https://www.illumos.org/issues/7175 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1600060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1600060] [NEW] ZFS "partially filled holes lose birth time"
Public bug reported: Note: This is different from Launchpad bug #1557151. This is another, similar, bug. Bug description from Matt Ahrens at OpenZFS: "If a ZFS object contains a hole at level one, and then a data block is created at level 0 underneath that l1 block, l0 holes will be created. However, these l0 holes do not have the birth time property set; as a result, incremental sends will not send those holes. Fix is to modify the dbuf_read code to fill in birth time data." -- https://www.illumos.org/issues/6513 >From pcd on IRC in #zfsonlinux: "basically, what happens is this: if you zero out an entire l1 indirect block's worth of data (several megabytes), we save space by storing that entire indirect block as a single hole in an l2 indirect block with birth time N. If you then modify some of the data under that, but not all of it, when the l1 indirect block is filled back in with mostly holes and some data blocks, the wholes will not have any" Fixed in ZoL here: https://github.com/zfsonlinux/zfs/commit/bc77ba73fec82d37c0b57949ec29edd9aa207677 This has *not* been merged into a ZoL release yet, nor the release branch. This is a very unfortunate bug because the fix only helps you moving forward. A separate bug has been opened to propose a fix for that: https://www.illumos.org/issues/7175 ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- 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/1600060 Title: ZFS "partially filled holes lose birth time" Status in zfs-linux package in Ubuntu: New Bug description: Note: This is different from Launchpad bug #1557151. This is another, similar, bug. Bug description from Matt Ahrens at OpenZFS: "If a ZFS object contains a hole at level one, and then a data block is created at level 0 underneath that l1 block, l0 holes will be created. However, these l0 holes do not have the birth time property set; as a result, incremental sends will not send those holes. Fix is to modify the dbuf_read code to fill in birth time data." -- https://www.illumos.org/issues/6513 From pcd on IRC in #zfsonlinux: "basically, what happens is this: if you zero out an entire l1 indirect block's worth of data (several megabytes), we save space by storing that entire indirect block as a single hole in an l2 indirect block with birth time N. If you then modify some of the data under that, but not all of it, when the l1 indirect block is filled back in with mostly holes and some data blocks, the wholes will not have any" Fixed in ZoL here: https://github.com/zfsonlinux/zfs/commit/bc77ba73fec82d37c0b57949ec29edd9aa207677 This has *not* been merged into a ZoL release yet, nor the release branch. This is a very unfortunate bug because the fix only helps you moving forward. A separate bug has been opened to propose a fix for that: https://www.illumos.org/issues/7175 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1600060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1423672] Re: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y
** Changed in: linux (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1423672 Title: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux package in Debian: Fix Released Bug description: SRU Justification: Impact: Users of VMs running 3.13/3.16 and ext4 can experience data corruption in the guest. Fix: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?h=7dec5603b6b8dc4c3e1c65d318bd2a5a8c62a424 Testcase: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818502#22 -- I noticed that one of my VM had this "dmesg -T" output: [Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204 [Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1): ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor inconsistent: 16446 vs 16445 free clusters [Thu Feb 19 06:25:09 2015] Aborting journal on device vda1-8. [Thu Feb 19 06:25:09 2015] EXT4-fs (vda1): Remounting filesystem read-only [Thu Feb 19 06:25:09 2015] [ cut here ] [Thu Feb 19 06:25:09 2015] WARNING: CPU: 0 PID: 9946 at /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0() [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables x_tables serio_raw psmouse floppy [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Not tainted 3.13.0-45-generic #74-Ubuntu [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [Thu Feb 19 06:25:09 2015] 0009 880003a11aa0 81720eb6 [Thu Feb 19 06:25:09 2015] 880003a11ad8 810677cd 88c41340 [Thu Feb 19 06:25:09 2015] 88000a58e000 81835280 1302 880003a11ae8 [Thu Feb 19 06:25:09 2015] Call Trace: [Thu Feb 19 06:25:09 2015] [] dump_stack+0x45/0x56 [Thu Feb 19 06:25:09 2015] [] warn_slowpath_common+0x7d/0xa0 [Thu Feb 19 06:25:09 2015] [] warn_slowpath_null+0x1a/0x20 [Thu Feb 19 06:25:09 2015] [] __ext4_handle_dirty_metadata+0x1a2/0x1c0 [Thu Feb 19 06:25:09 2015] [] ? ext4_dirty_inode+0x2a/0x60 [Thu Feb 19 06:25:09 2015] [] ext4_free_blocks+0x646/0xbf0 [Thu Feb 19 06:25:09 2015] [] ? wake_up_bit+0x25/0x30 [Thu Feb 19 06:25:09 2015] [] ext4_ext_rm_leaf+0x505/0x8f0 [Thu Feb 19 06:25:09 2015] [] ? __ext4_ext_check+0x197/0x370 [Thu Feb 19 06:25:09 2015] [] ? ext4_ext_remove_space+0xc0/0x7e0 [Thu Feb 19 06:25:09 2015] [] ext4_ext_remove_space+0x31c/0x7e0 [Thu Feb 19 06:25:09 2015] [] ext4_ext_truncate+0xb0/0xe0 [Thu Feb 19 06:25:09 2015] [] ext4_truncate+0x379/0x3c0 [Thu Feb 19 06:25:09 2015] [] ext4_evict_inode+0x408/0x4d0 [Thu Feb 19 06:25:09 2015] [] evict+0xb0/0x1b0 [Thu Feb 19 06:25:09 2015] [] iput+0xf5/0x180 [Thu Feb 19 06:25:09 2015] [] __dentry_kill+0x1a8/0x200 [Thu Feb 19 06:25:09 2015] [] dput+0xa5/0x180 [Thu Feb 19 06:25:09 2015] [] __fput+0x176/0x260 [Thu Feb 19 06:25:09 2015] [] fput+0xe/0x10 [Thu Feb 19 06:25:09 2015] [] task_work_run+0xa7/0xe0 [Thu Feb 19 06:25:09 2015] [] do_notify_resume+0x97/0xb0 [Thu Feb 19 06:25:09 2015] [] int_signal+0x12/0x17 [Thu Feb 19 06:25:09 2015] ---[ end trace ebff9843d81b5c41 ]--- [Thu Feb 19 06:25:09 2015] BUG: unable to handle kernel NULL pointer dereference at 0028 [Thu Feb 19 06:25:09 2015] IP: [] __ext4_error_inode+0x31/0x160 [Thu Feb 19 06:25:09 2015] PGD 167067 PUD 161067 PMD 0 [Thu Feb 19 06:25:09 2015] Oops: [#1] SMP [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables x_tables serio_raw psmouse floppy [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Tainted: G W 3.13.0-45-generic #74-Ubuntu [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [Thu Feb 19 06:25:09 2015] task: 880009ac4800 ti: 880003a1 task.ti: 880003a1 [Thu Feb 19 06:25:09 2015] RIP: 0010:[] [] __ext4_error_inode+0x31/0x160 [Thu Feb 19 06:25:09 2015] RSP: :880003a11a58 EFLAGS: 00010292 [Thu Feb 19 06:25:09 2015] RAX: RBX: RCX: 0086 [Thu Feb
Re: [Kernel-packages] [Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
Chrome flickers... but FF doesn't for me. Are you sure it isn't the browser. On Thu, Jul 7, 2016 at 7:58 PM, Thiago Martins wrote: > I'm on 4.4.0-28-generic (Xenial), problem still here. > > A good website to test it, is TradingView: > > https://www.tradingview.com/chart/7ipqeH3N/ > > Google Chrome window flickers a lot! Especially if you really use the > above website, by login in, clicking on its functions, pop-up windows > and etc... > > Hardware is a Macbook Pro, end-2015. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1552304). > https://bugs.launchpad.net/bugs/1554613 > > Title: > Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) > > Status in Linux: > Fix Released > Status in linux package in Ubuntu: > Fix Released > > Bug description: > *** Temporary workaround *** > Install Kernel from the following location: > - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ > > OR > Perform the following: > - $ apt-add-repository "deb > http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu yakkety main" > - $ echo -en "Package: *\nPin: release > o=LP-PPA-canonical-kernel-team-ppa\nPin-Priority: -1\n" >> > /etc/apt/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety > - $ apt update > - $ apt install linux-image-extra-4.6.0-6-generic > linux-headers-4.6.0-6-generic linux-tools-4.6.0-6-generic > ``` > There was a typo in instructions (/etc/preferences.d should have been > /etc/apt/preferences.d). > As result you might have upgraded Linux META packages and therefor you > won't receive proper upgrades of Xenial native Linux packages (hoping they > will ever contain the fix). > I suggest you move > /etc/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety to > /etc/apt/preferences.d/ and downgrade related packages: > $ apt update > $ apt install linux-headers-generic/xenial-updates > linux-tools-generic/xenial-updates linux-image-generic/xenial-updates > ``` > *** > > Please inspect duplicate reports for more details: > Bug #1522922 > Bug #1535048 > Bug #1552304 > Bug #1555158 > Bug #1561729 > Bug #1565234 > Bug #1568599 > Bug #1573392 > > does not affect 4.4.0-8 > affects 4.4.0-9 to 4.4.0-22 > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: linux-image-generic 4.4.0.11.12 > ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 > Uname: Linux 4.4.0-8-generic x86_64 > ApportVersion: 2.20-0ubuntu3 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: tbonfort 1498 F pulseaudio > CurrentDesktop: KDE > Date: Tue Mar 8 09:57:12 2016 > HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e > InstallationDate: Installed on 2016-01-07 (61 days ago) > InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 > (20151021) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 0c45:670c Microdia >Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Dell Inc. XPS 13 9350 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic > root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-4.4.0-8-generic N/A >linux-backports-modules-4.4.0-8-generic N/A >linux-firmware 1.156 > SourcePackage: linux > UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago) > dmi.bios.date: 01/08/2016 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.2.3 > dmi.board.name: 07TYC2 > dmi.board.vendor: Dell Inc. > dmi.board.version: A01 > dmi.chassis.type: 9 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: > dmi.product.name: XPS 13 9350 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: *** Temporary workaround *** Install Kernel from the following location: - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ OR Perform the following: - $ apt-add-repository "deb http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu yakkety main" - $ echo -en "Package: *\nPin: release o=LP-PPA-canonical-kernel-team-ppa\nPin-Priority: -1\n" >> /etc/apt/preferences.d/canonical-kernel-team-ubuntu-ppa-ya
[Kernel-packages] [Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
I'm on 4.4.0-28-generic (Xenial), problem still here. A good website to test it, is TradingView: https://www.tradingview.com/chart/7ipqeH3N/ Google Chrome window flickers a lot! Especially if you really use the above website, by login in, clicking on its functions, pop-up windows and etc... Hardware is a Macbook Pro, end-2015. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: *** Temporary workaround *** Install Kernel from the following location: - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ OR Perform the following: - $ apt-add-repository "deb http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu yakkety main" - $ echo -en "Package: *\nPin: release o=LP-PPA-canonical-kernel-team-ppa\nPin-Priority: -1\n" >> /etc/apt/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety - $ apt update - $ apt install linux-image-extra-4.6.0-6-generic linux-headers-4.6.0-6-generic linux-tools-4.6.0-6-generic ``` There was a typo in instructions (/etc/preferences.d should have been /etc/apt/preferences.d). As result you might have upgraded Linux META packages and therefor you won't receive proper upgrades of Xenial native Linux packages (hoping they will ever contain the fix). I suggest you move /etc/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety to /etc/apt/preferences.d/ and downgrade related packages: $ apt update $ apt install linux-headers-generic/xenial-updates linux-tools-generic/xenial-updates linux-image-generic/xenial-updates ``` *** Please inspect duplicate reports for more details: Bug #1522922 Bug #1535048 Bug #1552304 Bug #1555158 Bug #1561729 Bug #1565234 Bug #1568599 Bug #1573392 does not affect 4.4.0-8 affects 4.4.0-9 to 4.4.0-22 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.11.12 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tbonfort 1498 F pulseaudio CurrentDesktop: KDE Date: Tue Mar 8 09:57:12 2016 HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e InstallationDate: Installed on 2016-01-07 (61 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-8-generic N/A linux-backports-modules-4.4.0-8-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574845] Re: Hardware accelerated video decoding causes GPU crash (radeon driver)
** 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/1574845 Title: Hardware accelerated video decoding causes GPU crash (radeon driver) Status in linux package in Ubuntu: Confirmed Bug description: SMPlayer with vdpau output plays video ok, but after stopping video in few seconds system freezes. I attach smplayer.log with syslog messages during crash. The same happens with Kodi. I attach kodi.log with syslog messages during crash. WORKAROUND: Don't use hardware acceleration. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: multimedia 1757 F pulseaudio /dev/snd/controlC1: multimedia 1757 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7c796799-7a5f-45e4-8553-2d104ccaf5fd InstallationDate: Installed on 2013-11-30 (948 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer P5QL-E Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=002800d5-0471-42e5-abad-77cbf9f27354 ro quiet ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 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-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-28-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-23 (72 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0905 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.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.:bvr0905:bd12/01/2008:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5QL-E 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/1574845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555351] Re: High load freezes ubuntu completely everytime (have to reboot)
jion, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555351 Title: High load freezes ubuntu completely everytime (have to reboot) Status in linux package in Ubuntu: Incomplete Bug description: Whenever an intensive application runs which consumes lots of memory or hard drive i/o, Ubuntu freezes completely. It is even impossible to kill the offending task. Only "solution" is then to wait for the application to finish, or restart PC. Windows doesn't have this issue as bad as Ubuntu, in that Windows is always somewhat responsive, and you can attempt to kill the intensive application to recover the system. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-32-generic 4.2.0-32.37 ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 Uname: Linux 4.2.0-32-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Cannot stat file /proc/18210/fd/20: Input/output error USERPID ACCESS COMMAND /dev/snd/controlC0: cossio 2082 F pulseaudio /dev/snd/controlC1: cossio 2082 F pulseaudio CurrentDesktop: XFCE Date: Wed Mar 9 22:28:53 2016 HibernationDevice: RESUME=UUID=37d586ee-f517-4977-b9cd-189c200b0bac InstallationDate: Installed on 2015-08-03 (219 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: ASUSTeK COMPUTER INC. X550LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=52be177f-a0ea-4053-be39-bbeaff1a22df ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2016-01-31 (38 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.505 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.505:bd04/01/2014:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1530476] Re: Lenovo helix 2nd gen does not wake up from suspend
Richard Trabing, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1530476 Title: Lenovo helix 2nd gen does not wake up from suspend Status in linux package in Ubuntu: Incomplete Bug description: Using a fresh install of ubuntu 15.10. When the laptop enters suspend it wont wake up. Not from trigging the lid switch or pressing the power button. Using Latest kernel 4.2.0-22-generic. Tried with two different bios versions to rule out bios. The only option is to press and hold and do a new cold start. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jobe 1530 F pulseaudio /dev/snd/controlC0: jobe 1530 F pulseaudio CurrentDesktop: GNOME Date: Fri Jan 1 22:09:34 2016 HibernationDevice: RESUME=UUID=bbd6d6cd-2398-4046-ba00-e818132d983a InstallationDate: Installed on 2015-12-16 (16 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20CGCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-22-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N17ET83W (1.83 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CGCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K11826 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ET83W(1.83):bd12/02/2015:svnLENOVO:pn20CGCTO1WW:pvrThinkPadHelix2nd:rvnLENOVO:rn20CGCTO1WW:rvrSDK0K11826WIN:cvnLENOVO:ct11:cvrNone: dmi.product.name: 20CGCTO1WW dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 443278] Re: Logitech QuickCam USB webcams using pwc module (Pro, 3000, 4000) do not work if connected after booting
** Also affects: robert (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/443278 Title: Logitech QuickCam USB webcams using pwc module (Pro, 3000, 4000) do not work if connected after booting Status in linux package in Ubuntu: Won't Fix Status in robert package in Ubuntu: New Bug description: I am running Ubuntu 9.10 beta and am having problems with a Logitech QuickCam Pro 3000 USB camera. If the camera is connected when the computer boots, it works perfectly in the following applications: cheese, ekiga, gstreamer-properties, camorama. If the camera is connected AFTER I have booted the computer (either while within GNOME or while gdm is running), then it does not work with cheese, ekiga, gstreamer-properties, or camorama. I have verified both of these statements on both my desktop PC (from which this bug report is submitted) and on my laptop (which is also running Ubuntu 9.10 beta. Also, I have tested the camera from a third computer running Windows Vista so I do not believe the problem is related to the camera hardware or the hardware on either of my two computers running Ubuntu. This problem did not exist in earlier versions of Ubuntu so it is a regression. Due to the nature of the problem, I don't suspect that this is a bug with any of the desktop applications that I named or with gstreamer itself (since I have tried both gstreamer and non-gstreamer applications). I am happy to troubleshoot further but at this point I don't know how to determine if it is a problem with the kernel, kernel camera module (which is pwc), V4L or one of the hotplug frameworks. Thanks in advance to anyone who is able to assist with this! ProblemType: Bug Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jconte 2534 F pulseaudio /dev/snd/controlC0: jconte 2534 F pulseaudio /dev/snd/pcmC0D0p: jconte 2534 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0x9000, irq 23' Mixer name : 'eMicro EM28028' Components : 'AC97a:454d4328' Controls : 216 Simple ctrls : 38 Card1.Amixer.info: Card hw:1 'U0x46d0x8b0'/'USB Device 0x46d:0x8b0 at usb-:00:1d.1-1, full speed' Mixer name : 'USB Mixer' Components : 'USB046d:08b0' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined Capture channels: Mono Limits: Capture 0 - 3 Mono: Capture 3 [100%] [60.00dB] [on] Date: Mon Oct 5 12:43:02 2009 DistroRelease: Ubuntu 9.10 HibernationDevice: RESUME=UUID=56e17345-402e-481a-b849-53c844ecebcc MachineType: System Manufacturer System Name Package: linux-image-2.6.31-11-generic 2.6.31-11.38 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=d9defd99-23fc-4b9a-b330-ad7c31af5c10 ro quiet splash ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.38-generic RelatedPackageVersions: linux-backports-modules-2.6.31-11-generic N/A linux-firmware 1.20 RfKill: SourcePackage: linux Uname: Linux 2.6.31-11-generic i686 WpaSupplicantLog: dmi.bios.date: 11/10/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS P4PE ACPI BIOS Revision 1007 dmi.board.name: P4PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4PEACPIBIOSRevision1007:bd11/10/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4PE:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System 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/443278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1530476] Re: Lenovo helix 2nd gen does not wake up from suspend
** Tags removed: latest-bios-1.83 ** Tags added: bios-outdated-1.86 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1530476 Title: Lenovo helix 2nd gen does not wake up from suspend Status in linux package in Ubuntu: Incomplete Bug description: Using a fresh install of ubuntu 15.10. When the laptop enters suspend it wont wake up. Not from trigging the lid switch or pressing the power button. Using Latest kernel 4.2.0-22-generic. Tried with two different bios versions to rule out bios. The only option is to press and hold and do a new cold start. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jobe 1530 F pulseaudio /dev/snd/controlC0: jobe 1530 F pulseaudio CurrentDesktop: GNOME Date: Fri Jan 1 22:09:34 2016 HibernationDevice: RESUME=UUID=bbd6d6cd-2398-4046-ba00-e818132d983a InstallationDate: Installed on 2015-12-16 (16 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20CGCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-22-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N17ET83W (1.83 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CGCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K11826 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ET83W(1.83):bd12/02/2015:svnLENOVO:pn20CGCTO1WW:pvrThinkPadHelix2nd:rvnLENOVO:rn20CGCTO1WW:rvrSDK0K11826WIN:cvnLENOVO:ct11:cvrNone: dmi.product.name: 20CGCTO1WW dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
bhat3, if one thinks they have identified a fix commit, they may test it via https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_released_patch_from_upstream . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches Status in linux package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1531768] Re: [arm64] lockups some time after booting
http://lists.infradead.org/pipermail/linux-arm- kernel/2014-July/274251.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/1531768 Title: [arm64] lockups some time after booting Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I want to use for armhf autopkgtesting in LXD). I started with wily as that has lxd available (it's not yet available in trusty nor the PPA for arm64). However, pretty much any LXD task that I do (I haven't tried much else) on this machine takes unbearably long. A simple "lxc profile set default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes. I see tons of [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0 [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds. in dmesg (the attached apport info has the complete dmesg). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 09:18 seq crw-rw 1 root audio 116, 33 Jan 7 09:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Jan 7 09:24:01 2016 IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. Lspci: 00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008] Subsystem: Red Hat, Inc Device [1af4:1100] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=LABEL=cloudimg-rootfs earlyprintk RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1531768] Re: [arm64] lockups some time after booting
Bit more digging, I see that the CPU goes into idle either by a single WFI (wait for an interrupt) shallow sleep or a deeper arm_cpuidle_suspend() - the latter is akin to turning off the CPU. I wonder if we're seeing some issues with the wakeup latency taking a long time inside QEMU when the host is loaded, causing rcu sched issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1531768 Title: [arm64] lockups some time after booting Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I want to use for armhf autopkgtesting in LXD). I started with wily as that has lxd available (it's not yet available in trusty nor the PPA for arm64). However, pretty much any LXD task that I do (I haven't tried much else) on this machine takes unbearably long. A simple "lxc profile set default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes. I see tons of [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0 [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds. in dmesg (the attached apport info has the complete dmesg). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 09:18 seq crw-rw 1 root audio 116, 33 Jan 7 09:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Jan 7 09:24:01 2016 IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. Lspci: 00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008] Subsystem: Red Hat, Inc Device [1af4:1100] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=LABEL=cloudimg-rootfs earlyprintk RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 624510] Re: Copying To USB Is Very Slow
The issue has appeared on Ubuntu 16.04 with the 4.4.0-28-generic kernel. When doing sudo hdparm -tT /dev/sde /dev/sde: Timing cached reads: 8598 MB in 2.00 seconds = 4302.13 MB/sec Timing buffered disk reads: 56 MB in 3.11 seconds = 18.03 MB/sec Everything seems fine, but when writing into the USB drive the writing speed falls down to 9.34KB/s -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/624510 Title: Copying To USB Is Very Slow Status in linux package in Ubuntu: Fix Released Status in linux source package in Lucid: Fix Released Bug description: Copying files from hard disk to Usb or Usb to Hard Disk is very slow in Ubuntu 10.04.. Is there a way to speed up the process of copying with the installation of additional softwares... ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 Architecture: i386 Date: Thu Aug 26 14:03:27 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANG=en_IN.utf8 SHELL=/bin/bash SourcePackage: nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/624510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 159356] Re: System freeze on high memory usage
Maybe Linux 4.7 adresses the out-of-memory issues with the following changes: http://lwn.net/Articles/684945/ https://git.kernel.org/torvalds/c/0a0337e0d1d134465778a16f5cbea95086e8e9e0 https://git.kernel.org/torvalds/c/e28e909c36bb5d6319953822d84df00fce7cbd18 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/159356 Title: System freeze on high memory usage Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1599951] Re: On read_tsc function issue.
Thank you for providing a patch, and making Ubuntu better. Can you provide some information on the status of the patch with regards to getting it merged upstream? Has it been sent upstream, what sort of feedback has it received, is it getting applied to a subsystem maintainer's tree, etc? People affected by this bug are probably wondering why the kernel team doesn't just apply the patch and fix it. The reason is that the kernel team is reluctant (not opposed) to apply any patch to a stable kernel that is not from upstream. Applying patches that don't come from upstream add greatly to the support of the kernel as other upstream patches may touch the same area as the non-upstream patch and may prevent them from applying cleanly. To submit your patch, send your patch with the detailed description/changelog and your Signoff (ending with Signed-off-by: your name ), to the emails listed from ./scripts/get_maintainer.pl drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel sources). Once you have sent the patch upstream and it's accepted, please drop a note here so that we can cherry-pick/include the patch into Ubuntu kernel. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1599951 Title: On read_tsc function issue. Status in linux package in Ubuntu: Triaged Bug description: Below is result of perf report: read_tsc /proc/kcore │ │ │ │Disassembly of section load0: │ │81037780 : 66,67 │ push %rbp │ mov%rsp,%rbp │ lfence │ rdtsc 33,33 │ shl$0x20,%rdx │ or %rdx,%rax │ pop%rbp │← retq ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu2932 F pulseaudio CurrentDesktop: MATE Date: Thu Jul 7 21:18:17 2016 InstallationDate: Installed on 2016-04-29 (69 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1597897] modoc (ppc64el) - tests ran: 10, failed: 1
tests ran: 10, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-30.49/modoc__4.4.0-30.49__2016-07-07_21-39-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/1597897 Title: linux: 4.4.0-30.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-30.49 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
I built a Xenial test kernel[0] with the fix[1] suggested in comment #64. The fix was mentioned upstream[2]. That particular patch has not landed in mainline yet, but it was also cc'd to stable for all 4.4+ kernels. This commit can be added as a SAUCE patch if we find that it resolves this bug, it will be SAUCE until the real patch is applied through the normal stable update process. Can you test this kernel and see if it resolves this bug? Note, with this test kernel you need to install both the linux-image and linux- image-extra .deb packages. [0] http://kernel.ubuntu.com/~jsalisbury/lp1573062/ [1] https://patchwork.kernel.org/patch/8902401/ [2] https://lkml.org/lkml/2016/4/17/56 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04 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: memory_stress_ng, as part of server certification is failing for IBM Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is defined by the test locking up the server in an unrecoverable state which only a reboot will fix. I will be attaching screen and kern logs for the failures and a successful run on 14.04 on the same server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1531768] Re: [arm64] lockups some time after booting
On an idle Xenial cloud image I'm seeing: [ 1485.236760] [] __switch_to+0x90/0xa8 [ 1485.236772] [] __tick_nohz_idle_enter+0x50/0x3f0 [ 1485.236776] [] tick_nohz_idle_enter+0x40/0x70 [ 1485.236785] [] cpu_startup_entry+0x288/0x2d8 [ 1485.236791] [] secondary_start_kernel+0x120/0x130 [ 1485.236795] [<4008290c>] 0x4008290c after a while I get: [ 2462.806971] rcu_sched kthread starved for 15002 jiffies! g2579 c2578 f0x0 s3 ->state=0x1 [ 2667.835351] INFO: rcu_sched detected stalls on CPUs/tasks: [ 2667.836918] 0-...: (66 GPs behind) idle=cf0/0/0 softirq=5177/5177 fqs=0 [ 2667.838801] 2-...: (0 ticks this GP) idle=73a/0/0 softirq=4570/4570 fqs=0 [ 2667.840696] 3-...: (64 GPs behind) idle=eba/0/0 softirq=4654/4654 fqs=0 [ 2667.842533] (detected by 1, t=15002 jiffies, g=2638, c=2637, q=4389) and at this point sleeping blocks, for example strace on sleep(1) on the VM shows nanosleep({1, 0}) sleep forever, one has to SIGINT this as it never times out. Also the secondary_start_kernel() is indicative that the VM puts CPUs to sleep and wakes them on a timer. I can trigger this more often with more CPUs on the VM and also by loading the host, for example, producing a lot of cache or memory activity can trigger the initial hangs more frequently than having an idle host. So, I suspect there is a cpuhotplug and nohz combo causing issues here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1531768 Title: [arm64] lockups some time after booting Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I want to use for armhf autopkgtesting in LXD). I started with wily as that has lxd available (it's not yet available in trusty nor the PPA for arm64). However, pretty much any LXD task that I do (I haven't tried much else) on this machine takes unbearably long. A simple "lxc profile set default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes. I see tons of [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0 [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds. in dmesg (the attached apport info has the complete dmesg). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 09:18 seq crw-rw 1 root audio 116, 33 Jan 7 09:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Jan 7 09:24:01 2016 IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. Lspci: 00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008] Subsystem: Red Hat, Inc Device [1af4:1100] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=LABEL=cloudimg-rootfs earlyprintk RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580311] Re: Laptop panel output only if external display connected
I'm sorry, but there's no way I can do that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580311 Title: Laptop panel output only if external display connected Status in linux package in Ubuntu: Incomplete Bug description: Hi, Since updating to 16.04 with kernel vmlinuz-4.4.0-22-generic my laptop no longer completes the boot sequence under a normal boot scenario - the "loading initrd..." message is displayed, then, when the VGA modesetting usually kicks the display into a higher resolution, the screen blanks and the startup apparently halts. This is a regression from 4.2 series kernels. I can successfully bring up the system if I revert to 4.2.0-35, and also if I boot 4.4 with the failsafe setting (but then X is painfully slow, as its using software) Matt ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 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: Tue May 10 20:29:56 2016 DistUpgraded: 2016-05-04 00:10:55,503 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06ac] InstallationDate: Installed on 2015-05-12 (364 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 15-3552 PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-35-generic.efi.signed root=/dev/mapper/ubuntu--15--vg-root ro plymouth:debug i8042.nopnp=1 vesafb.invalid=1 drm.debug=0xe SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to xenial on 2016-05-03 (6 days ago) dmi.bios.date: 11/17/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.3 dmi.board.name: 0CP33T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.3:bd11/17/2015:svnDellInc.:pnInspiron15-3552:pvr4.0.3:rvnDellInc.:rn0CP33T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.3 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue May 10 12:26:45 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5578 vendor CMN xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
** No longer affects: linux (Ubuntu Wily) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04 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: memory_stress_ng, as part of server certification is failing for IBM Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is defined by the test locking up the server in an unrecoverable state which only a reboot will fix. I will be attaching screen and kern logs for the failures and a successful run on 14.04 on the same server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN
** Changed in: linux (Ubuntu Wily) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu Vivid) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1378123 Title: unix_socket_abstract.sh triggers an AppArmor WARN Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Won't Fix Status in linux source package in Wily: Won't Fix Status in linux source package in Xenial: Fix Released Bug description: Running the unix_socket_abstract.sh regression test script in a loop results in an AppArmor WARN message in the logs. On my test system, it typically takes between 1 and 3 runs of unix_socket_abstract.sh before the WARN is hit. It does not seem to occur with the unix_socket_pathname.sh or unix_socket_unnamed.sh tests. Here's the script I used: --- #!/bin/sh dmesg -C while ! dmesg -c | grep "AppArmor WARN"; do bash unix_socket_abstract.sh done --- The following back trace is emitted in the logs: [ 1365.017477] [ cut here ] [ 1365.017486] WARNING: CPU: 0 PID: 26026 at /build/buildd/linux-3.16.0/security/apparmor/label.c:1767 __aa_labelset_update_all+0x6f5/0x7f0() [ 1365.017487] AppArmor WARN __label_update: ((__aa_label_remove_and_insert((&(((label)->ent[(label)->size - 1])->ns)->labels), label, l) != l)): [ 1365.017489] Modules linked in: bnep rfcomm bluetooth 6lowpan_iphc kvm_intel kvm vmwgfx ttm drm_kms_helper serio_raw drm i2c_piix4 pvpanic parport_pc ppdev mac_hid lp parport psmouse pata_acpi floppy [ 1365.017505] CPU: 0 PID: 26026 Comm: apparmor_parser Tainted: GW 3.16.0-20-generic #27-Ubuntu [ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 1365.017509] 0009 88002dd23d88 8177f053 88002dd23dd0 [ 1365.017511] 88002dd23dc0 8106fcfd 880036602900 [ 1365.017513] 88003acaed00 0002 88003e02a0a0 88002dd23e20 [ 1365.017516] Call Trace: [ 1365.017522] [] dump_stack+0x45/0x56 [ 1365.017527] [] warn_slowpath_common+0x7d/0xa0 [ 1365.017530] [] warn_slowpath_fmt+0x4c/0x50 [ 1365.017533] [] ? __aa_label_remove_and_insert+0x7e/0x1a0 [ 1365.017536] [] __aa_labelset_update_all+0x6f5/0x7f0 [ 1365.017539] [] ? securityfs_remove+0x9a/0xb0 [ 1365.017542] [] aa_remove_profiles+0x143/0x4f0 [ 1365.017545] [] profile_remove+0x3e/0x70 [ 1365.017550] [] vfs_write+0xb7/0x1f0 [ 1365.017552] [] ? do_sys_open+0x1b9/0x280 [ 1365.017555] [] SyS_write+0x46/0xb0 [ 1365.017558] [] system_call_fastpath+0x1a/0x1f [ 1365.017560] ---[ end trace 1e09e2c565d9ef95 ]--- This occurs in an amd64 utopic vm: $ uname -a Linux sec-utopic-amd64 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:35:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1378123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574845] Re: Hardware accelerated video decoding causes GPU crash (radeon driver)
Christopher, I installed some of vdpau packages which was missing in 12.04. Which one exactly - I do not remember. If it is important and could be traced in log files - please give me a hint. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574845 Title: Hardware accelerated video decoding causes GPU crash (radeon driver) Status in linux package in Ubuntu: Incomplete Bug description: SMPlayer with vdpau output plays video ok, but after stopping video in few seconds system freezes. I attach smplayer.log with syslog messages during crash. The same happens with Kodi. I attach kodi.log with syslog messages during crash. WORKAROUND: Don't use hardware acceleration. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: multimedia 1757 F pulseaudio /dev/snd/controlC1: multimedia 1757 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7c796799-7a5f-45e4-8553-2d104ccaf5fd InstallationDate: Installed on 2013-11-30 (948 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer P5QL-E Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=002800d5-0471-42e5-abad-77cbf9f27354 ro quiet ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 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-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-28-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-23 (72 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0905 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.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.:bvr0905:bd12/01/2008:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5QL-E 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/1574845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1498667] Re: [Toshiba P50W-B00F] Touchscreen no longer working
** Changed in: linux (Ubuntu Wily) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1498667 Title: [Toshiba P50W-B00F] Touchscreen no longer working Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: Sometime in the last month or so my touchscreen stopped working on my Toshiba P50W. The dmesg log shows it constantly reconnecting to it: [ 556.407964] usb 1-4: new full-speed USB device number 119 using xhci_hcd [ 556.538341] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381 [ 556.538347] usb 1-4: New USB device strings: Mfr=4, Product=14, SerialNumber=0 [ 556.538349] usb 1-4: Product: Touchscreen [ 556.538351] usb 1-4: Manufacturer: ELAN [ 556.538505] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes [ 556.547788] input: ELAN Touchscreen as /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A1/input/input2374 [ 556.600478] hid-multitouch 0003:04F3:0381.04A1: input,hiddev0,hidraw4: USB HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0 [ 556.600584] usb 1-4: USB disconnect, device number 119 [ 556.860456] usb 1-4: new full-speed USB device number 120 using xhci_hcd [ 556.990494] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381 [ 556.990500] usb 1-4: New USB device strings: Mfr=4, Product=14, SerialNumber=0 [ 556.990503] usb 1-4: Product: Touchscreen [ 556.990506] usb 1-4: Manufacturer: ELAN [ 556.990755] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes [ 557.001248] input: ELAN Touchscreen as /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A2/input/input2376 [ 557.002517] hid-multitouch 0003:04F3:0381.04A2: input,hiddev0,hidraw4: USB HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0 [ 557.013831] usb 1-4: USB disconnect, device number 120 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-11-generic 4.2.0-11.13 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bob2041 F pulseaudio /dev/snd/controlC0: bob2041 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 23 09:46:25 2015 HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12 InstallationDate: Installed on 2013-12-26 (635 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: TOSHIBA Satellite P50W-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-11-generic N/A linux-backports-modules-4.2.0-11-generic N/A linux-firmware1.148 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2013-12-26 (635 days ago) dmi.bios.date: 08/08/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.40 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.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite P50W-B dmi.product.version: PSVP2A-00F002 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555351] Re: High load freezes ubuntu completely everytime (have to reboot)
Oh, and an important comment.. this bug happens to me in Ubuntu 14.04, 16.04, with unity and with kde (with unity the issue comes faster than with kde) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555351 Title: High load freezes ubuntu completely everytime (have to reboot) Status in linux package in Ubuntu: Incomplete Bug description: Whenever an intensive application runs which consumes lots of memory or hard drive i/o, Ubuntu freezes completely. It is even impossible to kill the offending task. Only "solution" is then to wait for the application to finish, or restart PC. Windows doesn't have this issue as bad as Ubuntu, in that Windows is always somewhat responsive, and you can attempt to kill the intensive application to recover the system. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-32-generic 4.2.0-32.37 ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 Uname: Linux 4.2.0-32-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Cannot stat file /proc/18210/fd/20: Input/output error USERPID ACCESS COMMAND /dev/snd/controlC0: cossio 2082 F pulseaudio /dev/snd/controlC1: cossio 2082 F pulseaudio CurrentDesktop: XFCE Date: Wed Mar 9 22:28:53 2016 HibernationDevice: RESUME=UUID=37d586ee-f517-4977-b9cd-189c200b0bac InstallationDate: Installed on 2015-08-03 (219 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: ASUSTeK COMPUTER INC. X550LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=52be177f-a0ea-4053-be39-bbeaff1a22df ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2016-01-31 (38 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.505 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.505:bd04/01/2014:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555351] Re: High load freezes ubuntu completely everytime (have to reboot)
I experience this bug all the time from at least 2 years. The issue started for me when I switch to 64bits ubuntu version. I'm a web developer and chrome is the main cause of this issue. Ubuntu starts to swap and all freezes until the application that is causing this stops or turn idle. CTRL+ALT+Fx and force kill works, but it is a slw proccess because the system turn very very very slow and the ctrl+alt+fx change + login + write the kill command takes a frustating long time that most of times I prefer to reboot hardly the PC. I've experienced this issue in many laptops (HP, Asus, dell) and in a desktop dell machine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555351 Title: High load freezes ubuntu completely everytime (have to reboot) Status in linux package in Ubuntu: Incomplete Bug description: Whenever an intensive application runs which consumes lots of memory or hard drive i/o, Ubuntu freezes completely. It is even impossible to kill the offending task. Only "solution" is then to wait for the application to finish, or restart PC. Windows doesn't have this issue as bad as Ubuntu, in that Windows is always somewhat responsive, and you can attempt to kill the intensive application to recover the system. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-32-generic 4.2.0-32.37 ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 Uname: Linux 4.2.0-32-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Cannot stat file /proc/18210/fd/20: Input/output error USERPID ACCESS COMMAND /dev/snd/controlC0: cossio 2082 F pulseaudio /dev/snd/controlC1: cossio 2082 F pulseaudio CurrentDesktop: XFCE Date: Wed Mar 9 22:28:53 2016 HibernationDevice: RESUME=UUID=37d586ee-f517-4977-b9cd-189c200b0bac InstallationDate: Installed on 2015-08-03 (219 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: ASUSTeK COMPUTER INC. X550LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=52be177f-a0ea-4053-be39-bbeaff1a22df ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2016-01-31 (38 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.505 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.505:bd04/01/2014:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1597053] modoc (ppc64el) - tests ran: 20, failed: 7
tests ran: 20, failed: 7; http://kernel.ubuntu.com/testing/4.2.0-42.49/modoc__4.2.0-42.49__2016-07-07_20-19-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/1597053 Title: linux: 4.2.0-42.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-42.49 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1534948] Re: Ubuntu 15.10 fails to boot from Sandisk USB stick
Christopher, Please find the post in the mailing list below http://thread.gmane.org/gmane.linux.usb.general/144630/focus=144635 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1534948 Title: Ubuntu 15.10 fails to boot from Sandisk USB stick Status in linux package in Ubuntu: Triaged Bug description: Booting from Sandisk USB stick fails and stops on "device descriptor read/64, error -71" and "device not accepting address 6, error -71" on Dell Latitude E5420 Laptop. I tried every USB socket but without success. Booting with "rootwait" parameter does not help either. [5.190746] ata5: SATA link down (SStatus 0 SControl 300) [5.510923] ata6: SATA link down (SStatus 0 SControl 300) [ 18.414128] usb 2-1.4: device descriptor read/64, error -110 [ 23.601028] usb 2-1.4: device descriptor read/64, error -71 [ 23.777126] usb 2-1.4: new high-speed USB device number 4 using ehci-pci [ 23.861176] usb 2-1.4: device descriptor read/64, error -71 [ 24.049280] usb 2-1.4: device descriptor read/64, error -71 [ 24.225377] usb 2-1.4: new high-speed USB device number 5 using ehci-pci [ 24.641614] usb 2-1.4: device not accepting address 5, error -71 [ 24.713649] usb 2-1.4: new high-speed USB device number 6 using ehci-pci [ 25.129882] usb 2-1.4: device not accepting address 6, error -71 [ 25.131599] usb 2-1-port4: unable to enumerate USB device [ 25.205925] usb 2-1.6: new full-speed USB device number 7 using ehci-pci [ 25.303424] usb 2-1.6: New USB device found, idVendor=413c, idProduct=8187 [ 25.304928] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 25.306409] usb 2-1.6: Product: DW375 Bluetooth Module [ 25.307864] usb 2-1.6: Manufacturer: Dell Computer Corp [ 25.309305] usb 2-1.6: SerialNumber: 90004EDB8100 however unpluging and repluging usb stick makes booting process go further [ 35.799849] usb 2-1.4: new high-speed USB device number 8 using ehci-pci [ 35.893824] usb 2-1.4: New USB device found, idVendor=0781, idProduct=5583 [ 35.895294] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 35.896728] usb 2-1.4: Product: Ultra Fit [ 35.898129] usb 2-1.4: Manufacturer: SanDisk [ 35.899521] usb 2-1.4: SerialNumber: 4C530001160413113001 [ 35.905302] usb-storage 2-1.4:1.0: USB Mass Storage device detected [ 35.907051] scsi host6: usb-storage 2-1.4:1.0 [ 35.908544] usbcore: registered new interface driver usb-storage [ 35.911586] usbcore: registered new interface driver uas [ 36.909422] scsi 6:0:0:0: Direct-Access SanDisk Ultra Fit1.00 PQ: 0 ANSI: 6 [ 36.911179] sd 6:0:0:0: Attached scsi generic sg2 type 0 [ 36.913169] sd 6:0:0:0: [sdb] 60751872 512-byte logical blocks: (31.1 GB/28.9 GiB) [ 36.915880] sd 6:0:0:0: [sdb] Write Protect is off [ 36.917297] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ 36.918317] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 36.950274] sdb: sdb1 sdb2 < sdb5 > [ 36.955479] sd 6:0:0:0: [sdb] Attached SCSI removable disk [ 37.254029] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: darek 1257 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e7e49edd-f274-4ac4-ae57-ebbeb8082257 InstallationDate: Installed on 2015-11-10 (181 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E5420 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=ee3725ef-3af5-4853-84aa-d4526d8e6014 ro priority=low rootwait ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-23 (17 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd07/10/2011:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 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/1534948/+subsc
[Kernel-packages] [Bug 1492146] Re: igb Detected Tx Unit Hang
Answer from asrock... i think that this is more of an issue with the Kernel. I can ask the engineers to look into it but as this OS is not on the tested list this does not warranty an rma. -- 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/1492146 Title: igb Detected Tx Unit Hang Status in linux-lts-utopic package in Ubuntu: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Bug description: Hello! Have a: >lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.3 LTS Release:14.04 Codename: trusty with kenel 3.16.0-46-generic. Today i do dist-upgrade and kernel was upgraded to 3.16.0-48-generic version. After reboot i've got this: Sep 4 09:02:52 mail kernel: [ 310.616324] igb :02:00.0 em1: Reset adapter Sep 4 09:02:52 mail kernel: [ 310.831157] igb :02:00.1 em2: Reset adapter Sep 4 09:02:56 mail kernel: [ 315.154686] igb :02:00.0 em1: igb: em1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 4 09:02:56 mail kernel: [ 315.202651] igb :02:00.1 em2: igb: em2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 4 09:03:02 mail kernel: [ 321.608099] igb :02:00.0: Detected Tx Unit Hang Sep 4 09:03:02 mail kernel: [ 321.608099] Tx Queue <6> Sep 4 09:03:02 mail kernel: [ 321.608099] TDH <23> Sep 4 09:03:02 mail kernel: [ 321.608099] TDT <23> Sep 4 09:03:02 mail kernel: [ 321.608099] next_to_use <25> Sep 4 09:03:02 mail kernel: [ 321.608099] next_to_clean<23> Sep 4 09:03:02 mail kernel: [ 321.608099] buffer_info[next_to_clean] Sep 4 09:03:02 mail kernel: [ 321.608099] time_stamp <112af> Sep 4 09:03:02 mail kernel: [ 321.608099] next_to_watch Sep 4 09:03:02 mail kernel: [ 321.608099] jiffies <11531> Sep 4 09:03:02 mail kernel: [ 321.608099] desc.status <120200> Sep 4 09:03:04 mail kernel: [ 323.607349] igb :02:00.0: Detected Tx Unit Hang Sep 4 09:03:04 mail kernel: [ 323.607349] Tx Queue <6> Sep 4 09:03:04 mail kernel: [ 323.607349] TDH <23> Sep 4 09:03:04 mail kernel: [ 323.607349] TDT <23> Sep 4 09:03:04 mail kernel: [ 323.607349] next_to_use <25> Sep 4 09:03:04 mail kernel: [ 323.607349] next_to_clean<23> Sep 4 09:03:04 mail kernel: [ 323.607349] buffer_info[next_to_clean] Sep 4 09:03:04 mail kernel: [ 323.607349] time_stamp <112af> Sep 4 09:03:04 mail kernel: [ 323.607349] next_to_watch Sep 4 09:03:04 mail kernel: [ 323.607349] jiffies <11725> Sep 4 09:03:04 mail kernel: [ 323.607349] desc.status <120200> Sep 4 09:03:06 mail kernel: [ 325.606602] igb :02:00.0: Detected Tx Unit Hang Sep 4 09:03:06 mail kernel: [ 325.606602] Tx Queue <6> Sep 4 09:03:06 mail kernel: [ 325.606602] TDH <23> Sep 4 09:03:06 mail kernel: [ 325.606602] TDT <23> Sep 4 09:03:06 mail kernel: [ 325.606602] next_to_use <25> Sep 4 09:03:06 mail kernel: [ 325.606602] next_to_clean<23> Sep 4 09:03:06 mail kernel: [ 325.606602] buffer_info[next_to_clean] Sep 4 09:03:06 mail kernel: [ 325.606602] time_stamp <112af> Sep 4 09:03:06 mail kernel: [ 325.606602] next_to_watch Sep 4 09:03:06 mail kernel: [ 325.606602] jiffies <11919> Sep 4 09:03:06 mail kernel: [ 325.606602] desc.status <120200> All network connections droped after that. System still unusable. Only after boot with old linux-image-3.16.0-46-generic my production mail server can work. It's a critical bug for me, can anybody help me? ethtool -i em1 driver: igb version: 5.2.13-k firmware-version: 1.61, 0x8cd5, 1.949.0 bus-info: :02:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp
Same issue with the folowing BT headphones: * Plantronic BackBeat FIT. * Plantronic BackBeat PRO. * B&O Beoplay H8. The computer has a BT USB dongle: Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) CSR8510 A10 USB ID = 0a12:0001 The following procedure solved the problem for us: 1. Purge Ubuntu pulseaudio packages and conf files. Backup and purge pulseaudio user conf files too. 2. Install the corresponding packages from Debian testing (June 2016). See attached script (get-pulseaudio8-debian-amd64.sh). 3. Restart. 4. A2DP profile should now work as expected with the default bluez/pulseaudio configuration (Use pavucontrol to select A2DP if needed). Since Debian Testing (June 2016) and Ubuntu 16.04 are based on the same pulseaudio upstream version (8.0) this suggests that this regression is maybe due to a difference in Debian and Ubuntu packaging: either the compilation options, the default conf or the specific patches (e.g. Ubuntu packages include more specific patches). ** Attachment added: "get-pulseaudio8-debian-amd64.sh" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1438510/+attachment/4697122/+files/get-pulseaudio8-debian-amd64.sh -- 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/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1597897] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 3, failed: 1
tests ran: 3, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-30.49/ms10-35-mcdivittB0-kernel__4.4.0-30.49__2016-07-07_19-08-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/1597897 Title: linux: 4.4.0-30.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-30.49 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447485] Re: serial: 8250_pci: Add support for 16 port Exar boards
** Changed in: linux (Ubuntu Trusty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1447485 Title: serial: 8250_pci: Add support for 16 port Exar boards Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Bug description: This is a request to add support for boards using two EXAR XR17V8358 chips in Master-Slave mode. The patch has also been send upstream, but is not reviewed yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Started run on 3.14-rc1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 Vivid: In Progress Status in linux source package in Wily: 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 1597053] modoc (ppc64el) - tests ran: 18, failed: 3
tests ran: 18, failed: 3; http://kernel.ubuntu.com/testing/4.2.0-42.49/modoc__4.2.0-42.49__2016-07-07_19-36-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/1597053 Title: linux: 4.2.0-42.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-42.49 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1597053] modoc (ppc64el) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-42.49/modoc__4.2.0-42.49__2016-07-07_18-40-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/1597053 Title: linux: 4.2.0-42.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-42.49 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1599110] Re: Blank screen 90 sec boot delay
Christopher, want to see if there is an additional failure after removing an autostart desktop file. The journal indicates a problem in gnome-session and indeed gsm-manager.c issues the failure message "WARNING: Application 'at-spi-dbus-bus.desktop' failed to register before timeout" after a 90 second delay. Looking back in the journal at about 90 seconds prior gnome-sessions had a problem with an ~/.config/autostart file 553047C893AEAF57E8DFE7143352B56DAC0A3820.chromium-service.desktop. No idea what this file is but since it causing a failure in gnome-session manager I'm removing it. If I see additional failures after this removal will follow your suggestions in comment #12. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1599110 Title: Blank screen 90 sec boot delay Status in linux package in Ubuntu: Incomplete Bug description: Tried to document this problem under bug 1559595 but have been requested to submit a new bug. Been having an intermittent problem booting (started on 16.04 and continues across multiple system rebuilds and 16.10) where just after entering my PW the screen goes blank for about 90 seconds. After that interval the normal desktop appears and all is well. Will supply a journal boot log of a failing boot (boot_0704.txt) and a normal boot log (boot_0704_good.txt). Do see in the failing log and all others that I have looked at a gnome-session timeout (time 06:16:41). Don't see this type of entry in the good log but haven't examined many non- failure logs. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.4.0-30-generic 4.4.0-30.49 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cliff 3761 F pulseaudio /dev/snd/controlC2: cliff 3761 F pulseaudio /dev/snd/controlC1: cliff 3761 F pulseaudio CurrentDesktop: GNOME Date: Tue Jul 5 06:19:34 2016 HibernationDevice: RESUME=UUID=51013622-8d36-45f8-89d8-8dc36d3b5ac5 InstallationDate: Installed on 2016-05-30 (35 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160529) MachineType: ASUS All Series 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-30-generic root=UUID=375f8904-0bcb-4f0b-bd19-2a200ca1db5a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-30-generic N/A linux-backports-modules-4.4.0-30-generic N/A linux-firmware1.158 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2012 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2012:bd09/30/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: 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/1599110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1568573] Re: [Lenovo Thinkpad T460] Ultra Dock external displays not detected after suspend/resume cycle
Exactly the same (and some more) problems are on my Lenovo X250 Broadwell machine with 4.4 kernel. I have tested 4.6.0, 4.6.3 and just now 4.7-rc6. All issues disapeared. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568573 Title: [Lenovo Thinkpad T460] Ultra Dock external displays not detected after suspend/resume cycle Status in linux package in Ubuntu: Incomplete Bug description: Hello, System is Thinkpad T460, Skylake graphics, Thinkpad Ultra dock. DVI and HDMI displays connected via dock. 4.4.0-18. After a suspend-resume cycle, when the laptop is docked the dock connected external displays are not initialized/connected. If I disconnect the displays from the dock and connect them directly to the laptop, they are initialized successfully and can be configured via xrandr etc. If the laptop is power cycled, the displays can be used normally until the next suspend-resume cycle. Example from relevant dmesg: [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_start_link_train [i915_bpo]] *ERROR* failed to train DP, aborting [drm:intel_dp_set_idle_link_train [i915_bpo]] *ERROR* Timed out waiting for DP idle patterns [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up 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: ryan 1838 F pulseaudio Date: Sun Apr 10 09:39:32 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (201 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic root=/dev/mapper/it--vg-root ro quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: 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: Upgraded to xenial on 2016-02-24 (45 days ago) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FNCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FNCTO1WW dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN
Thanks guys, I really think the solution here will be to move onto the lts-xenial kernel as all others lts- kernels will be end of life shortly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1378123 Title: unix_socket_abstract.sh triggers an AppArmor WARN Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: Confirmed Status in linux source package in Xenial: Fix Released Bug description: Running the unix_socket_abstract.sh regression test script in a loop results in an AppArmor WARN message in the logs. On my test system, it typically takes between 1 and 3 runs of unix_socket_abstract.sh before the WARN is hit. It does not seem to occur with the unix_socket_pathname.sh or unix_socket_unnamed.sh tests. Here's the script I used: --- #!/bin/sh dmesg -C while ! dmesg -c | grep "AppArmor WARN"; do bash unix_socket_abstract.sh done --- The following back trace is emitted in the logs: [ 1365.017477] [ cut here ] [ 1365.017486] WARNING: CPU: 0 PID: 26026 at /build/buildd/linux-3.16.0/security/apparmor/label.c:1767 __aa_labelset_update_all+0x6f5/0x7f0() [ 1365.017487] AppArmor WARN __label_update: ((__aa_label_remove_and_insert((&(((label)->ent[(label)->size - 1])->ns)->labels), label, l) != l)): [ 1365.017489] Modules linked in: bnep rfcomm bluetooth 6lowpan_iphc kvm_intel kvm vmwgfx ttm drm_kms_helper serio_raw drm i2c_piix4 pvpanic parport_pc ppdev mac_hid lp parport psmouse pata_acpi floppy [ 1365.017505] CPU: 0 PID: 26026 Comm: apparmor_parser Tainted: GW 3.16.0-20-generic #27-Ubuntu [ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 1365.017509] 0009 88002dd23d88 8177f053 88002dd23dd0 [ 1365.017511] 88002dd23dc0 8106fcfd 880036602900 [ 1365.017513] 88003acaed00 0002 88003e02a0a0 88002dd23e20 [ 1365.017516] Call Trace: [ 1365.017522] [] dump_stack+0x45/0x56 [ 1365.017527] [] warn_slowpath_common+0x7d/0xa0 [ 1365.017530] [] warn_slowpath_fmt+0x4c/0x50 [ 1365.017533] [] ? __aa_label_remove_and_insert+0x7e/0x1a0 [ 1365.017536] [] __aa_labelset_update_all+0x6f5/0x7f0 [ 1365.017539] [] ? securityfs_remove+0x9a/0xb0 [ 1365.017542] [] aa_remove_profiles+0x143/0x4f0 [ 1365.017545] [] profile_remove+0x3e/0x70 [ 1365.017550] [] vfs_write+0xb7/0x1f0 [ 1365.017552] [] ? do_sys_open+0x1b9/0x280 [ 1365.017555] [] SyS_write+0x46/0xb0 [ 1365.017558] [] system_call_fastpath+0x1a/0x1f [ 1365.017560] ---[ end trace 1e09e2c565d9ef95 ]--- This occurs in an amd64 utopic vm: $ uname -a Linux sec-utopic-amd64 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:35:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1378123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1599951] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1599951 Title: On read_tsc function issue. Status in linux package in Ubuntu: Confirmed Bug description: Below is result of perf report: read_tsc /proc/kcore │ │ │ │Disassembly of section load0: │ │81037780 : 66,67 │ push %rbp │ mov%rsp,%rbp │ lfence │ rdtsc 33,33 │ shl$0x20,%rdx │ or %rdx,%rax │ pop%rbp │← retq ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu2932 F pulseaudio CurrentDesktop: MATE Date: Thu Jul 7 21:18:17 2016 InstallationDate: Installed on 2016-04-29 (69 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1599951] [NEW] On read_tsc function issue.
Public bug reported: Below is result of perf report: read_tsc /proc/kcore │ │ │ │Disassembly of section load0: │ │81037780 : 66,67 │ push %rbp │ mov%rsp,%rbp │ lfence │ rdtsc 33,33 │ shl$0x20,%rdx │ or %rdx,%rax │ pop%rbp │← retq ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu2932 F pulseaudio CurrentDesktop: MATE Date: Thu Jul 7 21:18:17 2016 InstallationDate: Installed on 2016-04-29 (69 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1599951 Title: On read_tsc function issue. Status in linux package in Ubuntu: New Bug description: Below is result of perf report: read_tsc /proc/kcore │ │ │ │Disassembly of section load0: │ │81037780 : 66,67 │ push %rbp │ mov%rsp,%rbp │ lfence │ rdtsc 33,33 │ shl$0x20,%rdx │ or %rdx,%rax │ pop%rbp │← retq ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu2932 F pulseaudio CurrentDesktop: MATE Date: Thu Jul 7 21:18:17 2016 InstallationDate: Installed on 2016-04-29 (69 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sy
[Kernel-packages] [Bug 1597517] Re: linux-headers-3.2.0-105 not in precise-security
Here's the log from running `sudo unattended-upgrade --dry-run --debug` in case it's helpful: 2016-07-07 16:58:53,281 INFO Initial blacklisted packages: 2016-07-07 16:58:53,282 INFO Starting unattended upgrades script 2016-07-07 16:58:53,282 INFO Allowed origins are: ['o=Ubuntu,a=precise-security'] 2016-07-07 16:58:53,745 DEBUG adjusting candidate version: '' 2016-07-07 16:58:53,761 DEBUG adjusting candidate version: '' 2016-07-07 16:58:53,771 DEBUG adjusting candidate version: '' 2016-07-07 16:58:53,821 DEBUG adjusting candidate version: '' 2016-07-07 16:58:53,843 DEBUG adjusting candidate version: '' 2016-07-07 16:58:53,958 DEBUG adjusting candidate version: '' 2016-07-07 16:58:53,970 DEBUG adjusting candidate version: '' 2016-07-07 16:58:54,013 DEBUG adjusting candidate version: '' 2016-07-07 16:58:54,277 DEBUG adjusting candidate version: '' 2016-07-07 16:58:54,291 DEBUG adjusting candidate version: '' 2016-07-07 16:58:54,340 DEBUG adjusting candidate version: '' 2016-07-07 16:58:54,362 DEBUG adjusting candidate version: '' 2016-07-07 16:58:54,449 DEBUG adjusting candidate version: '' 2016-07-07 16:58:55,110 DEBUG Checking: cloud-init ([""]) 2016-07-07 16:58:55,138 DEBUG Checking: facter ([""]) 2016-07-07 16:58:55,178 DEBUG Checking: grub-legacy-ec2 ([""]) 2016-07-07 16:58:55,193 DEBUG Checking: instrumental-tools (["https://packagecloud.io/expectedbehavior/instrumental' label:'instrumental' site:'packagecloud.io' isTrusted:True>"]) 2016-07-07 16:58:55,401 DEBUG Checking: libruby2.0 ([""]) 2016-07-07 16:58:55,487 DEBUG Checking: linux-headers-virtual (["", ""]) 2016-07-07 16:58:55,957 DEBUG pkg 'linux-headers-3.2.0-105' not in allowed origin 2016-07-07 16:58:55,958 DEBUG sanity check failed 2016-07-07 16:58:56,173 DEBUG adjusting candidate version: '' 2016-07-07 16:58:56,174 DEBUG adjusting candidate version: '' 2016-07-07 16:58:56,174 DEBUG adjusting candidate version: '' 2016-07-07 16:58:56,214 DEBUG adjusting candidate version: '' 2016-07-07 16:58:56,224 DEBUG adjusting candidate version: '' 2016-07-07 16:58:56,330 DEBUG adjusting candidate version: '' 2016-07-07 16:58:56,330 DEBUG adjusting candidate version: '' 2016-07-07 16:58:56,364 DEBUG adjusting candidate version: '' 2016-07-07 16:58:56,619 DEBUG adjusting candidate version: '' 2016-07-07 16:58:56,620 DEBUG adjusting candidate version: '' 2016-07-07 16:58:56,659 DEBUG adjusting candidate version: '' 2016-07-07 16:58:56,670 DEBUG adjusting candidate version: '' 2016-07-07 16:58:56,748 DEBUG adjusting candidate version: '' 2016-07-07 16:58:56,785 DEBUG Checking: linux-image-virtual (["", ""]) 2016-07-07 16:58:57,253 DEBUG pkg 'linux-headers-3.2.0-105' not in allowed origin 2016-07-07 16:58:57,253 DEBUG sanity check failed 2016-07-07 16:58:57,459 DEBUG adjusting candidate version: '' 2016-07-07 16:58:57,460 DEBUG adjusting candidate version: '' 2016-07-07 16:58:57,461 DEBUG adjusting candidate version: '' 2016-07-07 16:58:57,499 DEBUG adjusting candidate version: '' 2016-07-07 16:58:57,509 DEBUG adjusting candidate version: '' 2016-07-07 16:58:57,613 DEBUG adjusting candidate version: '' 2016-07-07 16:58:57,614 DEBUG adjusting candidate version: '' 2016-07-07 16:58:57,647 DEBUG adjusting candidate version: '' 2016-07-07 16:58:57,902 DEBUG adjusting candidate version: '' 2016-07-07 16:58:57,903 DEBUG adjusting candidate version: '' 2016-07-07 16:58:57,941 DEBUG adjusting candidate version: '' 2016-07-07 16:58:57,953 DEBUG adjusting candidate version: '' 2016-07-07 16:58:58,030 DEBUG adjusting candidate version: '' 2016-07-07 16:58:58,066 DEBUG Checking: linux-virtual (["", ""]) 2016-07-07 16:58:58,490 DEBUG pkg 'linux-headers-3.2.0-105' not in allowed origin 2016-07-07 16:58:58,490 DEBUG sanity check failed 2016-07-07 16:58:58,699 DEBUG adjusting candidate version: '' 2016-07-07 16:58:58,700 DEBUG adjusting candidate version: '' 2016-07-07 16:58:58,701 DEBUG adjusting candidate version: '' 2016-07-07 16:58:58,739 DEBUG adjusting candidate version: '' 2016-07-07 16:58:58,749 DEBUG adjusting candidate version: '' 2016-07-07 16:58:58,853 DEBUG adjusting candidate version: '' 2016-07-07 16:58:58,854 DEBUG adjusting candidate version: '' 2016-07-07 16:58:58,887 DEBUG adjusting candidate version: '' 2016-07-07 16:58:59,142 DEBUG adjusting candidate version: '' 2016-07-07 16:58:59,143 DEBUG adjusting candidate version: '' 2016-07-07 16:58:59,181 DEBUG adjusting candidate version: '' 2016-07-07 16:58:59,193 DEBUG adjusting candidate version: '' 2016-07-07 16:58:59,270 DEBUG adjusting candidate version: '' 2016-07-07 16:58:59,355 DEBUG Checking: psmisc ([""]) 2016-07-07 16:58:59,357 DEBUG Checking: puppetlabs-release ([""]) 2016-07-07 16:58:59,398 DEBUG Checking: ruby2.0 ([""]) 2016-07-07 16:58:59,398 DEBUG Checking: ruby2.0-dev ([""]) 2016-07-07 16:58:59,466 DEBUG pkgs that look like they should be upgraded: 2016-07-07 16:58:59,473 DEBUG blacklist: [] 2016-07-07 16:58:59,474 DEBUG InstCount=0 DelCount=0 BrokenCout=0 2016-07-07 16:58:59,474 INFO Opt
[Kernel-packages] [Bug 1596631] modoc (ppc64el) - tests ran: 20, failed: 7
tests ran: 20, failed: 7; http://kernel.ubuntu.com/testing/3.19.0-65.73/modoc__3.19.0-65.73__2016-07-07_17-08-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/1596631 Title: linux: 3.19.0-65.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-65.73 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1596631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1548009] Re: ZFS pools should be automatically scrubbed
** Summary changed: - [FFe] ZFS pools should be automatically scrubbed + ZFS pools should be automatically scrubbed -- 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/1548009 Title: ZFS pools should be automatically scrubbed Status in zfs-linux package in Ubuntu: Confirmed Bug description: mdadm automatically checks MD arrays. ZFS should automatically scrub pools too. Scrubbing a pool allows ZFS to detect on-disk corruption and (when the pool has redundancy) correct it. Note that ZFS does not blindly assume the other copy is correct; it will only overwrite bad data with data that is known to be good (i.e. it passes the checksum). I've attached a debdiff which accomplishes this. It builds and installs cleanly. The meat of it is the scrub script I've been using on production systems, both servers and laptops, and recommending in my Ubuntu root- on-ZFS HOWTO, for years, which scrubs all *healthy* pools. If a pool is not healthy, scrubbing it is bad for two reasons: 1) It adds a lot of disk load which could theoretically lead to another failure. We should save that disk load for resilvering. 2) Performance is already less on a degraded pool and scrubbing can make that worse, even though scrubs are throttled. Arguably, I might be being too conservative here, but the marginal benefit of scrubbing a *degraded* pool is pretty minimal as pools should not be left degraded for very long. The cron.d in this patch scrubs on the second Sunday of the month. mdadm scrubs on the first Sunday of the month. This way, if a system has both MD and ZFS pools, the load doesn't all happen at the same time. If the system doesn't have both types, it shouldn't really matter which week. If you'd rather make it the same week as MD, I see no problem with that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1548009/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575380] Re: Unable to mount Kodak EasyShare Z1285 Zoom Digital Camera
Joseph, Shotwell seems to be working across 3 Ubuntu machines now. Sometimes I get a false-negative warning about the system not claiming the device...but then the camera shows up somewhere else. I think I'll skip the Upstream Kernel Test for now. Thanks, Richard Time, upgrades & updates seem to have rectified the problem. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) Assignee: (unassigned) => MeadeBaron (generalmeadeco) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575380 Title: Unable to mount Kodak EasyShare Z1285 Zoom Digital Camera Status in linux package in Ubuntu: Fix Released Bug description: I'm running Xenial Xerus 16.04 LTS...but this bug also affected Trusty 14.04. The very fact that Ubuntu recognizes the make and model of the camera is even more infuriating! Why the heck won't it mount it so I can download and manipulate my photos with programs like Digikam, Shotwell, etcetera? Gimp can open the files...but of course GIMP is not a photo-management program. Please resolve and/or tell me which program will communicate with this excellent little digital camera! I have combed the web for a solution and I am at wits end. Full Error message: "Unable to mount Kodak EasyShare Z1285 Zoom Digital Camera Error initializing camera:-53: Could not claim the USB device" Thank you for addressing this issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bruskald 1572 F pulseaudio /dev/snd/controlC0: bruskald 1572 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3216a142-aeeb-48ff-a79a-f3e0bddf07fd InstallationDate: Installed on 2016-04-29 (64 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. enp3s2no wireless extensions. MachineType: LENOVO To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-lowlatency root=UUID=2d1b6993-0f24-4c9a-b904-00ecf206e913 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-28.47-lowlatency 4.4.13 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-lowlatency N/A linux-backports-modules-4.4.0-28-lowlatency N/A linux-firmware 1.157.1 RfKill: Tags: xenial Uname: Linux 4.4.0-28-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/19/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 2UKT42AUS dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr2UKT42AUS:bd10/19/2007:svnLENOVO:pnToBeFilledByO.E.M.:pvrThinkCentrexxx:rvnLENOVO:rnLENOVO:rvr1.0:cvnLENOVO:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: ThinkCentre xxx dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596631] modoc (ppc64el) - tests ran: 18, failed: 3
tests ran: 18, failed: 3; http://kernel.ubuntu.com/testing/3.19.0-65.73/modoc__3.19.0-65.73__2016-07-07_16-23-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596631 Title: linux: 3.19.0-65.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-65.73 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1596631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1599924] Re: embed derivative kernel target names in repo git tags
** Description changed: To avoid git repo tag namespace collisions, the derivative kernel target names should be embedded in their git 'release' tags, e.g. in the Ubuntu Xenial git repo: tag Ubuntu-raspi2-4.4.0-1017.23 instead of Ubuntu-4.4.0-1017.23 tag Ubuntu-snapdragon-4.4.0-1020.23 instead of Ubuntu-4.4.0-1020.23 + + This new tag naming scheme should be applied to the main kernel branch + and the -meta branch for each derivative. + + Derivatives to be changed: + + xenial/raspi2 + xenial/snapdragon + wily/raspi2 + precise/ti-omap4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1599924 Title: embed derivative kernel target names in repo git tags Status in linux package in Ubuntu: In Progress Status in linux source package in Precise: New Status in linux source package in Wily: New Status in linux source package in Xenial: New Bug description: To avoid git repo tag namespace collisions, the derivative kernel target names should be embedded in their git 'release' tags, e.g. in the Ubuntu Xenial git repo: tag Ubuntu-raspi2-4.4.0-1017.23 instead of Ubuntu-4.4.0-1017.23 tag Ubuntu-snapdragon-4.4.0-1020.23 instead of Ubuntu-4.4.0-1020.23 This new tag naming scheme should be applied to the main kernel branch and the -meta branch for each derivative. Derivatives to be changed: xenial/raspi2 xenial/snapdragon wily/raspi2 precise/ti-omap4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1599924] [NEW] embed derivative kernel target names in repo git tags
Public bug reported: To avoid git repo tag namespace collisions, the derivative kernel target names should be embedded in their git 'release' tags, e.g. in the Ubuntu Xenial git repo: tag Ubuntu-raspi2-4.4.0-1017.23 instead of Ubuntu-4.4.0-1017.23 tag Ubuntu-snapdragon-4.4.0-1020.23 instead of Ubuntu-4.4.0-1020.23 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: bot-stop-nagging ** Changed in: linux (Ubuntu) Status: New => In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) 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/1599924 Title: embed derivative kernel target names in repo git tags Status in linux package in Ubuntu: In Progress Status in linux source package in Precise: New Status in linux source package in Wily: New Status in linux source package in Xenial: New Bug description: To avoid git repo tag namespace collisions, the derivative kernel target names should be embedded in their git 'release' tags, e.g. in the Ubuntu Xenial git repo: tag Ubuntu-raspi2-4.4.0-1017.23 instead of Ubuntu-4.4.0-1017.23 tag Ubuntu-snapdragon-4.4.0-1020.23 instead of Ubuntu-4.4.0-1020.23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596631] modoc (ppc64el) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/3.19.0-65.73/modoc__3.19.0-65.73__2016-07-07_15-34-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596631 Title: linux: 3.19.0-65.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-65.73 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1596631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1530476] Re: Lenovo helix 2nd gen does not wake up from suspend
Hi, I just wanted to keep this thread alive, as the bug seems still to be present. I recently tried suspend with the Helix 2 and Ubuntu 16.04 and can confirm the same behaviour. This issue is being tracked on the kernel bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=100171 There was a BIOS Update released by Lenovo on the 25th of May which addresses some Suspend issues for Windows 10. I haven't yet checked my BIOS version- will check tonight. If it is still an issue, I will post logs and DebuggingKernelSuspend results... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1530476 Title: Lenovo helix 2nd gen does not wake up from suspend Status in linux package in Ubuntu: Incomplete Bug description: Using a fresh install of ubuntu 15.10. When the laptop enters suspend it wont wake up. Not from trigging the lid switch or pressing the power button. Using Latest kernel 4.2.0-22-generic. Tried with two different bios versions to rule out bios. The only option is to press and hold and do a new cold start. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jobe 1530 F pulseaudio /dev/snd/controlC0: jobe 1530 F pulseaudio CurrentDesktop: GNOME Date: Fri Jan 1 22:09:34 2016 HibernationDevice: RESUME=UUID=bbd6d6cd-2398-4046-ba00-e818132d983a InstallationDate: Installed on 2015-12-16 (16 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20CGCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-22-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N17ET83W (1.83 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CGCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K11826 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ET83W(1.83):bd12/02/2015:svnLENOVO:pn20CGCTO1WW:pvrThinkPadHelix2nd:rvnLENOVO:rn20CGCTO1WW:rvrSDK0K11826WIN:cvnLENOVO:ct11:cvrNone: dmi.product.name: 20CGCTO1WW dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1441150] Re: Problems with transid in btrfs (linux 3.13)
I've restored the data and all kernels from Ubuntu-3.13.0-91.138 through to the latest upstream v4.7-rc6 can attempt to mount the restored data without oopsing the kernel. However, the data I have is definitely broken and cannot be mounted, even btrfs-image -r on the image reports a transid failure that is not fixable: $ btrfs-image -r btrfs_image btrfs_image_restored parent transid verify failed on 471304036352 wanted 407771 found 407769 parent transid verify failed on 471304036352 wanted 407771 found 407769 Ignoring transid failure So, since the kernel is not oopsing now, I think this a fix released for 3.13 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1441150 Title: Problems with transid in btrfs (linux 3.13) Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Bug description: Hello. We've got issues with volume mount on 3.13.0-43-generic with btrfs after crash due to OOM. I filed bug to bugzilla on kernel.org and they replied that bug has been fixed in newer version and it should be backported to 3.13. Bugzilla's original bugreport: https://bugzilla.kernel.org/show_bug.cgi?id=96251 Trace in the kernel: parent transid verify failed on 471304036352 wanted 407770 found 407769 parent transid verify failed on 471304036352 wanted 407770 found 407769 btrfs: failed to read log tree btrfs: open_ctree failed To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1441150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1599306] Re: 16.04: i8042 need to start early after grub
Joseph, thank you for your reply. All the tests I've made were done starting from fresh install. The issue persist on 4.7.0-040700rc6-generic (X64): at least 10 seconds before have the keyboard working again. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1599306 Title: 16.04: i8042 need to start early after grub Status in linux package in Ubuntu: Confirmed Bug description: The kernel module i8042 need to start early after grub selection. I've upgrade my notebook (HP dv2700 series, model dv2910us) with an SSD and now I need to wait 15 seconds after LightDM show up before I can use the internal keyboard.On bios and on GRUB the keyboard works fine but stops working the exact moment the kernel starts to load. An USB external keyboard works fine with no delay at all (different module, I know). It's not related to the SSD because even on recovery mode I can reproduce the issue with an old mechanical disk. Here's a video showing a full cycle of boots with Ubuntu 16.04: https://youtu.be/yseDPvqWNw4 And here a video of the recovery mode where the delay is much evident: https://youtu.be/vbsD9tb-Dn8 Here is my xinput configuration: ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS GlidePoint id=11[slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Sleep Button id=8 [slave keyboard (3)] ↳ HP Webcam id=9 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)] ↳ HP WMI hotkeys id=12[slave keyboard (3)] Keyboard on id 10. Would be nice have it working at the same time of the USB module. Tested with Ubuntu/Xubuntu 14.04, 14.10, 15.04, 15.10 and the latest 16.04. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: effe 1383 F pulseaudio CurrentDesktop: XFCE Date: Tue Jul 5 18:16:09 2016 HibernationDevice: RESUME=UUID=19d86b30-2bc7-4db2-9f45-c2e79b64d298 InstallationDate: Installed on 2016-06-25 (9 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=2841e7bc-0cd5-4641-8eee-c3954c5587e2 ro locale=pt_PT quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2008 dmi.bios.vendor: Phoenix dmi.bios.version: F.2B dmi.board.name: 30CD dmi.board.vendor: Wistron dmi.board.version: 80.52 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrF.2B:bd05/07/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2B:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv2700 Notebook PC dmi.product.version: F.2B dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1599599] Re: System beep broken (again) in Xenial Xerus
Thank you Joseph, I will test v4.7-rc6 mainline build. This is another first for me, so I need some time to learn this, plus I will set up and install Ubuntu 16.04 on a different machine to avoid risks, and test the bug on another computer. Hopefully I will have this all done within 24-48 hours. Please provide links if you know of any step-by-step tutorials (the kind that don't leave out critical steps with the assumption that everyone already knows to do, and how to do those steps). For example, if I have to identify and remove all "out-of-tree modules" as the wiki mentions, I would like to know exactly what I am doing. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1599599 Title: System beep broken (again) in Xenial Xerus Status in linux package in Ubuntu: Incomplete Bug description: This is my first ever bug report, so bear with me if I make mistakes. System bell (aka PC speaker beep) is not working upon installing Ubuntu 16.04 Xenial Xerus. The "beep" command has been installed and works, also "echo foo | wall" works. But "echo -e '\a'" and "printf '\a'" make no sound, nor does pressing the rubout or other keys in terminal and Gedit like it usually does. lsmod shows pcspkr is loaded Note The symptoms are exactly the same as in bug #486154 https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/486154 Just for the record, rmmod and reloading the pcspkr module, unblacklisting it, trying in vain to turn up the volume, and all the other usual steps are no longer relevant at this point. We are way beyond that here. Something very, very elusive in this 16.04 distro is blocking the bell. I suspect something new in 16.04 runs after you login which nullifies the standard error beep. Pressing down at the end in Gedit and the terminal also used to make the beep, but something is telling it not to anymore. The PC speaker works of course, as the alternative beep command and "echo foo | wall" prove. Interestingly, Ubuntu can and does produce the system beep in two other instances: 1) Edit the grub menu at /etc/default /grub and remove the # hash at GRUB_INIT_TUNE="480 440 1" and you will get a beep when grub loads. 2) Press Backspace without entering your password at login, and you will get the error beep. Description: Ubuntu 16.04 LTS Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dv430uuyn 1784 F pulseaudio /dev/snd/controlC0: dv430uuyn 1784 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 6 14:00:50 2016 HibernationDevice: RESUME=UUID=e8206eff-651f-4207-b0a8-9c5a06959711 InstallationDate: Installed on 2016-06-24 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Vostro 430 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=c3a8f971-548b-4666-b865-6bf917bef1c9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 054KM3 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:svnDellInc.:pnVostro430:pvr00:rvnDellInc.:rn054KM3:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: Vostro 430 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596631] modoc (ppc64el) - tests ran: 10, failed: 1
tests ran: 10, failed: 1; http://kernel.ubuntu.com/testing/3.19.0-65.73/modoc__3.19.0-65.73__2016-07-07_14-42-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/1596631 Title: linux: 3.19.0-65.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-65.73 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1596631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1599562] Re: linux: Homogenize changelog format across releases
** Changed in: linux (Ubuntu Wily) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Vivid) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Precise) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1599562 Title: linux: Homogenize changelog format across releases Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: Kernel changelogs should have the same format across all releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1595935] Re: Suspend not working on Ubuntu 16.04
hi again Christopher, Found some time to test various kernels as indicated. Here are the results in correct chronological order: 0) 15.10 / kernel 4.2.0: last known good configuration 1) 16.04 / kernel 4.4.0: error found, bug reported then tested: 2) v4.6-rc7-wily / 4.6.0: works as expected 3) v4.5-wily / 4.5.0: error found 4) v4.5.7-wily / 4.5.7: works as expected 5) v4.5-4-yakkety / 4.5.4: works as expected 6) v4.5-2-wily / 4.5.2: works as expected 7) v4.5-1-wily / 4.5.1: works as expected My conclusion would be that the error was introduced in 4.4.0, persisted in 4.5.0 but got fixed in 4.5.1. If you want me to test any versions between 4.2.0 and 4.4.0, let me know. For now I'll be running one of the higher versions that work for me as daily driver. cheers Tom -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1595935 Title: Suspend not working on Ubuntu 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Suspend stopped working after upgrade from 15.10 to 16.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 2349 F pulseaudio Date: Fri Jun 24 13:32:38 2016 HibernationDevice: RESUME=UUID=d2b33e2c-e0ac-4439-8484-3c684ac09f84 InstallationDate: Installed on 2014-06-24 (730 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude 3540 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=6f195f6e-f9f2-4c1a-bc96-3bf4a5516379 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-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157.1 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-26 (58 days ago) dmi.bios.date: 04/17/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 02RKKX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/17/2014:svnDellInc.:pnLatitude3540:pvrA06:rvnDellInc.:rn02RKKX:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.name: Latitude 3540 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1595935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581326] Re: Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.
To perform a reverse bisect, we need to identify the last bad kernel version and the first good one. We know that 4.4.14 is bad and 4.6 final is good. Can you next test the upstream 4.5. kernel? It can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/ If it is also good, we should test some of the release candidates. If it still bad, we should test some of the 4.6 release candidates. All of those kernels are also available from: http://kernel.ubuntu.com/~kernel-ppa/mainline/ ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581326 Title: Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS. Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver- v12.100.00.00, Successfully discovered HBA and the devices connected to HBA. >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). volume successfully created and listed from SAS3IRCU utility. >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU utility. Kernel crashed here while creating second volume. >>tried with all possible combinations of RAID volumes. Please find the attached kernel crash logs. >>cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 HBA used : LSI SAS3(Fury) Issue : Kernel gets crashed , when tried creating 2nd RAID volume. Expected : One should be able to create MAX 2 RAID volumes at any point of time successfully , without any kernel crash. --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2 InstallationDate: Installed on 2016-05-11 (1 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: enp5s0f0 no wireless extensions. enp5s0f1 no wireless extensions. lono wireless extensions. MachineType: Supermicro X9DRH-7TF/7F/iTF/iF Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DRH-7TF/7F/iTF/iF dmi.board.vendor: Supermicro dmi.board.version: 1234567890 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Supermicro dmi.chassis.version: 1234567890 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890: dmi.product.name: X9DRH-7TF/7F/iTF/iF dmi.product.version: 1234567890 dmi.sys.vendor: Supermicro --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2 InstallationDate: Installed on 2016-05-11 (1 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: enp5s0f0 no wireless extensions. enp5s0f1 no wireless extensions. lono wireless extensions. MachineType: Supermicro X9DRH-7TF/7F/iTF/iF Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1:
[Kernel-packages] [Bug 1544731] Re: After uptade in Ubuntu 15.04 LTS, i've got no Sound in the entire OS.
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1544731 Title: After uptade in Ubuntu 15.04 LTS, i've got no Sound in the entire OS. Status in linux package in Ubuntu: Incomplete Bug description: SInce i uptaded the Ubuntu 15.04 LTS, my computer got no sound. I've tried a lot of solutions that a found on the internet, but none worked. The OS don't recognize the sound board. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libdrm2:amd64 2.4.64-1~ubuntu14.04.1 ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10 Uname: Linux 3.19.0-47-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 AptdaemonVersion: 1.1.1-1ubuntu5.2 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 CrashReports: 640:0:116:386004:2016-02-11 19:00:34.354408740 -0200:2016-02-11 19:00:35.354408740 -0200:/var/crash/libudev1:amd64.0.crash 600:109:116:0:2016-02-11 19:00:41.018408391 -0200:2016-02-11 19:00:41.018408391 -0200:/var/crash/libudev1:amd64.0.uploaded 600:0:116:135672:2016-02-11 19:00:14.026409626 -0200:2016-02-11 19:00:15.026409626 -0200:/var/crash/libdrm2:amd64.0.crash 644:0:116:0:2016-02-11 19:00:36.950408572 -0200:2016-02-11 19:00:36.950408572 -0200:/var/crash/libudev1:amd64.0.upload 600:0:116:135667:2016-02-11 19:00:14.982409552 -0200:2016-02-11 19:00:14.750409562 -0200:/var/crash/ntpdate.0.crash Date: Thu Feb 11 19:00:15 2016 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.6 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libdrm2:amd64:2.4.64-1~ubuntu14.04.1:package libdrm2:amd64 is already installed and configured ErrorMessage: package libdrm2:amd64 is already installed and configured GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0718] InstallationDate: Installed on 2016-01-24 (18 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Acer Aspire E1-471 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic root=UUID=47708600-4eb9-45ee-88b1-ce3d92cdf302 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: dpkg Title: package libdrm2:amd64 2.4.64-1~ubuntu14.04.1 failed to install/upgrade: package libdrm2:amd64 is already installed and configured UdevLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA40_HC dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.18:bd05/02/2012:svnAcer:pnAspireE1-471:pvrV1.18:rvnAcer:rnEA40_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E1-471 dmi.product.version: V1.18 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-
[Kernel-packages] [Bug 1575194] Re: when suspend and unsuspend turn on fan of my laptop and turn off
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575194 Title: when suspend and unsuspend turn on fan of my laptop and turn off Status in linux package in Ubuntu: Incomplete Bug description: when i suspend and unsuspend , turn on fan of my laptop and turn off with full power. On ubuntu 16.04 cpu : Intel® Core™ i7-6500U CPU @ 2.50GHz × 4 grapthic : Intel® HD Graphics 520 (Skylake GT2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1567893] Re: System hangs on second time S3 sleep attempt
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1567893 Title: System hangs on second time S3 sleep attempt Status in linux package in Ubuntu: Incomplete Bug description: Board Information: Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X79S-UP5 memory: 4GB ASIC: Tonga OS: Ubuntu 16.04 beta2 Display: Dell 30" STEPS TO REPRODUCE: 1) install clean OS 2) Set system to sleep via OS or pm-suspend 3) Wake up system 4) Set system to sleep via OS or pm-suspend EXPECTED: - System goes into S3 sleep again ACTUAL: - Display goes black and system hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1567893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575114] Re: Shutdown doesn't work on Acer Aspire s7 191 after upgrade from trusty
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575114 Title: Shutdown doesn't work on Acer Aspire s7 191 after upgrade from trusty Status in linux package in Ubuntu: Incomplete Bug description: After upgrade from ubuntu 14.04.2 to 16.04 on Acer Aspire s7 191 , power shutdown does not work anymore by clicking on "shutdown" option on menu. The system perform the shutdown process but fails to perform power shutdown . shutdown -h now doesn't work either . systemctl start poweroff.target , instead, can successfully power off the system . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577797] Re: TTY non-functional after Resume from Suspend
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577797 Title: TTY non-functional after Resume from Suspend Status in linux package in Ubuntu: Incomplete Bug description: After Resume from Suspend, TTY 1-6 is non-functional. Sometimes I can see text but no prompt or cursor and no way to interact with the prompt. Sometimes the screen is blank. Reproducible: Always Steps to reproduce: 1.) Suspend 2.) Resume 3.) CTRL+ALt+F1-6 Results: Blank or non-functional screen. System Information: Kernel: 4.4.0-21-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.5 Distro: Ubuntu 16.04 xenial Machine: System: LENOVO (portable) product: 20428 v: Lenovo Yoga 2 11 Mobo: LENOVO model: VIUU4 v: 31900058WIN Bios: LENOVO v: AACN21WW date: 01/30/2015 CPU: Dual core Intel Core i3-4012Y (-HT-MCP-) cache: 3072 KB clock speeds: max: 1500 MHz 1: 1500 MHz 2: 1499 MHz 3: 1500 MHz 4: 1500 MHz Graphics: Card: Intel Device 0a1e Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa) Resolution: 1366x768@60.00hz GLX Renderer: Mesa DRI Intel Haswell GLX Version: 3.0 Mesa 11.2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1571289] Re: turn on fan and full brightness screen after unsuspend
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1571289 Title: turn on fan and full brightness screen after unsuspend Status in linux package in Ubuntu: Incomplete Bug description: After unsuspend First show desktop and fan turn on and brightness is 100% , later many second login appear. On ubutnu 15.10 cpu :Intel® Core™ i7-6500U CPU @ 2.50GHz × 4 graphic : Intel® Skylake ULT GT2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575380] Re: Unable to mount Kodak EasyShare Z1285 Zoom Digital Camera
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575380 Title: Unable to mount Kodak EasyShare Z1285 Zoom Digital Camera Status in linux package in Ubuntu: Incomplete Bug description: I'm running Xenial Xerus 16.04 LTS...but this bug also affected Trusty 14.04. The very fact that Ubuntu recognizes the make and model of the camera is even more infuriating! Why the heck won't it mount it so I can download and manipulate my photos with programs like Digikam, Shotwell, etcetera? Gimp can open the files...but of course GIMP is not a photo-management program. Please resolve and/or tell me which program will communicate with this excellent little digital camera! I have combed the web for a solution and I am at wits end. Full Error message: "Unable to mount Kodak EasyShare Z1285 Zoom Digital Camera Error initializing camera:-53: Could not claim the USB device" Thank you for addressing this issue. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bruskald 1572 F pulseaudio /dev/snd/controlC0: bruskald 1572 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3216a142-aeeb-48ff-a79a-f3e0bddf07fd InstallationDate: Installed on 2016-04-29 (64 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. enp3s2no wireless extensions. MachineType: LENOVO To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-lowlatency root=UUID=2d1b6993-0f24-4c9a-b904-00ecf206e913 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-28.47-lowlatency 4.4.13 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-lowlatency N/A linux-backports-modules-4.4.0-28-lowlatency N/A linux-firmware 1.157.1 RfKill: Tags: xenial Uname: Linux 4.4.0-28-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/19/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 2UKT42AUS dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr2UKT42AUS:bd10/19/2007:svnLENOVO:pnToBeFilledByO.E.M.:pvrThinkCentrexxx:rvnLENOVO:rnLENOVO:rvr1.0:cvnLENOVO:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: ThinkCentre xxx dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1598636] Re: INFO: task alsa-sink-ALC32:3263 blocked for more than 120 seconds.
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1598636 Title: INFO: task alsa-sink-ALC32:3263 blocked for more than 120 seconds. Status in linux package in Ubuntu: Incomplete Bug description: Jul 3 14:54:52 raven kernel: [ 1919.788166] INFO: task alsa-sink-ALC32:3263 blocked for more than 120 seconds. Jul 3 14:54:52 raven kernel: [ 1919.788171] Not tainted 4.4.0-28-generic #47-Ubuntu Jul 3 14:54:52 raven kernel: [ 1919.788173] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 3 14:54:52 raven kernel: [ 1919.788174] alsa-sink-ALC32 D 88003e343b98 0 3263 2779 0x0004 Jul 3 14:54:52 raven kernel: [ 1919.788179] 88003e343b98 88003e343b98 8800c51bb700 880415a21b80 Jul 3 14:54:52 raven kernel: [ 1919.788182] 88003e344000 88041a062c04 880415a21b80 Jul 3 14:54:52 raven kernel: [ 1919.788184] 88041a062c08 88003e343bb0 818235b5 88041a062c00 Jul 3 14:54:52 raven kernel: [ 1919.788187] Call Trace: Jul 3 14:54:52 raven kernel: [ 1919.788194] [] schedule+0x35/0x80 Jul 3 14:54:52 raven kernel: [ 1919.788197] [] schedule_preempt_disabled+0xe/0x10 Jul 3 14:54:52 raven kernel: [ 1919.788200] [] __mutex_lock_slowpath+0xb9/0x130 Jul 3 14:54:52 raven kernel: [ 1919.788203] [] mutex_lock+0x1f/0x30 Jul 3 14:54:52 raven kernel: [ 1919.788207] [] regmap_lock_mutex+0xe/0x10 Jul 3 14:54:52 raven kernel: [ 1919.788210] [] regmap_read+0x2f/0x60 Jul 3 14:54:52 raven kernel: [ 1919.788218] [] snd_hdac_regmap_read_raw+0x2a/0xa0 [snd_hda_core] Jul 3 14:54:52 raven kernel: [ 1919.788222] [] _snd_hdac_read_parm+0x1d/0x20 [snd_hda_core] Jul 3 14:54:52 raven kernel: [ 1919.788232] [] query_amp_caps+0x54/0x90 [snd_hda_codec] Jul 3 14:54:52 raven kernel: [ 1919.788238] [] snd_hda_codec_amp_update+0x4b/0x80 [snd_hda_codec] Jul 3 14:54:52 raven kernel: [ 1919.788244] [] snd_hda_mixer_amp_switch_put+0x82/0x100 [snd_hda_codec] Jul 3 14:54:52 raven kernel: [ 1919.788250] [] hda_gen_mixer_mute_put+0x42/0x50 [snd_hda_codec_generic] Jul 3 14:54:52 raven kernel: [ 1919.788257] [] slave_put_val+0x71/0xc0 [snd] Jul 3 14:54:52 raven kernel: [ 1919.788262] [] slave_put+0x60/0x90 [snd] Jul 3 14:54:52 raven kernel: [ 1919.788266] [] snd_ctl_elem_write+0x11c/0x1a0 [snd] Jul 3 14:54:52 raven kernel: [ 1919.788271] [] ? __kmalloc_track_caller+0x1b4/0x250 Jul 3 14:54:52 raven kernel: [ 1919.788275] [] snd_ctl_ioctl+0xe2/0x6b0 [snd] Jul 3 14:54:52 raven kernel: [ 1919.788278] [] do_vfs_ioctl+0x29f/0x490 Jul 3 14:54:52 raven kernel: [ 1919.788281] [] ? vfs_read+0x114/0x130 Jul 3 14:54:52 raven kernel: [ 1919.788284] [] SyS_ioctl+0x79/0x90 Jul 3 14:54:52 raven kernel: [ 1919.788286] [] entry_SYSCALL_64_fastpath+0x16/0x71 Jul 3 14:54:52 raven kernel: [ 1919.788293] INFO: task mplayer:3655 blocked for more than 120 seconds. Jul 3 14:54:52 raven kernel: [ 1919.788294] Not tainted 4.4.0-28-generic #47-Ubuntu Jul 3 14:54:52 raven kernel: [ 1919.788296] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 3 14:54:52 raven kernel: [ 1919.788297] mplayer D 8800c573bd38 0 3655 3373 0x0004 Jul 3 14:54:52 raven kernel: [ 1919.788300] 8800c573bd38 8800c573bef4 81e11500 88040f109b80 Jul 3 14:54:52 raven kernel: [ 1919.788302] 8800c573c000 88040e92d488 88040e92d470 Jul 3 14:54:52 raven kernel: [ 1919.788304] 0001 8800c573bd50 818235b5 88040f109b80 Jul 3 14:54:52 raven kernel: [ 1919.788307] Call Trace: Jul 3 14:54:52 raven kernel: [ 1919.788310] [] schedule+0x35/0x80 Jul 3 14:54:52 raven kernel: [ 1919.788313] [] rwsem_down_write_failed+0x202/0x350 Jul 3 14:54:52 raven kernel: [ 1919.788317] [] call_rwsem_down_write_failed+0x13/0x20 Jul 3 14:54:52 raven kernel: [ 1919.788320] [] ? down_write+
[Kernel-packages] [Bug 1598635] Re: NETDEV WATCHDOG: wwp0s20u4 (cdc_mbim): transmit queue 0 timed out
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1598635 Title: NETDEV WATCHDOG: wwp0s20u4 (cdc_mbim): transmit queue 0 timed out Status in linux package in Ubuntu: Incomplete Bug description: Jun 30 11:37:32 raven kernel: [ 544.865254] [ cut here ] Jun 30 11:37:32 raven kernel: [ 544.865262] WARNING: CPU: 3 PID: 0 at /build/linux-BvkamA/linux-4.4.0/net/sched/sch_generic.c:306 dev_watchdog+0x237/0x240() Jun 30 11:37:32 raven kernel: [ 544.865264] NETDEV WATCHDOG: wwp0s20u4 (cdc_mbim): transmit queue 0 timed out Jun 30 11:37:32 raven kernel: [ 544.865265] Modules linked in: rfcomm bnep nls_iso8859_1 btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev cdc_mbim cdc_wdm arc4 cdc_ncm cdc_acm media usbnet mii intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm mac80211 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic joydev iwlwifi input_leds serio_raw snd_hda_intel intel_pch_thermal snd_hda_codec thinkpad_acpi cfg80211 snd_seq_midi snd_seq_midi_event snd_hda_core nvram snd_hwdep snd_rawmidi lpc_ich snd_pcm rtsx_pci_ms memstick snd_seq mei_me shpchp mei snd_seq_device snd_timer snd soundcore mac_hid kvm_intel kvm irqbypass parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg dm_crypt mmc_block wacom usbhid hid rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul i915 aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper psmouse syscopya rea sysfillrect ahci sysimgblt e1000e libahci fb_sys_fops drm rtsx_pci ptp pps_core wmi video fjes Jun 30 11:37:32 raven kernel: [ 544.865335] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.4.0-28-generic #47-Ubuntu Jun 30 11:37:32 raven kernel: [ 544.865336] Hardware name: LENOVO 20CKCT01WW/20CKCT01WW, BIOS N11ET34W (1.10 ) 08/20/2015 Jun 30 11:37:32 raven kernel: [ 544.865339] 0286 a73de0ee261f184c 88042dcc3d98 813eb1a3 Jun 30 11:37:32 raven kernel: [ 544.865342] 88042dcc3de0 81d638a8 88042dcc3dd0 81081102 Jun 30 11:37:32 raven kernel: [ 544.865344] 8804184c3c80 0003 88040f14b000 Jun 30 11:37:32 raven kernel: [ 544.865347] Call Trace: Jun 30 11:37:32 raven kernel: [ 544.865348][] dump_stack+0x63/0x90 Jun 30 11:37:32 raven kernel: [ 544.865356] [] warn_slowpath_common+0x82/0xc0 Jun 30 11:37:32 raven kernel: [ 544.865359] [] warn_slowpath_fmt+0x5c/0x80 Jun 30 11:37:32 raven kernel: [ 544.865363] [] dev_watchdog+0x237/0x240 Jun 30 11:37:32 raven kernel: [ 544.865366] [] ? qdisc_rcu_free+0x40/0x40 Jun 30 11:37:32 raven kernel: [ 544.865370] [] call_timer_fn+0x35/0x120 Jun 30 11:37:32 raven kernel: [ 544.865372] [] ? qdisc_rcu_free+0x40/0x40 Jun 30 11:37:32 raven kernel: [ 544.865375] [] run_timer_softirq+0x23a/0x2f0 Jun 30 11:37:32 raven kernel: [ 544.865379] [] __do_softirq+0x101/0x290 Jun 30 11:37:32 raven kernel: [ 544.865381] [] irq_exit+0xa3/0xb0 Jun 30 11:37:32 raven kernel: [ 544.865385] [] smp_apic_timer_interrupt+0x42/0x50 Jun 30 11:37:32 raven kernel: [ 544.865387] [] apic_timer_interrupt+0x82/0x90 Jun 30 11:37:32 raven kernel: [ 544.865388][] ? cpuidle_enter_state+0x111/0x2b0 Jun 30 11:37:32 raven kernel: [ 544.865394] [] cpuidle_enter+0x17/0x20 Jun 30 11:37:32 raven kernel: [ 544.865397] [] call_cpuidle+0x32/0x60 Jun 30 11:37:32 raven kernel: [ 544.865400] [] ? cpuidle_select+0x13/0x20 Jun 30 11:37:32 raven kernel: [ 544.865403] [] cpu_startup_entry+0x290/0x350 Jun 30 11:37:32 raven kernel: [ 544.865407] [] start_secondary+0x154/0x190 Jun 30 11:37:32 raven kernel: [ 544.865409] ---[ end trace 0ba74276779b458d ]--- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1
[Kernel-packages] [Bug 1598638] Re: Using secondary monitors with modesetting driver causes system crash
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1598638 Title: Using secondary monitors with modesetting driver causes system crash Status in linux package in Ubuntu: Incomplete Bug description: Setup: 1. Use modesetting driver for X11. 2. Enable a secondary monitor, either VGA, HDMI or DisplayPort. Observe: a. Screen flickers, loses hsync, goes weird every few seconds. b. After a few minutes, system freezes, no logs, no recovery, no nothing, but display still on screen. Workaround: Switching to intel driver system still crashes, but less often, and differently. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shevek 2968 F pulseaudio /dev/snd/controlC1: shevek 2968 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 3 16:13:54 2016 HibernationDevice: RESUME=UUID=22fd2208-7557-432d-bbff-95dd97905323 InstallationDate: Installed on 2015-05-18 (412 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20CKCT01WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-23 (10 days ago) dmi.bios.date: 08/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET34W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CKCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET34W(1.10):bd08/20/2015:svnLENOVO:pn20CKCT01WW:pvrThinkPadT550:rvnLENOVO:rn20CKCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CKCT01WW dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1598638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1598394] Re: intel_pstate has too aggressive frequency selection
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1598394 Title: intel_pstate has too aggressive frequency selection Status in linux package in Ubuntu: Incomplete Bug description: I was recently upgrading from Ubuntu Gnome 15.10 to 16.04 on my ThinkPad. Before the frequency-scaling chose the minimum possible frequency when the system was on low load. Now, when I allow the CPU to choose anything between the lowest and highest possible frequency, it sticks to the highest frequency for 90% of time and only occasionally drops to the low frequency. I can confirm (htop) that my system load is practically zero. Also the CPU Power Manager Applet from Gnome Shell works well, because I can force low frequency by reducing the maximum allowed frequency and can also switch off Turbo Boost. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic 4.4.0.28.30 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timeshifter 1768 F pulseaudio /dev/snd/controlC1: timeshifter 1768 F pulseaudio CurrentDesktop: GNOME Date: Sat Jul 2 12:11:42 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe InstallationDate: Installed on 2016-03-19 (104 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20C0003SFR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-07-02 (0 days ago) dmi.bios.date: 11/07/2014 dmi.bios.vendor: LENOVO dmi.bios.version: B0ET24WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C0003SFR 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrB0ET24WW(1.11):bd11/07/2014:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C0003SFR dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1598394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1598637] Re: Dell Inspiron 5555 touchpad not working
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1598637 Title: Dell Inspiron touchpad not working Status in linux package in Ubuntu: Incomplete Bug description: Installed Ubuntu 16.04 64 bit (also Linux Mint and other Ubuntu 16.04 based distros) on my Dell Inspiron AMD A10-8700P Radeon R6. The touchpad sort-of works for a few seconds (pointer moves but cliking fails) and after a while it hangs completely. The USB mouse works with no issues though. I've found following the steps given here http://askubuntu.com/a/632570/55128 works: 1. Run $ sudo -H gedit /etc/default/grub In the open window edit line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" it should look this way GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.nopnp" Save file and run $ sudo update-grub 2. Run $ echo "blacklist i2c_hid" | sudo tee /etc/modprobe.d/i2c-hid.conf $ sudo depmod -a $ sudo update-initramfs -u $ echo "synaptics_i2c" | sudo tee -a /etc/modules 3. Reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1598637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1598649] Re: ASUS GL552VW touchpad not detected
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1598649 Title: ASUS GL552VW touchpad not detected Status in linux package in Ubuntu: Incomplete Bug description: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=1d57 Product=ad17 Version=0110 N: Name="ZLY ZELOTES GAME MOUSE" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:1D57:AD17.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Asus WMI hotkeys" P: Phys=asus-nb-wmi/input0 S: Sysfs=/devices/platform/asus-nb-wmi/input/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=100013 B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0 B: MSC=10 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=04f2 Product=b424 Version=6969 N: Name="USB2.0 HD UVC WebCam" P: Phys=usb-:00:14.0-4/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input11 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dhawal 1500 F pulseaudio DistroRelease: elementary OS 0.3.2 HibernationDevice: RESUME=UUID=35751668-1b31-4fe7-bf7e-eda17d2a5601 InstallationDate: Installed on 2016-06-14 (20 days ago) InstallationMedia: elementary OS 0.3.2 "Freya" - Stable amd64 (20151209) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 1d57:ad17 Xenta Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType:
[Kernel-packages] [Bug 1572562] Re: KASan: out of bounds access in isolate_migratepages_range
The commit that fixes this bug, may have introduced bug 1598197 ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Gavin Guo (mimi0213kimo) ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1572562 Title: KASan: out of bounds access in isolate_migratepages_range Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Bug description: [Impact] In the v3.13.0-76 kernel with KASan backported. The following error message could be observed during the kernel building stress test of the command[1]: "./parallel-73670.sh -r 2 -k 40" That means building 40 kernels in the same time with 2 rounds. Bad access happens when we read page->mapping->flags, and page->mapping is a pointer to anon_vma which is already freed in the do_exit path. == BUG: KASan: out of bounds access in isolate_migratepages_range+0x663/0xb30 at addr 880279cc76d1 Read of size 8 by task cc1/27473 = BUG anon_vma (Not tainted): kasan: bad access detected - Disabling lock debugging due to kernel taint INFO: Allocated in anon_vma_prepare+0x189/0x250 age=7323 cpu=16 pid=31029 __slab_alloc+0x4f8/0x560 kmem_cache_alloc+0x18b/0x1e0 anon_vma_prepare+0x189/0x250 do_wp_page+0x837/0xb10 handle_mm_fault+0x884/0x1160 __do_page_fault+0x218/0x750 do_page_fault+0x1a/0x70 page_fault+0x28/0x30 INFO: Freed in __put_anon_vma+0x69/0xe0 age=8588 cpu=4 pid=29418 __slab_free+0x2ab/0x3f0 kmem_cache_free+0x1c1/0x200 __put_anon_vma+0x69/0xe0 unlink_anon_vmas+0x2a8/0x320 free_pgtables+0x50/0x1c0 exit_mmap+0xca/0x1e0 mmput+0x82/0x1b0 do_exit+0x391/0x1060 do_group_exit+0x86/0x130 SyS_exit_group+0x1d/0x20 system_call_fastpath+0x1a/0x1f INFO: Slab 0xea0009e73100 objects=43 used=30 fp=0x880279cc67a8 flags=0x2004080 INFO: Object 0x880279cc7658 @offset=13912 fp=0x880279cc7c38 Bytes b4 880279cc7648: 10 00 00 00 5b 17 00 00 ef 25 6b 03 01 00 00 00 [%k. Object 880279cc7658: 58 76 cc 79 02 88 ff ff 00 00 00 00 00 00 00 00 Xv.y Object 880279cc7668: 00 00 00 00 5a 5a 5a 5a 70 76 cc 79 02 88 ff ff pv.y Object 880279cc7678: 70 76 cc 79 02 88 ff ff 01 00 00 00 03 00 00 00 pv.y Object 880279cc7688: 58 76 cc 79 02 88 ff ff b8 2a 20 31 02 88 ff ff Xv.y.* 1 CPU: 8 PID: 27473 Comm: cc1 Tainted: GB 3.13.0-76-generic #120hf00073670v20160120b0h5d3e6ab Hardware name: Cisco Systems Inc UCSC-C220-M3L/UCSC-C220-M3L, BIOS C220M3.2.0.3.0.080120140402 08/01/2014 ea0009e73100 880736bbf750 81a6e195 8804e881b840 880736bbf780 81244c1d 8804e881b840 ea0009e73100 880279cc7658 ea001aa99c98 880736bbf7a8 8124ad66 Call Trace: [] dump_stack+0x45/0x56 [] print_trailer+0xfd/0x170 [] object_err+0x36/0x40 [] kasan_report_error+0x1e9/0x3a0 [] ? memcg_check_events+0x28/0x380 [] ? rmap_walk+0x32d/0x340 [] kasan_report+0x40/0x50 [] ? isolate_migratepages_range+0x663/0xb30 [] __asan_load8+0x69/0xa0 [] isolate_migratepages_range+0x663/0xb30 [] ? zone_watermark_ok+0x57/0x70 [] compact_zone+0x416/0x700 [] compact_zone_order+0x95/0x100 [] try_to_compact_pages+0x102/0x1a0 [] __alloc_pages_direct_compact+0x96/0x290 [] __alloc_pages_nodemask+0x97e/0xc40 [] alloc_pages_vma+0xb4/0x200 [] do_huge_pmd_anonymous_page+0x13a/0x490 [] ? do_numa_page+0x192/0x200 [] handle_mm_fault+0x267/0x1160 [] __do_page_fault+0x218/0x750 [] ? do_mmap_pgoff+0x47d/0x500 [] ? vm_mmap_pgoff+0xa9/0xd0 [] do_page_fault+0x1a/0x70 [] page_fault+0x28/0x30 Memory state around the buggy address: 880279cc7580: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc 880279cc7600: fc fc fc fc fc fc fc fc fc fc fc 00 00 00 00 00 >880279cc7680: 00 00 00 fc fc fc fc fc fc fc fc fc fc fc fc fc ^ 880279cc7700: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc 880279cc7780: fc fc fc fc fc fc fc fc fc fc 00 00 00 00 00 00 == gavin@rotom:~/ddebs/ddebs-3.13.0-76.120hf00073670v20160120b0h5d3e6ab$ addr2line 0x81205ee3 -e u
[Kernel-packages] [Bug 1598197] Re: deadlock on balloon deflation
** Tags added: kernel-da-key ** Changed in: linux-lts-trusty (Ubuntu) Importance: Undecided => High ** Package changed: linux-lts-trusty (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1598197 Title: deadlock on balloon deflation Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Bug description: Latest Ubuntu trusty with kernel 3.13.0-91-generic run in a KVM virtual machine with virtio_balloon hangs when the previously inflated balloon is deflated. The problem is in the recently committed backport: commit 838478a8496ef9677256f53710144abe2ea49625 Author: Konstantin Khlebnikov AuthorDate: Mon May 16 14:43:10 2016 +0800 Commit: Kamal Mostafa CommitDate: Fri Jun 10 07:15:37 2016 -0700 mm/balloon_compaction: redesign ballooned pages management BugLink: http://bugs.launchpad.net/bugs/1572562 Sasha Levin reported KASAN splash inside isolate_migratepages_range(). Problem is in the function __is_movable_balloon_page() which tests AS_BALLOON_MAP in page->mapping->flags. This function has no protection against anonymous pages. As result it tried to check address space flags inside struct anon_vma. Further investigation shows more problems in current implementation: * Special branch in __unmap_and_move() never works: balloon_page_movable() checks page flags and page_count. In __unmap_and_move() page is locked, reference counter is elevated, thus balloon_page_movable() always fails. As a result execution goes to the normal migration path. virtballoon_migratepage() returns MIGRATEPAGE_BALLOON_SUCCESS instead of MIGRATEPAGE_SUCCESS, move_to_new_page() thinks this is an error code and assigns newpage->mapping to NULL. Newly migrated page lose connectivity with balloon an all ability for further migration. * lru_lock erroneously required in isolate_migratepages_range() for isolation ballooned page. This function releases lru_lock periodically, this makes migration mostly impossible for some pages. * balloon_page_dequeue have a tight race with balloon_page_isolate: balloon_page_isolate could be executed in parallel with dequeue between picking page from list and locking page_lock. Race is rare because they use trylock_page() for locking. This patch fixes all of them. Instead of fake mapping with special flag this patch uses special state of page->_mapcount: PAGE_BALLOON_MAPCOUNT_VALUE = -256. Buddy allocator uses PAGE_BUDDY_MAPCOUNT_VALUE = -128 for similar purpose. Storing mark directly in struct page makes everything safer and easier. PagePrivate is used to mark pages present in page list (i.e. not isolated, like PageLRU for normal pages). It replaces special rules for reference counter and makes balloon migration similar to migration of normal pages. This flag is protected by page_lock together with link to the balloon device. Signed-off-by: Konstantin Khlebnikov Reported-by: Sasha Levin Link: http://lkml.kernel.org/p/53e6ceaa.9020...@oracle.com Cc: Rafael Aquini Cc: Andrey Ryabinin Cc: [3.8+] Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds (backported from commit d6d86c0a7f8ddc5b38cf089222cb1d9540762dc2) Signed-off-by: Gavin Guo Conflicts: mm/balloon_compaction.c mm/migrate.c Acked-by: Stefan Bader Signed-off-by: Kamal Mostafa It was applied after another backport: commit 47618e32c2a729554bf56b8ee7b541b63aadad97 Author: Minchan Kim AuthorDate: Mon Dec 28 08:35:13 2015 +0900 Commit: Luis Henriques CommitDate: Mon Feb 22 19:31:53 2016 + virtio_balloon: fix race between migration and ballooning BugLink: http://bugs.launchpad.net/bugs/1542497 commit 21ea9fb69e7c4b1b1559c3e410943d3ff248ffcb upstream. In balloon_page_dequeue, pages_lock should cover the loop (ie, list_for_each_entry_safe). Otherwise, the cursor page could be isolated by compaction and then list_del by isolation could poison the page->lru.{prev,next} so the loop finally could access wrong address like this. This patch fixes the bug. general protection fault: [#1] SMP Dumping ftrace bu
[Kernel-packages] [Bug 1599349] Re: Ubuntu-Touch closing apps/screens on reboot
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key ** Tags added: bot-stop-nagging ** Package changed: linux (Ubuntu) => ubuntu-touch-meta (Ubuntu) ** Changed in: ubuntu-touch-meta (Ubuntu) Importance: Medium => Undecided ** Changed in: ubuntu-touch-meta (Ubuntu) Status: Confirmed => 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/1599349 Title: Ubuntu-Touch closing apps/screens on reboot Status in ubuntu-touch-meta package in Ubuntu: New Bug description: When I turn my Ubuntu phone off, on restart all of my previously open screens/apps are now closed. This is a bit annoying as I need to open everything up again. In Android, if you turn off your phone and then start it up again, all the apps, pages and such like, that you had open before the shut-down/reboot are all still visible on start-up. I really think it is something that new users coming to Ubuntu Touch will be expecting as standard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1599349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1599350] Re: Ubunth Touch - Unable to add to the Notifications apps list
** Tags added: bot-stop-nagging ** Tags added: kernel-da-key ** Package changed: linux (Ubuntu) => ubuntu-touch-meta (Ubuntu) ** Changed in: ubuntu-touch-meta (Ubuntu) Status: Confirmed => 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/1599350 Title: Ubunth Touch - Unable to add to the Notifications apps list Status in ubuntu-touch-meta package in Ubuntu: New Bug description: I have a "Proton" email account, which works very nice through my Ubuntu phone. However, I am not receiving notifications when I get emails come through. So I can miss them. I am unable to add Proton email (or anything else) to the list of applications I receive notifications from in Settings > Notifications screen? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1599350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1599457] Re: On idle_cpu function issue.
Thank you for providing a patch, and making Ubuntu better. Can you provide some information on the status of the patch with regards to getting it merged upstream? Has it been sent upstream, what sort of feedback has it received, is it getting applied to a subsystem maintainer's tree, etc? People affected by this bug are probably wondering why the kernel team doesn't just apply the patch and fix it. The reason is that the kernel team is reluctant (not opposed) to apply any patch to a stable kernel that is not from upstream. Applying patches that don't come from upstream add greatly to the support of the kernel as other upstream patches may touch the same area as the non-upstream patch and may prevent them from applying cleanly. To submit your patch, send your patch with the detailed description/changelog and your Signoff (ending with Signed-off-by: your name ), to the emails listed from ./scripts/get_maintainer.pl drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel sources). Once you have sent the patch upstream and it's accepted, please drop a note here so that we can cherry-pick/include the patch into Ubuntu kernel. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1599457 Title: On idle_cpu function issue. Status in linux package in Ubuntu: Triaged Bug description: Below is result of perf report: idle_cpu /proc/kcore │ │ │ │Disassembly of section load0: │ │810adbb0 : 33,33 │ nop │ movslq %edi,%rdi │ mov$0x16d00,%rax │ push %rbp 16,67 │ add-0x7e0cb600(,%rdi,8),%rax │ mov%rsp,%rbp 16,67 │ mov%rax,%rdx │ xor%eax,%eax │ mov0x8e0(%rdx),%rcx 33,33 │ cmp%rcx,0x8d8(%rdx) │↓ je 32 │30: pop%rbp │← retq ... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: asu3285 F...m pulseaudio /dev/snd/controlC0: asu3285 F pulseaudio CurrentDesktop: XFCE Date: Wed Jul 6 13:11:05 2016 InstallationDate: Installed on 2016-04-29 (67 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1598579] Re: Check for NULL on io_is_direct function.
Thank you for providing a patch, and making Ubuntu better. Can you provide some information on the status of the patch with regards to getting it merged upstream? Has it been sent upstream, what sort of feedback has it received, is it getting applied to a subsystem maintainer's tree, etc? People affected by this bug are probably wondering why the kernel team doesn't just apply the patch and fix it. The reason is that the kernel team is reluctant (not opposed) to apply any patch to a stable kernel that is not from upstream. Applying patches that don't come from upstream add greatly to the support of the kernel as other upstream patches may touch the same area as the non-upstream patch and may prevent them from applying cleanly. To submit your patch, send your patch with the detailed description/changelog and your Signoff (ending with Signed-off-by: your name ), to the emails listed from ./scripts/get_maintainer.pl drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel sources). Once you have sent the patch upstream and it's accepted, please drop a note here so that we can cherry-pick/include the patch into Ubuntu kernel. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1598579 Title: Check for NULL on io_is_direct function. Status in linux package in Ubuntu: Triaged Bug description: When is posible will add zero reponse when missing pointer. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu3013 F pulseaudio CurrentDesktop: MATE Date: Sun Jul 3 16:42:01 2016 InstallationDate: Installed on 2016-04-29 (64 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1598579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1598854] Re: usb-scanner Problem
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1598854 Title: usb-scanner Problem Status in linux package in Ubuntu: Incomplete Bug description: Es ist mir nicht möglich einen USB-Scanner EpsonPerfection V500 Photo einzubinden oder über Sahne/xsahne zu starten ! Können Sie hier helfen?? Vielen Dank Ruhtz ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-41.48-generic 4.2.8-ckt11 Uname: Linux 4.2.0-41-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 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 Date: Mon Jul 4 15:24:19 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: ndiswrapper, 1.59, 3.19.0-31-generic, x86_64: installed ndiswrapper, 1.59, 4.2.0-38-generic, x86_64: installed ndiswrapper, 1.59, 4.2.0-41-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:174b] InstallationDate: Installed on 2015-09-09 (299 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Lsusb: Bus 001 Device 003: ID 03f0:3612 Hewlett-Packard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7250 ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-41-generic root=UUID=27512330-f06a-4644-82da-93c6aceb2909 ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2007 dmi.bios.vendor: MS-7250 dmi.bios.version: V1.7 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7250 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnMS-7250:bvrV1.7:bd05/17/2007:svnMSI:pnMS-7250:pvr1.0:rvnMSI:rnMS-7250:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7250 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Jul 4 15:17:13 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech M705MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1598854/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : ht
[Kernel-packages] [Bug 1599115] Re: On __remove_hrtimer function issue.
Thank you for providing a patch, and making Ubuntu better. Can you provide some information on the status of the patch with regards to getting it merged upstream? Has it been sent upstream, what sort of feedback has it received, is it getting applied to a subsystem maintainer's tree, etc? People affected by this bug are probably wondering why the kernel team doesn't just apply the patch and fix it. The reason is that the kernel team is reluctant (not opposed) to apply any patch to a stable kernel that is not from upstream. Applying patches that don't come from upstream add greatly to the support of the kernel as other upstream patches may touch the same area as the non-upstream patch and may prevent them from applying cleanly. To submit your patch, send your patch with the detailed description/changelog and your Signoff (ending with Signed-off-by: your name ), to the emails listed from ./scripts/get_maintainer.pl drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel sources). Once you have sent the patch upstream and it's accepted, please drop a note here so that we can cherry-pick/include the patch into Ubuntu kernel. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1599115 Title: On __remove_hrtimer function issue. Status in linux package in Ubuntu: Triaged Bug description: Below is result of perf report: │1e: pop%rbx │ pop%r12 │ pop%r13 │ pop%r14 │ pop%rbp │← retq │27: mov%rdi,%rbx │ lea0x10(%rsi),%rdi 50,00 │ mov%rsi,%r12 │ mov%rbx,%rsi │ mov%ecx,%r13d │ callq 0x813f40a0 │ test %al,%al │↓ je 7a │40: test %r13d,%r13d │↑ je 1e │ cmp0x28(%r14),%rbx │↑ jne1e │ testb $0x2,0x1e(%r14) │↑ je 1e │ mov%r14,%rdi │ callq 0x810eec20 │ cmp0x20(%r14),%rax ... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu2974 F pulseaudio CurrentDesktop: MATE Date: Tue Jul 5 13:46:22 2016 InstallationDate: Installed on 2016-04-29 (66 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1598474] Re: On clear_page_orig function issue.
Thank you for providing a patch, and making Ubuntu better. Can you provide some information on the status of the patch with regards to getting it merged upstream? Has it been sent upstream, what sort of feedback has it received, is it getting applied to a subsystem maintainer's tree, etc? People affected by this bug are probably wondering why the kernel team doesn't just apply the patch and fix it. The reason is that the kernel team is reluctant (not opposed) to apply any patch to a stable kernel that is not from upstream. Applying patches that don't come from upstream add greatly to the support of the kernel as other upstream patches may touch the same area as the non-upstream patch and may prevent them from applying cleanly. To submit your patch, send your patch with the detailed description/changelog and your Signoff (ending with Signed-off-by: your name ), to the emails listed from ./scripts/get_maintainer.pl drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel sources). Once you have sent the patch upstream and it's accepted, please drop a note here so that we can cherry-pick/include the patch into Ubuntu kernel. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1598474 Title: On clear_page_orig function issue. Status in linux package in Ubuntu: Triaged Bug description: Bellow is result of perf report: clear_page_orig /proc/kcore │ │ │ │Disassembly of section load0: │ │813f7b30 : │ xor%eax,%eax │ mov$0x40,%ecx │ nop 5,71 │10: dec%ecx │ mov%rax,(%rdi) 80,00 │ mov%rax,0x8(%rdi) 2,86 │ mov%rax,0x10(%rdi) │ mov%rax,0x18(%rdi) 2,86 │ mov%rax,0x20(%rdi) 5,71 │ mov%rax,0x28(%rdi) 2,86 │ mov%rax,0x30(%rdi) │ mov%rax,0x38(%rdi) │ lea0x40(%rdi),%rdi │↑ jne10 │ nop │← retq ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu3104 F pulseaudio CurrentDesktop: MATE Date: Sat Jul 2 20:15:06 2016 InstallationDate: Installed on 2016-04-29 (64 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1598474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1599076] Re: On exit_idle function issue
Thank you for providing a patch, and making Ubuntu better. Can you provide some information on the status of the patch with regards to getting it merged upstream? Has it been sent upstream, what sort of feedback has it received, is it getting applied to a subsystem maintainer's tree, etc? People affected by this bug are probably wondering why the kernel team doesn't just apply the patch and fix it. The reason is that the kernel team is reluctant (not opposed) to apply any patch to a stable kernel that is not from upstream. Applying patches that don't come from upstream add greatly to the support of the kernel as other upstream patches may touch the same area as the non-upstream patch and may prevent them from applying cleanly. To submit your patch, send your patch with the detailed description/changelog and your Signoff (ending with Signed-off-by: your name ), to the emails listed from ./scripts/get_maintainer.pl drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel sources). Once you have sent the patch upstream and it's accepted, please drop a note here so that we can cherry-pick/include the patch into Ubuntu kernel. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1599076 Title: On exit_idle function issue Status in linux package in Ubuntu: Triaged Bug description: Below is result of perf report: exit_idle /proc/kcore │ ▒ │ ▒ │ ▒ │Disassembly of section load0: ▒ │ ▒ │81039530 : ▒ │ nop ▒ │ mov%gs:0xd3c0,%rax ▒ 50,00 │ mov0x428(%rax),%eax ▒ │ test %eax,%eax ▒ │↓ jne27 ▒ │ btrl $0x0,%gs:0x7efd3db7(%rip)# 0xd308 ▒ 50,00 │ sbb%eax,%eax ▒ │ test %eax,%eax ▒ │↓ jne28 ▒ │27: ← retq ▒ │28: push %rbp ▒ │ xor%edx,%edx ◆ │ mov$0x2,%esi ▒ │ mov$0x820cbd50,%rdi ▒ │ mov%rsp,%rbp ▒ │ callq 0x810a1790 ▒ │ pop%rbp ▒ │← retq ▒ ▒ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu2989 F pulseaudio Curre