[Kernel-packages] [Bug 1770845] [NEW] Make vfio-pci built-in or xhci_hcd optional
Public bug reported:
Because of
nazar-pc@nazar-pc ~> cat '/boot/config-4.15.0-21-generic' | grep
CONFIG_USB_XHCI_HCD
CONFIG_USB_XHCI_HCD=y
Following doesn't work:
nazar-pc@nazar-pc ~> cat /etc/modprobe.d/gpu-passthrough.conf
options vfio-pci ids=10de:1b06,10de:10ef,1b21:2142
softdep nouveau pre: vfio-pci
softdep xhci_hcd pre: vfio-pci
GPU is fine (first 2 IDs), but USB controller is always occupied by
xhci_hcd and I can't change that while xhci_hcd is built-in.
I'd like you to resolve this issue by either embedding vfio-pci module
too (prefered solution) or making xhci_hcd optional.
There are some discussions withot clean solution online like this:
https://www.reddit.com/r/VFIO/comments/4o6wla/cant_get_vfiopci_to_bind_to_usb_30_card_at_boot/
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.15.0-21-generic 4.15.0-21.22
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-21-generic.
ApportVersion: 2.20.10-0ubuntu2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: S51 [SB Omni Surround 5.1], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0c: nazar-pc 2226 F...m pulseaudio
/dev/snd/pcmC1D0p: nazar-pc 2226 F...m pulseaudio
/dev/snd/controlC1: nazar-pc 2226 F pulseaudio
nazar-pc 2267 F volumeicon
Card1.Amixer.info:
Card hw:1 'S51'/'Creative Technology Ltd SB Omni Surround 5.1 at
usb-:00:14.0-9.2, full spee'
Mixer name : 'USB Mixer'
Components : 'USB041e:322c'
Controls : 12
Simple ctrls : 5
CurrentDesktop: Custom
Date: Sat May 12 16:44:11 2018
IwConfig: Error: [Errno 2] Немає такого файла або каталогу: 'iwconfig':
'iwconfig'
MachineType: Micro-Star International Co., Ltd. MS-7B45
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/root/boot/vmlinuz-4.15.0-21-generic
root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root
nosplash intel_pstate=disable scsi_mod.use_blk_mq=1 intel_iommu=on
RelatedPackageVersions:
linux-restricted-modules-4.15.0-21-generic N/A
linux-backports-modules-4.15.0-21-generic N/A
linux-firmware 1.173
RfKill: Error: [Errno 2] Немає такого файла або каталогу: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.51
dmi.board.asset.tag: Default string
dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrA.51:bd03/29/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
dmi.product.family: Default string
dmi.product.name: MS-7B45
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug cosmic package-from-proposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770845
Title:
Make vfio-pci built-in or xhci_hcd optional
Status in linux package in Ubuntu:
Confirmed
Bug description:
Because of
nazar-pc@nazar-pc ~> cat '/boot/config-4.15.0-21-generic' | grep
CONFIG_USB_XHCI_HCD
CONFIG_USB_XHCI_HCD=y
Following doesn't work:
nazar-pc@nazar-pc ~> cat /etc/modprobe.d/gpu-passthrough.conf
options vfio-pci ids=10de:1b06,10de:10ef,1b21:2142
softdep nouveau pre: vfio-pci
softdep xhci_hcd pre: vfio-pci
GPU is fine (first 2 IDs), but USB controller is always occupied by
xhci_hcd and I can't change that while xhci_hcd is built-in.
I'd like you to resolve this issue by either embedding vfio-pci module
too (prefered solution) or making xhci_hcd optional.
There are some discussions withot clean solution online like this:
https://www.reddit.com/r/VFIO/comments/4o6wla/cant_get_vfiopci_to_bind_to_usb_30_card_at_boot/
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.15.0-21-generic 4.15.0-21.22
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-21-generic.
ApportVersion: 2.20.10-0ubuntu2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: S51 [SB Omni Surround 5.1], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevic
[Kernel-packages] [Bug 1770849] [NEW] Ubuntu 18.04 kernel crashed while in degraded mode
Public bug reported: kernel crash The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes [ 64.713154] kexec_core: Starting new kernel [ 156.281504630,5] OPAL: Switch to big-endian OS [ 158.440263459,5] OPAL: Switch to little-endian OS [1.889211] Unable to handle kernel paging request for data at address 0x678e549df9e2878c [1.889289] Faulting instruction address: 0xc038aa30 [1.889344] Oops: Kernel access of bad area, sig: 11 [#1] [1.889386] LE SMP NR_CPUS=2048 NUMA PowerNV [1.889432] Modules linked in: [1.889468] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.15.0-20-generic #21-Ubuntu [1.889545] NIP: c038aa30 LR: c038aa1c CTR: [1.889608] REGS: c03fed193840 TRAP: 0380 Not tainted (4.15.0-20-generic) [1.889670] MSR: 90009033 CR: 28000884 XER: 2004 [1.889742] CFAR: c0016e1c SOFTE: 1 [1.889742] GPR00: c038a914 c03fed193ac0 c16eae00 0001 [1.889742] GPR04: c03fd754c7f8 002c 0001 002b [1.889742] GPR08: 678e549df9e28874 fffe [1.889742] GPR12: 28000888 cfa82100 c000d3b8 [1.889742] GPR16: [1.889742] GPR20: a78e54a22eb64f8c [1.889742] GPR24: c03fd754c800 678e549df9e2878c 0300 c02bd05c [1.889742] GPR28: c03fed01ea00 014080c0 c03fd754c800 c03fed01ea00 [1.890286] NIP [c038aa30] kmem_cache_alloc_trace+0x2d0/0x330 [1.890340] LR [c038aa1c] kmem_cache_alloc_trace+0x2bc/0x330 [1.890391] Call Trace: [1.890416] [c03fed193ac0] [c038a914] kmem_cache_alloc_trace+0x1b4/0x330 (unreliable) [1.890491] [c03fed193b30] [c02bd05c] pmu_dev_alloc+0x3c/0x170 [1.890547] [c03fed193bb0] [c10e3210] perf_event_sysfs_init+0x8c/0xf0 [1.890611] [c03fed193c40] [c000d144] do_one_initcall+0x64/0x1d0 [1.890676] [c03fed193d00] [c10b4400] kernel_init_freeable+0x280/0x374 [1.890740] [c03fed193dc0] [c000d3d4] kernel_init+0x24/0x160 [1.890795] [c03fed193e30] [c000b528] ret_from_kernel_thread+0x5c/0xb4 [1.890857] Instruction dump: [1.890909] 7c97ba78 fb210038 38a50001 7f19ba78 fb29 f8aa 4bc8c3f1 6000 [1.890978] 7fb8b840 419e0028 e93f0022 e91f0140 <7d59482a> 7d394a14 7d4a4278 7fa95040 [1.891050] ---[ end trace 41b3fe7a827f3888 ]--- [2.900027] [3.900175] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [3.900175] [4.71868[ 175.340944355,5] OPAL: Reboot request... 2] Rebooting in 10 seconds.. This fix is needed to resolve the crash https://lists.ozlabs.org/pipermail/linuxppc-dev/2018-May/172835.html ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-167482 severity-critical targetmilestone-inin1804 ** Tags added: architecture-ppc64le bugnameltc-167482 severity-critical targetmilestone-inin1804 ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770849 Title: Ubuntu 18.04 kernel crashed while in degraded mode Status in linux package in Ubuntu: New Bug description: kernel crash The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes [ 64.713154] kexec_core: Starting new kernel [ 156.281504630,5] OPAL: Switch to big-endian OS [ 158.440263459,5] OPAL: Switch to little-endian OS [1.889211] Unable to handle kernel paging request for data at address 0x678e549df9e2878c [1.889289] Faulting instruction address: 0xc038aa30 [1.889344] Oops: Kernel access of bad area, sig: 11 [#1] [1.889386] LE SMP NR_CPUS=2048 NUMA PowerNV [1.889432] Modules linked in: [1.889468] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.15.0-20-generic #21-Ubuntu [1.889545] NIP: c038aa30 LR: c038aa1c CTR: [1.889608] REGS: c03fed193840 TRAP: 0380 Not tainted (4.15.0-20-generic) [1.889670] MSR: 90009033 CR: 28000884 XER: 2004 [1.889742] CFAR: c0016e1c SOFTE: 1 [1.889742] GPR00: c038a914 c03fed193ac0 c16eae00 0001 [1.889742] GPR04: c03fd754c7f8 002c 0001 002b [1.889742] GPR08: 678
[Kernel-packages] [Bug 1770845] 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/1770845
Title:
Make vfio-pci built-in or xhci_hcd optional
Status in linux package in Ubuntu:
Confirmed
Bug description:
Because of
nazar-pc@nazar-pc ~> cat '/boot/config-4.15.0-21-generic' | grep
CONFIG_USB_XHCI_HCD
CONFIG_USB_XHCI_HCD=y
Following doesn't work:
nazar-pc@nazar-pc ~> cat /etc/modprobe.d/gpu-passthrough.conf
options vfio-pci ids=10de:1b06,10de:10ef,1b21:2142
softdep nouveau pre: vfio-pci
softdep xhci_hcd pre: vfio-pci
GPU is fine (first 2 IDs), but USB controller is always occupied by
xhci_hcd and I can't change that while xhci_hcd is built-in.
I'd like you to resolve this issue by either embedding vfio-pci module
too (prefered solution) or making xhci_hcd optional.
There are some discussions withot clean solution online like this:
https://www.reddit.com/r/VFIO/comments/4o6wla/cant_get_vfiopci_to_bind_to_usb_30_card_at_boot/
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.15.0-21-generic 4.15.0-21.22
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-21-generic.
ApportVersion: 2.20.10-0ubuntu2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: S51 [SB Omni Surround 5.1], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0c: nazar-pc 2226 F...m pulseaudio
/dev/snd/pcmC1D0p: nazar-pc 2226 F...m pulseaudio
/dev/snd/controlC1: nazar-pc 2226 F pulseaudio
nazar-pc 2267 F volumeicon
Card1.Amixer.info:
Card hw:1 'S51'/'Creative Technology Ltd SB Omni Surround 5.1 at
usb-:00:14.0-9.2, full spee'
Mixer name : 'USB Mixer'
Components : 'USB041e:322c'
Controls : 12
Simple ctrls : 5
CurrentDesktop: Custom
Date: Sat May 12 16:44:11 2018
IwConfig: Error: [Errno 2] Немає такого файла або каталогу: 'iwconfig':
'iwconfig'
MachineType: Micro-Star International Co., Ltd. MS-7B45
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/root/boot/vmlinuz-4.15.0-21-generic
root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root
nosplash intel_pstate=disable scsi_mod.use_blk_mq=1 intel_iommu=on
RelatedPackageVersions:
linux-restricted-modules-4.15.0-21-generic N/A
linux-backports-modules-4.15.0-21-generic N/A
linux-firmware 1.173
RfKill: Error: [Errno 2] Немає такого файла або каталогу: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.51
dmi.board.asset.tag: Default string
dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrA.51:bd03/29/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
dmi.product.family: Default string
dmi.product.name: MS-7B45
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770845/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1770836/+attachment/5138351/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1770836/+attachment/5138349/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1770836/+attachment/5138353/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] Re: amdgpu+xorg possibly marks displays as off while they wake from sleep
apport information ** Tags added: apport-collected bionic ** Description changed: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. - One way or the other, that's not how it used to work in older kernels - (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a - regression. + One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. + --- + ApportVersion: 2.20.9-0ubuntu7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: mmazur 2270 F pulseaudio + /dev/snd/controlC1: mmazur 2270 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 18.04 + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 + ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-20-generic N/A + linux-backports-modules-4.15.0-20-generic N/A + linux-firmware 1.173 + RfKill: + 1: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: bionic + Uname: Linux 4.15.0-20-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/29/2016 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P2.10 + dmi.board.name: Z97E-ITX/ac + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1770836/+attachment/5138346/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides th
[Kernel-packages] [Bug 1770836] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1770836/+attachment/5138350/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1770836/+attachment/5138352/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1770836/+attachment/5138347/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1770836/+attachment/5138356/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1770836/+attachment/5138357/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1770836/+attachment/5138354/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1770836/+attachment/5138355/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1770836/+attachment/5138348/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1770836/+attachment/5138358/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] Re: amdgpu+xorg possibly marks displays as off while they wake from sleep
Went with amdgpu.dc_log=1 to make the kernel more chatty. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] Re: amdgpu+xorg possibly marks displays as off while they wake from sleep
** Description changed: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. - When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display - not yet fully woken up seem to be reported as disconnected. This happens - both when waking the whole computer from sleep (systemctl suspend) or - just the displays themselves (due to me not touching mouse+keyboard for - a while). + When waking the displays from sleep with 4.15 any display not yet fully + woken up seem to be reported as disconnected. This happens both when + waking the whole computer from sleep (systemctl suspend) or just the + displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off - Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU + Video of how it should work using 4.4.15: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. - One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. - --- + One way or the other, that's not how it used to work in older kernels, so as far as I'm concerned it's a regression. + --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: mmazur 2270 F pulseaudio - /dev/snd/controlC1: mmazur 2270 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: mmazur 2270 F pulseaudio + /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: - linux-restricted-modules-4.15.0-20-generic N/A - linux-backports-modules-4.15.0-20-generic N/A - linux-firmware 1.173 + linux-restricted-modules-4.15.0-20-generic N/A + linux-backports-modules-4.15.0-20-generic N/A + linux-firmware 1.173 RfKill: - 1: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 1: hci0: Bluetooth + Soft blocked: no + Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on
[Kernel-packages] [Bug 1770836] Re: amdgpu+xorg possibly marks displays as off while they wake from sleep
** Description changed: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off - Video of how it should work using 4.4.15: https://www.youtube.com/watch?v=h7nMYbm5ZxU + Video of how it should work, using 4.4.15 (and 4.15 with amdgpu.dc=0): https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels, so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work, using 4.4.15 (and 4.15 with amdgpu.dc=0): https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right
[Kernel-packages] [Bug 1770836] Re: amdgpu+xorg possibly marks displays as off while they wake from sleep
Oh, and I did a single sleep/wake, so if there's gonna be anything in the logs regarding the displays coming back up, it'll be after 15:48:32. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1770836/+attachment/5138359/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version
Yes, the patches were reverted, then replaced with the ones you listed from next/master tree. As you noticed, they did not revert cleanly, so I had to back port and remove code that was added by newer commits. If you could create a new patch with just the diffs that would be great! I could revert all the cxlflash SAUCE patches and apply the ones from next, but that would make it more difficult to get the changes into a stable release. Changes to a stable release should be as minimal as possible. Just let me know if you are able to create a new patch with just the diffs or not. If you can not, I'll build a test kernel with a revert of all the cxlflash SAUCE patches and apply the ones from next/master. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768431 Title: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 == ---Problem Description--- Request to revert SAUCE patches from 18.04 and apply the patches from next/master. Below set of cxlflash patches were submitted to Canonical after they were sent to the community. Based on review comments, there has been minor changes from that version. This BZ is to request reverting those SAUCE patches with the ones that are queued in next/master tree for 4.18. - SAUCE: cxlflash: Preserve number of interrupts for master contexts - SAUCE: cxlflash: Avoid clobbering context control register value - SAUCE: cxlflash: Add argument identifier names - SAUCE: cxlflash: Introduce OCXL backend - SAUCE: cxlflash: Hardware AFU for OCXL - SAUCE: cxlflash: Read host function configuration - SAUCE: cxlflash: Setup function acTag range - SAUCE: cxlflash: Read host AFU configuration - SAUCE: cxlflash: Setup AFU acTag range - SAUCE: cxlflash: Setup AFU PASID - SAUCE: cxlflash: Adapter context support for OCXL - SAUCE: cxlflash: Use IDR to manage adapter contexts - SAUCE: cxlflash: Support adapter file descriptors for OCXL - SAUCE: cxlflash: Support adapter context discovery - SAUCE: cxlflash: Support image reload policy modification - SAUCE: cxlflash: MMIO map the AFU - SAUCE: cxlflash: Support starting an adapter context - SAUCE: cxlflash: Support process specific mappings - SAUCE: cxlflash: Support AFU state toggling - SAUCE: cxlflash: Support reading adapter VPD data - SAUCE: cxlflash: Setup function OCXL link - SAUCE: cxlflash: Setup OCXL transaction layer - SAUCE: cxlflash: Support process element lifecycle - SAUCE: cxlflash: Support AFU interrupt management - SAUCE: cxlflash: Support AFU interrupt mapping and registration - SAUCE: cxlflash: Support starting user contexts - SAUCE: cxlflash: Support adapter context polling - SAUCE: cxlflash: Support adapter context reading - SAUCE: cxlflash: Support adapter context mmap and release - SAUCE: cxlflash: Support file descriptor mapping - SAUCE: cxlflash: Introduce object handle fop - SAUCE: cxlflash: Setup LISNs for user contexts - SAUCE: cxlflash: Setup LISNs for master contexts - SAUCE: cxlflash: Update synchronous interrupt status bits - SAUCE: cxlflash: Introduce OCXL context state machine - SAUCE: cxlflash: Register for translation errors - SAUCE: cxlflash: Support AFU reset - SAUCE: cxlflash: Enable OCXL operations Also, there are 3 additional patches added to end of this series that we would like to request being pulled into the SRU stream. These 3 patches address bug fixes. The commit ids for the patches queued in next/master tree are, 768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of interrupts for master contexts 6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering context control register value fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument identifier names 863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL backend f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL 1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function configuration ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag range f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cxlflash: Read host AFU configuration c5a8fec11278e245136c7f696c914269c58a6000 scsi: cxlflash: Setup AFU acTag range b42d68d728a63337bcb7860b59e6458946d94a84 scsi: cxlflash: Setup AFU PASID de25ec59a75802584aac97aed05fd94094dbbb58 scsi: cxlflash: Adapter context support for OCXL a76fc993e399f54b37f46107a31e817c779f2b82 scsi: cxlflash: Use IDR to manage adapter contexts 09f35da5fe218baf73f7b4efd281e2c19490512c scsi: cxlfla
[Kernel-packages] [Bug 1770836] Re: amdgpu+xorg possibly marks displays as off while they wake from sleep
** Description changed: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off - Video of how it should work, using 4.4.15 (and 4.15 with amdgpu.dc=0): https://www.youtube.com/watch?v=h7nMYbm5ZxU + Video of how it should work, using 4.4.15: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels, so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work, using 4.4.15: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up
[Kernel-packages] [Bug 1770836] Re: amdgpu+xorg possibly marks displays as off while they wake from sleep
Looks like I'm not the only one: https://bugs.freedesktop.org/show_bug.cgi?id=104300. And, interestingly enough, running 4.15 with amdgpu.dc=0 makes this issue happen, but not 100% of the time (had it work correctly when waking computer from sleep, but have a problem when only the monitors went to sleep and the computer was on). So whatever amdgpu changes were made between 4.14 and 4.15, introduce this issue a bit even on the non- DC code path. ** Bug watch added: freedesktop.org Bugzilla #104300 https://bugs.freedesktop.org/show_bug.cgi?id=104300 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work, using 4.4.15: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels, so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 843431] Re: Logitech camera microphone does not work / makes "chipmunk" sound
Hi Kai-Heng, Yes, you are right, but the real question is why does this disappear from the latest kernel ? It was in the previous. So i suggest to that the bug need to be reopened in order for dev to merge from previous branch and have all "non stereo" webcam working again. I unfortunatly can't reopen it myself (or i don't know how to do it). Regards, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/843431 Title: Logitech camera microphone does not work / makes "chipmunk" sound Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Oneiric: Fix Released Status in linux package in Debian: New Bug description: Did not know which application to log so feel free to let me know and I'll upload the correct log. In Natty, this mic worked great. Now, in the sound control panel, the mic does not show any input level at all and sound recorder does not record any sound. edit: I can also confirm the same behavior as Alex Popovskiy. It either works but plays too fast (high pitch) or it doesn't work at all. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.91-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Sep 6 20:31:13 2011 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.22.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1594 F pulseaudio /dev/snd/controlC0: alex 1594 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xf9ef4000 irq 16' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,18490397,0010' Controls : 36 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'U0x46d0x809'/'USB Device 0x46d:0x809 at usb-:00:13.2-6, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0809' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 6400 Mono: Capture 6400 [100%] [31.00dB] [on] DistroRelease: Ubuntu 11.10 HibernationDevice: RESUME=UUID=8ccfea11-7ba8-42e2-bc75-a37e20a8c83c InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=3c8a3aec-07c0-47ad-bab8-0365abb68a42 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 RelatedPackageVersions: linux-restricted-modules-3.0.0-10-generic N/A linux-backports-modules-3.0.0-10-generic N/A linux-firmware1.60 Tags: oneiric running-unity Uname: Linux 3.0.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 09/07/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: M3A770DE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd09/07/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A770DE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/843431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770862] [NEW] ASUS GU501GM touchpad not detected
Public bug reported: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log information" https://bugs.launchpad.net/bugs/1770862/+attachment/5138419/+files/info.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: New Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireles
[Kernel-packages] [Bug 1770862] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1770862 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Incomplete Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
See also this report, where if I read it correctly they seem to have a patch. https://bbs.archlinux.org/viewtopic.php?id=235862 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764645 Title: Bluetooth not working Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I've installed the Ubuntu Bionic Beta 2 and everything works fine but the bluetooth (perfectly working with Xenial). In bluetooth control panel the slider is impossible to move to "on". 1) Ubuntu Release (via 'lsb_release -rd') Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) Version of package (apt-cache policy gnome-bluetooth) gnome-bluetooth: Installato: 3.28.0-2 Candidato: 3.28.0-2 Tabella versione: *** 3.28.0-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected to switch on the bluetooth. 4) What happened instead Bluetooth won't switch on. 5) Output of rfkill list is: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is: 03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01) Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half- size Mini PCIe Card [1a56:2003] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit Ethernet [1969:10a1] (rev 10) Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 17.715399] Bluetooth: Core ver 2.22 [ 17.715414] Bluetooth: HCI device and connection manager initialized [ 17.715416] Bluetooth: HCI socket layer initialized [ 17.715418] Bluetooth: L2CAP socket layer initialized [ 17.715422] Bluetooth: SCO socket layer initialized [ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102 [ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 18.600649] Bluetooth: BNEP filters: protocol multicast [ 18.600651] Bluetooth: BNEP socket layer initialized ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stormy 1484 F pulseaudio /dev/snd/controlC0: stormy 1484 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 08:46:30 2018 HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11 InstallationDate: Installed on 2018-04-16 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: ASUSTeK COMPUTER INC. G750JH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G750JH.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G750JH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG750JH.206:bd12/02/2013:svnASUSTeKCOMPUTERINC.:pnG750JH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG750JH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G750JH dmi.product.vers
[Kernel-packages] [Bug 1770862] Re: ASUS GU501GM touchpad not detected
apport information ** Tags added: apport-collected bionic ** Description changed: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] + --- + ApportVersion: 2.20.9-0ubuntu7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: mustangsally 1416 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-05-12 (0 days ago) + InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + MachineType: ASUSTeK COMPUTER INC. ROG GU501GM + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-20-generic N/A + linux-backports-modules-4.15.0-20-generic N/A + linux-firmware 1.173 + Tags: bionic + Uname: Linux 4.15.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/16/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: GU501GM.301 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: GU501GM + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: ROG + dmi.product.name: ROG GU501GM + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138495/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package
[Kernel-packages] [Bug 1770862] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138503/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mustangsally 1416 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-12 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. ROG GU501GM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.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/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU501GM.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU501GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG GU501GM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications
[Kernel-packages] [Bug 1770862] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138508/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mustangsally 1416 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-12 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. ROG GU501GM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.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/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU501GM.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU501GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG GU501GM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this
[Kernel-packages] [Bug 1770862] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138509/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mustangsally 1416 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-12 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. ROG GU501GM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.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/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU501GM.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU501GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG GU501GM dmi.product.version: 1
[Kernel-packages] [Bug 1770862] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138502/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mustangsally 1416 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-12 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. ROG GU501GM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.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/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU501GM.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU501GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG GU501GM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage
[Kernel-packages] [Bug 1770862] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138505/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mustangsally 1416 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-12 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. ROG GU501GM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.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/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU501GM.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU501GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG GU501GM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications
[Kernel-packages] [Bug 1770862] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138498/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mustangsally 1416 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-12 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. ROG GU501GM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.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/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU501GM.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU501GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG GU501GM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about
[Kernel-packages] [Bug 1770862] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138499/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mustangsally 1416 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-12 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. ROG GU501GM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.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/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU501GM.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU501GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG GU501GM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bu
[Kernel-packages] [Bug 1770862] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138501/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mustangsally 1416 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-12 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. ROG GU501GM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.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/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU501GM.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU501GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG GU501GM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications
[Kernel-packages] [Bug 1770862] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138506/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mustangsally 1416 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-12 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. ROG GU501GM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.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/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU501GM.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU501GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG GU501GM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications abou
[Kernel-packages] [Bug 1770862] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138497/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mustangsally 1416 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-12 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. ROG GU501GM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.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/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU501GM.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU501GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG GU501GM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notification
[Kernel-packages] [Bug 1770862] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138507/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mustangsally 1416 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-12 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. ROG GU501GM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.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/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU501GM.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU501GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG GU501GM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this
[Kernel-packages] [Bug 1770862] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138500/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mustangsally 1416 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-12 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. ROG GU501GM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.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/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU501GM.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU501GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG GU501GM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bu
[Kernel-packages] [Bug 1770862] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138496/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mustangsally 1416 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-12 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. ROG GU501GM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.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/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU501GM.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU501GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG GU501GM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug
[Kernel-packages] [Bug 1770862] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1770862/+attachment/5138504/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a Best Buy exclusive) does not seem to be detected whatsoever. Below is a printout of "xinput list". I've also attached output files for devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log. I suspect it is an Elantech. I did manage to get one command to print ELAN120x (x being some number). Alas, I don't remember the command now, and none of what I've attached is showing it. (Sorry, I've had a long night of troubleshooting.) The Windows 10 device manager won't even list the brand, even though it's working there. Still, I am fairly confident it's Elan, as that's what ASUS seems to roll with these days. I've tried various combinations of i8042.* kernel parameters, but to no avail. I've also tried blacklisting i2c_hid. It's like it thinks the touchpad is a keyboard? I'm on Ubuntu 18.04. I've tried the mainstream kernel 4.16.7, also to no avail. The latest release candidate (#4) for 4.17 would not let me log in past SDDM, and I noticed no touchpad miracle while I was in the SDDM login screen. If you have any further suggestions of what I could try, I would very much appreciate it! Thanks in advance! xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouseid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19 [slave keyboard (3)] --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mustangsally 1416 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-12 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. ROG GU501GM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.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/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU501GM.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU501GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG GU501GM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifica
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
Tired of this update that never arrives? In the meantime, to make it work, install the 4.14.30 kernel as follows: 1. Open a terminal 2. Add repository: sudo apt-add-repository ppa:teejee2008/ppa 3. Update: sudo apt-get update 4. Install: sudo apt-get install ukuu 5. On dash, call: ukuu 6. Install version 4.14.30 7. Restart, advanced options, choose 4.14.30 kernel, and... voilà Wait for the update of this BUG more peacefully. :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764645 Title: Bluetooth not working Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I've installed the Ubuntu Bionic Beta 2 and everything works fine but the bluetooth (perfectly working with Xenial). In bluetooth control panel the slider is impossible to move to "on". 1) Ubuntu Release (via 'lsb_release -rd') Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) Version of package (apt-cache policy gnome-bluetooth) gnome-bluetooth: Installato: 3.28.0-2 Candidato: 3.28.0-2 Tabella versione: *** 3.28.0-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected to switch on the bluetooth. 4) What happened instead Bluetooth won't switch on. 5) Output of rfkill list is: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is: 03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01) Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half- size Mini PCIe Card [1a56:2003] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit Ethernet [1969:10a1] (rev 10) Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 17.715399] Bluetooth: Core ver 2.22 [ 17.715414] Bluetooth: HCI device and connection manager initialized [ 17.715416] Bluetooth: HCI socket layer initialized [ 17.715418] Bluetooth: L2CAP socket layer initialized [ 17.715422] Bluetooth: SCO socket layer initialized [ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102 [ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 18.600649] Bluetooth: BNEP filters: protocol multicast [ 18.600651] Bluetooth: BNEP socket layer initialized ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stormy 1484 F pulseaudio /dev/snd/controlC0: stormy 1484 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 08:46:30 2018 HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11 InstallationDate: Installed on 2018-04-16 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: ASUSTeK COMPUTER INC. G750JH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G750JH.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G750JH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor:
[Kernel-packages] [Bug 1757445] Re: Suspend does not always resume
I noticed the existence of this error during the boot: "nouveau : 01: 00.0: bus: MMIO read of FAULT at 612004 [IBUS]". So I decided to search and found a suggestion to include the following parameter in the kernel command line "nouveau.modeset = 0". So I decided to test it and immediately the boot errors disappeared, there were no more crashes when suspending and resuming, just as there were no more crashes when shutting down. Either with the 4.16-0 kernel nor with the official 4.15.0-20 kernel. I suggest to those affected by this bug that they try this suggestion. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757445 Title: Suspend does not always resume Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Dell XPS 13 9350 on AC power left running overnight, suspends after a given timeout. When coming back the next morning sometimes the laptop resumes to an aubergine desktop (just the screen, no GDM) and cursor and sits there forever. Sometimes it resumes to a black screen and cursor. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 21 14:15:04 2018 InstallationDate: Installed on 2018-02-13 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201) MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=bc5b647b-38ca-4206-9e96-774a5ac6b833 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/18/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: NULL 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/1757445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757445] Re: Suspend does not always resume
EDIT: "nouveau.modeset=0" no spaces. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757445 Title: Suspend does not always resume Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Dell XPS 13 9350 on AC power left running overnight, suspends after a given timeout. When coming back the next morning sometimes the laptop resumes to an aubergine desktop (just the screen, no GDM) and cursor and sits there forever. Sometimes it resumes to a black screen and cursor. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 21 14:15:04 2018 InstallationDate: Installed on 2018-02-13 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201) MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=bc5b647b-38ca-4206-9e96-774a5ac6b833 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/18/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: NULL 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/1757445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574080] Re: Ubuntu did not reboot after install in VM
*** This bug is a duplicate of bug 1447038 *** https://bugs.launchpad.net/bugs/1447038 I believe the duplicate status is wrong. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574080 Title: Ubuntu did not reboot after install in VM Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 Desktop amd64 did not reboot after a fresh install in a VirtualBox VM (Mac Host, VM Version 5.0.18r106667). What I expected to happen: After the „Installation is complete.“ window, the system reboots properly and loads into Ubuntu What happened: The system did not reboot. A black screen with the error message „19.408093] intel_rapl: no valid rapl domains found in package 0alized - upgrade BIOS or use force_addr=0xaddr“ appeared. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kiwikaki 1483 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 20:18:49 2016 HibernationDevice: RESUME=UUID=aba791f4-b86f-4d1b-a141-bbd5a9bc47fb InstallationDate: Installed on 2016-04-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=36862181-950e-4674-9a92-9a5d151ffa84 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) 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/1574080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770784] sol console log
--- Comment on attachment From chngu...@us.ibm.com 2018-05-12 22:40
EDT---
System crashes after 2nd attempt for few hours but the dump is not completed
and the guest is not coming back.
The console log shows more details where system is at..
** Attachment added: "sol console log"
https://bugs.launchpad.net/bugs/1770784/+attachment/5138580/+files/boslcp4g4.0512.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770784
Title:
ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp4g4:ubuntu1604:P8 compat: guest
crashes in apparmor_file_alloc_security()
Status in linux package in Ubuntu:
New
Bug description:
Test was running an Ubuntu 16.04 guest with a Ubuntu 18.04 host when
the guest dumped a vmcore.
According to the dump, the crash is actually a BUG_ON() raised from
apparmor_file_alloc_security() having called aa_begin_current_label()
which calls aa_current_raw_label() that in turn calls
aa_cred_raw_label() where the BUG_ON() resides:
static inline struct aa_label *aa_cred_raw_label(const struct cred *cred)
{
struct aa_task_ctx *ctx = cred_ctx(cred);
BUG_ON(!ctx || !ctx->label);
return ctx->label;
}
Now, the warnings we previously had seen raised from aa_file_perm()
may have been related since rcu_dereference() as fctx->label is NULL.
fctx = file_ctx(file);
rcu_read_lock();
flabel = rcu_dereference(fctx->label);
AA_BUG(!flabel);
KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-124-generic
DUMPFILE: dump.201805110830 [PARTIAL DUMP]
CPUS: 32
DATE: Fri May 11 06:30:35 2018
UPTIME: 03:40:43
LOAD AVERAGE: 102.77, 103.38, 100.54
TASKS: 862
NODENAME: boslcp4g4
RELEASE: 4.4.0-124-generic
VERSION: #148-Ubuntu SMP Wed May 2 13:02:22 UTC 2018
MACHINE: ppc64le (2134 Mhz)
MEMORY: 16 GB
PANIC: "kernel BUG at
/build/linux-VRGJAN/linux-4.4.0/security/apparmor/include/context.h:69!"
PID: 18397
COMMAND: "chgrp"
TASK: c0035be322c0 [THREAD_INFO: c0035b5c]
CPU: 10
STATE: TASK_RUNNING (PANIC)
crash> bt
PID: 18397 TASK: c0035be322c0 CPU: 10 COMMAND: "chgrp"
#0 [c0035b5c3430] crash_kexec at c0176274
#1 [c0035b5c35d0] die at c0020ef8
#2 [c0035b5c3660] _exception at c0021244
#3 [c0035b5c37f0] program_check_common at c0006208
Program Check [700] exception frame:
R0: c04923e4R1: c0035b5c3ae0R2: c15fa700
R3: c000fcd01a00R4: 0001R5: ffc0
R6: c000fcd01b00R7: 0003fe8dR8: c163a700
R9: 0001R10: R11:
R12: c04fd880R13: c7b06400R14:
R15: R16: 0013R17:
R18: 3fffb7501468R19: R20: 3fffb74ff7e0
R21: R22: R23: 3fffdf3cbd40
R24: 9001R25: 0041R26: f000
R27: c0035b5c3dd0R28: c16342f8R29: c000fcd01a00
R30: c000fcd01a00R31:
NIP: c04fd8c8MSR: 80029033OR3: c04923e0
CTR: c04fd880LR: c04923e4XER:
CCR: 24004248MQ: 0001DAR: c00328004288
DSISR: c0035b5c39e0 Syscall Result:
#4 [c0035b5c3ae0] apparmor_file_alloc_security at c04fd8c8
[Link Register] [c0035b5c3ae0] security_file_alloc at c04923e4
#5 [c0035b5c3b50] security_file_alloc at c04923e4 (unreliable)
#6 [c0035b5c3b90] get_empty_filp at c02e7010
#7 [c0035b5c3c10] path_openat at c02faa2c
#8 [c0035b5c3c90] do_filp_open at c02fc9bc
#9 [c0035b5c3db0] do_sys_open at c02e3150
#10 [c0035b5c3e30] system_call at c0009484
System Call [c01] exception frame:
R0: 0005R1: 3fffdf3cb8c0R2: 3fffb7507e00
R3: 0100270514b0R4: 0008R5: 3fffb7501ef8
R6: 0008R7: 9001R8: 3fffdf3cbd40
R9: R10: R11:
R12: R13: 3fffb750a190
NIP: 3fffb74dbdacMSR: 8280f033OR3: 0100270514b0
CTR: LR: 3fffb74b7034XER:
CCR: 44004442MQ: 0001DAR: 3fffb748
DSISR: 4000 Syscall Result: fffe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
[Kernel-packages] [Bug 1768898] Comment bridged from LTC Bugzilla
--- Comment From ppaid...@in.ibm.com 2018-05-13 00:08 EDT--- (In reply to comment #32) > I built a test kernel with commit c0f7f5b6c69107ca92909512533e70258ee19188. > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1768898 > > Can you test this kernel and see if it resolves this bug? > > Note about installing test kernels: > ? If the test kernel is prior to 4.15(Bionic) you need to install the > linux-image and linux-image-extra .deb packages. > ? If the test kernel is 4.15(Bionic) or newer, you need to install the > linux-image-unsigned, linux-modules and linux-modules-extra .deb packages. > > Thanks in advance! System is having bionic kernel, while installing the above packages getting an error. root@ltc-boston125:~/test_bug# ls linux-image-unsigned-4.15.0-20-generic_4.15.0-20.21~lp1768898_ppc64el.deb linux-modules-extra-4.15.0-20-generic_4.15.0-20.21~lp1768898_ppc64el.deb linux-modules-4.15.0-20-generic_4.15.0-20.21~lp1768898_ppc64el.deb root@ltc-boston125:~/test_bug# dpkg -i *.deb Selecting previously unselected package linux-image-unsigned-4.15.0-20-generic. dpkg: regarding linux-image-unsigned-4.15.0-20-generic_4.15.0-20.21~lp1768898_ppc64el.deb containing linux-image-unsigned-4.15.0-20-generic: linux-image-unsigned-4.15.0-20-generic conflicts with linux-image-4.15.0-20-generic linux-image-4.15.0-20-generic (version 4.15.0-20.21) is present and installed. dpkg: error processing archive linux-image-unsigned-4.15.0-20-generic_4.15.0-20.21~lp1768898_ppc64el.deb (--install): conflicting packages - not installing linux-image-unsigned-4.15.0-20-generic dpkg: warning: downgrading linux-modules-4.15.0-20-generic from 4.15.0-20.21 to 4.15.0-20.21~lp1768898 (Reading database ... 67065 files and directories currently installed.) Preparing to unpack linux-modules-4.15.0-20-generic_4.15.0-20.21~lp1768898_ppc64el.deb ... Unpacking linux-modules-4.15.0-20-generic (4.15.0-20.21~lp1768898) over (4.15.0-20.21) ... dpkg: warning: downgrading linux-modules-extra-4.15.0-20-generic from 4.15.0-20.21 to 4.15.0-20.21~lp1768898 Preparing to unpack linux-modules-extra-4.15.0-20-generic_4.15.0-20.21~lp1768898_ppc64el.deb ... Unpacking linux-modules-extra-4.15.0-20-generic (4.15.0-20.21~lp1768898) over (4.15.0-20.21) ... Setting up linux-modules-4.15.0-20-generic (4.15.0-20.21~lp1768898) ... Setting up linux-modules-extra-4.15.0-20-generic (4.15.0-20.21~lp1768898) ... Processing triggers for linux-image-4.15.0-20-generic (4.15.0-20.21) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinux-4.15.0-20-generic Found initrd image: /boot/initrd.img-4.15.0-20-generic done Errors were encountered while processing: linux-image-unsigned-4.15.0-20-generic_4.15.0-20.21~lp1768898_ppc64el.deb uname -a Linux ltc-boston125 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Can you please let me know why it is failing to install. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768898 Title: smp_call_function_single/many core hangs with stop4 alone Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Recently we discovered this bug occurs just alone with stop4 which results in soft lockups/rcu stalls. ``` root@ltc-boston125:~# [15523.619395] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode. [15523.619508] systemd[1]: systemd-journald.service: Failed with result 'timeout'. [15523.619769] systemd[1]: Failed to start Journal Service. [15523.620618] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart. [15523.620774] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 21. [15523.621462] systemd[1]: Stopped Journal Service. [15523.621635] systemd[1]: systemd-journald.service: Found left-over process 1561 (systemd-journal) in control group while starting unit. Ignoring. [15523.621756] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [15523.621888] systemd[1]: systemd-journald.service: Found left-over process 69060 (systemd-journal) in control group while starting unit. Ignoring. [15523.622029] systemd[1]: This usually indica[15541.629904] INFO: rcu_sched self-detected stall on CPU [15541.629958]60-: (2 GPs behind) idle=146/142/0 softirq=300022/300022 fqs=999069 [15541.630046] (t=2415546 jiffies g=184827 c=184826 q=57111) [15541.6301
[Kernel-packages] [Bug 1744508] Re: iphone tethering stops working quickly after connection
[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/1744508 Title: iphone tethering stops working quickly after connection Status in linux package in Ubuntu: Expired Bug description: Repro steps for my computer: 1.) I use internet via iPhone USB tethering for a while, say 10 mins or less. 2.) I notice there is no internet connection anymore. 3.) I see these errors at syslog. *Re-plugging USB to same USB port changes nothing but the other ports are working for tethering. *Using different port works for a while, than same things happening. I can connect to internet until all USB ports disconnects the iPhone. *Restart solving the issue. *I have been encountering with this issue since a month or so. *I have iPhone 8 with iOS 11.2.2 Jan 21 02:12:23 javier-f22 kernel: [ 1297.768522] NETDEV WATCHDOG: enp0s20f0u1c4i2 (ipheth): transmit queue 0 timed out Jan 21 02:12:23 javier-f22 kernel: [ 1297.768543] [ cut here ] Jan 21 02:12:23 javier-f22 kernel: [ 1297.768555] WARNING: CPU: 3 PID: 2277 at /build/linux-4LIBhY/linux-4.13.0/net/sched/sch_generic.c:316 dev_watchdog+0x21e/0x230 Jan 21 02:12:23 javier-f22 kernel: [ 1297.768557] Modules linked in: ipheth ccm thunderbolt arc4 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_wmi wmi_bmof snd_hda_codec_realtek snd_hda_codec_generic dell_laptop dell_smbios dcdbas snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_rapl ath10k_pci x86_pkg_temp_thermal intel_powerclamp ath10k_core uvcvideo videobuf2_vmalloc snd_seq_midi videobuf2_memops snd_seq_midi_event videobuf2_v4l2 ath kvm_intel videobuf2_core kvm videodev snd_rawmidi media btusb irqbypass intel_cstate nouveau mac80211 intel_rapl_perf btrtl rtsx_pci_ms cfg80211 memstick mxm_wmi snd_seq ttm snd_seq_device snd_timer input_leds snd joydev serio_raw soundcore mei_me idma64 mei shpchp virt_dma processor_thermal_device intel_soc_dts_iosf Jan 21 02:12:23 javier-f22 kernel: [ 1297.768639] intel_lpss_pci intel_pch_thermal hci_uart btbcm serdev btqca int3403_thermal btintel bluetooth wmi ecdh_generic dell_smo8800 intel_lpss_acpi int3402_thermal intel_lpss int340x_thermal_zone intel_hid mac_hid sparse_keymap int3400_thermal acpi_thermal_rel acpi_pad acpi_als kfifo_buf industrialio ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat coretemp nf_conntrack_ftp parport_pc nf_conntrack ppdev libcrc32c iptable_filter lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt nvidia_drm(POE) nvidia_modeset(POE) Jan 21 02:12:23 javier-f22 kernel: [ 1297.768711] i915 crct10dif_pclmul nvidia(POE) crc32_pclmul ghash_clmulni_intel pcbc rtsx_pci_sdmmc i2c_algo_bit aesni_intel aes_x86_64 crypto_simd glue_helper drm_kms_helper cryptd syscopyarea psmouse sysfillrect sysimgblt fb_sys_fops nvme ahci drm nvme_core rtsx_pci libahci i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel Jan 21 02:12:23 javier-f22 kernel: [ 1297.768749] CPU: 3 PID: 2277 Comm: compiz Tainted: P OE 4.13.0-25-generic #29-Ubuntu Jan 21 02:12:23 javier-f22 kernel: [ 1297.768751] Hardware name: Dell Inc. XPS 15 9550/0N7TVV, BIOS 1.6.1 12/11/2017 Jan 21 02:12:23 javier-f22 kernel: [ 1297.768753] task: 8f86498a8000 task.stack: a7ae054d4000 Jan 21 02:12:23 javier-f22 kernel: [ 1297.768760] RIP: 0010:dev_watchdog+0x21e/0x230 Jan 21 02:12:23 javier-f22 kernel: [ 1297.768762] RSP: :8f867dcc3e48 EFLAGS: 00010286 Jan 21 02:12:23 javier-f22 kernel: [ 1297.768766] RAX: 0045 RBX: RCX: Jan 21 02:12:23 javier-f22 kernel: [ 1297.768768] RDX: RSI: 8f867dcd3578 RDI: 8f867dcd3578 Jan 21 02:12:23 javier-f22 kernel: [ 1297.768770] RBP: 8f867dcc3e78 R08: 0001 R09: 04a3 Jan 21 02:12:23 javier-f22 kernel: [ 1297.768772] R10: 8f867dcc3e18 R11: R12: 0001 Jan 21 02:12:23 javier-f22 kernel: [ 1297.768773] R13: 0003 R14: 8f853533c000 R15: 8f86604e8e80 Jan 21 02:12:23 javier-f22 kernel: [ 1297.768776] FS: 7f18f8564dc0() GS:8f867dcc() knlGS: Jan 21 02:12:23 javier-f22 kernel: [ 1297.768778] CS: 0010 DS: ES: CR0: 80050033 Jan 21 02:12:23 javier-f22 kernel: [ 1297.768781] CR2: 1207ba360510 CR3: 000686cb4004 CR4: 0036
[Kernel-packages] [Bug 1754814] Re: Touchaod not working
[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/1754814 Title: Touchaod not working Status in linux package in Ubuntu: Expired Bug description: General information: 1. Laptop- lenovo ideapad 520 2. Touch-pad manufacturer - Elan 3. When the symptom first occurred - 1st February 2018. (10 days ago) Problem description: I am using ubuntu 16.04LTS and after a week of installing it using dual boot the touch-pad stopped working. I followed the steps provided at here- https://wiki.ubuntu.com/DebuggingTouchpadDetection My case is : touch-pad does not work at all from the list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751676] Re: Synaptics' touchpad not detected in 'CyberpowerPC Tracer II' laptop after kernel, system and multiple packages upgrade (for instance: CUDA, libinput, etc.
[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/1751676 Title: Synaptics' touchpad not detected in 'CyberpowerPC Tracer II' laptop after kernel, system and multiple packages upgrade (for instance: CUDA, libinput, etc. Status in linux package in Ubuntu: Expired Bug description: Installed ubuntu 16.04 a while ago and touchpad was working. It does work as well on LiveCDs. After upgrading kernel and some system packages (i've even removed xorg-input-synaptics), touchpad does not even show in `xinput list`. USB mouse works though. I've skimmed dozens of pages in askubuntu and stackexchange to no avail: https://unix.stackexchange.com/questions/28736/what-does-the-i8042-nomux-1-kernel-option-do-during-booting-of-ubuntu https://askubuntu.com/questions/763584/elantech-touchpad-not-working-on-ubuntu-16-04-and-arch-linux https://ubuntuforums.org/showthread.php?t=2323564 https://ubuntuforums.org/showthread.php?t=2352021 Most of these revolved around tampering with the `GRUB_CMDLINE_LINUX_DEFAULT=` argument in `/etc/default/grub` and removing `xserver-xorg-input-synaptics` package along with confs. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: t2063 F pulseaudio /dev/snd/pcmC0D0p: t2063 F...m pulseaudio /dev/snd/controlC0: t2063 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e86768f6-cc8c-4bdc-91fb-a25e5184ee57 InstallationDate: Installed on 2017-08-27 (182 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: CyberpowerPC Tracer II NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=6814f425-7e3f-4911-8fa7-e4637ae009c4 ro atkbd.reset=1 i8042.nomux=1 i8042.reset=1 i8042.nopnp=1 i8042.dumbkbd=1 i8042.kbdreset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.157.16 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.03 dmi.board.asset.tag: Standard dmi.board.name: Tracer II dmi.board.vendor: CyberpowerPC dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 9 dmi.chassis.vendor: Standard dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.03:bd02/23/2017:svnCyberpowerPC:pnTracerII:pvrStandard:rvnCyberpowerPC:rnTracerII:rvrStandard:cvnStandard:ct9:cvrStandard: dmi.product.family: KBL dmi.product.name: Tracer II dmi.product.version: Standard dmi.sys.vendor: CyberpowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755214] Re: general protection fault: 0000 [#1] SMP PTI
[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/1755214 Title: general protection fault: [#1] SMP PTI Status in linux package in Ubuntu: Expired Bug description: new beta install only thing i know is the bluetooth while says connected isn't working. The message appeared upon trying to login first thing this am after just sitting idle over the evening. I had to use the usb direct ties. The gui says the mouse, keyboard, and speakers are connected but none respond. went to the gui and cycled bluetooth off/on to no effect tried a lsb_release got No LSB modules are available?? uname -a Linux steve-nuc 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux. the install was from daily build Mar 10 6:56 ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 [modified: boot/vmlinuz-4.15.0-10-generic] ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2785 F pulseaudio steve 3370 F pulseaudio Date: Sun Mar 11 17:24:17 2018 Failure: oops HibernationDevice: RESUME=UUID=902f332a-f18d-4c50-b896-66f084b8d048 InstallationDate: Installed on 2018-03-11 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) MachineType: Intel Corporation NUC7i7BNH ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=4a9d8673-b237-495c-9966-fa7c74d8d206 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: general protection fault: [#1] SMP PTI UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0052.2017.0918.1346 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-307 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0052.2017.0918.1346:bd09/18/2017:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i7BNH dmi.product.version: J31153-308 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1266738] Re: Bluetooth headphone pairing works, but no audio output - Mako #116
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1266738 Title: Bluetooth headphone pairing works, but no audio output - Mako #116 Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Running Ubuntu Touch image #116 on Mako. I got a pair of bluetooth headphones for xmas, so I haven't tested this before today. Pairing works, I can see the headphones in the bluetooth applet. Playing music no longer works once paired, the music app appears to freeze and the music timeline doesn't move, no audio output. Making and receiving calls is broken once a headset is paired with the phone. Incoming calls drop to answerphone. Outgoing calls never complete. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu7 Uname: Linux 3.4.0-3-mako armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.12.7-0ubuntu3 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CurrentDmesg: dmesg: klogctl failed: Operation not permitted Date: Tue Jan 7 11:36:05 2014 InstallationDate: Installed on 2014-01-07 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140107) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1266738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763189] Re: kernel 4.15 breaks nouveau on Lenovo P50
** Changed in: linux Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763189 Title: kernel 4.15 breaks nouveau on Lenovo P50 Status in Linux: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == A regression was introduced in Bionic. The bug reporter states that the system freezes at boot, apparently when the nouveau driver tries to start. The console is still in 80x25 text mode at this point. No panic or error message is displayed, only unrelated log messages. This regression was introduced by commit af2405af07d168e2 in v4.14-rc1 and fixed by the patch submitted in this SRU request. The patch originated in the following upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=106456 The patch has been submitted upstream, but has not yet landed in linux-next or mainline. The patch is being send as SAUCE until it lands upstream. == Fix == UBUNTU: SAUCE: drm/nouveau: Fix deadlock in nv50_mstm_register_connector() == Regression Potential == Low. This is to fix an existing regression and had been sent to upstream stable, so it will recieve additional upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Original Bug Description == After updating to linux 4.15.0-13-generic, the system freezes at boot, apparently when the nouveau driver tries to start. The console is still in 80x25 text mode at this point. No panic or error message is displayed, only unrelated log messages (screenshot attached). Booting in recovery mode is possible and allows X11 to start using the vesa driver. nouveau still works fine when booting an older kernel (4.13.0-36-generic) so this problem seems to be specific to 4.15.0. ProblemType: Bug ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Apr 11 17:25:27 2018 Dependencies: adduser 3.113+nmu3ubuntu4 apt 1.2.26 apt-utils 1.2.26 busybox-initramfs 1:1.22.0-15ubuntu1 coreutils 8.25-2ubuntu3~16.04 cpio 2.11+dfsg-5ubuntu1 debconf 1.5.58ubuntu1 debianutils 4.7 dpkg 1.18.4ubuntu1.4 e2fslibs 1.42.13-1ubuntu1 e2fsprogs 1.42.13-1ubuntu1 gcc-5-base 5.4.0-6ubuntu1~16.04.9 gcc-6-base 6.0.1-0ubuntu1 gettext-base 0.19.7-2ubuntu3 gnupg 1.4.20-1ubuntu3.1 gpgv 1.4.20-1ubuntu3.1 grub-common 2.02~beta2-36ubuntu3.17 grub-gfxpayload-lists 0.7 grub-pc 2.02~beta2-36ubuntu3.17 grub-pc-bin 2.02~beta2-36ubuntu3.17 grub2-common 2.02~beta2-36ubuntu3.17 init-system-helpers 1.29ubuntu4 initramfs-tools 0.122ubuntu8.11 initramfs-tools-bin 0.122ubuntu8.11 initramfs-tools-core 0.122ubuntu8.11 initscripts 2.88dsf-59.3ubuntu2 insserv 1.14.0-5ubuntu3 klibc-utils 2.0.4-8ubuntu1.16.04.4 kmod 22-1ubuntu5 libacl1 2.2.52-3 libapt-inst2.0 1.2.26 libapt-pkg5.0 1.2.26 libasprintf0v5 0.19.7-2ubuntu3 libattr1 1:2.4.47-2 libaudit-common 1:2.4.5-1ubuntu2.1 libaudit1 1:2.4.5-1ubuntu2.1 libblkid1 2.27.1-6ubuntu3.4 libbz2-1.0 1.0.6-8 libc6 2.23-0ubuntu10 libcomerr2 1.42.13-1ubuntu1 libdb5.3 5.3.28-11ubuntu0.1 libdevmapper1.02.1 2:1.02.110-1ubuntu10 libfdisk1 2.27.1-6ubuntu3.4 libfreetype6 2.6.1-0.1ubuntu2.3 libfuse2 2.9.4-1ubuntu3.1 libgcc1 1:6.0.1-0ubuntu1 libgcrypt20 1.6.5-2ubuntu0.4 libgpg-error0 1.21-2ubuntu1 libgpm2 1.20.4-6.1 libklibc 2.0.4-8ubuntu1.16.04.4 libkmod2 22-1ubuntu5 liblz4-1 0.0~r131-2ubuntu2 liblzma5 5.1.1alpha+20120614-2ubuntu2 libmount1 2.27.1-6ubuntu3.4 libncurses5 6.0+20160213-1ubuntu1 libncursesw5 6.0+20160213-1ubuntu1 libpam-modules 1.1.8-3.2ubuntu2 libpam-modules-bin 1.1.8-3.2ubuntu2 libpam0g 1.1.8-3.2ubuntu2 libpcre3 2:8.38-3.1 libpng12-0 1.2.54-1ubuntu1 libprocps4 2:3.3.10-4ubuntu2.3 libreadline6 6.3-8ubuntu2 libselinux1 2.4-3build2 libsemanage-common 2.3-1build3 libsemanage1 2.3-1build3 libsepol1 2.4-2 libsmartcols1 2.27.1-6ubuntu3.4 libss2 1.42.13-1ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.9 libsystemd0 229-4ubuntu21.2 libtinfo5 6.0+20160213-1ubuntu1 libudev1 229-4ubuntu21.2 libusb-0.1-4 2:0.1.12-28 libustr-1.0-1 1.0.4-5 libuuid1 2.27.1-6ubuntu3.4 linux-base 4.0ubuntu1 lsb-base 9.20160110ubuntu0.2 mount 2.27.1-6ubuntu3.4 multiarch-support 2.23-0ubuntu10 os-prober 1.70ubuntu3.3 passwd 1:4.2-3.1ubuntu5.3 perl-base 5.22.1-9ubuntu0.2 procps 2:3.3.10-4ubuntu2.3 psmisc 22.21-2.1build1 readline-common 6.3-8ubuntu2 sensible-utils 0.0.9ubuntu0.16.04.1 sysv-rc 2.88dsf-59.3ubuntu2 sysvinit-utils 2.88dsf-59.3ubuntu2 tar 1.28-2.1ubuntu0.1 ubuntu-keyring 2012.05.19 ucf 3.
[Kernel-packages] [Bug 1770916] Re: package crda 3.18-1build1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1770916 Title: package crda 3.18-1build1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 Status in crda package in Ubuntu: New Bug description: On upgrading 16.04 - >18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: crda 3.18-1build1 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: crda:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat May 12 13:51:43 2018 DpkgTerminalLog: Preparing to unpack .../crda_3.18-1build1_amd64.deb ... Unpacking crda (3.18-1build1) over (3.13-1) ... dpkg: error processing archive /var/cache/apt/archives/crda_3.18-1build1_amd64.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 DuplicateSignature: package:crda:3.18-1build1 Unpacking crda (3.18-1build1) over (3.13-1) ... dpkg: error processing archive /var/cache/apt/archives/crda_3.18-1build1_amd64.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: crda Title: package crda 3.18-1build1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1770916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770916] [NEW] package crda 3.18-1build1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07
Public bug reported: On upgrading 16.04 - >18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: crda 3.18-1build1 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: crda:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat May 12 13:51:43 2018 DpkgTerminalLog: Preparing to unpack .../crda_3.18-1build1_amd64.deb ... Unpacking crda (3.18-1build1) over (3.13-1) ... dpkg: error processing archive /var/cache/apt/archives/crda_3.18-1build1_amd64.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 DuplicateSignature: package:crda:3.18-1build1 Unpacking crda (3.18-1build1) over (3.13-1) ... dpkg: error processing archive /var/cache/apt/archives/crda_3.18-1build1_amd64.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: crda Title: package crda 3.18-1build1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago) ** Affects: crda (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1770916 Title: package crda 3.18-1build1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 Status in crda package in Ubuntu: New Bug description: On upgrading 16.04 - >18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: crda 3.18-1build1 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: crda:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat May 12 13:51:43 2018 DpkgTerminalLog: Preparing to unpack .../crda_3.18-1build1_amd64.deb ... Unpacking crda (3.18-1build1) over (3.13-1) ... dpkg: error processing archive /var/cache/apt/archives/crda_3.18-1build1_amd64.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 DuplicateSignature: package:crda:3.18-1build1 Unpacking crda (3.18-1build1) over (3.13-1) ... dpkg: error processing archive /var/cache/apt/archives/crda_3.18-1build1_amd64.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: crda Title: package crda 3.18-1build1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1770916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] Re: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1769403 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713252] Re: Bluetooth lenovo yoga 500 doesn't work
apport information ** Tags added: apport-collected ** Description changed: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20.1-0ubuntu2.16 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio + /dev/snd/controlC1: victoria 1991 F pulseaudio + /dev/snd/controlC0: victoria 1991 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c + InstallationDate: Installed on 2018-02-28 (72 days ago) + InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + MachineType: LENOVO 80NA + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-41-generic N/A + linux-backports-modules-4.13.0-41-generic N/A + linux-firmware 1.157.17 + Tags: xenial + Uname: Linux 4.13.0-41-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/26/2015 + dmi.bios.vendor: Lenovo + dmi.bios.version: BECN53WW + dmi.board.asset.tag: No Asset Tag + dmi.board.name: Lenovo Yoga 500-14ACL + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40700 WIN + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Lenovo Yoga 500-14ACL + dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: + dmi.product.family: IDEAPAD + dmi.product.name: 80NA + dmi.product.version: Lenovo Yoga 500-14ACL + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138189/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin
[Kernel-packages] [Bug 1713252] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138193/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BECN53WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14ACL dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14ACL dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: dmi.product.family: IDEAPAD dmi.product.name: 80NA dmi.product.version: Lenovo Yoga 500-14ACL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713252] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138191/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BECN53WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14ACL dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14ACL dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: dmi.product.family: IDEAPAD dmi.product.name: 80NA dmi.product.version: Lenovo Yoga 500-14ACL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713252] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138192/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BECN53WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14ACL dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14ACL dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: dmi.product.family: IDEAPAD dmi.product.name: 80NA dmi.product.version: Lenovo Yoga 500-14ACL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713252] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138202/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BECN53WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14ACL dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14ACL dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: dmi.product.family: IDEAPAD dmi.product.name: 80NA dmi.product.version: Lenovo Yoga 500-14ACL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713252] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138200/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BECN53WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14ACL dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14ACL dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: dmi.product.family: IDEAPAD dmi.product.name: 80NA dmi.product.version: Lenovo Yoga 500-14ACL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713252] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138195/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BECN53WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14ACL dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14ACL dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: dmi.product.family: IDEAPAD dmi.product.name: 80NA dmi.product.version: Lenovo Yoga 500-14ACL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713252] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138194/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BECN53WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14ACL dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14ACL dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: dmi.product.family: IDEAPAD dmi.product.name: 80NA dmi.product.version: Lenovo Yoga 500-14ACL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713252] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138198/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BECN53WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14ACL dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14ACL dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: dmi.product.family: IDEAPAD dmi.product.name: 80NA dmi.product.version: Lenovo Yoga 500-14ACL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713252] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138190/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BECN53WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14ACL dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14ACL dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: dmi.product.family: IDEAPAD dmi.product.name: 80NA dmi.product.version: Lenovo Yoga 500-14ACL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713252] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138203/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BECN53WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14ACL dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14ACL dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: dmi.product.family: IDEAPAD dmi.product.name: 80NA dmi.product.version: Lenovo Yoga 500-14ACL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713252] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138199/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BECN53WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14ACL dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14ACL dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: dmi.product.family: IDEAPAD dmi.product.name: 80NA dmi.product.version: Lenovo Yoga 500-14ACL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713252] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138201/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BECN53WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14ACL dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14ACL dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: dmi.product.family: IDEAPAD dmi.product.name: 80NA dmi.product.version: Lenovo Yoga 500-14ACL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713252] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138197/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BECN53WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14ACL dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14ACL dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: dmi.product.family: IDEAPAD dmi.product.name: 80NA dmi.product.version: Lenovo Yoga 500-14ACL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713252] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1713252/+attachment/5138196/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713252 Title: Bluetooth lenovo yoga 500 doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 The bluetooth is not visible and cannot be detected even though it's supposedly running. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 26 19:17:51 2017 InstallationDate: Installed on 2017-04-05 (142 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: victoria 1991 F...m pulseaudio /dev/snd/controlC1: victoria 1991 F pulseaudio /dev/snd/controlC0: victoria 1991 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=25565afa-99b0-4622-bd70-48393ee8f28c InstallationDate: Installed on 2018-02-28 (72 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80NA Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-41-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BECN53WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14ACL dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14ACL dmi.modalias: dmi:bvnLenovo:bvrBECN53WW:bd11/26/2015:svnLENOVO:pn80NA:pvrLenovoYoga500-14ACL:rvnLENOVO:rnLenovoYoga500-14ACL:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ACL: dmi.product.family: IDEAPAD dmi.product.name: 80NA dmi.product.version: Lenovo Yoga 500-14ACL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770828] [NEW] Lan disconnects on wakeup from suspend
Public bug reported: I just recently updated to 18.04 lts using -d option. Earlier in 17.10 I had issues while shutting down. And thought that seems to be less in this since the last two days I updated, now a new problem is annoying me. As soon as I suspend (which I do more than often) and resume my pc, I see a disconnected sign in the top bar in networks. I tried restarting my router and also reconnected the lan cable but it doesn’t connect until I restart the system! I also tried using the network service restart option but still the network is disconnected. I was redirected here by the budgie support page. You can get my hardware info from this link of the same problem: https://discourse.ubuntubudgie.org/t/network-disconnects-after-resuming-pc-from-suspend/344/3?u=jagoneye Earlier I had shutdown problems. Now that problem is gone but this new problem came up. I upgraded my kernel to 4.15.0-20-generic to solve the shutdown issue. Hope someone can help me as I use the suspend feature more often. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat May 12 15:54:07 2018 InstallationDate: Installed on 2017-10-19 (204 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-04-29 (12 days ago) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1770828 Title: Lan disconnects on wakeup from suspend Status in linux-signed package in Ubuntu: New Bug description: I just recently updated to 18.04 lts using -d option. Earlier in 17.10 I had issues while shutting down. And thought that seems to be less in this since the last two days I updated, now a new problem is annoying me. As soon as I suspend (which I do more than often) and resume my pc, I see a disconnected sign in the top bar in networks. I tried restarting my router and also reconnected the lan cable but it doesn’t connect until I restart the system! I also tried using the network service restart option but still the network is disconnected. I was redirected here by the budgie support page. You can get my hardware info from this link of the same problem: https://discourse.ubuntubudgie.org/t/network-disconnects-after-resuming-pc-from-suspend/344/3?u=jagoneye Earlier I had shutdown problems. Now that problem is gone but this new problem came up. I upgraded my kernel to 4.15.0-20-generic to solve the shutdown issue. Hope someone can help me as I use the suspend feature more often. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat May 12 15:54:07 2018 InstallationDate: Installed on 2017-10-19 (204 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-04-29 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1770828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757180] Re: nvidia-prime can't switch off the discrete GPU
I have the same issue. Ubuntu 18.04 with Nvidia 1070 MaxQ GPU. Have switched to intel GPU but still powerdrain is enormous so obvioulsy the nvidia card is still in use. Powertop show me that the network interfaces wlp3s0 (iwlwifi) drains around 14W which cannot be true. So it also can't detect that its the nvidia card. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1757180 Title: nvidia-prime can't switch off the discrete GPU Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a change in the nvidia packaging, and a change of behaviour in logind, broke this feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1757180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758496] Re: Backlight does not work on a MacBookAir3, 2
Ok! Thanks kaihengfeng! I'll do it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758496 Title: Backlight does not work on a MacBookAir3,2 Status in linux package in Ubuntu: Incomplete Bug description: Backlight control does not work and there are no entries in /sys/class/backlight. When I boot my system with the option GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=vendor" I can change the brightness with the command xrandr on a terminal. I attach all the system information about this problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: victor 2932 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 07:22:05 2018 InstallationDate: Installed on 2018-03-04 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Apple Inc. MacBookAir3,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=dd2bcce2-7d14-4df7-b7c8-6aea4fbb9c13 ro acpi_backlight=vendor RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA31.88Z.0061.B01.1011181342 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-942C5DF58193131B dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir3,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942C5DF58193131B dmi.modalias: dmi:bvnAppleInc.:bvrMBA31.88Z.0061.B01.1011181342:bd11/18/10:svnAppleInc.:pnMacBookAir3,2:pvr1.0:rvnAppleInc.:rnMac-942C5DF58193131B:rvrMacBookAir3,2:cvnAppleInc.:ct10:cvrMac-942C5DF58193131B: dmi.product.family: MacBook dmi.product.name: MacBookAir3,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
Upgrading to 18.04 seems has made this bug appear for me. I have tried updating to the latest kernel but that did not help. $ uname -a Linux erikkallen-laptop 4.17.0-041700rc4-generic #201805070430 SMP Mon May 7 04:31:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413440 Title: USB stops working after a while (xhci_hcd :00:14.0: Timeout while waiting for setup device command) Status in System76: Triaged Status in linux package in Ubuntu: Triaged Bug description: On my laptop the kernel will sometimes drop the USB hub. After this, the laptop doesn't recognise any device plugged in to the USB ports - plugging and unplugging any device I've tried into any of the USB ports produces no response, not even dmesg entries. Strangely this also applies to bluetooth - it no longer works once USB has dropped (possibly the module is hung of the bus internally). Once this has happened only a reboot fixes it; I've not managed to find any combination of module unload/reload or suspend cycles to reinitialise things correctly. Relevant snippet of dmesg: [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead [48838.079742] xhci_hcd :00:14.0: Abort command ring failed [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079806] sched: RT throttling activated [48838.079981] usb 1-1: USB disconnect, device number 16 [48838.079985] usb 1-1.2: USB disconnect, device number 18 [48838.079987] usb 1-1.2.3: USB disconnect, device number 19 [48838.080285] usb 1-1.2.4: USB disconnect, device number 20 [48838.111892] usb 1-1.4: USB disconnect, device number 17 [48838.191292] usb 1-4: USB disconnect, device number 6 [48838.267550] usb 1-10: USB disconnect, device number 8 [48838.282968] usb 2-1: device not accepting address 8, error -62 [48838.282983] usb 2-1: USB disconnect, device number 8 [48838.282986] usb 2-1.2: USB disconnect, device number 9 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 4255 F pulseaudio /dev/snd/controlC0: chris 4255 F pulseaudio CRDA: country AU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (3, 23), (N/A) (5250 - 5330 @ 40), (3, 23), (0 ms), DFS (5735 - 5835 @ 40), (3, 30), (N/A) CurrentDesktop: Unity Date: Thu Jan 22 12:59:27 2015 InstallationDate: Installed on 2013-08-06 (533 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd break=mount RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.141 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1413440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770836] [NEW] amdgpu+xorg possibly marks displays as off while they wake from sleep
Public bug reported: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: New Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770003] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2018-05-12 08:42 EDT---
(In reply to comment #42)
>...
>
> After that, the OK kernel follows with:
> [0001:03:00.0]-580e:2: Asynchronous P2P MODE received
> [0001:03:00.0]-18b9:2: Format 1: VP[0] enabled - status 0 - with port id
> 050500.
> [0001:03:00.0]-5875:2: Format 1: Remote WWPN 20:05:00:05:1e:02:da:3e.
>
> While the NOK kernel follows with:
> [0001:03:00.0]-5809:2: LIP occurred (f700)
> [0001:03:00.0]-580c:2: LIP reset occurred (f7f7).
>
> Later, when the OK kernel seems to detect something, as:
> [0001:03:00.0]-289f:2: Device wrap (030a00).
> [0001:03:00.0]-28d8:2: qla24xx_fcport_handle_login 50:05:07:68:02:16:5e:37
> DS 0 LS 7 P 0 fl 3 confl
> [0001:03:00.0]-28bd:2: qla24xx_fcport_handle_login 982
> 50:05:07:68:02:16:5e:37 post gnl
>
> The NOK kernel just prints:
> [0001:03:00.0]-107ff:2: Async-gpnft hdl=2 FC4Type 8.
Looks like the OK kernel completes the FC login, while the NOK kernel
does not. I believe there were some extra patches added that may be
missing other requirements. Looking at the two different patch lists, I
see this:
1) "scsi: qla2xxx: Fixup locking for session deletion" is missing from
the NOK kernel.
2) There are 16 added patches to the NOK kernel, which were not be
required when we built our test kernel.
It's possible those 16 patches are missing some critical companion
patches, but it should not be necessary to add those 16.
I don't think it is any more acceptable for SRU, but I'll bring it up
anyway: another option is to do a full qla2xxx driver refresh to version
10.00.00.04-k, plus the "scsi: qla2xxx: Fixup locking for session
deletion" patch (a vital fix).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770003
Title:
qla2xxx: Fix page fault at kmem_cache_alloc_node()
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
Dear Canonical,
We found that the current Ubuntu kernel contains a problem related to
qla2xxx driver which causes:
[ 66.295233] Unable to handle kernel paging request for data at address
0x8882f6ed90e9151a
[ 66.295297] Faulting instruction address: 0xc038a110
cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
sp: c692f8d0
msr: 90009033
dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000 softe: 0irq_happened: 0x01
pid = 1762, comm = systemd-journal
Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu
4.15.0-20.21-generic 4.15.20)
enter ? for help
[c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350
(unreliable)
[c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
[c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
[c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
[c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
[c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
[c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
[c692fe30] c000b184 system_call+0x58/0x6c
--- Exception: c00 (System Call) at 74826f6fa9c4
SP (75dc5510) is in userspace
We were able to get rid of this problem cherry picking some of the
upstream patches. Do you think they might fit in the SRU criteria?
The commit ids are below and they were easily cherry picked.
eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug
after firmware timeout
6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin
trigger from sending too many commands
7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in
qla2x00_async_iocb_timeout()
045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call
dma_free_coherent with IRQ disabled.
1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session
free in qlt_free_session_done
d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session
deletion by using work_lock
Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx:
Fixup locking for session deletion')
94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused
argument from qlt_schedule_sess_for_dele?
9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup
for N2N
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+subscriptions
--
Mailing list: https://la
[Kernel-packages] [Bug 1770836] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1770836 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767398] Re: linux-oem: 4.15.0-1005.8 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1767398 Title: linux-oem: 4.15.0-1005.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1767397 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767398] Re: linux-oem: 4.15.0-1005.8 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1767398 Title: linux-oem: 4.15.0-1005.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1767397 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770840] [NEW] My Inspiron-1420 shuts down when waking from Suspended Mode.
Public bug reported: Hello, I installed Ubuntu Budgie - amd64 on my Inspiron 1420. When I close the lid the Notebook (apparently) goes into suspend mode. Instead of starting-up upon opening the lid, the notebook shuts down. I couldn't find the settings for the lid in the settings menu. I can think of two possible reasons (not necessarily true): 1) My HDD is password protected. When I open my notebook it asks for HD password and then takes to the boot menu. 2) I have two operating systems (Dual Boot) installed on my Notebook: Windows 10 developer edition and Ubuntu Budgie. Please look into this. Thanks, Sakib. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat May 12 18:34:57 2018 InstallationDate: Installed on 2018-05-10 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1770840 Title: My Inspiron-1420 shuts down when waking from Suspended Mode. Status in linux-signed package in Ubuntu: New Bug description: Hello, I installed Ubuntu Budgie - amd64 on my Inspiron 1420. When I close the lid the Notebook (apparently) goes into suspend mode. Instead of starting-up upon opening the lid, the notebook shuts down. I couldn't find the settings for the lid in the settings menu. I can think of two possible reasons (not necessarily true): 1) My HDD is password protected. When I open my notebook it asks for HD password and then takes to the boot menu. 2) I have two operating systems (Dual Boot) installed on my Notebook: Windows 10 developer edition and Ubuntu Budgie. Please look into this. Thanks, Sakib. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat May 12 18:34:57 2018 InstallationDate: Installed on 2018-05-10 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1770840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755055] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd-timesyn:669]
Update to this version and apparently everything is fine http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.7/ ** Changed in: linux (Ubuntu) Status: Expired => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755055 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd- timesyn:669] Status in linux package in Ubuntu: Fix Released Bug description: I think it's the video driver ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm 963 F pulseaudio alex 1360 F pulseaudio Date: Sun Mar 11 17:20:20 2018 Failure: oops HibernationDevice: RESUME=UUID=943843be-4a06-4a9e-a69c-db6a069044e3 InstallationDate: Installed on 2018-03-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=af348c5c-232b-45cb-9a50-5affe02e8082 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd-timesyn:669] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL553VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] Re: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude
apport information ** Tags added: apport-collected xenial ** Description changed: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards + --- + ApportVersion: 2.20.1-0ubuntu2.16 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: kpapadim 2115 F pulseaudio + CurrentDesktop: MATE + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 + InstallationDate: Installed on 2017-07-23 (292 days ago) + InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) + MachineType: Dell Inc. Latitude E6420 + Package: xorg 1:7.7+13ubuntu3 + PackageArchitecture: amd64 + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 + ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-39-generic N/A + linux-backports-modules-4.13.0-39-generic N/A + linux-firmware 1.157.17 + Tags: xenial xenial + Uname: Linux 4.13.0-39-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/11/2011 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A04 + dmi.board.name: 0K0DNP + dmi.board.vendor: Dell Inc. + dmi.board.version: A01 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: + dmi.product.name: Latitude E6420 + dmi.product.version: 01 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138314/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be
[Kernel-packages] [Bug 1769403] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138315/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138317/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138319/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138318/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138316/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138321/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138322/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138323/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138324/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138320/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138328/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138327/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138325/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769403] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1769403/+attachment/5138326/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
