[Kernel-packages] [Bug 1424293] Re: BYD trackpad detected as PS/2 mouse
So I made systemd-udevd in comment #59 has the ability to use byd psmouse protocol via hwdb. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1424293 Title: BYD trackpad detected as PS/2 mouse Status in linux package in Ubuntu: Triaged Bug description: In 14.04.2, I expected to be able to use as touchpad with two finger vertical/horizontal scrolling. Currently only able to use plainly. The exact device is this: http://bydit.com/doce/products/microelectronics/2474.html I: Bus=0011 Vendor=0002 Product=0005 Version= N: Name="ImPS/2 Generic Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input7 U: Uniq= H: Handlers=mouse0 event10 B: PROP=0 B: EV=7 B: KEY=7 0 0 0 0 B: REL=103 Output of xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ USB 2.0 Camera id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=11 [slave keyboard (3)] --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vjftw 1362 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=d58116d7-f5eb-4b3c-b986-a9a29b608880 InstallationDate: Installed on 2015-04-25 (28 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 058f:3821 Alcor Micro Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation SharkBay Platform Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed root=UUID=cd943b28-f170-4ce9-b836-18c395f1df6d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: Fab2 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd02/03/2015:svnIntelCorporation:pnSharkBayPlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrFab2:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.: dmi.product.name: SharkBay Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1424293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690586] Re: Kernel v4.8.0: Black screen and automatic shutdown
** Description changed: - When using the kernel version 4.8.0, at some unpredictable time after - boot, the screen goes black, the compute fan starts working at top + When using the Ubuntu kernel version 4.8.0, at some unpredictable time + after boot, the screen goes black, the compute fan starts working at top speed, and after a couple seconds the computer shuts down (probably due to overheating). This does not happen with the mainline kernel version 3.19.8, but it - does also happen with the mainline kernel version 4.10.0. + does also happen with the mainline kernel versions 4.10.0, 4.10.12 and + 4.11.0. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-51-generic 4.8.0-51.54 ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: jakob 1713 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: jakob 1713 F pulseaudio CurrentDesktop: KDE Date: Sat May 13 14:21:58 2017 InstallationDate: Installed on 2017-03-01 (73 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlStatus: - Socket 0: -3.3V - 16-bit - PC Card -Subdevice 0 (function 0) bound to driver "pata_pcmcia" + Socket 0: + 3.3V + 16-bit + PC Card + Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic root=UUID=824f0ac8-4d2b-416d-85c3-40c13ee483ee ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.8.0-51-generic N/A - linux-backports-modules-4.8.0-51-generic N/A - linux-firmware1.161.1 + linux-restricted-modules-4.8.0-51-generic N/A + linux-backports-modules-4.8.0-51-generic N/A + linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.60 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.35 dmi.chassis.asset.tag: CZC04543TK dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.60:bd11/11/2015:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard ** Description changed: When using the Ubuntu kernel version 4.8.0, at some unpredictable time - after boot, the screen goes black, the compute fan starts working at top - speed, and after a couple seconds the computer shuts down (probably due - to overheating). + after boot, the screen goes black, the computer fan starts working at + top speed, and after a couple seconds the computer shuts down (probably + due to overheating). This does not happen with the mainline kernel version 3.19.8, but it does also happen with the mainline kernel versions 4.10.0, 4.10.12 and 4.11.0. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-51-generic 4.8.0-51.54 ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jakob 1713 F pulseaudio CurrentDesktop: KDE Date: Sat May 13 14:21:58 2017 InstallationDate: Installed on 2017-03-01 (73 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic root=UUID=824f0ac8-4d2b-416d-85c3-40c13ee483ee ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-51-generic N/A linux-backports-modules-4.8.0-51-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.60 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.35 dmi.chassis.asset.tag: CZC04543TK dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.60:bd11/11/2015:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.35:cvnHewle
[Kernel-packages] [Bug 1671854] Re: Bluetooth not enabling
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671854 Title: Bluetooth not enabling Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: i m using hp probook 6460b and i am unbale to enable my bluetooth. i have tried everything i can find on google and http://askubuntu.com. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: boot/vmlinuz-4.4.0-31-generic] ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kamran F pulseaudio CurrentDesktop: Unity Date: Fri Mar 10 20:37:29 2017 HibernationDevice: RESUME=UUID=4c928787-6e98-4d4c-9712-faabc24813da InstallationDate: Installed on 2017-03-09 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 003: ID 0461:4dc7 Primax Electronics, Ltd Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP ProBook 6460b ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=e339ab8f-1d8f-44ed-bba2-a8e950cdbe55 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCE Ver. F.08 dmi.board.name: 161D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.45 dmi.chassis.asset.tag: CNU14903Y9 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCEVer.F.08:bd08/26/2011:svnHewlett-Packard:pnHPProBook6460b:pvrA0001D02:rvnHewlett-Packard:rn161D:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6460b dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671854/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671854] Re: Bluetooth not enabling
[Expired for linux (Ubuntu Xenial) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671854 Title: Bluetooth not enabling Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: i m using hp probook 6460b and i am unbale to enable my bluetooth. i have tried everything i can find on google and http://askubuntu.com. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: boot/vmlinuz-4.4.0-31-generic] ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kamran F pulseaudio CurrentDesktop: Unity Date: Fri Mar 10 20:37:29 2017 HibernationDevice: RESUME=UUID=4c928787-6e98-4d4c-9712-faabc24813da InstallationDate: Installed on 2017-03-09 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 003: ID 0461:4dc7 Primax Electronics, Ltd Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP ProBook 6460b ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=e339ab8f-1d8f-44ed-bba2-a8e950cdbe55 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCE Ver. F.08 dmi.board.name: 161D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.45 dmi.chassis.asset.tag: CNU14903Y9 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCEVer.F.08:bd08/26/2011:svnHewlett-Packard:pnHPProBook6460b:pvrA0001D02:rvnHewlett-Packard:rn161D:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6460b dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671854/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668031] Re: Network adapter keeps on hanging up
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1668031 Title: Network adapter keeps on hanging up Status in linux package in Ubuntu: Expired Bug description: Every hour or so, I'm unable to access the internet through this laptop. dmesg usually reports errors related to the network adapter, but not always. Disconnecting from the current Wifi network and connecting to another, usually works. Immediately connecting to the original network after that does not cause the problem to reoccur. At least, not for another hour or so. I'm not sure how to better describe this bug. The network also provides a nfs drive that is mounted on the laptop, if that is significant. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-39-generic 4.8.0-39.42 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruud 2810 F pulseaudio CurrentDesktop: Unity Date: Sun Feb 26 02:13:55 2017 HibernationDevice: RESUME=UUID=2f2d2c45-4fef-49ec-932a-8314b15c2f6b InstallationDate: Installed on 2016-11-08 (109 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-39-generic N/A linux-backports-modules-4.8.0-39-generic N/A linux-firmware1.162 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672536] Re: task btrfs:841 blocked for more than 120 seconds.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672536 Title: task btrfs:841 blocked for more than 120 seconds. Status in linux package in Ubuntu: Expired Bug description: After starting `btrfs scrub start /` `dmesg` contains ``` [Mär13 21:49] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,09] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,07] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,04] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,02] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,03] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,02] [] mutex_lock+0x1f/0x30 [ +0,33] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,03] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,02] [] ? do_nanosleep+0x96/0xf0 [ +0,03] [] do_vfs_ioctl+0xa3/0x610 [ +0,03] [] ? __hrtimer_init+0xa0/0xa0 [ +0,02] [] ? do_nanosleep+0x5a/0xf0 [ +0,03] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:51] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,10] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,07] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,03] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,03] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,02] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,03] [] mutex_lock+0x1f/0x30 [ +0,34] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,03] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,03] [] ? do_nanosleep+0x96/0xf0 [ +0,02] [] do_vfs_ioctl+0xa3/0x610 [ +0,03] [] ? __hrtimer_init+0xa0/0xa0 [ +0,03] [] ? do_nanosleep+0x5a/0xf0 [ +0,02] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:53] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,11] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,32] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,03] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,03] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,02] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,03] [] mutex_lock+0x1f/0x30 [ +0,33] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,02] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,03] [] ? do_nanosleep+0x96/0xf0 [ +0,04] [] do_vfs_ioctl+0xa3/0x610 [ +0,02] [] ? __hrtimer_init+0xa0/0xa0 [ +0,03] [] ? do_nanosleep+0x5a/0xf0 [ +0,
[Kernel-packages] [Bug 1672518] Re: Suspend -> Freeze
[Expired for linux (Ubuntu Yakkety) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Yakkety) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672518 Title: Suspend -> Freeze Status in linux package in Ubuntu: Expired Status in linux source package in Yakkety: Expired Bug description: Thinkpad SL510 freezes after SUSPEND Halfmoon-shaped LED is flashing, screen is black as should be, but nothing wakes the System up. Freeze or is system waiting for imput I cant deliver eg missing button? Google: Display driver at fault?! Keep up the good work! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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: Mon Mar 13 20:52:38 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:213a] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:213a] InstallationDate: Installed on 2017-03-06 (7 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 2847BTG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6JET83WW (1.41 ) dmi.board.name: 2847BTG 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:bvr6JET83WW(1.41):bd09/21/2010:svnLENOVO:pn2847BTG:pvrThinkPadSL510:rvnLENOVO:rn2847BTG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2847BTG dmi.product.version: ThinkPad SL510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 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-video-nouveau N/A xserver.bootTime: Mon Mar 13 20:43:42 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672518] Re: Suspend -> Freeze
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672518 Title: Suspend -> Freeze Status in linux package in Ubuntu: Expired Status in linux source package in Yakkety: Expired Bug description: Thinkpad SL510 freezes after SUSPEND Halfmoon-shaped LED is flashing, screen is black as should be, but nothing wakes the System up. Freeze or is system waiting for imput I cant deliver eg missing button? Google: Display driver at fault?! Keep up the good work! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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: Mon Mar 13 20:52:38 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:213a] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:213a] InstallationDate: Installed on 2017-03-06 (7 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 2847BTG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6JET83WW (1.41 ) dmi.board.name: 2847BTG 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:bvr6JET83WW(1.41):bd09/21/2010:svnLENOVO:pn2847BTG:pvrThinkPadSL510:rvnLENOVO:rn2847BTG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2847BTG dmi.product.version: ThinkPad SL510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 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-video-nouveau N/A xserver.bootTime: Mon Mar 13 20:43:42 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unattended-upgrades (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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: update-notifier (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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
Why doesn't linux-image-extra's postrm simply run update-initramfs. That seems the more sensible thing to do as it is the same as with any other package that wants to put things into the initrd. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501884 Title: linux-image-extra-*-generic postrm script runs install actions Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591669] Re: duplicate touchpad reported and syndaemon/synclient does not work
I am experiencing the same(?) bug with Kubuntu 17.04, all updates as of May-13 2017. Suspending/Resuming does not help in my case. Dell Precision 5510 9550 Interestingly, the problem started to show up only recently and intermittently. I can't for sure say since when exactly. I will try the above workaround by ignoring the spurious entry in xinput. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00: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/ubuntu/+source/linux/+bug/1591669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug
The following workaround fixes for me: https://ubuntuforums.org/showthread.php?t=2226734 Here are the steps adapted for systemd: - Check the output of `ls /sys/bus/pci/drivers/xhci_hcd`. In my laptop I see ":00:14.0 bind new_id remove_id uevent unbind". The goal is to get the id of the xhci_hcd, for me it is ":00:14.0"(which I will use in the following steps). Also verify that the output shows "bind" and "unbind" as directory entries. The following commands should be executed in a root shell - Create a script to unbind the xhci: # cat > /usr/local/bin/unbind-xhci << "EOF" #!/bin/sh echo -n ':00:14.0' | tee /sys/bus/pci/drivers/xhci_hcd/unbind EOF # chmod +x /usr/local/bin/unbind-xhci - Create a script to rebind the xhci: # cat > /usr/local/bin/rebind-xhci << "EOF" #!/bin/sh echo -n ':00:14.0' | tee /sys/bus/pci/drivers/xhci_hcd/bind EOF # chmod +x /usr/local/bin/rebind-xhci - Create a systemd service that runs before sleep: # cat > /etc/systemd/system/unbind-xhci.service << "EOF" [Unit] Description=Unbind xHCI Host Controller Driver before sleep Before=sleep.target [Service] Type=oneshot ExecStart=/usr/local/bin/unbind-xhci [Install] WantedBy=sleep.target EOF - Create a systemd service that runs after wakeup: # cat > /etc/systemd/system/rebind-xhci.service << "EOF" [Unit] Description=Unbind xHCI Host Controller Driver after wakeup After=suspend.target After=hibernate.target After=hybrid-sleep.target [Service] Type=oneshot ExecStart=/usr/local/bin/rebind-xhci [Install] WantedBy=suspend.target WantedBy=hibernate.target WantedBy=hybrid-sleep.target EOF - Reload systemd # systemctl daemon-reload -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Every linux user should put that linux is not support in their gigabyte review. I always bought ASUS motherboards, I gave gigabyte a try because of Ryzen motherboards shortage, however I was my last gigabyte board. On Sat, May 13, 2017 at 4:20 PM edward <1671...@bugs.launchpad.net> wrote: > Hi guys, > > i think we should do something about this gigabyte-situation, kinda of > writing then a bunch of letters from all of us, there is also a bunch of > ppl on reddit having this same problem, and still, gigabyte is not > giving a breath to address this situation... do we really have to accept > this kinda answers "we do not support linux, see by yourself what u > do"... > > i think we should make us ourselves to a big voice of this thing, so > that gigabyte stop threating our problem like nothing they have to do > with... > > any suggestions? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1671360 > > Title: > System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/linux/+bug/1671360/+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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
linux-image--generic is present when removing linux-image- extra--generic. initramfs-tools needs to re-create initrd.img, at least if linux-image--generic will not be removed. If that is the only reason, I think it would be better to do the re-creation in a postrm script than run all postinst scripts. /etc/kernel/postrm.d /initramfs-tools could detect it is removing a linux-image-extra package and then do the right thing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501884 Title: linux-image-extra-*-generic postrm script runs install actions Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
As for the apt-auto-removal problem, it is fixed, right? Bug #1440608 Yet to be fixed at least: Bug #1458204 Bug #1678187 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501884 Title: linux-image-extra-*-generic postrm script runs install actions Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1689390] Re: Kernel 4.11 update
I've been about two days recovering my Ubuntu in a try to update the nvidia driver... I don't know if want to try to update the kernel now :-)) -- 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/1689390 Title: Kernel 4.11 update Status in dkms package in Ubuntu: Confirmed Bug description: I was trying to update my Ubuntu 16.04 with the last kernel version. My current version is uname -r 4.8.8-040808-generic And I would like to update the kernel to the new 4.11. I downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/ the files linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb to a folder, there I executed the first one without errors, but on the second one I have a problem. This is the log generated on the installation... root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dpkg -i linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb Seleccionando el paquete linux-headers-4.11.0-041100 previamente no seleccionado. (Leyendo la base de datos ... 389575 ficheros o directorios instalados actualmente.) Preparando para desempaquetar linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb ... Desempaquetando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ... Configurando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ... root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dpkg -i linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb Seleccionando el paquete linux-headers-4.11.0-041100-generic previamente no seleccionado. (Leyendo la base de datos ... 407178 ficheros o directorios instalados actualmente.) Preparando para desempaquetar linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb ... Desempaquetando linux-headers-4.11.0-041100-generic (4.11.0-041100.201705041534) ... Configurando linux-headers-4.11.0-041100-generic (4.11.0-041100.201705041534) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 4.11.0-041100-generic /boot/vmlinuz-4.11.0-041100-generic ERROR (dkms apport): kernel package linux-headers-4.11.0-041100-generic is not supported Error! Bad return status for module build on kernel: 4.11.0-041100-generic (x86_64) Consult /var/lib/dkms/nvidia-304/304.135/build/make.log for more information. I have attached the make.log file. How could I make the update? Thank you very much in advance Kind regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1689390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 448332] ☂some helpful articles
Hello, I've been looking for some information and came across these nice articles, they may be helpful for you. You may read them here http://pipeline.sarkissov.com Yours sincerely, c.arcella Sent from Mail for Windows 10 ** Attachment added: "9C0FC04D97AE81273DAF71B0E6A6AF15.jpg" https://bugs.launchpad.net/bugs/448332/+attachment/4876290/+files/9C0FC04D97AE81273DAF71B0E6A6AF15.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/448332 Title: BUG: scheduling while atomic: swapper/0/0x1001 Status in linux package in Ubuntu: Won't Fix Bug description: Binary package hint: linux-image-2.6.31-13-generic After updating to kernel 2.6.31-13-generic my system became more unstable Description:Ubuntu karmic (development branch) Release:9.10 Installed: 2.6.31-13.43 Candidate: 2.6.31-13.43 Version table: *** 2.6.31-13.43 0 500 http://br.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andre 21242 F pulseaudio andre 21244 F kmix CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 21' Mixer name : 'SigmaTel STAC9228' Components : 'HDA:14f12c06,14f1000f,0010 HDA:10951392,10280242,0010 HDA:83847616,10280242,00100402' Controls : 33 Simple ctrls : 20 Date: Sat Oct 10 13:08:30 2009 DistroRelease: Ubuntu 9.10 Failure: oops HibernationDevice: RESUME=UUID=5c911086-b42e-4b82-8ae7-98f9a565b1d9 MachineType: Dell Inc. Inspiron 1525 NonfreeKernelModules: wl Package: linux-image-2.6.31-13-generic 2.6.31-13.43 ProcCmdLine: root=UUID=0c1b8172-52a0-4bc5-91f4-98e6569c6ed3 ro splash ProcVersionSignature: Ubuntu 2.6.31-13.43-generic RelatedPackageVersions: linux-firmware 1.21 RfKill: 0: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux Tags: kernel-oops Title: BUG: scheduling while atomic: swapper/0/0x1001 Uname: Linux 2.6.31-13-generic i686 WpaSupplicantLog: dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0D109D dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0D109D:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/448332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
Steve Langasek, such a bug has been reported (Bug #1501884) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: New Status in update-notifier package in Ubuntu: New Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463120] Re: Failure to boot if fstab disk mounts fail
In the absence of a fix, would some be gracious enough to let me know of a workaround? I just rebooted a remote server (14.04) and am staring at "ssh... Connection Refused". I suspect it has to do with fstab since I just edited it to mount a USB drive. I can provide more details (if needed) once I drive over and connect directly *stare*. 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/1463120 Title: Failure to boot if fstab disk mounts fail Status in linux package in Ubuntu: Confirmed Bug description: I found this on my main 15.04 desktop but have reproduced it in a VM: 1. Install Ubuntu 15.04 (I included updates and non-free but I doubt that matters). 2. Add a bogus entry to /etc/fstab, eg: /dev/sdd1 /mnt/sdd1 ext4 errors=remount-ro 0 0 Note that /mnd/sdd1 exists but /dev/sdd1 does not 3. Reboot Expected: Failure to mount /dev/sdd1 reported and option to boot without mounting it Actual: System appears to hang, although it will eventually present a root terminal (with no indication of the cause of the problem). It appears to hang prior to switching graphical mode, with the result that any warnings/errors that are present on all boots but invisible because the screen clears before they're seen become visible for the first time incorrectly suggesting they are the cause of the problem. Removing (or commenting out) the problematic entries and rebooting allows the system to boot. HOWEVER: The grub boot menu now appears and any pre-existing menu timeout and default action seems to have been lost; it's now necessary to select a boot option on each boot. This may be a separate bug (or feature?). My actual case: I have external drives permanently connected via USB, however the USB card appears to have failed hence the drives are not accessible. With no clues (and being unfamiliar to systemd) working out why the system wouldn't boot was a tough job. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1382 F pulseaudio DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=76b7b79b-0cdd-4605-bc58-381fad8fa67f InstallationDate: Installed on 2015-06-08 (4 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=53f2fcea-e84c-4736-ac69-f34305a63432 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 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-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 RfKill: Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690586] 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/1690586 Title: Kernel v4.8.0: Black screen and automatic shutdown Status in linux package in Ubuntu: Confirmed Bug description: When using the kernel version 4.8.0, at some unpredictable time after boot, the screen goes black, the compute fan starts working at top speed, and after a couple seconds the computer shuts down (probably due to overheating). This does not happen with the mainline kernel version 3.19.8, but it does also happen with the mainline kernel version 4.10.0. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-51-generic 4.8.0-51.54 ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jakob 1713 F pulseaudio CurrentDesktop: KDE Date: Sat May 13 14:21:58 2017 InstallationDate: Installed on 2017-03-01 (73 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic root=UUID=824f0ac8-4d2b-416d-85c3-40c13ee483ee ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-51-generic N/A linux-backports-modules-4.8.0-51-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.60 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.35 dmi.chassis.asset.tag: CZC04543TK dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.60:bd11/11/2015:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690586] [NEW] Kernel v4.8.0: Black screen and automatic shutdown
Public bug reported: When using the kernel version 4.8.0, at some unpredictable time after boot, the screen goes black, the compute fan starts working at top speed, and after a couple seconds the computer shuts down (probably due to overheating). This does not happen with the mainline kernel version 3.19.8, but it does also happen with the mainline kernel version 4.10.0. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-51-generic 4.8.0-51.54 ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jakob 1713 F pulseaudio CurrentDesktop: KDE Date: Sat May 13 14:21:58 2017 InstallationDate: Installed on 2017-03-01 (73 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic root=UUID=824f0ac8-4d2b-416d-85c3-40c13ee483ee ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-51-generic N/A linux-backports-modules-4.8.0-51-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.60 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.35 dmi.chassis.asset.tag: CZC04543TK dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.60:bd11/11/2015:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690586 Title: Kernel v4.8.0: Black screen and automatic shutdown Status in linux package in Ubuntu: Confirmed Bug description: When using the kernel version 4.8.0, at some unpredictable time after boot, the screen goes black, the compute fan starts working at top speed, and after a couple seconds the computer shuts down (probably due to overheating). This does not happen with the mainline kernel version 3.19.8, but it does also happen with the mainline kernel version 4.10.0. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-51-generic 4.8.0-51.54 ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jakob 1713 F pulseaudio CurrentDesktop: KDE Date: Sat May 13 14:21:58 2017 InstallationDate: Installed on 2017-03-01 (73 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic root=UUID=824f0ac8-4d2b-416d-85c3-40c13ee483ee ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-51-generic N/A linux-backports-modules-4.8.0-51-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.60 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.35 dmi.chassis.asset.tag: CZC04543TK dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.60:bd11/11/2015:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 528222] ☑that's so exciting
*** This bug is a duplicate of bug 607617 *** https://bugs.launchpad.net/bugs/607617 Hey, I've got something exciting for you, you'll definitely love it, take a look http://citationtype.rachelroybal.com c.arcella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/528222 Title: package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu2 failed to install/upgrade: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: I am getting same error if i install b43-fwcutter in order to enable wifi in Dell E1505. ProblemType: Package Architecture: i386 Date: Thu Feb 25 22:58:48 2010 DistroRelease: Ubuntu 10.04 ErrorMessage: bcmwl kernel module failed to build InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1) Package: bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu2 PackageVersion: 5.60.48.36+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-14.20-generic SourcePackage: bcmwl Title: package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu2 failed to install/upgrade: bcmwl kernel module failed to build Uname: Linux 2.6.32-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/528222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Hi guys, i think we should do something about this gigabyte-situation, kinda of writing then a bunch of letters from all of us, there is also a bunch of ppl on reddit having this same problem, and still, gigabyte is not giving a breath to address this situation... do we really have to accept this kinda answers "we do not support linux, see by yourself what u do"... i think we should make us ourselves to a big voice of this thing, so that gigabyte stop threating our problem like nothing they have to do with... any suggestions? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1689390] Re: Kernel 4.11 update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dkms (Ubuntu) Status: New => Confirmed -- 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/1689390 Title: Kernel 4.11 update Status in dkms package in Ubuntu: Confirmed Bug description: I was trying to update my Ubuntu 16.04 with the last kernel version. My current version is uname -r 4.8.8-040808-generic And I would like to update the kernel to the new 4.11. I downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/ the files linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb to a folder, there I executed the first one without errors, but on the second one I have a problem. This is the log generated on the installation... root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dpkg -i linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb Seleccionando el paquete linux-headers-4.11.0-041100 previamente no seleccionado. (Leyendo la base de datos ... 389575 ficheros o directorios instalados actualmente.) Preparando para desempaquetar linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb ... Desempaquetando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ... Configurando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ... root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dpkg -i linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb Seleccionando el paquete linux-headers-4.11.0-041100-generic previamente no seleccionado. (Leyendo la base de datos ... 407178 ficheros o directorios instalados actualmente.) Preparando para desempaquetar linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb ... Desempaquetando linux-headers-4.11.0-041100-generic (4.11.0-041100.201705041534) ... Configurando linux-headers-4.11.0-041100-generic (4.11.0-041100.201705041534) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 4.11.0-041100-generic /boot/vmlinuz-4.11.0-041100-generic ERROR (dkms apport): kernel package linux-headers-4.11.0-041100-generic is not supported Error! Bad return status for module build on kernel: 4.11.0-041100-generic (x86_64) Consult /var/lib/dkms/nvidia-304/304.135/build/make.log for more information. I have attached the make.log file. How could I make the update? Thank you very much in advance Kind regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1689390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1689390] Re: Kernel 4.11 update
DKMS make.log for spl-0.6.5.9 for kernel 4.11.0-041100-generic (x86_64) Sun 14 May 03:28:51 AEST 2017 make: *** No targets specified and no makefile found. Stop. -- 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/1689390 Title: Kernel 4.11 update Status in dkms package in Ubuntu: New Bug description: I was trying to update my Ubuntu 16.04 with the last kernel version. My current version is uname -r 4.8.8-040808-generic And I would like to update the kernel to the new 4.11. I downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/ the files linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb to a folder, there I executed the first one without errors, but on the second one I have a problem. This is the log generated on the installation... root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dpkg -i linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb Seleccionando el paquete linux-headers-4.11.0-041100 previamente no seleccionado. (Leyendo la base de datos ... 389575 ficheros o directorios instalados actualmente.) Preparando para desempaquetar linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb ... Desempaquetando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ... Configurando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ... root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dpkg -i linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb Seleccionando el paquete linux-headers-4.11.0-041100-generic previamente no seleccionado. (Leyendo la base de datos ... 407178 ficheros o directorios instalados actualmente.) Preparando para desempaquetar linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb ... Desempaquetando linux-headers-4.11.0-041100-generic (4.11.0-041100.201705041534) ... Configurando linux-headers-4.11.0-041100-generic (4.11.0-041100.201705041534) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 4.11.0-041100-generic /boot/vmlinuz-4.11.0-041100-generic ERROR (dkms apport): kernel package linux-headers-4.11.0-041100-generic is not supported Error! Bad return status for module build on kernel: 4.11.0-041100-generic (x86_64) Consult /var/lib/dkms/nvidia-304/304.135/build/make.log for more information. I have attached the make.log file. How could I make the update? Thank you very much in advance Kind regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1689390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1689390] Re: Kernel 4.11 update
Distribution: Ubuntu 17.04 System architecture: amd64 Running kernel: 4.10.12-041012-generic Kernel version: 4.10.12-041012-generic Using cache directory: /home/aio/.cache/ukuu Found installed: 4.6.7-040607.201608160432 Found installed: 4.9.0-040900.201612111631 Found installed: 4.8.17-040817.201701090438 Found installed: 1.0.amdgpu Found installed: 4.10.6-041006.201703260832 Found installed: 4.8.7-040807.201611101131 Found installed: 4.7.3-040703.201609070334 Found installed: 4.2.8-040208.201512150620 Found installed: 4.10.0.21.23 Found installed: 4.10.0-20.22 Found installed: 4.10.12-041012.201704210512 Found installed: 4.10.0-21.23 Found installed: 4.7.2-040702.201608201334 Found installed: 4.10.8-041008.201703310531 Downloading: 'linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb'... aria2c version: 1.30.0 OK Downloading: 'linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb'... 48.6 MB / 50.1 MB, 850.9 KB/s (1s) (ukuu:8557): GLib-GIO-CRITICAL **: g_output_stream_close: assertion 'G_IS_OUTPUT_STREAM (stream)' failed (ukuu:8557): GLib-GIO-CRITICAL **: g_output_stream_clear_pending: assertion 'G_IS_OUTPUT_STREAM (stream)' failed OK Downloading: 'linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb'... E: Error removing file /tmp/ukuu/r0Bjkbx6/vYRr1oZC/linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb: No such file or directory E: Failed to move file: '/tmp/ukuu/r0Bjkbx6/vYRr1oZC/linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb' → '/home/aio/.cache/ukuu/v4.11/amd64/linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb' OK Preparing to install 'v4.11' Selecting previously unselected package linux-headers-4.11.0-041100-generic. (Reading database ... 800276 files and directories currently installed.) Preparing to unpack linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb ... Unpacking linux-headers-4.11.0-041100-generic (4.11.0-041100.201705041534) ... Selecting previously unselected package linux-image-4.11.0-041100-generic. Preparing to unpack linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb ... Examining /etc/kernel/preinst.d/ Done. Unpacking linux-image-4.11.0-041100-generic (4.11.0-041100.201705041534) ... Selecting previously unselected package linux-headers-4.11.0-041100. Preparing to unpack linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb ... Unpacking linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ... Setting up linux-image-4.11.0-041100-generic (4.11.0-041100.201705041534) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.11.0-041100-generic /boot/vmlinuz-4.11.0-041100-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.11.0-041100-generic /boot/vmlinuz-4.11.0-041100-generic configure: error: unknown ERROR (dkms apport): kernel package linux-headers-4.11.0-041100-generic is not supported Error! Bad return status for module build on kernel: 4.11.0-041100-generic (x86_64) Consult /var/lib/dkms/spl/0.6.5.9/build/make.log for more information. -- 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/1689390 Title: Kernel 4.11 update Status in dkms package in Ubuntu: New Bug description: I was trying to update my Ubuntu 16.04 with the last kernel version. My current version is uname -r 4.8.8-040808-generic And I would like to update the kernel to the new 4.11. I downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/ the files linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb to a folder, there I executed the first one without errors, but on the second one I have a problem. This is the log generated on the installation... root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dpkg -i linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb Seleccionando el paquete linux-headers-4.11.0-041100 previamente no seleccionado. (Leyendo la base de datos ... 389575 ficheros o directorios instalados actualmente.) Preparando para desempaquetar linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb ... Desempaquetando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ... Configurando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ... root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dp
[Kernel-packages] [Bug 1183690] Re: dkms only using one core for compiling
Fixed in 2.2.0.3-4 and above from Debian https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=663114 Unfortunately, looks like only older versions are available in Ubuntu until Zesty. ** Bug watch added: Debian Bug tracker #663114 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663114 -- 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/1183690 Title: dkms only using one core for compiling Status in dkms package in Ubuntu: Confirmed Bug description: I've set my CONCURRENCY_LEVEL variable to 8 to use all CPU cores of the i7. This works fine when compiling programs from the command line. But whenever dkms needs to compile something, like e.g. the vboxdrv, it only uses one single core (can be seen with htop) and thus takes a lot longer. This is on Ubuntu 13.04 with dkms 2.2.0.3-1.1ubuntu2. I also noticed this on Quantal with older dkms versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1183690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1183690] Re: dkms only using one core for compiling
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dkms (Ubuntu) Status: New => Confirmed -- 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/1183690 Title: dkms only using one core for compiling Status in dkms package in Ubuntu: Confirmed Bug description: I've set my CONCURRENCY_LEVEL variable to 8 to use all CPU cores of the i7. This works fine when compiling programs from the command line. But whenever dkms needs to compile something, like e.g. the vboxdrv, it only uses one single core (can be seen with htop) and thus takes a lot longer. This is on Ubuntu 13.04 with dkms 2.2.0.3-1.1ubuntu2. I also noticed this on Quantal with older dkms versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1183690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1688478] Re: USB drive not recognize (intermittent detection)
Just noticed something, when I try to unmount a get a message that this device was mounted for another user and I have to enter my admin password to unmount ??? There is only one (1) user in my config. Le 2017-05-12 à 13:47, Joseph Salisbury a écrit : > Does this issue go away if you boot back into the prior kernel version? > > ** Changed in: linux (Ubuntu) > Importance: Undecided => High > > ** Tags added: kernel-da-key > -- ** Attachment added: "courriel.jpeg" https://bugs.launchpad.net/bugs/1688478/+attachment/4876229/+files/courriel.jpeg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1688478 Title: USB drive not recognize (intermittent detection) Status in linux package in Ubuntu: Incomplete Bug description: Since I updated to kernel 4.10.0.20 I have a problem when inserting a usb key, the system play the insertion sound but the drive (key) does'nt appear in the file manager or the desktop. I use the same usb key on 3 different OS and it works flawlessly. Linux mint 18.1 Kernel 4.10.0.20 Asus A88XM-A --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: teletech 1846 F pulseaudio /dev/snd/pcmC1D0p: teletech 1846 F...m pulseaudio /dev/snd/controlC1: teletech 1846 F pulseaudio /dev/snd/controlC0: teletech 1846 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.1 HibernationDevice: RESUME=UUID=337f9bba-738a-4925-bfa3-26d8a9d3e4ee InstallationDate: Installed on 2016-09-04 (242 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-20.22~16.04.1-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.157.8 RfKill: Tags: serena Uname: Linux 4.10.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690569] 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/1690569 Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Automatically filed report (Ubuntu GNOME 17.04 Zesty Zapus) ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1023 F pulseaudio sahekyto 1400 F pulseaudio Date: Sat May 13 19:35:38 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-13 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c4f:0048 SiGma Micro Bus 001 Device 003: ID 5986: Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Lemur ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=ed0bafa6-440e-491a-8285-41a4db80695e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: Lemur dmi.board.vendor: System76 dmi.board.version: lemu7 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/17/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A: dmi.product.name: Lemur dmi.product.version: lemu7 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1688478] Re: USB drive not recognize (intermittent detection)
Hello, I installed kernel 4.4.0.53 and booted back into this kernel and the problem is still present. I then tried to install kernel 4.11 but I get a message dependencies not satisfied and cannot proceed. Have a nice day ! Fernand Le 2017-05-12 à 13:47, Joseph Salisbury a écrit : > Does this issue go away if you boot back into the prior kernel version? > > ** Changed in: linux (Ubuntu) > Importance: Undecided => High > > ** Tags added: kernel-da-key > -- ** Attachment added: "courriel.jpeg" https://bugs.launchpad.net/bugs/1688478/+attachment/4876228/+files/courriel.jpeg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1688478 Title: USB drive not recognize (intermittent detection) Status in linux package in Ubuntu: Incomplete Bug description: Since I updated to kernel 4.10.0.20 I have a problem when inserting a usb key, the system play the insertion sound but the drive (key) does'nt appear in the file manager or the desktop. I use the same usb key on 3 different OS and it works flawlessly. Linux mint 18.1 Kernel 4.10.0.20 Asus A88XM-A --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: teletech 1846 F pulseaudio /dev/snd/pcmC1D0p: teletech 1846 F...m pulseaudio /dev/snd/controlC1: teletech 1846 F pulseaudio /dev/snd/controlC0: teletech 1846 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.1 HibernationDevice: RESUME=UUID=337f9bba-738a-4925-bfa3-26d8a9d3e4ee InstallationDate: Installed on 2016-09-04 (242 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-20.22~16.04.1-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.157.8 RfKill: Tags: serena Uname: Linux 4.10.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690569] Re: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690569 Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: Automatically filed report (Ubuntu GNOME 17.04 Zesty Zapus) ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1023 F pulseaudio sahekyto 1400 F pulseaudio Date: Sat May 13 19:35:38 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-13 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c4f:0048 SiGma Micro Bus 001 Device 003: ID 5986: Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Lemur ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=ed0bafa6-440e-491a-8285-41a4db80695e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: Lemur dmi.board.vendor: System76 dmi.board.version: lemu7 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/17/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A: dmi.product.name: Lemur dmi.product.version: lemu7 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690569] [NEW] package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: Automatically filed report (Ubuntu GNOME 17.04 Zesty Zapus) ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1023 F pulseaudio sahekyto 1400 F pulseaudio Date: Sat May 13 19:35:38 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-13 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c4f:0048 SiGma Micro Bus 001 Device 003: ID 5986: Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Lemur ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=ed0bafa6-440e-491a-8285-41a4db80695e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: Lemur dmi.board.vendor: System76 dmi.board.version: lemu7 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/17/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A: dmi.product.name: Lemur dmi.product.version: lemu7 dmi.sys.vendor: System76 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690569 Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: Automatically filed report (Ubuntu GNOME 17.04 Zesty Zapus) ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1023 F pulseaudio sahekyto 1400 F pulseaudio Date: Sat May 13 19:35:38 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-13 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c4f:0048 SiGma Micro Bus 001 Device 003: ID 5986: Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Lemur ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=ed0bafa6-440e-491a-8285-41a4db80695e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: Lemur dmi.board.vendor: System76 dmi.board.version: lemu7 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/17/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A: dmi.product.name: Lemur dmi.product.version: lemu7 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux
[Kernel-packages] [Bug 1683184] Re: GPU problems on HP 15-ba009ng
thanks! ** Also affects: linux via https://bugs.freedesktop.org/show_bug.cgi?id=101029 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683184 Title: GPU problems on HP 15-ba009ng Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Problem description: The notebook does not work when not booted using nomodeset: It is not possible to login - after logging in the login screen shows up (sometimes the computer also shuts down, or shows information similiar to the shutdown screen (not using quiet splash boot options, so it is white text on black background)), until the login screen shows up again, only the background image is shown. When using an USB stick, plymouth hangs after some time. When using a text console to login instead of a graphical session, one can login, but sees how the console gets spammed with the following lines repeating itself frequently: [ XXX.XX] AMD-Vi: Event logged [ (usually once) [ XXX.XX] AMD-Vi: Completion-Wait loop timed out (usually twice) When using nomodeset, things work fine, but I only get software rendering (I do not intend using the notebook as a loud heating). During startup I found the following, potentially related messages: (...) [0.718421] ACPI Error: Method parse/execution failes [\_SB.WLBU._STA] (Node 94cad68b6b68), AE_NOT_FOUND (20160930/psparse-543) [6.291431] amd_gpio AMD0030:00: Failed to get gpio IRQ. (plymouth started showing some boot screen) And, during a different startup (please note this is transcribed from an older photo, Ubuntu version can be an early version of zesty, but also might be yakkety): (...) [ 12.950688] amdgpu :05:00.0:fence driver on ring 10 use gpu addr 0x000100b0, cpu addr 0x8a4fcb63d0b0 [ 12.954029] can't get the mac of 5 [ 12.960416] [drm] ring test on 0 succeeded in 16 usecs (other ring tests, until:) [ 12.966726] [drm] ring test on 10 succeeded in 6 usecs [ 12.967789] [drm] ib test on ring 0 succeeded (other ib test, until:) [ 12.985277] [drm] ib test on ring 10 succeeded [ 12.985277] [drm] Initialized amdgpu 3.9.0 20150101 for :05:00.0 on minor 1 Begin: Loading essential drivers ... done. (...) Ubuntu version: Ubuntu 17.04 (16.04 had less problems, with 16.10 installation failed) Hardware: Notebook: HP 15-ba009ng CPU: AMD A10-9600P GPU: AMD Radeon R7 M440 4 GB DDR3-RAM (according to the web page of the vendor) xorg version: 1:7.7+16ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.4-0ubuntu4 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:Unity7 Date: Sun Apr 16 22:24:26 2017 DistUpgraded: 2017-03-11 13:02:33,428 DEBUG apt btrfs snapshots supported: True DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:81fa] Subsystem: Hewlett-Packard Company Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] [103c:81fa] InstallationDate: Installed on 2016-12-25 (112 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=af212aa7-7cfe-4e46-a312-da2a25fb0df1 ro rootflags=subvol=@ nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-03-11 (36 days ago) dmi.bios.date: 09/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81FA dmi.board.vendor: HP dmi.board.version: 67.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.17:bd09/01/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81FA:rvr67.34:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libg
[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
May 13 04:14:41 Trouble systemd[1]: Starting Cryptography Setup for nvme0n1p3_crypt... May 13 04:14:41 Trouble systemd-cryptsetup[618]: Volume nvme0n1p3_crypt already active. May 13 04:14:41 Trouble systemd[1]: Started Cryptography Setup for nvme0n1p3_crypt. May 13 04:14:41 Trouble systemd-fsck[682]: /dev/nvme0n1p2: clean, 321/124928 files, 169069/499712 blocks May 13 04:14:41 Trouble systemd-fsck[686]: /dev/nvme0n1p1: 16 files, 5393/130812 clusters May 13 04:14:41 Trouble systemd[1]: Found device /dev/mapper/nvme0n1p3_crypt. May 13 04:14:41 Trouble kernel: [1.320827] nvme :04:00.0: Samsung/Dell NVMe quirk is being ignored -- please report your results May 13 04:14:41 Trouble kernel: [1.320866] nvme nvme0: pci function :04:00.0 May 13 04:14:41 Trouble kernel: [1.430158] nvme nvme0: APST enabled: max PS = 4, max round-trip latency = 24000us, table = 18130100181301001813010020f05500 May 13 04:14:41 Trouble kernel: [1.448104] nvme0n1: p1 p2 p3 May 13 04:14:41 Trouble kernel: [ 12.893967] EXT4-fs (nvme0n1p2): mounting ext2 file system using the ext4 subsystem May 13 04:14:41 Trouble kernel: [ 12.900921] EXT4-fs (nvme0n1p2): mounted filesystem without journal. Opts: (null) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: APST support just landed in the latest Zesty kernel (4.10.0-14.16) as part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602. That patch has a quirk for certain 256GB Samsung drives found in Dell laptops that do not behave well when APST is enabled. I am experiencing the same symptoms with the same model laptop except with a 512GB Samsung. Prior to manually disabling APST the drive would die and system would go down in flames with I/O errors within 20 to 40 minutes of boot. $ sudo nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 ** PM951 NVMe SAMSUNG 512GB 1 500.20 GB / 512.11 GB512 B + 0 B BXV76D0Q ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ajclayton 3305 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri Mar 31 09:42:38 2017 InstallationDate: Installed on 2012-09-08 (1665 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt nouveau.modeset=0 log_buf_len=20M RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
@jdrewes: just for completeness, can you post the nvme-related log messages from the beginning of that boot? I want to verify that I programmed the controller the way I meant to. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: APST support just landed in the latest Zesty kernel (4.10.0-14.16) as part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602. That patch has a quirk for certain 256GB Samsung drives found in Dell laptops that do not behave well when APST is enabled. I am experiencing the same symptoms with the same model laptop except with a 512GB Samsung. Prior to manually disabling APST the drive would die and system would go down in flames with I/O errors within 20 to 40 minutes of boot. $ sudo nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 ** PM951 NVMe SAMSUNG 512GB 1 500.20 GB / 512.11 GB512 B + 0 B BXV76D0Q ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ajclayton 3305 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri Mar 31 09:42:38 2017 InstallationDate: Installed on 2012-09-08 (1665 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt nouveau.modeset=0 log_buf_len=20M RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1424293] Re: BYD trackpad detected as PS/2 mouse
Hi! Automatic detection of BYD touchpads was sadly disabled at the end of last year. They can be still be used by forcing the protocol manually as described by Kai-Heng Feng above. The reason for disabling detection was that the detection code generated false positives with normal PS/2 mice (meaning that some people's normal mice didn't work, because they were detected as BYD touchpads instead). This obviously isn't good. I investigated using DMI data to restrict probing to only machines which have that touchpad. However, the values were too generic - see https://patchwork.kernel.org/patch/9423801/ The patch disabling probing is here: https://patchwork.kernel.org/patch/9424421/ Potential solutions are: - Persuade OEMs shipping these touchpads to provide sensible DMI values - Experiment with the driver to see if the touchpad will identify itself reliably *in a way which can't be interpreted as normal PS/2 commands by a PS/2 mouse*. Regards, Chris -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1424293 Title: BYD trackpad detected as PS/2 mouse Status in linux package in Ubuntu: Triaged Bug description: In 14.04.2, I expected to be able to use as touchpad with two finger vertical/horizontal scrolling. Currently only able to use plainly. The exact device is this: http://bydit.com/doce/products/microelectronics/2474.html I: Bus=0011 Vendor=0002 Product=0005 Version= N: Name="ImPS/2 Generic Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input7 U: Uniq= H: Handlers=mouse0 event10 B: PROP=0 B: EV=7 B: KEY=7 0 0 0 0 B: REL=103 Output of xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ USB 2.0 Camera id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=11 [slave keyboard (3)] --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vjftw 1362 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=d58116d7-f5eb-4b3c-b986-a9a29b608880 InstallationDate: Installed on 2015-04-25 (28 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 058f:3821 Alcor Micro Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation SharkBay Platform Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed root=UUID=cd943b28-f170-4ce9-b836-18c395f1df6d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: Fab2 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd02/03/2015:svnIntelCorporation:pnSharkBayPlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrFab2:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.: dmi.product.name: SharkBay Platform dmi.product.version: 0.1 dmi.sys.vendo
[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
Another update: after running well for a few days, I have now encountered this bug (first time for me). After the bug hit, the NVMe drive disappeared, and only a hard reset solved the problem (I lost some work...). May 13 10:42:59 Trouble kernel: [23310.930585] nvme :04:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x May 13 10:42:59 Trouble kernel: [23310.944569] nvme :04:00.0: enabling device ( -> 0002) May 13 10:42:59 Trouble kernel: [23310.944626] nvme nvme0: Removing after probe failure status: -19 May 13 10:42:59 Trouble kernel: [23310.944634] nvme0n1: detected capacity change from 512110190592 to 0 May 13 10:42:59 Trouble kernel: [23310.944918] blk_update_request: I/O error, dev nvme0n1, sector 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: APST support just landed in the latest Zesty kernel (4.10.0-14.16) as part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602. That patch has a quirk for certain 256GB Samsung drives found in Dell laptops that do not behave well when APST is enabled. I am experiencing the same symptoms with the same model laptop except with a 512GB Samsung. Prior to manually disabling APST the drive would die and system would go down in flames with I/O errors within 20 to 40 minutes of boot. $ sudo nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 ** PM951 NVMe SAMSUNG 512GB 1 500.20 GB / 512.11 GB512 B + 0 B BXV76D0Q ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ajclayton 3305 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri Mar 31 09:42:38 2017 InstallationDate: Installed on 2012-09-08 (1665 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt nouveau.modeset=0 log_buf_len=20M RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1424293] Re: BYD trackpad detected as PS/2 mouse
What detection was disabled and what was the good reason? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1424293 Title: BYD trackpad detected as PS/2 mouse Status in linux package in Ubuntu: Triaged Bug description: In 14.04.2, I expected to be able to use as touchpad with two finger vertical/horizontal scrolling. Currently only able to use plainly. The exact device is this: http://bydit.com/doce/products/microelectronics/2474.html I: Bus=0011 Vendor=0002 Product=0005 Version= N: Name="ImPS/2 Generic Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input7 U: Uniq= H: Handlers=mouse0 event10 B: PROP=0 B: EV=7 B: KEY=7 0 0 0 0 B: REL=103 Output of xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ USB 2.0 Camera id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=11 [slave keyboard (3)] --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vjftw 1362 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=d58116d7-f5eb-4b3c-b986-a9a29b608880 InstallationDate: Installed on 2015-04-25 (28 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 058f:3821 Alcor Micro Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation SharkBay Platform Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed root=UUID=cd943b28-f170-4ce9-b836-18c395f1df6d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: Fab2 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd02/03/2015:svnIntelCorporation:pnSharkBayPlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrFab2:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.: dmi.product.name: SharkBay Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1424293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683184] Re: GPU problems on HP 15-ba009ng
added in the following link: https://bugs.freedesktop.org/show_bug.cgi?id=101029 Bug #101029 ** Bug watch added: freedesktop.org Bugzilla #101029 https://bugs.freedesktop.org/show_bug.cgi?id=101029 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683184 Title: GPU problems on HP 15-ba009ng Status in linux package in Ubuntu: Triaged Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Problem description: The notebook does not work when not booted using nomodeset: It is not possible to login - after logging in the login screen shows up (sometimes the computer also shuts down, or shows information similiar to the shutdown screen (not using quiet splash boot options, so it is white text on black background)), until the login screen shows up again, only the background image is shown. When using an USB stick, plymouth hangs after some time. When using a text console to login instead of a graphical session, one can login, but sees how the console gets spammed with the following lines repeating itself frequently: [ XXX.XX] AMD-Vi: Event logged [ (usually once) [ XXX.XX] AMD-Vi: Completion-Wait loop timed out (usually twice) When using nomodeset, things work fine, but I only get software rendering (I do not intend using the notebook as a loud heating). During startup I found the following, potentially related messages: (...) [0.718421] ACPI Error: Method parse/execution failes [\_SB.WLBU._STA] (Node 94cad68b6b68), AE_NOT_FOUND (20160930/psparse-543) [6.291431] amd_gpio AMD0030:00: Failed to get gpio IRQ. (plymouth started showing some boot screen) And, during a different startup (please note this is transcribed from an older photo, Ubuntu version can be an early version of zesty, but also might be yakkety): (...) [ 12.950688] amdgpu :05:00.0:fence driver on ring 10 use gpu addr 0x000100b0, cpu addr 0x8a4fcb63d0b0 [ 12.954029] can't get the mac of 5 [ 12.960416] [drm] ring test on 0 succeeded in 16 usecs (other ring tests, until:) [ 12.966726] [drm] ring test on 10 succeeded in 6 usecs [ 12.967789] [drm] ib test on ring 0 succeeded (other ib test, until:) [ 12.985277] [drm] ib test on ring 10 succeeded [ 12.985277] [drm] Initialized amdgpu 3.9.0 20150101 for :05:00.0 on minor 1 Begin: Loading essential drivers ... done. (...) Ubuntu version: Ubuntu 17.04 (16.04 had less problems, with 16.10 installation failed) Hardware: Notebook: HP 15-ba009ng CPU: AMD A10-9600P GPU: AMD Radeon R7 M440 4 GB DDR3-RAM (according to the web page of the vendor) xorg version: 1:7.7+16ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.4-0ubuntu4 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:Unity7 Date: Sun Apr 16 22:24:26 2017 DistUpgraded: 2017-03-11 13:02:33,428 DEBUG apt btrfs snapshots supported: True DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:81fa] Subsystem: Hewlett-Packard Company Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] [103c:81fa] InstallationDate: Installed on 2016-12-25 (112 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=af212aa7-7cfe-4e46-a312-da2a25fb0df1 ro rootflags=subvol=@ nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-03-11 (36 days ago) dmi.bios.date: 09/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81FA dmi.board.vendor: HP dmi.board.version: 67.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.17:bd09/01/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81FA:rvr67.34:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-me