[Kernel-packages] [Bug 2054866] Re: package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to install/upgrade: installed linux-headers-6.5.0-21-generic package post-installation script subprocess r
Find the problem, it isn't a broken/unsupported DKMS module for my case.
The system's default gcc/g++ version is 13. While installing CUDA 11.8,
I used update-alternatives to change the gcc/g++ version to 11. Switch
back to gcc/g++ 13 solved this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054866
Title:
package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to
install/upgrade: installed linux-headers-6.5.0-21-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Invalid
Bug description:
plese slove this
.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-21-generic 6.5.0-21.21
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: almamunpc 2365 F wireplumber
/dev/snd/controlC1: almamunpc 2365 F wireplumber
/dev/snd/seq:almamunpc 2355 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sat Feb 24 12:40:52 2024
ErrorMessage: installed linux-headers-6.5.0-21-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-02-10 (14 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
IwConfig:
lono wireless extensions.
enp5s0no wireless extensions.
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB:
0 EFI VGA
1 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=6adb3052-5462-40b3-a845-fe252d1d312e ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
RfKill:
SourcePackage: linux
Title: package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to
install/upgrade: installed linux-headers-6.5.0-21-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F16
dmi.board.asset.tag: Default string
dmi.board.name: B760M DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF16:bd12/14/2023:br5.27:svnGigabyteTechnologyCo.,Ltd.:pnB760MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB760MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B760 MB
dmi.product.name: B760M DS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054866/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054866] Re: package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to install/upgrade: installed linux-headers-6.5.0-21-generic package post-installation script subprocess r
Same problem. From /var/log/dpkg.log, Ubuntu 23.10 seems to
automatically install kernel 6.5.0-21-generic today. However, it fails
with a half-installed status.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054866
Title:
package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to
install/upgrade: installed linux-headers-6.5.0-21-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Confirmed
Bug description:
plese slove this
.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-21-generic 6.5.0-21.21
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: almamunpc 2365 F wireplumber
/dev/snd/controlC1: almamunpc 2365 F wireplumber
/dev/snd/seq:almamunpc 2355 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sat Feb 24 12:40:52 2024
ErrorMessage: installed linux-headers-6.5.0-21-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-02-10 (14 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
IwConfig:
lono wireless extensions.
enp5s0no wireless extensions.
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB:
0 EFI VGA
1 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=6adb3052-5462-40b3-a845-fe252d1d312e ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
RfKill:
SourcePackage: linux
Title: package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to
install/upgrade: installed linux-headers-6.5.0-21-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F16
dmi.board.asset.tag: Default string
dmi.board.name: B760M DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF16:bd12/14/2023:br5.27:svnGigabyteTechnologyCo.,Ltd.:pnB760MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB760MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B760 MB
dmi.product.name: B760M DS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054866/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042043] Re: system boot freeze while typing crypt password
** Description changed:
Rebooted my system and at the luks/crypt password entry screen, I was
able to type about half my password when the system locked up and became
unresponsive. Hard poweroff was the only thing that worked. Same
problem in recovery mode at the text prompt for the crypt password. saw
- the same behavior after multiple reboots.
+ the same behavior after multiple reboots with both 6.5.0-10 and 6.5.0-9
+ kernels.
Eventually was able to boot successfully by waiting a while before
typing the password, and typing it very slowly. no idea what triggered
the succesful password entry though
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: jbarnett 5022 F wireplumber
- /dev/snd/seq:jbarnett 5015 F pipewire
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: jbarnett 5022 F wireplumber
+ /dev/snd/seq:jbarnett 5015 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Mon Oct 30 20:16:01 2023
InstallationDate: Installed on 2019-08-17 (1536 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
Lsusb:
- Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
- Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
- Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd.
Fingerprint Reader
- Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
Integrated_Webcam_HD
- Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
+ Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd.
Fingerprint Reader
+ Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
Integrated_Webcam_HD
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash
RelatedPackageVersions:
- linux-restricted-modules-6.5.0-10-generic N/A
- linux-backports-modules-6.5.0-10-generic N/A
- linux-firmware20230919.git3672ccab-0ubuntu2.1
+ linux-restricted-modules-6.5.0-10-generic N/A
+ linux-backports-modules-6.5.0-10-generic N/A
+ linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-09-26 (34 days ago)
dmi.bios.date: 03/25/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 0N338G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.
** Description changed:
Rebooted my system and at the luks/crypt password entry screen, I was
able to type about half my password when the system locked up and became
unresponsive. Hard poweroff was the only thing that worked. Same
problem in recovery mode at the text prompt for the crypt password. saw
the same behavior after multiple reboots with both 6.5.0-10 and 6.5.0-9
kernels.
Eventually was able to boot successfully by waiting a while before
typing the password, and typing it very slowly. no idea what triggered
- the succesful password entry though
+ the succesful password entry though, or how to even debug the system
+ when its in this state
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jbarnett 5022 F wireplumber
/dev/snd/seq:jbarnett 5015 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Mon Oct 30 20:16:01 2023
InstallationDate: Installed on 2019-08-17 (1536 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd.
Fingerprint Reader
Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
Integrated_Webcam_HD
Bus 001 Device
[Kernel-packages] [Bug 2042043] [NEW] system boot freeze while typing crypt password
Public bug reported:
Rebooted my system and at the luks/crypt password entry screen, I was
able to type about half my password when the system locked up and became
unresponsive. Hard poweroff was the only thing that worked. Same
problem in recovery mode at the text prompt for the crypt password. saw
the same behavior after multiple reboots.
Eventually was able to boot successfully by waiting a while before
typing the password, and typing it very slowly. no idea what triggered
the succesful password entry though
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jbarnett 5022 F wireplumber
/dev/snd/seq:jbarnett 5015 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Mon Oct 30 20:16:01 2023
InstallationDate: Installed on 2019-08-17 (1536 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd.
Fingerprint Reader
Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
Integrated_Webcam_HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-09-26 (34 days ago)
dmi.bios.date: 03/25/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 0N338G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2042043
Title:
system boot freeze while typing crypt password
Status in linux package in Ubuntu:
New
Bug description:
Rebooted my system and at the luks/crypt password entry screen, I was
able to type about half my password when the system locked up and
became unresponsive. Hard poweroff was the only thing that worked.
Same problem in recovery mode at the text prompt for the crypt
password. saw the same behavior after multiple reboots.
Eventually was able to boot successfully by waiting a while before
typing the password, and typing it very slowly. no idea what
triggered the succesful password entry though
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jbarnett 5022 F wireplumber
/dev/snd/seq:jbarnett 5015 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Mon Oct 30 20:16:01 2023
InstallationDate: Installed on 2019-08-17 (1536 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd.
Fingerprint Reader
Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
Integrated_Webcam_HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-09-26 (34 days ago)
dmi.bios.date: 03/25/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
[Kernel-packages] [Bug 2037560] Re: wireless modules not loaded after suspend?
This may be related to this file that I had set up at some point (to
workaround some suspend bluetooth issues?):
$ cat /usr/lib/systemd/system-sleep/bluetooth
#!/bin/sh
case $1 in
pre)
systemctl stop NetworkManager.service
rmmod ath10k_pci ath10k_core ath
btmgmt power off
;;
post)
btmgmt power on
modprobe ath10k_pci
systemctl start NetworkManager.service
;;
esac
... at least that would explain the unloading of the modules, but not
sure why the `post` section isn't reloading them?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037560
Title:
wireless modules not loaded after suspend?
Status in linux package in Ubuntu:
Confirmed
Bug description:
On mantic, after a suspend my network doesn't come up automatically.
I have historically run the following to "reset" networking; not sure
what of it is necessary and what's not, but this brings it up:
$ sudo systemctl stop NetworkManager.service; sudo rmmod ath10k_pci
ath10k_core ath; sleep 3; sudo modprobe ath10k_pci ; sudo systemctl
start NetworkManager.service
rmmod does complain that none of the ath* modules are currently
loaded, so perhaps that's why the network doesn't come up
automatically?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jbarnett 74523 F wireplumber
/dev/snd/controlC0: jbarnett 74523 F wireplumber
/dev/snd/seq:jbarnett 74508 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Wed Sep 27 08:12:37 2023
InstallationDate: Installed on 2019-08-17 (1502 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-09-26 (1 days ago)
dmi.bios.date: 03/25/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 0N338G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037560/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037560] [NEW] wireless modules not loaded after suspend?
Public bug reported:
On mantic, after a suspend my network doesn't come up automatically. I
have historically run the following to "reset" networking; not sure what
of it is necessary and what's not, but this brings it up:
$ sudo systemctl stop NetworkManager.service; sudo rmmod ath10k_pci
ath10k_core ath; sleep 3; sudo modprobe ath10k_pci ; sudo systemctl
start NetworkManager.service
rmmod does complain that none of the ath* modules are currently loaded,
so perhaps that's why the network doesn't come up automatically?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jbarnett 74523 F wireplumber
/dev/snd/controlC0: jbarnett 74523 F wireplumber
/dev/snd/seq:jbarnett 74508 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Wed Sep 27 08:12:37 2023
InstallationDate: Installed on 2019-08-17 (1502 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-09-26 (1 days ago)
dmi.bios.date: 03/25/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 0N338G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037560
Title:
wireless modules not loaded after suspend?
Status in linux package in Ubuntu:
New
Bug description:
On mantic, after a suspend my network doesn't come up automatically.
I have historically run the following to "reset" networking; not sure
what of it is necessary and what's not, but this brings it up:
$ sudo systemctl stop NetworkManager.service; sudo rmmod ath10k_pci
ath10k_core ath; sleep 3; sudo modprobe ath10k_pci ; sudo systemctl
start NetworkManager.service
rmmod does complain that none of the ath* modules are currently
loaded, so perhaps that's why the network doesn't come up
automatically?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jbarnett 74523 F wireplumber
/dev/snd/controlC0: jbarnett 74523 F wireplumber
/dev/snd/seq:jbarnett 74508 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Wed Sep 27 08:12:37 2023
InstallationDate: Installed on 2019-08-17 (1502 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-09-26 (1 days ago)
dmi.bios.date: 03/25/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 0N338G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037560/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to :
[Kernel-packages] [Bug 2020757] Re: Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic (HWE kernel on 22.04)
It's affecting me as well. Had to roll back to 5.19.0-41 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2020757 Title: Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic (HWE kernel on 22.04) Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: I use Ubuntu 22.04 in VMWare Player 17.0.2 (Windows host, due to corporate IT...). I installed the HWE kernel since I have an Intel CPU with P/E-cores. 3D acceleration is enabled in VMWare. With linux-image-5.19.0-41-generic it is rock solid. With linux- image-5.19.0-42-generic it invariably crashes after anything between a minute and an hour. In the journalctl after rebooting it showed that X.Org had crashed followed by a Kernel BUG/Oops due to NULL pointer dereference in drm_gem_object_release_handle. A journalctl log from the Xorg crash up until the kernel OOPS has been attached to this case. This issue happened twice with this kernel. In addition, after trying to reproduce it with kdump tools installed, I got a different issue: refcount_t: saturated; leaking memory. in the log, leading to the OOM killing everything on the system, including (based on what was printed on the terminal), systemd-udevd and journald. That OOM killing never made it into the journal however, as can be expected. I have attached what I could get from the journal for this case as well. One thing that helped trigger this bug (but not every time) was launching Firefox, but once it didn't crash from that and only crashed much much later. Unfortunately I could not get ubuntu-bug to work for this case. I tried "ubuntu-bug --package linux-image-5.19.0-42-generic" but it did absolutely nothing. I'm happy to provide any additional information you require however. $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy linux-generic-hwe-22.04 linux-generic-hwe-22.04: Installed: 5.19.0.42.43~22.04.15 Candidate: 5.19.0.42.43~22.04.15 Version table: *** 5.19.0.42.43~22.04.15 500 500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://se.archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ apt-cache policy linux-image-5.19.0-42-generic linux-image-5.19.0-42-generic: Installed: 5.19.0-42.43~22.04.1 Candidate: 5.19.0-42.43~22.04.1 Version table: *** 5.19.0-42.43~22.04.1 500 500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: No crash. What happened instead: The crash in the attached log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2020757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013186] Re: 5.15.0-69 breaks my wifi
I use Linux Mint, the command above is not found in my terminal. In case Linux Mint bugs are not supposed to be reported here I have also reported it on the Linux Mint forum: https://forums.linuxmint.com/viewtopic.php?t=394200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013186 Title: 5.15.0-69 breaks my wifi Status in linux package in Ubuntu: Incomplete Bug description: Latest linux kernel completely kills my Wifi. Have had to use the GRUB boot loader to revert the kernel back twice. Kernel 5.15.0-67 works perfectly with my wifi. In network settings the wifi option is entirely missing when I am on the -69 version. Output of command `lspci`: ➜ ~ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a80a 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream 03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 04:00.0 Network controller: Broadcom Inc. and subsidiaries Device 43c3 (rev 04) 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 26) 06:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP 06:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller 06:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller 07:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) 08:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) 09:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1) 09:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP 0b:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller 0b:00.4 Audio device: Advanced Micro Devices, Inc.
[Kernel-packages] [Bug 2013186] [NEW] 5.15.0-69 breaks my wifi
Public bug reported: Latest linux kernel completely kills my Wifi. Have had to use the GRUB boot loader to revert the kernel back twice. Kernel 5.15.0-67 works perfectly with my wifi. In network settings the wifi option is entirely missing when I am on the -69 version. Output of command `lspci`: ➜ ~ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a80a 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream 03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 04:00.0 Network controller: Broadcom Inc. and subsidiaries Device 43c3 (rev 04) 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 26) 06:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP 06:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller 06:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller 07:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) 08:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) 09:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1) 09:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP 0b:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller 0b:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller Version log (but as noted, I have reverted my kernel version. It is the '-69' version which is the one that breaks the wifi, which I need for my work): ➜ ~ cat version.log Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 I attach the much longer output of lspci-vnvn.log as a separate attachment. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: kernel-bug ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/2013186/+attachment/5658600/+files/lspci-vnvn.log -- You
[Kernel-packages] [Bug 1999937] [NEW] package nvidia-dkms-470-server 470.103.01-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-470-server package post-installation script subprocess returne
Public bug reported: Errors were encountered while processing: nvidia-dkms-470-server nvidia-driver-470-server ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-470-server 470.103.01-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Dec 16 14:15:27 2022 ErrorMessage: installed nvidia-dkms-470-server package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-12-01 (15 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: nvidia-graphics-drivers-470-server Title: package nvidia-dkms-470-server 470.103.01-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-470-server package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/137 Title: package nvidia-dkms-470-server 470.103.01-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-470-server package post- installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-470-server package in Ubuntu: New Bug description: Errors were encountered while processing: nvidia-dkms-470-server nvidia-driver-470-server ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-470-server 470.103.01-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Dec 16 14:15:27 2022 ErrorMessage: installed nvidia-dkms-470-server package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-12-01 (15 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: nvidia-graphics-drivers-470-server Title: package nvidia-dkms-470-server 470.103.01-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-470-server package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470-server/+bug/137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953235] Re: systemctl suspend stopped working: laptop immeadeately wakes up again
You saved my day. I also install cuda stuff from nvidia driver repository (using ubuntu 20.04 and needed cuda 11) /etc/systemd/system/systemd-suspend.service.requires contained symbolic links which point to /lib/systemd/system/nvidia-resume.service removing these symbolic links made suspend work again. another symptom was: systemctl suspend was not working but pm-suspend was working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1953235 Title: systemctl suspend stopped working: laptop immeadeately wakes up again Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I always suspend my laptop using `systemctl suspend`. It worked for a year as expected until today. Buggy Behavior: after `systemctl suspend` the seemingly usual suspend happens, however the laptop wakes up immediately. Things get more weird from here, as I need to input my password twice to get back into GNOME. Troubleshooting I did: 1. apt update && apt dist-upgrade 2. Disabled nvidia-suspend.service, nvidia-persistenced.service, nvidia-resume.service 3. Booted with an earlier kernel version where it used to work: `5.11.0-40`, `5.11.0-38` 3. Detached all devices, and the power cable 4. Rebooted into a separate user that has no tweaks, gnome-extensions etc 5. The issue persists -- I attached relevant parts of `journalctl`: from the time when I used `systemctl suspend` till a minute or so after I logged back into GNOME. Additionally: ``` user@myLaptop:~$ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7 01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1) 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 25) 04:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c2) 05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller 05:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 05:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 05:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller 06:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 61) ``` ``` user@myLaptop:~$ cat /proc/acpi/wakeup DeviceS-state Status Sysfs node GPP0S4*enabled pci::00:01.1 GPP1S4*enabled pci::00:01.2 GPP2S4*disabled GPP3S4*disabled GPP4S4*disabled GPP5S4*enabled pci::00:01.6 GP17S4*enabled pci::00:08.1 XHC0S4*enabled pci::05:00.3 XHC1S4
[Kernel-packages] [Bug 1992696] Re: Realtek USB 802.11ac + Bluetooth 5.0 Fails wifi Network function
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1992696 Title: Realtek USB 802.11ac + Bluetooth 5.0 Fails wifi Network function Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: I plug in this usb wifi 802.11ac + Bluetooth 5.0 Realtek adaptor and I get no networking from it. I also have a wireless N adapter on usb as well. This was pretty much the same behavior since 20.04. I haven't been able to use this adaptor for wifi for quite a while. I heard that Fedora has no problem with this device. It may be that the order of activation is what needs to be modified. Like activate the bluetooth first, and then make the wifi part active. Thanks for all the great work! Here is the Dmesg I get the following which shows up using dmesg... [ 107.256812] usb 3-3: new high-speed USB device number 3 using xhci_hcd [ 107.405398] usb 3-3: New USB device found, idVendor=0bda, idProduct=b82c, bcdDevice= 2.10 [ 107.405415] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 107.405421] usb 3-3: Product: 802.11ac+Bluetooth 5.0 Adapter [ 107.405425] usb 3-3: Manufacturer: Realtek [ 107.405428] usb 3-3: SerialNumber: 123456 [ 107.409742] Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b lmp_ver=07 lmp_subver=8822 [ 107.410730] Bluetooth: hci0: RTL: rom_version status=0 version=2 [ 107.410740] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_fw.bin [ 107.411027] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_config.bin [ 107.411173] Bluetooth: hci0: RTL: cfg_sz 14, total sz 20270 [ 108.152731] Bluetooth: hci0: RTL: fw version 0xab6b705c ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-19-generic 5.19.0-19.19 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uplifting 4065 F wireplumber /dev/snd/seq:uplifting 4058 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 15:00:44 2022 MachineType: Hewlett-Packard HP ProBook 4540s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_uiqi22@/vmlinuz-5.19.0-19-generic root=ZFS=rpool/ROOT/ubuntu_uiqi22 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: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) dmi.bios.date: 05/20/2013 dmi.bios.release: 15.65 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.41 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 88.30 dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.41:bd05/20/2013:br15.65:efr88.30:svnHewlett-Packard:pnHPProBook4540s:pvrA1019D1103:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1E:cvnHewlett-Packard:ct10:cvr:skuC9K70UT#ABA: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 4540s dmi.product.sku: C9K70UT#ABA dmi.product.version: A1019D1103 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992696/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992696] [NEW] Realtek USB 802.11ac + Bluetooth 5.0 Fails wifi Network function
Public bug reported: I plug in this usb wifi 802.11ac + Bluetooth 5.0 Realtek adaptor and I get no networking from it. I also have a wireless N adapter on usb as well. This was pretty much the same behavior since 20.04. I haven't been able to use this adaptor for wifi for quite a while. I heard that Fedora has no problem with this device. It may be that the order of activation is what needs to be modified. Like activate the bluetooth first, and then make the wifi part active. Thanks for all the great work! Here is the Dmesg I get the following which shows up using dmesg... [ 107.256812] usb 3-3: new high-speed USB device number 3 using xhci_hcd [ 107.405398] usb 3-3: New USB device found, idVendor=0bda, idProduct=b82c, bcdDevice= 2.10 [ 107.405415] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 107.405421] usb 3-3: Product: 802.11ac+Bluetooth 5.0 Adapter [ 107.405425] usb 3-3: Manufacturer: Realtek [ 107.405428] usb 3-3: SerialNumber: 123456 [ 107.409742] Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b lmp_ver=07 lmp_subver=8822 [ 107.410730] Bluetooth: hci0: RTL: rom_version status=0 version=2 [ 107.410740] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_fw.bin [ 107.411027] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_config.bin [ 107.411173] Bluetooth: hci0: RTL: cfg_sz 14, total sz 20270 [ 108.152731] Bluetooth: hci0: RTL: fw version 0xab6b705c ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-19-generic 5.19.0-19.19 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uplifting 4065 F wireplumber /dev/snd/seq:uplifting 4058 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 15:00:44 2022 MachineType: Hewlett-Packard HP ProBook 4540s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_uiqi22@/vmlinuz-5.19.0-19-generic root=ZFS=rpool/ROOT/ubuntu_uiqi22 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: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) dmi.bios.date: 05/20/2013 dmi.bios.release: 15.65 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.41 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 88.30 dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.41:bd05/20/2013:br15.65:efr88.30:svnHewlett-Packard:pnHPProBook4540s:pvrA1019D1103:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1E:cvnHewlett-Packard:ct10:cvr:skuC9K70UT#ABA: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 4540s dmi.product.sku: C9K70UT#ABA dmi.product.version: A1019D1103 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992696 Title: Realtek USB 802.11ac + Bluetooth 5.0 Fails wifi Network function Status in linux package in Ubuntu: New Bug description: I plug in this usb wifi 802.11ac + Bluetooth 5.0 Realtek adaptor and I get no networking from it. I also have a wireless N adapter on usb as well. This was pretty much the same behavior since 20.04. I haven't been able to use this adaptor for wifi for quite a while. I heard that Fedora has no problem with this device. It may be that the order of activation is what needs to be modified. Like activate the bluetooth first, and then make the wifi part active. Thanks for all the great work! Here is the Dmesg I get the following which shows up using dmesg... [ 107.256812] usb 3-3: new high-speed USB device number 3 using xhci_hcd [ 107.405398] usb 3-3: New USB device found, idVendor=0bda, idProduct=b82c, bcdDevice= 2.10 [ 107.405415] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 107.405421] usb 3-3: Product: 802.11ac+Bluetooth 5.0 Adapter [ 107.405425] usb 3-3: Manufacturer: Realtek [ 107.405428] usb 3-3: SerialNumber: 123456 [ 107.409742] Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b lmp_ver=07 lmp_subver=8822 [ 107.410730] Bluetooth: hci0: RTL: rom_version status=0
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
fwiw, this is fixed in kinetic with its 5.19 kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990447] Re: New linux makes wifi driver unstable again
** Tags added: apport-collected una ** Changed in: linux (Ubuntu) Status: Incomplete => Opinion ** Changed in: linux (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990447 Title: New linux makes wifi driver unstable again Status in linux package in Ubuntu: Invalid Bug description: I'm new to this, sorry if I get it wrong. I'm using Mint, but the update manager links to here as kernels aren't changed by the Mint team. I'm using the rtl8821ce wifi driver which previously had trouble loading again after waking up from sleep. Not every time though and without any pattern. The recent kernel, 5.15.0.46.49~20.04.16 had fixed this problem, which had gone on for over a year before that. Just now I updated again to linux_5.15.0-48.54~20.04.18 and the problem is back. Waking up, sometimes the wifi doesn't work, NetworkManager icon says it's connected but nothing works. I have found that suspending and waking back up, then sudo modprobe -r rtl8821ce, sudo modprobe rtl8821ce will get it working again but that's the only way without shutting down. cat /proc/version_signature Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex [1022:15d0] Subsystem: Hewlett-Packard Company Raven/Raven2 Root Complex [103c:87b7] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee0 Data: 0022 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 8GT/s, Width x2, ASPM L1, Exit Latency L1 <64us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s (ok), Width x2 (ok) TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #0, PowerLimit 0.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState+ RootCap: CRSVisible+ RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible+ RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, NROPrPrP-, LTR+ 10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt+, EETLPPrefix+, MaxEETLPPrefixes 1 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS-, LN System CLS Not Supported, TPHComp-, ExtTPHComp-, ARIFwd+ AtomicOpsCap: Routing- 32bit+ 64bit+ 128bitCAS- DevCtl2: Completion Timeout: 65ms to 210ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- AtomicOpsCtl: ReqEn- EgressBlck- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB
[Kernel-packages] [Bug 1990447] [NEW] New linux makes wifi driver unstable again
Public bug reported: I'm new to this, sorry if I get it wrong. I'm using Mint, but the update manager links to here as kernels aren't changed by the Mint team. I'm using the rtl8821ce wifi driver which previously had trouble loading again after waking up from sleep. Not every time though and without any pattern. The recent kernel, 5.15.0.46.49~20.04.16 had fixed this problem, which had gone on for over a year before that. Just now I updated again to linux_5.15.0-48.54~20.04.18 and the problem is back. Waking up, sometimes the wifi doesn't work, NetworkManager icon says it's connected but nothing works. I have found that suspending and waking back up, then sudo modprobe -r rtl8821ce, sudo modprobe rtl8821ce will get it working again but that's the only way without shutting down. cat /proc/version_signature Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex [1022:15d0] Subsystem: Hewlett-Packard Company Raven/Raven2 Root Complex [103c:87b7] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee0 Data: 0022 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 8GT/s, Width x2, ASPM L1, Exit Latency L1 <64us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s (ok), Width x2 (ok) TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #0, PowerLimit 0.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState+ RootCap: CRSVisible+ RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible+ RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, NROPrPrP-, LTR+ 10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt+, EETLPPrefix+, MaxEETLPPrefixes 1 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS-, LN System CLS Not Supported, TPHComp-, ExtTPHComp-, ARIFwd+ AtomicOpsCap: Routing- 32bit+ 64bit+ 128bitCAS- DevCtl2: Completion Timeout: 65ms to 210ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- AtomicOpsCtl: ReqEn- EgressBlck- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, EqualizationPhase1+ EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:1234] Capabilities: [c8] HyperTransport:
[Kernel-packages] [Bug 1986857] [NEW] fan doesn't work
Public bug reported: The fan does not work in either the current version of ubuntu or previous (focal fossa). it was working a few months ago, so this may be new to this kernel, i didn't discover when it stopped working directly :( symptoms: gets very hot. no fan. eventually blackscreens while the power remains on. `sensors-detect` eventually outputs: ``` Sorry, no sensors were detected. This is relatively common on laptops, where thermal management is handled by ACPI rather than the OS. ``` `sensors` output is as follows: ``` jdub@compy4:~$ sudo sensors iwlwifi_1-virtual-0 Adapter: Virtual device temp1:+41.0°C asus-isa- Adapter: ISA adapter cpu_fan: 2900 RPM nvme-pci-0500 Adapter: PCI adapter Composite:+55.9°C (low = -5.2°C, high = +83.8°C) (crit = +87.8°C) BAT0-acpi-0 Adapter: ACPI interface in0: 15.83 V amdgpu-pci-0600 Adapter: PCI adapter vddgfx: 756.00 mV vddnb: 874.00 mV edge: +51.0°C slowPPT: 2.00 mW ucsi_source_psy_USBC000:001-isa- Adapter: ISA adapter in0: 0.00 V (min = +0.00 V, max = +0.00 V) curr1: 0.00 A (max = +0.00 A) k10temp-pci-00c3 Adapter: PCI adapter Tctl: +52.9°C nvme-pci-0400 Adapter: PCI adapter Composite:+32.9°C (low = -0.1°C, high = +76.8°C) (crit = +79.8°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+52.0°C (crit = +120.0°C) ``` Description:Ubuntu 22.04.1 LTS Release:22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jdub 2341 F pulseaudio /dev/snd/controlC0: jdub 2341 F pulseaudio /dev/snd/controlC1: jdub 2341 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 17 12:51:23 2022 InstallationDate: Installed on 2021-04-08 (496 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA502IU_GA502IU ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=84a0282e-1a9f-4814-a551-45a4be446ec9 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (0 days ago) dmi.bios.date: 12/30/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA502IU.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA502IU 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.ec.firmware.release: 3.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA502IU.221:bd12/30/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA502IU_GA502IU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA502IU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus G15 dmi.product.name: ROG Zephyrus G15 GA502IU_GA502IU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986857 Title: fan doesn't work Status in linux package in Ubuntu: New Bug description: The fan does not work in either the current version of ubuntu or previous (focal fossa). it was working a few months ago, so this may be new to this kernel, i didn't discover when it stopped working directly :( symptoms: gets very hot. no fan. eventually blackscreens while the power remains on. `sensors-detect` eventually outputs: ``` Sorry, no sensors were detected. This is relatively common on laptops, where thermal management is handled by ACPI rather than the OS. ``` `sensors` output is as follows: ``` jdub@compy4:~$ sudo sensors iwlwifi_1-virtual-0 Adapter: Virtual device temp1:+41.0°C asus-isa- Adapter: ISA adapter cpu_fan: 2900 RPM nvme-pci-0500 Adapter: PCI adapter Composite:+55.9°C (low = -5.2°C, high = +83.8°C) (crit = +87.8°C) BAT0-acpi-0 Adapter: ACPI interface in0: 15.83 V amdgpu-pci-0600 Adapter: PCI adapter vddgfx: 756.00 mV vddnb: 874.00 mV edge: +51.0°C slowPPT: 2.00 mW ucsi_source_psy_USBC000:001-isa-
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
This bug is not fixed by 5.15.0-40-generic, and still occurs with that kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
any plans to address this in jammy? haven't had any movement on the upstream bug so I assume reverting that one commit is probably the best option? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
also fwiw, confirmed that starting from tag Ubuntu-5.15.0-25.25 (commit f4a9abe17854fc753c84a0ba4ac275e715a008f3), reverting commit 6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0 applies cleanly and fixes the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
found some other reports that claim i915.fastboot=0 is a workaround, and can confirm it does work around the issue on jammy's current 5.15 kernel. https://www.reddit.com/r/pop_os/comments/scqr4n/dell_xps_15_9575_screen_flickering_upon_boot/ https://bugs.archlinux.org/task/72134 https://gitlab.freedesktop.org/drm/intel/-/issues/4952 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #4952 https://gitlab.freedesktop.org/drm/intel/-/issues/4952 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #5534 https://gitlab.freedesktop.org/drm/intel/-/issues/5534 ** Also affects: linux via https://gitlab.freedesktop.org/drm/intel/-/issues/5534 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
If I didn't get my good/bad confused on the reverse bisection, this appears to be the commit that fixes it: 5ac860cc52540df8bca27e0bb25b6744df67e8f0 is the first bad commit commit 5ac860cc52540df8bca27e0bb25b6744df67e8f0 Author: Ville Syrjälä Date: Thu Mar 3 21:12:06 2022 +0200 drm/i915: Fix DBUF bandwidth vs. cdclk handling Make the dbuf bandwidth min cdclk calculations match the spec more closely. Supposedly the arbiter can only guarantee an equal share of the total bandwidth of the slice to each active plane on that slice. So we take the max bandwidth of any of the planes on each slice and multiply that by the number of active planes on the slice to get a worst case estimate on how much bandwidth we require. Signed-off-by: Ville Syrjälä Link: https://patchwork.freedesktop.org/patch/msgid/20220303191207.27931-9-ville.syrj...@linux.intel.com Reviewed-by: Stanislav Lisovskiy drivers/gpu/drm/i915/display/intel_bw.c| 157 - drivers/gpu/drm/i915/display/intel_bw.h| 10 +- drivers/gpu/drm/i915/display/intel_cdclk.c | 67 +--- drivers/gpu/drm/i915/display/intel_cdclk.h | 2 + 4 files changed, 147 insertions(+), 89 deletions(-) ** Attachment added: "bisect log 2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+attachment/5574955/+files/bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
appears to be fixed in drm-tip 2022-03-29 packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
Yeah I was confused that the built kernel versions were in the v5.13-rc range, but according to `git tag --contains 6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0` (and the list of tags in https://github.com/torvalds/linux/commit/6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0) v5.14-rc1 is the first tag that has this commit in 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/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Confirmed Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
after bisection:
6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0 is the first bad commit
commit 6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0
Author: José Roberto de Souza
Date: Fri May 14 16:22:45 2021 -0700
drm/i915/display: Allow fastsets when DP_SDP_VSC infoframe do not match
with PSR enabled
When PSR is enabled it handles DP_SDP_VSC, changing revision and all
the other fields as necessary.
It can also enabled and disable this SDP as needed without a full
modeset.
So here masking DP_SDP_VSC bit when previous and future state PSR
enabled, it will still be checked when comparing the asked state
to what was programmed to hardware.
Cc: Gwan-gyeong Mun
Cc: Radhakrishna Sripada
Reported-by: Ville Syrjälä
Fixes: 78b772e1a01f ("drm/i915/display: Fill PSR state during hardware
configuration read out")
Signed-off-by: José Roberto de Souza
Reviewed-by: Gwan-gyeong Mun
Link:
https://patchwork.freedesktop.org/patch/msgid/20210514232247.144542-2-jose.so...@intel.com
drivers/gpu/drm/i915/display/intel_display.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
** Attachment added: "bisect log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+attachment/5573585/+files/bisect
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1958620
Title:
[Dell XPS 15 9575] Flickering white/black screen once KMS comes up
Status in linux package in Ubuntu:
Confirmed
Bug description:
This looks like a regression from the 5.13.0-20-generic kernel to the
5.15.0-17-generic kernel. The display works fine under efifb, but as
soon as the DRM drivers are loaded and KMS kicks in the display is
replaced by black with flickering white (apparently when what would be
on the output changes).
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-17-generic 5.15.0-17.17
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: chris 7134 F pipewire-media-
/dev/snd/seq:chris 7133 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 21 17:07:08 2022
InstallationDate: Installed on 2021-06-26 (208 days ago)
InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
MachineType: Dell Inc. XPS 15 9575
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-20-generic N/A
linux-backports-modules-5.13.0-20-generic N/A
linux-firmware 1.204
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
dmi.bios.date: 07/07/2019
dmi.bios.release: 1.7
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.1
dmi.board.name: 0C32VW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
Was the Precision 5530 2-in-1 version of this machine ever certified? don't know if it would have the exact same issue but its the same chipset. In the meantime I'm attempting to bisect the mainline kernel to find the commit that broke this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Confirmed Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot
based on previous comment no longer testing with i915.enable_psr=0, but here's what i've narrowed it down to: v5.13.19: works v5.14.0rc2: black screen looks like the v5.14.0rc1 build failed so can't test that? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965968 Title: post jammy update, black/flickering screen on boot Status in linux package in Ubuntu: Confirmed Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot
v5.14: black screen v5.13: black screen with i915.enable_psr=0, works without went back and tried the initial 5.13.0-35 as well, and it also does the black screen with i915.enable_psr=0 will try to find the first mainline 5.13 that doesn't work today (or if they all work). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965968 Title: post jammy update, black/flickering screen on boot Status in linux package in Ubuntu: Confirmed Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot
both of those exhibit the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965968 Title: post jammy update, black/flickering screen on boot Status in linux package in Ubuntu: Confirmed Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot
i915.enable_psr=0 did not fix the black screen issue, but did appear to remove the flickering purple streaks, fwiw. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965968 Title: post jammy update, black/flickering screen on boot Status in linux package in Ubuntu: Confirmed Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962477] Re: Can't pair Bluetooth devices using TP-Link UB500 Adaptor
I have since purchased a different model bluetooth adaptor, which works correctly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1962477 Title: Can't pair Bluetooth devices using TP-Link UB500 Adaptor Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: $ lsusb Bus 001 Device 006: ID 2357:0604 TP-Link TP-Link UB500 Adapter Other users have fixed by patching the kernel: https://askubuntu.com/questions/1370663/bluetooth-scan-doesnt-detect- any-device-on-ubuntu-21-10 Please add support for this device so that Users don't need to patch the kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Feb 28 22:31:55 2022 SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1962477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962477] Re: Can't pair Bluetooth devices using TP-Link UB500 Adaptor
** Summary changed: - Can't pair Bluetooth devicesusing TP-Link UB500 Adaptor + Can't pair Bluetooth devices using TP-Link UB500 Adaptor -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1962477 Title: Can't pair Bluetooth devices using TP-Link UB500 Adaptor Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: $ lsusb Bus 001 Device 006: ID 2357:0604 TP-Link TP-Link UB500 Adapter Other users have fixed by patching the kernel: https://askubuntu.com/questions/1370663/bluetooth-scan-doesnt-detect- any-device-on-ubuntu-21-10 Please add support for this device so that Users don't need to patch the kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Feb 28 22:31:55 2022 SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1962477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962477] [NEW] Can't pair Bluetooth devicesusing TP-Link UB500 Adaptor
Public bug reported: $ lsusb Bus 001 Device 006: ID 2357:0604 TP-Link TP-Link UB500 Adapter Other users have fixed by patching the kernel: https://askubuntu.com/questions/1370663/bluetooth-scan-doesnt-detect- any-device-on-ubuntu-21-10 Please add support for this device so that Users don't need to patch the kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Feb 28 22:31:55 2022 SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: $ lsusb Bus 001 Device 006: ID 2357:0604 TP-Link TP-Link UB500 Adapter Other users have fixed by patching the kernel: https://askubuntu.com/questions/1370663/bluetooth-scan-doesnt-detect- any-device-on-ubuntu-21-10 + + Please add support for this device so that Users don't need to patch the + kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Feb 28 22:31:55 2022 SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1962477 Title: Can't pair Bluetooth devicesusing TP-Link UB500 Adaptor Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: $ lsusb Bus 001 Device 006: ID 2357:0604 TP-Link TP-Link UB500 Adapter Other users have fixed by patching the kernel: https://askubuntu.com/questions/1370663/bluetooth-scan-doesnt-detect- any-device-on-ubuntu-21-10 Please add support for this device so that Users don't need to patch the kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Feb 28 22:31:55 2022 SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1962477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
I am experiencing the same problem. The trackpad seems laggy after suspend. Also, it seems to commonly get "stuck" in two finger scrolling, where after lifting one of the two fingers it stays in scrolling mode. The only way to get it out is to tap on the trackpad randomly to, I assume, get it to detect different finger actions. Linux x 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 15:58:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 20.04.3 LTS \n \l -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from the impish repos. To recreate: 1. Reboot a X1C9 machine and see that the touchpad works fine 2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a software suspend) 3. Resume from suspend and see that touchpad acts differently and less responsive than right after a clean boot What is expected: 1. Same responsive touchpad experience after resuming from suspend as right after a clean boot. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Pop!_OS 21.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] MachineType: LENOVO 20XW005PMX Package: libinput10 1.18.0-1 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet systemd.show_status=false loglevel=0 splash Tags: hirsute third-party-packages ubuntu Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: This does not seem to be an official Pop!_OS package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 06/15/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET66W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW005PMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW005PMX dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938096/+subscriptions
[Kernel-packages] [Bug 1878321] Re: TP-Link UE300 [2357:0601]: Kernel workqueue rtl_work_func_t [r8152] gets stuck, preventing network connectivity: Bad RIP value
FYI, I picked this up again with Ubuntu 20.10 and still see the same issue. # lsb_release -d ; uname -srmo Description:Ubuntu 20.10 Linux 5.8.0-43-generic x86_64 GNU/Linux Dmesg output: [Sun Feb 28 11:44:52 2021] NOHZ: local_softirq_pending 08 [Sun Feb 28 11:44:52 2021] NOHZ: local_softirq_pending 08 [Sun Feb 28 12:00:56 2021] INFO: task NetworkManager:1421 blocked for more than 120 seconds. [Sun Feb 28 12:00:56 2021] Tainted: PW OE 5.8.0-43-generic #49-Ubuntu [Sun Feb 28 12:00:56 2021] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Sun Feb 28 12:00:56 2021] NetworkManager D0 1421 1 0x [Sun Feb 28 12:00:56 2021] Call Trace: [Sun Feb 28 12:00:56 2021] __schedule+0x212/0x5d0 [Sun Feb 28 12:00:56 2021] schedule+0x55/0xc0 [Sun Feb 28 12:00:56 2021] schedule_preempt_disabled+0xe/0x10 [Sun Feb 28 12:00:56 2021] __mutex_lock.constprop.0+0x14a/0x490 [Sun Feb 28 12:00:56 2021] ? netlink_dump+0xc3/0x400 [Sun Feb 28 12:00:56 2021] __mutex_lock_slowpath+0x13/0x20 [Sun Feb 28 12:00:56 2021] mutex_lock+0x34/0x40 [Sun Feb 28 12:00:56 2021] rtnl_lock+0x15/0x20 [Sun Feb 28 12:00:56 2021] nl80211_dump_scan+0x34/0x160 [cfg80211] [Sun Feb 28 12:00:56 2021] ? __alloc_skb+0xa4/0x200 [Sun Feb 28 12:00:56 2021] netlink_dump+0x18e/0x400 [Sun Feb 28 12:00:56 2021] __netlink_dump_start+0x20e/0x2f0 [Sun Feb 28 12:00:56 2021] genl_family_rcv_msg_dumpit+0x8f/0x110 [Sun Feb 28 12:00:56 2021] ? genl_rcv_msg+0xa0/0xa0 [Sun Feb 28 12:00:56 2021] ? nl80211_dump_survey+0x2e0/0x2e0 [cfg80211] [Sun Feb 28 12:00:56 2021] ? genl_family_rcv_msg_dumpit+0x110/0x110 [Sun Feb 28 12:00:56 2021] genl_family_rcv_msg+0x1ef/0x290 [Sun Feb 28 12:00:56 2021] ? do_poll.constprop.0+0x287/0x3a0 [Sun Feb 28 12:00:56 2021] ? free_pcp_prepare+0x59/0x110 [Sun Feb 28 12:00:56 2021] ? genl_family_rcv_msg+0x290/0x290 [Sun Feb 28 12:00:56 2021] genl_rcv_msg+0x4c/0xa0 [Sun Feb 28 12:00:56 2021] ? genl_family_rcv_msg+0x290/0x290 [Sun Feb 28 12:00:56 2021] netlink_rcv_skb+0x4e/0x110 [Sun Feb 28 12:00:56 2021] genl_rcv+0x29/0x40 [Sun Feb 28 12:00:56 2021] netlink_unicast+0x218/0x330 [Sun Feb 28 12:00:56 2021] netlink_sendmsg+0x23b/0x460 [Sun Feb 28 12:00:56 2021] ? aa_sk_perm+0x43/0x1b0 [Sun Feb 28 12:00:56 2021] sock_sendmsg+0x65/0x70 [Sun Feb 28 12:00:56 2021] sys_sendmsg+0x257/0x2a0 [Sun Feb 28 12:00:56 2021] ? sendmsg_copy_msghdr+0x7e/0xa0 [Sun Feb 28 12:00:56 2021] ? get_order+0x20/0x20 [Sun Feb 28 12:00:56 2021] ___sys_sendmsg+0x82/0xc0 [Sun Feb 28 12:00:56 2021] ? get_order+0x20/0x20 [Sun Feb 28 12:00:56 2021] ? get_order+0x20/0x20 [Sun Feb 28 12:00:56 2021] ? get_order+0x20/0x20 [Sun Feb 28 12:00:56 2021] ? ep_poll+0x2ec/0x480 [Sun Feb 28 12:00:56 2021] ? __fget_light+0x32/0x80 [Sun Feb 28 12:00:56 2021] __sys_sendmsg+0x62/0xb0 [Sun Feb 28 12:00:56 2021] __x64_sys_sendmsg+0x1f/0x30 [Sun Feb 28 12:00:56 2021] do_syscall_64+0x49/0xc0 [Sun Feb 28 12:00:56 2021] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Sun Feb 28 12:00:56 2021] RIP: 0033:0x7fca1587b91d [Sun Feb 28 12:00:56 2021] Code: Unable to access opcode bytes at RIP 0x7fca1587b8f3. [Sun Feb 28 12:00:56 2021] RSP: 002b:7ffcd45b2210 EFLAGS: 0293 ORIG_RAX: 002e [Sun Feb 28 12:00:56 2021] RAX: ffda RBX: 55abfea2bc40 RCX: 7fca1587b91d [Sun Feb 28 12:00:56 2021] RDX: RSI: 7ffcd45b2260 RDI: 000b [Sun Feb 28 12:00:56 2021] RBP: 7ffcd45b2260 R08: R09: 55abfec2d3a0 [Sun Feb 28 12:00:56 2021] R10: 55abfebc8ba0 R11: 0293 R12: 55abfea2bc40 [Sun Feb 28 12:00:56 2021] R13: 55abfea2bdc0 R14: 7fca158e2f80 R15: 55abfea2c340 If I try to run any other networking commands (like ip), they hang. Here's the NetworkManager callstack: # cat /proc/1421/stack [<0>] rtnl_lock+0x15/0x20 [<0>] nl80211_dump_scan+0x34/0x160 [cfg80211] [<0>] netlink_dump+0x18e/0x400 [<0>] __netlink_dump_start+0x20e/0x2f0 [<0>] genl_family_rcv_msg_dumpit+0x8f/0x110 [<0>] genl_family_rcv_msg+0x1ef/0x290 [<0>] genl_rcv_msg+0x4c/0xa0 [<0>] netlink_rcv_skb+0x4e/0x110 [<0>] genl_rcv+0x29/0x40 [<0>] netlink_unicast+0x218/0x330 [<0>] netlink_sendmsg+0x23b/0x460 [<0>] sock_sendmsg+0x65/0x70 [<0>] sys_sendmsg+0x257/0x2a0 [<0>] ___sys_sendmsg+0x82/0xc0 [<0>] __sys_sendmsg+0x62/0xb0 [<0>] __x64_sys_sendmsg+0x1f/0x30 [<0>] do_syscall_64+0x49/0xc0 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 ** Changed in: linux (Ubuntu) Status: Expired => 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/1878321 Title: TP-Link UE300 [2357:0601]: Kernel workqueue rtl_work_func_t [r8152] gets stuck, preventing network connectivity: Bad RIP value Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 Package:
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Works fine after installing hwe kernel using apt.(5.8.0.44 Ubuntu 20.04
Lenovo R7000P)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 82B5
ProcEnviron:
TERM=xterm-256color
PATH=(custom,
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Lenovo R7000P Laptop. Sadly, still not a good solution. The touch pad
now works with kernel 5.11.0, but it has problem with Nvidia GPU and the
brightness control is not working. I can have Nvidia GPU working and
manually do some fixes to enable brightness control with 5.8.0, though
touch pad is not working.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25
[Kernel-packages] [Bug 1762248] Re: WiFi connection suddenly drops
Just experienced this bug on Xubuntu 20.04.1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762248 Title: WiFi connection suddenly drops Status in linux package in Ubuntu: Expired Bug description: This started to happen only with newer kernel versions. The WiFi was previously absolutely solid. When the WiFi connection drops, there are clear kernel error messages: Apr 08 22:39:29 konstantin kernel: iwl3945 :02:00.0: Queue 4 stuck for 2048 ms. Apr 08 22:39:30 konstantin kernel: iwl3945 :02:00.0: On demand firmware reload Apr 08 22:39:30 konstantin kernel: ieee80211 phy0: Hardware restart was requested Apr 08 22:39:30 konstantin kernel: iwl3945 :02:00.0: BSM uCode verification failed at addr 0x3800+0 Apr 08 22:39:30 konstantin kernel: iwl3945 :02:00.0: Unable to set up bootstrap uCode: -5 The last two messsages are repeated a few times. This is followed by more detailed stack traces, but the hardware does not recover. Unloading the iwl3945 module and reloading it did not help in a few tests. Looking at the log some more, I see this line Apr 08 22:33:38 konstantin kernel: iwl3945 :02:00.0: Enabling power save might cause firmware crashes I will try to find out if this can be disabled and do more test then. 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: regina 1098 F pulseaudio CurrentDesktop: GNOME Date: Sun Apr 8 22:56:35 2018 HibernationDevice: RESUME=UUID=4c990619-fde4-4d44-b45a-f240be602537 InstallationDate: Installed on 2017-04-19 (354 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC ProcEnviron: LANG=de_DE.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash video=SVIDEO-1:d vt.handoff=7 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: Upgraded to artful on 2018-01-19 (78 days ago) dmi.bios.date: 04/04/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.05 dmi.board.name: 30CC dmi.board.vendor: Quanta dmi.board.version: 79.10 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.05:bd04/04/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.10:cvnQuanta:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv6500 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
acpidump on latest (1.13.0) firmware. ** Attachment added: "1.13.0.acpidump" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+attachment/5415405/+files/1.13.0.acpidump -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
1.2.0 firmware acpidump attached ** Attachment added: "1.2.0.acpidump" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+attachment/5415318/+files/1.2.0.acpidump -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889114] Re: Ubuntu 18.04 Update Breaks KVM Wireless Mouse
Sorry for the delay in responding. We were helping a relative pack and move. The history log had already been moved to a .gz file. The file is attached. It covers the dates from 1 Jul to 22 Jul. ** Attachment added: "history.log.2.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889114/+attachment/5407897/+files/history.log.2.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev
[Kernel-packages] [Bug 1893795] [NEW] [Ubuntu 20.04.1 LTS] Backlight brightness can't be changed, even in /sys/
Public bug reported: None of the boot parameters worked, but with acpi_backlight=vendor the backlight was dimmer (systemd-backlight didn't fail). The only way it starts working is to do "setpci -v -H1 -s 00:01.00 BRIDGE_CONTROL=0" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xma1345 F pulseaudio /dev/snd/controlC0: xma1345 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 1 14:36:14 2020 InstallationDate: Installed on 2020-08-30 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. MacBookPro11,3 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=01482a85-82e8-44ce-a63d-a429cd6d5381 ro acpi_osi= RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 162.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2BD1B31983FE1663 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,3 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2BD1B31983FE1663 dmi.modalias: dmi:bvnAppleInc.:bvr162.0.0.0.0:bd06/10/2020:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663: dmi.product.family: Mac dmi.product.name: MacBookPro11,3 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "backlight.tar" https://bugs.launchpad.net/bugs/1893795/+attachment/5406558/+files/backlight.tar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893795 Title: [Ubuntu 20.04.1 LTS] Backlight brightness can't be changed, even in /sys/ Status in linux package in Ubuntu: New Bug description: None of the boot parameters worked, but with acpi_backlight=vendor the backlight was dimmer (systemd-backlight didn't fail). The only way it starts working is to do "setpci -v -H1 -s 00:01.00 BRIDGE_CONTROL=0" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xma1345 F pulseaudio /dev/snd/controlC0: xma1345 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 1 14:36:14 2020 InstallationDate: Installed on 2020-08-30 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. MacBookPro11,3 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=01482a85-82e8-44ce-a63d-a429cd6d5381 ro acpi_osi= RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 162.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2BD1B31983FE1663 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,3 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2BD1B31983FE1663 dmi.modalias: dmi:bvnAppleInc.:bvr162.0.0.0.0:bd06/10/2020:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663: dmi.product.family: Mac dmi.product.name: MacBookPro11,3 dmi.product.sku: System SKU# 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/1893795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889114] Re: Ubuntu 18.04 Update Breaks KVM Wireless Mouse
I executed the apport-collect 1889114 command as instructed. It appears that a number of txt files were uploaded. However, the instructions also said to change the status to "Confirmed". I was not able to change the status. The "status" info pulldown seems to indicate that the "reporter" can not change the status to "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/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
[Kernel-packages] [Bug 1889114] Re: Ubuntu 18.04 Update Breaks KVM Wireless Mouse
** 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/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTDBAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: NOK dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M.
[Kernel-packages] [Bug 1889114] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1889114/+attachment/5397279/+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/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTDBAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO
[Kernel-packages] [Bug 1889114] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1889114/+attachment/5397274/+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/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTDBAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: NOK
[Kernel-packages] [Bug 1889114] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1889114/+attachment/5397281/+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/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTDBAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: NOK
[Kernel-packages] [Bug 1889114] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1889114/+attachment/5397278/+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/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTDBAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: NOK
[Kernel-packages] [Bug 1889114] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1889114/+attachment/5397276/+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/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTDBAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: NOK
[Kernel-packages] [Bug 1889114] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1889114/+attachment/5397282/+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/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTDBAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: NOK
[Kernel-packages] [Bug 1889114] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1889114/+attachment/5397275/+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/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTDBAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: NOK
[Kernel-packages] [Bug 1889114] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1889114/+attachment/5397280/+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/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTDBAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version:
[Kernel-packages] [Bug 1889114] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1889114/+attachment/5397284/+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/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTDBAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: NOK
[Kernel-packages] [Bug 1889114] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1889114/+attachment/5397277/+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/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTDBAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: NOK
[Kernel-packages] [Bug 1889114] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1889114/+attachment/5397283/+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/1889114 Title: Ubuntu 18.04 Update Breaks KVM Wireless Mouse Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe_admin 7605 F pulseaudio /dev/snd/controlC1: joe_admin 7605 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (134 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10ALCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTDBAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: NOK
[Kernel-packages] [Bug 1889114] Re: Ubuntu 18.04 Update Breaks KVM Wireless Mouse
apport information ** Tags added: apport-collected ** Description changed: I installed Ubuntu 18.04 updates on July 21st. This was a relatively small update with kernel related files from what I remember when installing the update. Since the update, my KVM connected Logitech G305 wireless mouse functionality is broken. The KVM keyboard and display still function correctly. I have 2 computers (desktop and laptop) connected to a KVM switch. The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro. This KVM setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu 18.04, and Windows 7 Pro. The KVM (ConnectPro 14+) • Has a video cable from each computer to the KVM • Has a USB control cable from each computer to the KVM • Has a video cable from the KVM to the display • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 keyboard • Has a KVM USB extension cable with the Logitech G305 wireless mouse receiver plugged into the USB connector. The extension cable is used to locate the receiver in proximity to the wireless mouse. I updated Ubuntu on the desktop on July 21st. Since the update, I have lost wireless mouse functionality to the desktop. But, I still have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was not updated. KVM Wireless Mouse function matrix (see attached image) I replaced the mouse battery, so that is not the problem. I verified that a wired mouse and the wireless Logitech G305 mouse both work properly when plugged directly into a USB port on the M83 desktop. I replaced the wireless mouse with a wired mouse on the KVM mouse input, and the 4 configurations above worked OK (including the desktop with the July updates). So, I think that the July 21st update broke some function(s) in the handling of the wireless mouse USB controls signals between the desktop computer and the KVM switch. 1. Can I provide any additional configuration information, and, if so, what terminal commands should I run? 2. How do I recover from this problem? 3. Can I back-out the update? If so, how will this impact future updates? 4. What else can I try to restore the wireless mouse functionality? Thank you in advance for your assistance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 14:29:36 2020 InstallationDate: Installed on 2020-03-18 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.15 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: joe_admin 7605 F pulseaudio + /dev/snd/controlC1: joe_admin 7605 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-03-18 (134 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + IwConfig: + eno1 no wireless extensions. + + lono wireless extensions. + MachineType: LENOVO 10ALCTO1WW + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=d0cb764f-7be8-4e81-b87c-3de2ef7d074c ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-42-generic N/A + linux-backports-modules-5.4.0-42-generic N/A + linux-firmware1.173.19 + RfKill: + + Tags: bionic + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/24/2019 + dmi.bios.vendor: LENOVO + dmi.bios.version: FBKTDBAUS + dmi.board.name: SHARKBAY + dmi.board.vendor: LENOVO + dmi.board.version: NOK + 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:bvnLENOVO:bvrFBKTDBAUS:bd12/24/2019:svnLENOVO:pn10ALCTO1WW:pvrThinkCentreM83:rvnLENOVO:rnSHARKBAY:rvrNOK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To be filled by O.E.M.
[Kernel-packages] [Bug 1878321] [NEW] Kernel workqueue rtl_work_func_t [r8152] gets stuck, preventing network connectivity: Bad RIP value
Public bug reported: $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 Package: linux-image-5.3.0-51-generic What happened: After plugging my TP-Link (Realtek 8152 based) USB GbE ethernet device into my laptop and using it, network connectivity loss occurs several minutes later. Once this has occurred, various processes on the system hang when I run them (eg "ip a"; "sudo"). It appears that the rtnetlink lock is held and is never released. The device disappears from the list of available devices. What I expected: I can plug the ethernet device in and use it to successfully observe cats on the internet for hours at a time. Kernel logs: May 11 22:15:58 allosaurus kernel: usb 2-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd May 11 22:15:58 allosaurus kernel: usb 2-2: New USB device found, idVendor=2357, idProduct=0601, bcdDevice=30.00 May 11 22:15:58 allosaurus kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=6 May 11 22:15:58 allosaurus kernel: usb 2-2: Product: USB 10/100/1000 LAN May 11 22:15:58 allosaurus kernel: usb 2-2: Manufacturer: TP-LINK May 11 22:15:58 allosaurus kernel: usb 2-2: SerialNumber: 0100 May 11 22:15:59 allosaurus kernel: usbcore: registered new interface driver r8152 May 11 22:15:59 allosaurus kernel: usbcore: registered new interface driver cdc_ether May 11 22:15:59 allosaurus kernel: usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd May 11 22:15:59 allosaurus kernel: r8152 2-2:1.0 eth0: v1.09.11 May 11 22:15:59 allosaurus kernel: r8152 2-2:1.0 enxd03745081b4b: renamed from eth0 May 11 22:16:02 allosaurus kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enxd03745081b4b: link becomes ready May 11 22:16:02 allosaurus kernel: r8152 2-2:1.0 enxd03745081b4b: carrier on May 11 22:16:02 allosaurus kernel: r8152 2-2:1.0 enxd03745081b4b: carrier off May 11 22:16:05 allosaurus kernel: r8152 2-2:1.0 enxd03745081b4b: carrier on May 11 22:20:17 allosaurus kernel: NOHZ: local_softirq_pending 08 May 11 22:24:33 allosaurus kernel: NOHZ: local_softirq_pending 08 May 11 22:24:39 allosaurus kernel: NOHZ: local_softirq_pending 08 May 11 22:25:14 allosaurus kernel: NOHZ: local_softirq_pending 08 May 11 22:30:31 allosaurus kernel: INFO: task kworker/1:2:10776 blocked for more than 120 seconds. May 11 22:30:31 allosaurus kernel: Tainted: P OE 5.3.0-51-generic #44-Ubuntu May 11 22:30:31 allosaurus kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. May 11 22:30:31 allosaurus kernel: kworker/1:2 D0 10776 2 0x80004000 May 11 22:30:31 allosaurus kernel: Workqueue: events rtl_work_func_t [r8152] May 11 22:30:31 allosaurus kernel: Call Trace: May 11 22:30:31 allosaurus kernel: __schedule+0x2b9/0x6c0 May 11 22:30:31 allosaurus kernel: schedule+0x42/0xb0 May 11 22:30:31 allosaurus kernel: rpm_resume+0x174/0x780 May 11 22:30:31 allosaurus kernel: ? wait_woken+0x80/0x80 May 11 22:30:31 allosaurus kernel: rpm_resume+0x31d/0x780 May 11 22:30:31 allosaurus kernel: ? __switch_to_asm+0x34/0x70 May 11 22:30:31 allosaurus kernel: ? __switch_to_xtra+0x1c5/0x5c0 May 11 22:30:31 allosaurus kernel: ? __switch_to_asm+0x34/0x70 May 11 22:30:31 allosaurus kernel: ? __switch_to_asm+0x40/0x70 May 11 22:30:31 allosaurus kernel: ? __switch_to_asm+0x34/0x70 May 11 22:30:31 allosaurus kernel: __pm_runtime_resume+0x52/0x80 May 11 22:30:31 allosaurus kernel: usb_autopm_get_interface+0x1d/0x50 May 11 22:30:31 allosaurus kernel: rtl_work_func_t+0x70/0x285 [r8152] May 11 22:30:31 allosaurus kernel: ? __schedule+0x2c1/0x6c0 May 11 22:30:31 allosaurus kernel: process_one_work+0x1db/0x380 May 11 22:30:31 allosaurus kernel: worker_thread+0x4d/0x400 May 11 22:30:31 allosaurus kernel: kthread+0x104/0x140 May 11 22:30:31 allosaurus kernel: ? process_one_work+0x380/0x380 May 11 22:30:31 allosaurus kernel: ? kthread_park+0x80/0x80 May 11 22:30:31 allosaurus kernel: ret_from_fork+0x35/0x40 May 11 22:31:34 allosaurus kernel: usb 2-2: USB disconnect, device number 2 May 11 22:32:32 allosaurus kernel: INFO: task NetworkManager:1470 blocked for more than 120 seconds. May 11 22:32:32 allosaurus kernel: Tainted: P OE 5.3.0-51-generic #44-Ubuntu May 11 22:32:32 allosaurus kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. May 11 22:32:32 allosaurus kernel: NetworkManager D0 1470 1 0x May 11 22:32:32 allosaurus kernel: Call Trace: May 11 22:32:32 allosaurus kernel: __schedule+0x2b9/0x6c0 May 11 22:32:32 allosaurus kernel: schedule+0x42/0xb0 May 11 22:32:32 allosaurus kernel: schedule_preempt_disabled+0xe/0x10 May 11 22:32:32 allosaurus kernel: __mutex_lock.isra.0+0x182/0x4f0 May 11 22:32:32 allosaurus kernel: __mutex_lock_slowpath+0x13/0x20 May 11 22:32:32 allosaurus kernel: mutex_lock+0x2e/0x40 May 11 22:32:32 allosaurus kernel: rtnl_lock+0x15/0x20 May 11 22:32:32 allosaurus kernel: nl80211_dump_scan+0x34/0x6d0
[Kernel-packages] [Bug 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
verified fixed with proposed kernel on dell xps15 2-in-1. Device: Mesa Intel(R) HD Graphics 630 (KBL GT2) (0x591b) ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1861521 Title: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled Status in linux-5.4 package in Ubuntu: In Progress Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux-5.4 source package in Focal: In Progress Bug description: [Impact] After Ubuntu-5.4.0-9.12 which introduce DPCD backlight patches, the backlight control on some platforms fail to work. It seems using OUI string to map the panels which support DPCD backlight doesn't work well, it mis-mapped those panel that doesn't support DPCD backlight, and breaks the backlight control. [Fix] The author of the origin DPCD backlight patches recently provides a DP quirks based on EDID identification. [Fix] Verified on the machine with DPCD backlight and also on the machine which has regression with the OUI quirks, both of them work now. [Regression Potential] Low, it introduce a new quirks to list the panels which support DPCD backlight. === After upgrading from Eoan (5.3.0-29.31) to Focal (5.4.0-12.15), I no longer have the ability to control the backlight brightness on my HP EliteBook 840 G5. When pressing the brightness hotkeys, the on-screen indicator pops up and shows that the brightness setting is being changed but the actual screen brightness is stuck on the lowest setting. This laptop has a built-in privacy screen. If I activate the privacy screen (fn-f2), then the actual screen brightness goes to the maximum setting and then I am able to dim and brighten the backlight as long as the privacy screen functionality is turned on. This is a regression from Eoan's 5.3.0-29.31 kernel where I was able to control the brightness with and without the privacy screen functionality being turned on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 11:42:16 2020 InstallationDate: Installed on 2019-06-24 (221 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-28 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1861521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854896] Re: Synaptics TM3336-004 Touchpad Stopped working after update to the latest kernel 4.15.0-72 generic
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 Tank you very much Nilesh, this solution was the perfect fix for me! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854896 Title: Synaptics TM3336-004 Touchpad Stopped working after update to the latest kernel 4.15.0-72 generic Status in linux package in Ubuntu: Incomplete Bug description: Please see to it, my touchpad all of a sudden stopped working after reboot. it happened after updating to the latest kernel 4.15.0-72, i am using linux mint 19.2. Pointer version: Synaptics TM3336-004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
** Changed in: linux (Ubuntu) Status: Fix Committed => 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/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Fix Released Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
confirmed fixed in 5.3.0-24.26 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Fix Committed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
added to the 5.3-stable tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable- queue.git/tree/queue-5.3/drm-amdgpu-user-pages-array-memory-leak- fix.patch can this get into the next ubuntu kernel as well? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
fwiw, with a 5.3 kernel on eoan and a system-sleep script that does `btmgmt power off` pre sleep, and `btmgmt power on` post sleep, I haven't been seeing the lock up issue. just an occasional instant wake from suspend with the system usable after that, and able to successfully suspend with another attempt. `PM: Some devices failed to suspend, or early wake event detected` in the logs when the instant wake happens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
** Tags added: patch-accepted-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
in drm-next: https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm- next=06f7f57e87d09900a7c3109a357b73521ab40771 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
patch update: https://lists.freedesktop.org/archives/amd- gfx/2019-October/041187.html (also see review in https://lists.freedesktop.org/archives/amd-gfx/2019-October/041194.html) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
The patch in https://lists.freedesktop.org/archives/amd- gfx/2019-October/040850.html appears to fix the issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
https://lists.freedesktop.org/archives/amd-gfx/2019-October/040688.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
(also, still an issue with 5.3.0-13) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
899fbde1464639e3d12eaffdad8481a59b367fcb is the first bad commit commit 899fbde1464639e3d12eaffdad8481a59b367fcb Author: Philip Yang Date: Thu Dec 13 15:35:28 2018 -0500 drm/amdgpu: replace get_user_pages with HMM mirror helpers Use HMM helper function hmm_vma_fault() to get physical pages backing userptr and start CPU page table update track of those pages. Then use hmm_vma_range_done() to check if those pages are updated before amdgpu_cs_submit for gfx or before user queues are resumed for kfd. If userptr pages are updated, for gfx, amdgpu_cs_ioctl will restart from scratch, for kfd, restore worker is rescheduled to retry. HMM simplify the CPU page table concurrent update check, so remove guptasklock, mmu_invalidations, last_set_pages fields from amdgpu_ttm_tt struct. HMM does not pin the page (increase page ref count), so remove related operations like release_pages(), put_page(), mark_page_dirty(). Signed-off-by: Philip Yang Reviewed-by: Felix Kuehling Reviewed-by: Christian König Signed-off-by: Alex Deucher :04 04 0c9f0e2e82e5e4d2d3a4c0daea22eb911244b771 fdcdc7c80f5383486962edf4561e205b55bd8c21 M drivers $ git bisect log # bad: [f74c2bb98776e2de508f4d607cd519873065118e] Linux 5.3-rc8 # good: [1c163f4c7b3f621efff9b28a47abb36f7378d783] Linux 5.0 git bisect start 'v5.3-rc8' 'v5.0' # good: [a2d635decbfa9c1e4ae15cb05b68b2559f7f827c] Merge tag 'drm-next-2019-05-09' of git://anongit.freedesktop.org/drm/drm git bisect good a2d635decbfa9c1e4ae15cb05b68b2559f7f827c # good: [a2d635decbfa9c1e4ae15cb05b68b2559f7f827c] Merge tag 'drm-next-2019-05-09' of git://anongit.freedesktop.org/drm/drm git bisect good a2d635decbfa9c1e4ae15cb05b68b2559f7f827c # good: [8f6ccf6159aed1f04c6d179f61f6fb2691261e84] Merge tag 'clone3-v5.3' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux git bisect good 8f6ccf6159aed1f04c6d179f61f6fb2691261e84 # good: [8f6ccf6159aed1f04c6d179f61f6fb2691261e84] Merge tag 'clone3-v5.3' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux git bisect good 8f6ccf6159aed1f04c6d179f61f6fb2691261e84 # bad: [be8454afc50f43016ca8b6130d9673bdd0bd56ec] Merge tag 'drm-next-2019-07-16' of git://anongit.freedesktop.org/drm/drm git bisect bad be8454afc50f43016ca8b6130d9673bdd0bd56ec # bad: [be8454afc50f43016ca8b6130d9673bdd0bd56ec] Merge tag 'drm-next-2019-07-16' of git://anongit.freedesktop.org/drm/drm git bisect bad be8454afc50f43016ca8b6130d9673bdd0bd56ec # good: [d72619706abc4aa7e540ea882dae883cee7cc3b3] Merge tag 'tty-5.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty git bisect good d72619706abc4aa7e540ea882dae883cee7cc3b3 # bad: [83145f110eb2ada9d54fcbcf416c02de126381c1] drm/amdgpu: don't invalidate caches in RELEASE_MEM, only do the writeback git bisect bad 83145f110eb2ada9d54fcbcf416c02de126381c1 # bad: [b239c01727459ba08c44b79e6225d3c58723f282] drm/amdgpu: add mcbp driver parameter git bisect bad b239c01727459ba08c44b79e6225d3c58723f282 # good: [e1dc68a4b149d47536cd001d0d0abadbb62d37bd] drm: atmel-hlcdc: avoid initializing cfg with zero git bisect good e1dc68a4b149d47536cd001d0d0abadbb62d37bd # bad: [c53e4db71276bf257b09010935a04bdafddd458e] drm/amdgpu: cancel late_init_work before gpu reset git bisect bad c53e4db71276bf257b09010935a04bdafddd458e # good: [2da4605dce38b84cd2e5b86686f43adae1b2cacb] drm/amd/display: Use DCN functions instead of DCE git bisect good 2da4605dce38b84cd2e5b86686f43adae1b2cacb # bad: [1c1e53f7f2ce191e6787d3d0648fe8ce7088ceaa] drm/amd/doc: Add XGMI sysfs documentation git bisect bad 1c1e53f7f2ce191e6787d3d0648fe8ce7088ceaa # good: [89cd9d23e9a74d94f0db5bbbaf2ef1f6ede36ae5] drm/amdkfd: avoid HMM change cause circular lock git bisect good 89cd9d23e9a74d94f0db5bbbaf2ef1f6ede36ae5 # bad: [0803e7a9e850f9d6397c594d6c6deac9b2b6d696] drm/amdkfd: Allocate hiq and sdma mqd from mqd trunk git bisect bad 0803e7a9e850f9d6397c594d6c6deac9b2b6d696 # bad: [972fcdb52fe865a2f639e3200b97e648f34a0f41] drm/amdkfd: Introduce asic-specific mqd_manager_init function git bisect bad 972fcdb52fe865a2f639e3200b97e648f34a0f41 # bad: [6c55d6e90e68a4789cbd72a0287026d4dfb4a9f9] drm/amdkfd: support concurrent userptr update for HMM git bisect bad 6c55d6e90e68a4789cbd72a0287026d4dfb4a9f9 # bad: [ad595b8634f36f04bf69bef4eff854091d94f8b3] drm/amdgpu: fix HMM config dependency issue git bisect bad ad595b8634f36f04bf69bef4eff854091d94f8b3 # bad: [899fbde1464639e3d12eaffdad8481a59b367fcb] drm/amdgpu: replace get_user_pages with HMM mirror helpers git bisect bad 899fbde1464639e3d12eaffdad8481a59b367fcb # first bad commit: [899fbde1464639e3d12eaffdad8481a59b367fcb] drm/amdgpu: replace get_user_pages with HMM mirror helpers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed?
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
seems this gets triggered by the dolphin emulator, but not under disco kernel 5.0.0-25 with an otherwise eoan system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
** Attachment added: ""bad" memory usage" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+attachment/5290532/+files/Screenshot%20from%202019-09-22%2021-24-40.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: New Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] [NEW] apparent memory usage regression - not getting freed?
Public bug reported: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session ** Attachment added: ""good" memory usage" https://bugs.launchpad.net/bugs/1844962/+attachment/5290516/+files/Screenshot%20from%202019-09-20%2007-01-42.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: New Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago)
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
any chance we can see this in an ubuntu kernel despite the lack of response on lkml? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr 02 13:39:59 taplop kernel: PM: Syncing filesystems ... done. Apr
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
ok thanks, my 2nd attempt at patching 5.0.0.20.21 with v2 appears to be working as well as your older build. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr 02 13:39:59 taplop kernel: PM: Syncing
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
fwiw, i tried to build 5.0.0.20.21 with v2 applied, and was able to reproduce the bug (I may have built it incorrectly though? I git applied the two patches from a clone of git://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/disco and then did `fakeroot debian/rules clean` ; `AUTOBUILD=1 fakeroot debian/rules binary-debs` and installed the resulting packages) tail of journalctl during reproduction: Jul 04 21:48:54 taplop systemd-sleep[11530]: Suspending system... Jul 04 21:48:54 taplop kernel: PM: suspend entry (deep) Jul 04 21:48:58 taplop kernel: PM: Syncing filesystems ... done. Jul 04 21:48:58 taplop kernel: Freezing user space processes ... (elapsed 0.003 seconds) done. Jul 04 21:48:58 taplop kernel: OOM killer disabled. Jul 04 21:48:58 taplop kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jul 04 21:48:58 taplop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Jul 04 21:48:58 taplop kernel: usb usb2: usb auto-resume Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: hub_resume Jul 04 21:48:58 taplop kernel: usb usb1: usb auto-resume Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: hub_resume Jul 04 21:48:58 taplop kernel: usb usb1-port1: status 0507 change Jul 04 21:48:58 taplop kernel: usb usb1-port6: status 0107 change Jul 04 21:48:58 taplop kernel: usb usb1-port10: status 0107 change Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: hub_suspend Jul 04 21:48:58 taplop kernel: usb usb1: bus suspend, wakeup 0 Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: hub_suspend Jul 04 21:48:58 taplop kernel: usb usb2: bus suspend, wakeup 0 Jul 04 21:48:58 taplop kernel: PM: Some devices failed to suspend, or early wake event detected Jul 04 21:48:58 taplop kernel: usb usb1: usb resume Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: hub_resume Jul 04 21:48:58 taplop kernel: usb usb1-port1: status 0507 change Jul 04 21:48:58 taplop kernel: usb usb1-port6: status 0107 change Jul 04 21:48:58 taplop kernel: usb usb1-port10: status 0107 change Jul 04 21:48:58 taplop kernel: usb usb2: usb resume Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: hub_resume Jul 04 21:48:58 taplop kernel: ACPI: button: The lid device is not compliant to SW_LID. Jul 04 21:48:58 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Jul 04 21:48:58 taplop kernel: usb 1-1: usb resume Jul 04 21:48:58 taplop kernel: usb 1-10: usb resume Jul 04 21:48:58 taplop kernel: usb 1-6: usb resume Jul 04 21:48:58 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Jul 04 21:48:58 taplop kernel: usb 1-10: Waited 0ms for CONNECT Jul 04 21:48:58 taplop kernel: usb 1-10: finish resume Jul 04 21:48:58 taplop kernel: usb 1-6: Waited 0ms for CONNECT Jul 04 21:48:58 taplop kernel: usb 1-6: finish resume Jul 04 21:48:58 taplop kernel: usb 1-1: Waited 0ms for CONNECT Jul 04 21:48:58 taplop kernel: usb 1-1: finish resume Jul 04 21:48:58 taplop kernel: [drm] VCE initialized successfully. Jul 04 21:48:58 taplop kernel: nvme nvme0: 8/0/0 default/read/poll queues Jul 04 21:48:58 taplop kernel: amdgpu :01:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test f Jul 04 21:48:58 taplop kernel: amdgpu :01:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test f Jul 04 21:48:58 taplop kernel: amdgpu :01:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test f Jul 04 21:48:58 taplop kernel: [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* ib ring tes Jul 04 21:48:58 taplop kernel: OOM killer enabled. Jul 04 21:48:58 taplop kernel: Restarting tasks ... Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: state 7 ports 8 chg evt Jul 04 21:48:58 taplop kernel: done. Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: hub_suspend Jul 04 21:48:58 taplop kernel: usb usb2: bus auto-suspend, wakeup 1 Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: state 7 ports 16 chg evt 0442 Jul 04 21:48:58 taplop kernel: usb 1-10: usb auto-suspend, wakeup 0 Jul 04 21:48:58 taplop kernel: usb 1-6: usb auto-suspend, wakeup 1 Jul 04 21:48:58 taplop kernel: usb 1-1: usb auto-suspend, wakeup 0 Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: hub_suspend Jul 04 21:48:58 taplop kernel: usb usb1: bus auto-suspend, wakeup 1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
looks like no responses to v2, anything I can do to help move this along? could it at least make it into an updated kernel build with security patches, if not the ubuntu patch set? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel:
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
Either way, whatever fix is in the https://people.canonical.com/~khfeng/lp1823029/ kernel is very effective if not perfect -- can it be put into the main repo kernels or will I need to keep kernel packages held for a while? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
>From reading the logs that's what it looks like -- it appears the lid was closed at 21:48:40 and then suspend was successful at 21:49:10 or 21:49:25, but then the system immediately resumes at 21:49:25, and doesn't fully recover -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]:
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
(but unlike the on-suspend lockup, the journal continues to accumulate some entries -- possible the system wasn't fully locked up but the display was?) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
Had another failure with similar symptoms (fan on, screen black once laptop lid opened), but logs look different this time. ** Attachment added: "differentfailure.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823029/+attachment/5256275/+files/differentfailure.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/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
still looking good after several more sleep cycles today -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr 02 13:39:59 taplop kernel: PM: Syncing filesystems ... done. Apr 02 13:39:59 taplop kernel:
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
initial tests are looking good (4 successful suspends & resumes during this boot so far). Will keep testing and report back. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr 02 13:39:59 taplop
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
linux-modules-extra package looks corrupt: (Reading database ... 367458 files and directories currently installed.) Preparing to unpack linux-modules-extra-5.0.0-11-generic_5.0.0-11.12~lp1823029_amd64.deb ... Unpacking linux-modules-extra-5.0.0-11-generic (5.0.0-11.12~lp1823029) ... dpkg-deb (subprocess): cannot copy archive member from 'linux-modules-extra-5.0.0-11-generic_5.0.0-11.12~lp1823029_amd64.deb' to decompressor pipe: unexpected end of file or stream dpkg-deb (subprocess): decompressing archive member: lzma error: unexpected end of input dpkg-deb: error: subprocess returned error exit status 2 dpkg: error processing archive linux-modules-extra-5.0.0-11-generic_5.0.0-11.12~lp1823029_amd64.deb (--install): cannot copy extracted data for './lib/modules/5.0.0-11-generic/kernel/drivers/net/wireless/marvell/mwifiex/mwifiex.ko' to '/lib/modules/5.0.0-11-generic/kernel/drivers/net/wireless/marvell/mwifiex/mwifiex.ko.dpkg-new': unexpected end of file or stream Errors were encountered while processing: linux-modules-extra-5.0.0-11-generic_5.0.0-11.12~lp1823029_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
Saw same thing with the btmgr commands added to system-sleep script, attaching kernel log from that boot ** Attachment added: "kernel log with btmgr privacy set during system-sleep script" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823029/+attachment/5255096/+files/kern-btprivacy.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
yes, all packages are up to date, and specifically the gnome-bluetooth package at 3.32.1-1 since april 3rd. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr 02 13:39:59 taplop kernel: PM: Syncing
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
ok, have added those commands to a /lib/systemd/system-sleep script to have that happen before suspend and will report back if it helps or not. It appears that with privacy on, my bt mouse doesn't connect anymore, is that expected? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]:
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
here's the bottom of journalctl -b -1 from a boot with "usbcore.dyndbg=+p" that reproduced the issue (let me know if there's a better way to get the kernel log you're looking for): Apr 10 17:31:18 taplop systemd-sleep[8074]: Suspending system... Apr 10 17:31:18 taplop kernel: PM: suspend entry (deep) Apr 10 17:31:18 taplop kernel: PM: Syncing filesystems ... done. Apr 10 17:31:20 taplop kernel: Freezing user space processes ... (elapsed 0.004 seconds) done. Apr 10 17:31:20 taplop kernel: OOM killer disabled. Apr 10 17:31:20 taplop kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Apr 10 17:31:20 taplop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Apr 10 17:31:20 taplop kernel: usb usb2: usb auto-resume Apr 10 17:31:20 taplop kernel: hub 2-0:1.0: hub_resume Apr 10 17:31:20 taplop kernel: hub 2-0:1.0: hub_suspend Apr 10 17:31:20 taplop kernel: usb usb2: bus suspend, wakeup 0 Apr 10 17:31:20 taplop kernel: usb 1-6: usb suspend, wakeup 1 Apr 10 17:31:20 taplop kernel: hub 1-0:1.0: hub_suspend Apr 10 17:31:20 taplop kernel: usb usb1: bus suspend, wakeup 0 Apr 10 17:31:20 taplop kernel: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 Apr 10 17:31:20 taplop kernel: dpm_run_callback(): pci_pm_suspend+0x0/0x130 returns -16 Apr 10 17:31:20 taplop kernel: PM: Device :00:14.0 failed to suspend async: error -16 Apr 10 17:31:20 taplop kernel: PM: Some devices failed to suspend, or early wake event detected Apr 10 17:31:20 taplop kernel: usb usb1: usb resume Apr 10 17:31:20 taplop kernel: hub 1-0:1.0: hub_resume Apr 10 17:31:20 taplop kernel: usb usb1-port1: status 0507 change Apr 10 17:31:20 taplop kernel: usb usb1-port6: status 0103 change 0004 Apr 10 17:31:20 taplop kernel: usb usb1-port10: status 0107 change Apr 10 17:31:20 taplop kernel: usb usb2: usb resume Apr 10 17:31:20 taplop kernel: hub 2-0:1.0: hub_resume Apr 10 17:31:20 taplop kernel: usb 1-6: Waited 0ms for CONNECT Apr 10 17:31:20 taplop kernel: usb 1-6: finish resume Apr 10 17:31:20 taplop kernel: ACPI: button: The lid device is not compliant to SW_LID. Apr 10 17:31:20 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 10 17:31:20 taplop kernel: usb 1-1: usb resume Apr 10 17:31:20 taplop kernel: usb 1-10: usb resume Apr 10 17:31:20 taplop kernel: usb 1-1: Waited 0ms for CONNECT Apr 10 17:31:20 taplop kernel: usb 1-1: finish resume Apr 10 17:31:20 taplop kernel: usb 1-10: Waited 0ms for CONNECT Apr 10 17:31:20 taplop kernel: usb 1-10: finish resume Apr 10 17:31:20 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 10 17:31:20 taplop kernel: nvme nvme0: 8/0/0 default/read/poll queues Apr 10 17:31:20 taplop kernel: [drm] VCE initialized successfully. Apr 10 17:31:20 taplop kernel: OOM killer enabled. Apr 10 17:31:20 taplop kernel: Restarting tasks ... Apr 10 17:31:20 taplop kernel: hub 2-0:1.0: state 7 ports 8 chg evt Apr 10 17:31:20 taplop kernel: hub 1-0:1.0: state 7 ports 16 chg 0040 evt 0402 Apr 10 17:31:20 taplop kernel: usb usb1-port6: status 0103, change , 12 Mb/s Apr 10 17:31:20 taplop kernel: hub 2-0:1.0: hub_suspend Apr 10 17:31:20 taplop kernel: usb usb2: bus auto-suspend, wakeup 1 Apr 10 17:31:20 taplop kernel: done. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]:
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
** Attachment added: "full kernel log from that boot extracted via: journalctl -b-1 -k > kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823029/+attachment/5254820/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
downgrading to the 1.2.0 bios on xps 9575 appears to be working properly (tested 3 reboots with no issues) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9757] Occasionally fails to suspend and locks up instead
Yes, I've seen it on both bionic and cosmic kernels in addition to disco's ** Summary changed: - [Dell XPS 15 9757] Occasionally fails to suspend and locks up instead + [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9757] Occasionally fails to suspend and locks up instead
trying to boot with the 5.1-rc3 kernel resulted in a black screen that never asked for my encrypted drive password. I could ctrl+alt+delete to reboot back to bios/grub, but could not successfully boot the system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9757] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system...
[Kernel-packages] [Bug 1823029] [NEW] [Dell XPS 15 9757] Occasionally fails to suspend and locks up instead
Public bug reported: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr 02 13:39:59 taplop kernel: PM: Syncing filesystems ... done. Apr 02 13:39:59 taplop kernel: Freezing user space processes ... (elapsed 0.003 seconds) done. Apr 02 13:39:59 taplop kernel: OOM killer disabled. Apr 02 13:39:59 taplop kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Apr 02 13:39:59 taplop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Apr 02 13:39:59 taplop kernel: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 Apr 02 13:39:59 taplop kernel:
[Kernel-packages] [Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing
I have issue and my root partition is ext4. `mount` is full of other crap I don't understand but I don't think any of it's "real" drives. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722778 Title: System frequently becomes completely unresponsive due to thrashing Status in linux package in Ubuntu: Confirmed Bug description: To replicate: Run firefox for a couple of hours. Expected results: All open applications should run normally: occasional slowdown for page faults are tolerable but the observed behaviour is not. Actual results: Several times per day my computer will become completely unresponsive apart from high hard disk activity. Once it enters this state: it will not recover without a hard reset regardless of any time waited or input given. On one occasion I have tested it by leaving it thrashing for 12 hours, at the end of which there was no evidence of progress. This behaviour was not observed when running Ubuntu 16.04 on the same computer and swap settings. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jeremy 3367 F...m pulseaudio /dev/snd/controlC0: jeremy 3367 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 00:41:01 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=6ef78518-5d77-4673-9917-36ed31b247d9 InstallationDate: Installed on 2017-08-15 (56 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 80TV ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-12-generic root=UUID=f2087105-8407-42b8-af6c-f00fe6846c51 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-09-14 (27 days ago) dmi.bios.date: 03/07/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-15IKB dmi.modalias: dmi:bvnLENOVO:bvr3JCN26WW:bd03/07/2017:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnVIUU4:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80TV dmi.product.version: Lenovo ideapad 310-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport
Hi, Still present in latest i386 Bionic 18.04.02 LTS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800901] Re: Updating breaks wifi on Intel Compute Stick
After the bios update the issues that occurred after the apt-get upgrade have disappeared. Let's mark this as closed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800901 Title: Updating breaks wifi on Intel Compute Stick Status in linux package in Ubuntu: Incomplete Bug description: On an Intel Compute Stick model STCK1A8LFC the stock install works fine. The default kernel: uname -a Linux joe-STCK1A8LFC 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux When an apt-get update/upgrade is run all network connectivity is lost. Run wpa_cli scan shows no networks at all. A return to the factory default returns connectivity. Any help would be greatly appreciated. Cheers,-Joe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800901] Re: Updating breaks wifi on Intel Compute Stick
I updated to the most recent Bios from Intel FC0038: https://downloadcenter.intel.com/download/28070/BIOS-Update-FCBYT10H- 86A- Initial result is faster network access after power up and connectivity remains working after 10 reboots. *-firmware description: BIOS vendor: Intel Corp. physical id: 0 version: FCBYT10H.86A.0038.2018.0802.1745 date: 08/02/2018 size: 64KiB capacity: 6528KiB capabilities: pci upgrade shadowing cdboot bootselect edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int14serial int17printer acpi usb biosbootspecification uefi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800901 Title: Updating breaks wifi on Intel Compute Stick Status in linux package in Ubuntu: Incomplete Bug description: On an Intel Compute Stick model STCK1A8LFC the stock install works fine. The default kernel: uname -a Linux joe-STCK1A8LFC 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux When an apt-get update/upgrade is run all network connectivity is lost. Run wpa_cli scan shows no networks at all. A return to the factory default returns connectivity. Any help would be greatly appreciated. Cheers,-Joe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800901] Re: Updating breaks wifi on Intel Compute Stick
Notes as it is currently unreliable on WiFi, making appport-collect hard. After restoring from the recovery partition I am able to add this WPA2 network. I then run apt-get upgrade and it gets buggy. Thanks for helping out. root@joe-STCK1A8LFC:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: chestersmill-settings cups-filters cups-filters-core-drivers grub-common grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed grub2-common linux-generic-lts-utopic linux-headers-generic-lts-utopic linux-image-generic-lts-utopic linux-signed-generic-lts-utopic linux-signed-image-generic-lts-utopic python3-software-properties python3-update-manager qpdf shim shim-signed software-properties-common software-properties-gtk update-manager update-manager-core update-notifier update-notifier-common The following packages will be upgraded: accountsservice activity-log-manager activity-log-manager-control-center apparmor apparmor-easyprof apport apport-gtk apt apt-transport-https apt-utils aptdaemon aptdaemon-data apturl apturl-common avahi-autoipd avahi-daemon avahi-utils base-files bash bash-completion bind9-host binutils bluez bluez-cups bsdutils btrfs-tools ca-certificates click click-apparmor compiz compiz-core compiz-gnome compiz-plugins-default coreutils cpio cpp-4.8 cups cups-browsed cups-bsd cups-client cups-common cups-core-drivers cups-daemon cups-ppdc cups-server-common dbus dbus-x11 desktop-file-utils dh-python dkms dnsmasq-base dnsutils dosfstools dpkg e2fslibs e2fsprogs ecryptfs-utils efibootmgr eject empathy empathy-common eog evince evince-common evolution-data-server evolution-data-server-common evolution-data-server-online-accounts file file-roller fontconfig fontconfig-config fonts-droid fonts-opensymbol fuse gcc-4.8 gcc-4.8-base gcc-4.9-base gdb gdisk ghostscript ghostscript-x gir1.2-click-0.4 gir1.2-ebook-1.2 gir1.2-ebookcontacts-1.2 gir1.2-edataserver-1.2 gir1.2-gdkpixbuf-2.0 gir1.2-gst-plugins-base-1.0 gir1.2-gstreamer-1.0 gir1.2-gtk-3.0 gir1.2-gudev-1.0 gir1.2-ibus-1.0 gir1.2-javascriptcoregtk-3.0 gir1.2-networkmanager-1.0 gir1.2-soup-2.4 gir1.2-udisks-2.0 gir1.2-vte-2.90 gir1.2-webkit-3.0 gir1.2-wnck-3.0 glib-networking glib-networking-common glib-networking-services gnome-contacts gnome-desktop3-data gnome-keyring gnome-user-guide gnupg gpgv gstreamer0.10-plugins-base gstreamer0.10-plugins-base-apps gstreamer0.10-plugins-good gstreamer0.10-pulseaudio gstreamer0.10-x gstreamer1.0-plugins-base gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good gstreamer1.0-pulseaudio gstreamer1.0-tools gstreamer1.0-x gvfs gvfs-backends gvfs-bin gvfs-common gvfs-daemons gvfs-fuse gvfs-libs hplip hplip-data ibus ibus-gtk ibus-gtk3 ifupdown im-config indicator-session init-system-helpers initramfs-tools initramfs-tools-bin initscripts iproute iproute2 irqbalance isc-dhcp-client isc-dhcp-common klibc-utils kmod kpartx kpartx-boot krb5-locales landscape-client-ui-install libaccountsservice0 libapparmor-perl libapparmor1 libapt-inst1.5 libapt-pkg4.12 libarchive-zip-perl libarchive13 libasan0 libasn1-8-heimdal libatomic1 libavahi-client3 libavahi-common-data libavahi-common3 libavahi-core7 libavahi-glib1 libavahi-gobject0 libbind9-90 libblkid1 libbluetooth3 libc-bin libc-dev-bin libc6 libc6-dev libcamel-1.2-45 libcgmanager0 libclick-0.4-0 libcomerr2 libcompizconfig0 libcups2 libcupscgi1 libcupsfilters1 libcupsimage2 libcupsmime1 libcupsppdc1 libcurl3 libcurl3-gnutls libdb5.3 libdbus-1-3 libdebian-installer4 libdecoration0 libdns100 libdpkg-perl libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libebackend-1.2-7 libebook-1.2-14 libebook-contacts-1.2-0 libecal-1.2-16 libecryptfs0 libedata-book-1.2-20 libedata-cal-1.2-23 libedataserver-1.2-18 libelf1 libevdocument3-4 libevview3-3 libexempi3 libexiv2-12 libexpat1 libffi6 libfontconfig1 libfontembed1 libfreerdp1 libfreetype6 libfuse2 libgail-3-0 libgail-common libgail18 libgbm1 libgc1c2 libgcc-4.8-dev libgcc1 libgcrypt11 libgd3 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libglib2.0-0 libglib2.0-bin libglib2.0-data libgnome-desktop-3-7 libgnutls-openssl27 libgnutls26 libgomp1 libgraphite2-3 libgs9 libgs9-common libgssapi-krb5-2 libgssapi3-heimdal libgstreamer-plugins-base0.10-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 libgtk-3-0 libgtk-3-bin libgtk-3-common libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgudev-1.0-0 libgweather-3-6 libgweather-common libharfbuzz-icu0 libharfbuzz0b libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhpmud0 libhunspell-1.3-0 libhx509-5-heimdal libibus-1.0-5 libicu52 libidn11 libido3-0.1-0 libimobiledevice4 libisc95 libisccc90 libisccfg90 libitm1 libjasper1 libjavascriptcoregtk-3.0-0 libjbig2dec0 libjpeg-turbo8 libk5crypto3
[Kernel-packages] [Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Hi, I would like to confirm this as this also affects not only my client but also my Colleagues (thinkpad T460s and T470s). The Problem seem to occur after a few minutes of inactiviy randomly. Some experience this 3-4 times/day while some 2-5 times a week. Running on Ubuntu Bionic 18.04 Kernel Version: 4.15.0-36-generic Kernel Log is attached. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5205731/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1727662 Title: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in Linux: Invalid Status in linux package in Ubuntu: Confirmed Bug description: What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the following three things happen ~50% of the time when I come back to unlock it: * Most of the time the computer is found shut down. * Sometimes the notebook screen flickers weirdly and one of the two external monitors show pixelation. * The notebook screen shows the lock screen but is completely frozen. Occasionally unlocking works. I have two external monitors attached to the docking station. When I dock my laptop, the battery indicator does recognize its charging. I've not seen this issue when: 1) With the laptop in the dock, while actively using the laptop. 2) With the laptop out of the dock and no external monitors present. This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10. Using or not using the following kernel parameter didn't change anything: i915.enable_rc6=0 Updated docking station firmware to latest 2.33.00. PC temperatures are normal as per lm-sensors. 20171109 - Not reproducible testing drm-tip for 1.5 days. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: akops 3337 F pulseaudio /dev/snd/controlC0: akops 3337 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:44:11 2017 HibernationDevice: RESUME=/dev/mapper/system-swap_1 MachineType: LENOVO 20BWS2YL00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS2YL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS2YL00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1727662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
