[Kernel-packages] [Bug 2054121] Re: Random whole system lockups on Lenovo ThinkStation P350 Tiny
Should I still submit logs?
I think I'll just buy a new PC w/o NVIDIA and re-purpose this one...
Here is the latest
Lockup 070244 - SSL not avail
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5758328/+files/prevboot.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/2054121
Title:
Random whole system lockups on Lenovo ThinkStation P350 Tiny
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
I see the status change of the bug. Did the logs finally show anything?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
17:15:47 - SSL not avail
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5757691/+files/prevboot.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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
Incomplete
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
Got it. Testing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
Incomplete
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
9:14:36 No SSL Possible. Attached.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5756414/+files/prevboot.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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
Incomplete
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
Trying to upload the latest file. It's 1.3 G
Uh oh!
Something has gone wrong. We're sorry!
If we are in the middle of an update, Launchpad will be back in a couple
of minutes. Otherwise, we are working to fix the unexpected problems.
Check @launchpadstatus on Twitter or @launchpadstatus@ubuntu.social on
Mastodon for updates.
If the problem persists, let us know in the #launchpad IRC channel on
libera.chat.
Technically, the load balancer took too long to connect to an
application server.
Reload this page or try again in a few minutes
No one on Launchpad chat responds to 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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
Incomplete
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
I'm not sure how to do this:
"drm.debug=0xff loglevel=8"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
Came in this morning and it was locked up. NO SSH.
Going to move back to 6.5
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5755959/+files/prevboot.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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
What kernel do you suggest.
Disabling NVIDA isn't an option. I need all 4 monitors.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
130538 full lockup, no ssh available.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5755711/+files/prevboot.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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
110230 - Locked up, but instead of staying locked up the desktop crashed
and took me to the login screen.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5755691/+files/prevboot.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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
uname -r
5.19.17-051917-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
Still lockups- No ssh
18:08:04 attached
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5755386/+files/prevboot.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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
Ok, running 6.8.
uname -r
6.8.0-060800rc7-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
Newest or a specific one?
Never locks up if I run Windows and passes all hardware testing
(repeated testing for overnight/ several passes)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
Should I continue to report this? Is there anything else?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
Ssh works fine until it freezes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
And another. Crash at 85128
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5754304/+files/prevboot.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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
Incomplete
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
Here is the latest crash file.
Unresponsive - even trying ssh won't work
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5754028/+files/prevboot.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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
Incomplete
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
I am running the x.org X server Nouveau display driver now. I will
advise.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
Incomplete
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
Use x.org X server Nouveau dissplay drivers?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
Incomplete
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049092] [NEW] summary of a possible bug fix. I have not seen this bug for some time.
Public bug reported: Some years ago I had this bug with my Lenovo X1 computers. The problem was that a left mouse click was received, but then releasing the button, the click was not turned off. I used this program to test the problem: >> sudo evtest /dev/input/event15 | grep EV_KEY This will tell you which event to type in. The left mouse key seems to be 8 then I click on left most mouse button. Nothing happens. The command should report an error when the mouse-left is released I just tried to trigger the bug, and it seems to be fixed. I would suggest setting this bug "CLOSED" If needed you can contact me at http://auditorymodels.org I suspect this was fixed a long time ago, but was never confirmed. I consider it fixed, and someone who can, should close the bug report. Version log: Ubuntu 5.15.0-1045.51-intel-iotg 5.15.126 00:00.0 Host bridge [0600]: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers [8086:9a14] (rev 01) Subsystem: Lenovo 11th Gen Core Processor Host Bridge/DRAM Registers [17aa:22d5] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: igen6_edac 00:02.0 VGA compatible controller [0300]: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d5] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled, AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit- Address: fee40004 Data: 0024 Masking: Pending: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Jont Allen Jan 11 2024. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049092 Title: summary of a possible bug fix. I have not seen this bug for some time. Status in linux package in Ubuntu: New Bug description: Some years ago I had this bug with my Lenovo X1 computers. The problem was that a left mouse click was received, but then releasing the button, the click was not turned off. I used this program to test the problem: >> sudo evtest /dev/input/event15 | grep EV_KEY This will tell you which event to type in. The left mouse key seems to be 8 then I click on left most mouse button. Nothing happens. The command should report an error when the mouse-left is released I just tried to trigger the bug, and it seems to be fixed. I would suggest setting this bug "CLOSED" If needed you can contact me at http://auditorymodels.org I suspect this was fixed a long time ago, but was never confirmed. I consider it fixed, and someone who can, should close the bug report. Version log: Ubuntu 5.15.0-1045.51-intel-iotg 5.15.126 00:00.0 Host bridge [0600]: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers [8086:9a14] (rev 01) Subsyste
[Kernel-packages] [Bug 2043061] [NEW] System suspension is encountered on Ubuntu 23.10 RISC-V image on VisionFive 2
Public bug reported: After the user has installed and used Ubuntu 23.10 on VisionFive 2 (Model 1.3B), his system is always suspended with slow or no response. StarFive FAE has reproduced the issue in the following practices. 1. Install the Ubuntu system on VisionFive 2. 2. Type in the account "ubuntu" several times with deliberate mistakes. 3. The system is suspended with no response. Find the screenshot attached. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Ubuntu_2310_error_VF2.png" https://bugs.launchpad.net/bugs/2043061/+attachment/5717388/+files/Ubuntu_2310_error_VF2.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2043061 Title: System suspension is encountered on Ubuntu 23.10 RISC-V image on VisionFive 2 Status in linux-riscv package in Ubuntu: New Bug description: After the user has installed and used Ubuntu 23.10 on VisionFive 2 (Model 1.3B), his system is always suspended with slow or no response. StarFive FAE has reproduced the issue in the following practices. 1. Install the Ubuntu system on VisionFive 2. 2. Type in the account "ubuntu" several times with deliberate mistakes. 3. The system is suspended with no response. Find the screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2043061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023986] Re: Drivers not working using kernel linux-image-6.2.0-1003-oracle
I'm having the same issue, in order to get around it I had to use the generic 6.2.0-20-generic kernel as well! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2023986 Title: Drivers not working using kernel linux-image-6.2.0-1003-oracle Status in linux-signed-oracle package in Ubuntu: Confirmed Bug description: My Ubuntu 23.04 installed two kernels linux-image-6.2.0-1003-oracle and linux-image-6.2.0-1003-lowlatency using software updater along with other updates. After install and restart, most drivers including wifi, bluetooth, touchpad and ethernet stopped working. Rebooting using 6.2.0-1003-lowlatency or 6.2.0-20-generic solved the driver issues. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-1003-oracle 6.2.0-1003.3 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 Uname: Linux 6.2.0-1003-lowlatency x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 15 16:34:56 2023 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oracle/+bug/2023986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018687] Re: rm -r dir on USB disk locks up hdparm on different disk
Unfortunately, an unacceptable side-effect of "sysctl -w
vm.dirty_ratio=0" is that disk operations that move a lot of data are
taking much too long. An rsync that normally takes less than an hour of
real time was still running over 12 hours later (and hasn't finished
yet). I'm reverting the vm.dirty_ratio back up to 20 to see if that
clears out all the unfinished disk I/O.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2018687
Title:
rm -r dir on USB disk locks up hdparm on different disk
Status in linux-meta-hwe-5.15 package in Ubuntu:
New
Bug description:
Description:Ubuntu 20.04.6 LTS
Linux 5.15.0-72-generic #79~20.04.1-Ubuntu SMP Thu Apr 20 22:12:07 UTC 2023
x86_64 GNU/Linux
Intel(R) Xeon(R) CPU E5-1620 v4 @ 3.50GHz
Running a "rm -r dir" on a directory with millions of files that resides
on a disk in an external USB-3 hard drive dock locks up an unrelated
hdparm processes running on an internal disk such that the kernel says:
May 7 04:24:02 kernel: [163606.041862] INFO: task hdparm:1391162 blocked
for more than 120 seconds.
[...]
May 7 04:26:03 kernel: [163726.876357] INFO: task hdparm:1391162 blocked
for more than 241 seconds.
[...]
May 7 04:28:04 kernel: [163847.702980] INFO: task hdparm:1391162 blocked
for more than 362 seconds.
First a normal run of "hdparm -t /dev/sda" with the offending "rm -r"
SIGSTOPped so that
it doesn't affect anything:
#Â \time hdparm -t /dev/sda
/dev/sda:
 Timing buffered disk reads: 1128 MB in 3.00 seconds = 375.50 MB/sec
0.01user 0.67system 0:06.21elapsed 11%CPU (0avgtext+0avgdata
4584maxresident)k
2312704inputs+8outputs (0major+664minor)pagefaults 0swaps
Elapsed time is about six seconds, as expected. /dev/sda is an
internal SSD drive.
I now run this loop to show the timings and process states below:
#Â while sleep 1 ; do date ; ps laxww | grep '[ ]D' | grep -v
refrig ; done
(I have some processes stopped in a freezer cgroup ("refrig") that I
don't want to see in the grep output.) I SIGCONT the offending "rm -r"
running on the drive in the USB3 drive dock and you see the rm appear
in uninterruptible sleep along with a couple of kernel processes:
Sun May 7 05:01:07 EDT 2023
Sun May 7 05:01:08 EDT 2023
Sun May 7 05:01:09 EDT 2023
Sun May 7 05:01:10 EDT 2023
Sun May 7 05:01:11 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
4 0 1423283 11939 20 0 10648 580 wait_o D+ pts/28 0:00
rm -rf 15tb3
Sun May 7 05:01:12 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
1 04016 1 20 0 161136 1900 usbhid Dsl ? 1:39
/sbin/apcupsd
4 0 1423283 11939 20 0 10648 580 wait_o D+ pts/28 0:00
rm -rf 15tb3
Sun May 7 05:01:13 EDT 2023
The above lines showing those processes in uninterruptible sleep repeat
over and over each second as the "rm -r" continues. I then start up
"hdparm -t /dev/sda" on the internal SSD disk, and it also appears in
uninterruptible sleep and doesn't finish even after minutes of waiting:
Sun May 7 05:01:25 EDT 2023
1 0 368 2 20 0 0 0 md_sup D? 2:57
[md0_raid5]
1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[kworker/u16:2+flush-8:144]
4 0 1423283 11939 20 0 11260 2544 wait_o D+ pts/28 0:00
rm -rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:26 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[kworker/u16:2+flush-8:144]
4 0 1423283 11939 20 0 11260 2544 wait_o D+ pts/28 0:00
rm -rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:27 EDT 2023
[...]
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:35 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
4 0 1423283 11939 20 0 11260 2544 blk_mq D+ pts/28 0:00
rm -rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:36 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
1 04985 2 20 0 0 0 rq_qos D? 0:24
[jbd2/sdj1-8]
1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[Kernel-packages] [Bug 2018687] Re: rm -r dir on USB disk locks up hdparm on different disk
If I do this:
# sysctl -w vm.dirty_ratio=0
the hdparm no longer hangs. It has to be zero; anything non-zero, even
1, causes large delays in disk-related commands such as hdparm, sync,
smartctl, etc.
I got this idea from here:
https://serverfault.com/questions/405210/can-high-load-cause-server-
hang-and-error-blocked-for-more-than-120-seconds
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2018687
Title:
rm -r dir on USB disk locks up hdparm on different disk
Status in linux-meta-hwe-5.15 package in Ubuntu:
New
Bug description:
Description:Ubuntu 20.04.6 LTS
Linux 5.15.0-72-generic #79~20.04.1-Ubuntu SMP Thu Apr 20 22:12:07 UTC 2023
x86_64 GNU/Linux
Intel(R) Xeon(R) CPU E5-1620 v4 @ 3.50GHz
Running a "rm -r dir" on a directory with millions of files that resides
on a disk in an external USB-3 hard drive dock locks up an unrelated
hdparm processes running on an internal disk such that the kernel says:
May 7 04:24:02 kernel: [163606.041862] INFO: task hdparm:1391162 blocked
for more than 120 seconds.
[...]
May 7 04:26:03 kernel: [163726.876357] INFO: task hdparm:1391162 blocked
for more than 241 seconds.
[...]
May 7 04:28:04 kernel: [163847.702980] INFO: task hdparm:1391162 blocked
for more than 362 seconds.
First a normal run of "hdparm -t /dev/sda" with the offending "rm -r"
SIGSTOPped so that
it doesn't affect anything:
#Â \time hdparm -t /dev/sda
/dev/sda:
 Timing buffered disk reads: 1128 MB in 3.00 seconds = 375.50 MB/sec
0.01user 0.67system 0:06.21elapsed 11%CPU (0avgtext+0avgdata
4584maxresident)k
2312704inputs+8outputs (0major+664minor)pagefaults 0swaps
Elapsed time is about six seconds, as expected. /dev/sda is an
internal SSD drive.
I now run this loop to show the timings and process states below:
#Â while sleep 1 ; do date ; ps laxww | grep '[ ]D' | grep -v
refrig ; done
(I have some processes stopped in a freezer cgroup ("refrig") that I
don't want to see in the grep output.) I SIGCONT the offending "rm -r"
running on the drive in the USB3 drive dock and you see the rm appear
in uninterruptible sleep along with a couple of kernel processes:
Sun May 7 05:01:07 EDT 2023
Sun May 7 05:01:08 EDT 2023
Sun May 7 05:01:09 EDT 2023
Sun May 7 05:01:10 EDT 2023
Sun May 7 05:01:11 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
4 0 1423283 11939 20 0 10648 580 wait_o D+ pts/28 0:00
rm -rf 15tb3
Sun May 7 05:01:12 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
1 04016 1 20 0 161136 1900 usbhid Dsl ? 1:39
/sbin/apcupsd
4 0 1423283 11939 20 0 10648 580 wait_o D+ pts/28 0:00
rm -rf 15tb3
Sun May 7 05:01:13 EDT 2023
The above lines showing those processes in uninterruptible sleep repeat
over and over each second as the "rm -r" continues. I then start up
"hdparm -t /dev/sda" on the internal SSD disk, and it also appears in
uninterruptible sleep and doesn't finish even after minutes of waiting:
Sun May 7 05:01:25 EDT 2023
1 0 368 2 20 0 0 0 md_sup D? 2:57
[md0_raid5]
1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[kworker/u16:2+flush-8:144]
4 0 1423283 11939 20 0 11260 2544 wait_o D+ pts/28 0:00
rm -rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:26 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[kworker/u16:2+flush-8:144]
4 0 1423283 11939 20 0 11260 2544 wait_o D+ pts/28 0:00
rm -rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:27 EDT 2023
[...]
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:35 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
4 0 1423283 11939 20 0 11260 2544 blk_mq D+ pts/28 0:00
rm -rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:36 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
1 04985 2 20 0 0 0 rq_qos D? 0:24
[jbd2/sdj1-8]
1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[Kernel-packages] [Bug 2018687] Re: rm -r dir on USB disk locks up hdparm on different disk
I now have a Perl script running that is removing duplicate files by doing thousands of hard links on a different external USB3 disk and it is locking up or timing out many disk-related things on all my other disks. Both this USB3 external drive and the one above are plugged directly into the motherboard (HP Z440 Workstation). F UID PIDPPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 4 0 2210112 2210111 20 0 53680 42588 blk_mq D+ pts/24 3:00 /usr/bin/perl [...] May 14 13:37:49 kernel: [259424.745462] INFO: task smartd:2719 blocked for more than 120 seconds. May 15 00:08:09 kernel: [297244.761855] INFO: task smartd:2719 blocked for more than 120 seconds. May 15 00:10:10 kernel: [297365.592485] INFO: task smartd:2719 blocked for more than 241 seconds. May 15 01:08:34 kernel: [300869.682961] INFO: task smartd:2719 blocked for more than 120 seconds. May 15 01:28:43 kernel: [302077.989582] INFO: task hdparm:2052842 blocked for more than 120 seconds. May 15 01:30:43 kernel: [302198.820278] INFO: task hdparm:2052842 blocked for more than 241 seconds. May 15 01:32:44 kernel: [302319.654907] INFO: task hdparm:2052842 blocked for more than 362 seconds. May 15 01:34:45 kernel: [302440.481601] INFO: task hdparm:2052842 blocked for more than 483 seconds. May 15 01:36:46 kernel: [302561.316237] INFO: task hdparm:2052842 blocked for more than 604 seconds. May 15 02:06:58 kernel: [304373.770194] INFO: task smartd:2719 blocked for more than 120 seconds. From one of the logged events: May 15 02:06:58 kernel: [304373.770194] INFO: task smartd:2719 blocked for more than 120 seconds. May 15 02:06:58 kernel: [304373.770209] Tainted: G O 5.15.0-72-generic #79~20.04.1-Ubuntu May 15 02:06:58 kernel: [304373.770215] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. May 15 02:06:58 kernel: [304373.770218] task:smartd state:D stack: 0 pid: 2719 ppid: 1 flags:0x May 15 02:06:58 kernel: [304373.770226] Call Trace: May 15 02:06:58 kernel: [304373.770230] May 15 02:06:58 kernel: [304373.770236] __schedule+0x2cd/0x890 May 15 02:06:58 kernel: [304373.770251] schedule+0x69/0x110 May 15 02:06:58 kernel: [304373.770260] schedule_preempt_disabled+0xe/0x20 May 15 02:06:58 kernel: [304373.770269] __mutex_lock.isra.0+0x20c/0x470 May 15 02:06:58 kernel: [304373.770276] ? iput.part.0+0x61/0x1e0 May 15 02:06:58 kernel: [304373.770287] __mutex_lock_slowpath+0x13/0x20 May 15 02:06:58 kernel: [304373.770294] mutex_lock+0x36/0x40 May 15 02:06:58 kernel: [304373.770299] blkdev_get_by_dev+0x11d/0x2d0 May 15 02:06:58 kernel: [304373.770309] ? blkdev_close+0x30/0x30 May 15 02:06:58 kernel: [304373.770318] blkdev_open+0x50/0x90 May 15 02:06:58 kernel: [304373.770325] do_dentry_open+0x169/0x3e0 May 15 02:06:58 kernel: [304373.770336] vfs_open+0x2d/0x40 May 15 02:06:58 kernel: [304373.770342] do_open.isra.0+0x20d/0x480 May 15 02:06:58 kernel: [304373.770351] path_openat+0x18e/0xe50 May 15 02:06:58 kernel: [304373.770361] ? put_device+0x13/0x20 May 15 02:06:58 kernel: [304373.770371] ? scsi_device_put+0x31/0x40 May 15 02:06:58 kernel: [304373.770380] ? sd_release+0x3b/0xb0 May 15 02:06:58 kernel: [304373.770388] do_filp_open+0xb2/0x120 May 15 02:06:58 kernel: [304373.770398] ? __check_object_size+0x14f/0x160 May 15 02:06:58 kernel: [304373.770408] do_sys_openat2+0x249/0x330 May 15 02:06:58 kernel: [304373.770418] do_sys_open+0x46/0x80 May 15 02:06:58 kernel: [304373.770424] __x64_sys_openat+0x20/0x30 May 15 02:06:58 kernel: [304373.770430] do_syscall_64+0x5c/0xc0 May 15 02:06:58 kernel: [304373.770440] ? do_syscall_64+0x69/0xc0 May 15 02:06:58 kernel: [304373.770448] entry_SYSCALL_64_after_hwframe+0x61/0xcb May 15 02:06:58 kernel: [304373.770458] RIP: 0033:0x7f9b0d188d3b May 15 02:06:58 kernel: [304373.770465] RSP: 002b:7ffd72a3caf0 EFLAGS: 0246 ORIG_RAX: 0101 May 15 02:06:58 kernel: [304373.770473] RAX: ffda RBX: 55f1346783c0 RCX: 7f9b0d188d3b May 15 02:06:58 kernel: [304373.770479] RDX: 0800 RSI: 55f1346783f8 RDI: ff9c May 15 02:06:58 kernel: [304373.770484] RBP: 55f1346783f8 R08: 0001 R09: May 15 02:06:58 kernel: [304373.770488] R10: R11: 0246 R12: 0800 May 15 02:06:58 kernel: [304373.770493] R13: R14: 55f1334c26a4 R15: 7f9b0cd17250 May 15 02:06:58 kernel: [304373.770500] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2018687 Title: rm -r dir on USB disk locks up hdparm on different disk Status in linux-meta-hwe-5.15 package in Ubuntu: New Bug description: Description:Ubuntu 20.04.6 LTS Linux 5.15.0-72-generic #79~20.04.1-Ubuntu SMP Thu Apr 20 22:12:07 UTC 2023 x86_64 GNU/Linux Intel(R) Xeon(R)
[Kernel-packages] [Bug 2018687] Re: rm -r dir on USB disk locks up hdparm on different disk
** Description changed:
Description:Ubuntu 20.04.6 LTS
Linux 5.15.0-72-generic #79~20.04.1-Ubuntu SMP Thu Apr 20 22:12:07 UTC 2023
x86_64 GNU/Linux
Intel(R) Xeon(R) CPU E5-1620 v4 @ 3.50GHz
Running a "rm -r dir" on a directory with millions of files that resides
on a disk in an external USB-3 hard drive dock locks up an unrelated
hdparm processes running on an internal disk such that the kernel says:
- May 7 04:24:02 kernel: [163606.041862] INFO: task hdparm:1391162 blocked
for more than 120 seconds.
+ May 7 04:24:02 kernel: [163606.041862] INFO: task hdparm:1391162 blocked
for more than 120 seconds.
+ [...]
+ May 7 04:26:03 kernel: [163726.876357] INFO: task hdparm:1391162 blocked
for more than 241 seconds.
+ [...]
+ May 7 04:28:04 kernel: [163847.702980] INFO: task hdparm:1391162 blocked
for more than 362 seconds.
[...]
- May 7 04:26:03 kernel: [163726.876357] INFO: task hdparm:1391162 blocked
for more than 241 seconds.
- [...]
- May 7 04:28:04 kernel: [163847.702980] INFO: task hdparm:1391162 blocked
for more than 362 seconds.
+ May 7 04:30:05 kernel: [163968.537842] INFO: task hdparm:1391162 blocked
for more than 483 seconds.
First a normal run of "hdparm -t /dev/sda" with the offending "rm -r"
SIGSTOPped so that
it doesn't affect anything:
- #Â \time hdparm -t /dev/sda
- /dev/sda:
- Timing buffered disk reads: 1128 MB in 3.00 seconds = 375.50 MB/sec
- 0.01user 0.67system 0:06.21elapsed 11%CPU (0avgtext+0avgdata
4584maxresident)k
- 2312704inputs+8outputs (0major+664minor)pagefaults 0swaps
+ #Â \time hdparm -t /dev/sda
+ /dev/sda:
+ Â Timing buffered disk reads: 1128 MB in 3.00 seconds = 375.50 MB/sec
+ 0.01user 0.67system 0:06.21elapsed 11%CPU (0avgtext+0avgdata
4584maxresident)k
+ 2312704inputs+8outputs (0major+664minor)pagefaults 0swaps
Elapsed time is about six seconds, as expected. /dev/sda is an internal
SSD drive.
I now run this loop to show the timings and process states below:
- #Â while sleep 1 ; do date ; ps laxww | grep '[ ]D' | grep -v refrig
+ #Â while sleep 1 ; do date ; ps laxww | grep '[ ]D' | grep -v refrig
; done
(I have some processes stopped in a freezer cgroup ("refrig") that I
don't want to see in the grep output.) I SIGCONT the offending "rm -r"
running on the drive in the USB3 drive dock and you see the rm appear
in uninterruptible sleep along with a couple of kernel processes:
- Sun May 7 05:01:07 EDT 2023
- Sun May 7 05:01:08 EDT 2023
- Sun May 7 05:01:09 EDT 2023
- Sun May 7 05:01:10 EDT 2023
- Sun May 7 05:01:11 EDT 2023
- 1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
- 4 0 1423283 11939 20 0 10648 580 wait_o D+ pts/28 0:00
rm -rf 15tb3
- Sun May 7 05:01:12 EDT 2023
- 1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
- 1 04016 1 20 0 161136 1900 usbhid Dsl ? 1:39
/sbin/apcupsd
- 4 0 1423283 11939 20 0 10648 580 wait_o D+ pts/28 0:00
rm -rf 15tb3
- Sun May 7 05:01:13 EDT 2023
+ Sun May 7 05:01:07 EDT 2023
+ Sun May 7 05:01:08 EDT 2023
+ Sun May 7 05:01:09 EDT 2023
+ Sun May 7 05:01:10 EDT 2023
+ Sun May 7 05:01:11 EDT 2023
+ 1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
+ 4 0 1423283 11939 20 0 10648 580 wait_o D+ pts/28 0:00
rm -rf 15tb3
+ Sun May 7 05:01:12 EDT 2023
+ 1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
+ 1 04016 1 20 0 161136 1900 usbhid Dsl ? 1:39
/sbin/apcupsd
+ 4 0 1423283 11939 20 0 10648 580 wait_o D+ pts/28 0:00
rm -rf 15tb3
+ Sun May 7 05:01:13 EDT 2023
The above lines showing those processes in uninterruptible sleep repeat
over and over each second as the "rm -r" continues. I then start up
"hdparm -t /dev/sda" on the internal SSD disk, and it also appears in
uninterruptible sleep and doesn't finish even after minutes of waiting:
- Sun May 7 05:01:25 EDT 2023
- 1 0 368 2 20 0 0 0 md_sup D? 2:57
[md0_raid5]
- 1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[kworker/u16:2+flush-8:144]
- 4 0 1423283 11939 20 0 11260 2544 wait_o D+ pts/28 0:00
rm -rf 15tb3
- 4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
- Sun May 7 05:01:26 EDT 2023
- 1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
- 1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[kworker/u16:2+flush-8:144]
- 4 0 1423283 11939 20 0 11260 2544 wait_o D+ pts/28 0:00
rm -rf
[Kernel-packages] [Bug 2018687] Re: rm -r dir on USB disk locks up hdparm on different disk
** Description changed:
Description:Ubuntu 20.04.6 LTS
Linux 5.15.0-72-generic #79~20.04.1-Ubuntu SMP Thu Apr 20 22:12:07 UTC 2023
x86_64 GNU/Linux
Intel(R) Xeon(R) CPU E5-1620 v4 @ 3.50GHz
Running a "rm -r dir" on a directory with millions of files that resides
on a disk in an external USB-3 hard drive dock locks up an unrelated
hdparm processes running on an internal disk such that the kernel says:
May 7 04:24:02 kernel: [163606.041862] INFO: task hdparm:1391162 blocked
for more than 120 seconds.
[...]
May 7 04:26:03 kernel: [163726.876357] INFO: task hdparm:1391162 blocked
for more than 241 seconds.
[...]
May 7 04:28:04 kernel: [163847.702980] INFO: task hdparm:1391162 blocked
for more than 362 seconds.
- [...]
- May 7 04:30:05 kernel: [163968.537842] INFO: task hdparm:1391162 blocked
for more than 483 seconds.
First a normal run of "hdparm -t /dev/sda" with the offending "rm -r"
SIGSTOPped so that
it doesn't affect anything:
#Â \time hdparm -t /dev/sda
/dev/sda:
 Timing buffered disk reads: 1128 MB in 3.00 seconds = 375.50 MB/sec
0.01user 0.67system 0:06.21elapsed 11%CPU (0avgtext+0avgdata
4584maxresident)k
2312704inputs+8outputs (0major+664minor)pagefaults 0swaps
Elapsed time is about six seconds, as expected. /dev/sda is an internal
SSD drive.
I now run this loop to show the timings and process states below:
#Â while sleep 1 ; do date ; ps laxww | grep '[ ]D' | grep -v refrig
; done
(I have some processes stopped in a freezer cgroup ("refrig") that I
don't want to see in the grep output.) I SIGCONT the offending "rm -r"
running on the drive in the USB3 drive dock and you see the rm appear
in uninterruptible sleep along with a couple of kernel processes:
Sun May 7 05:01:07 EDT 2023
Sun May 7 05:01:08 EDT 2023
Sun May 7 05:01:09 EDT 2023
Sun May 7 05:01:10 EDT 2023
Sun May 7 05:01:11 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
4 0 1423283 11939 20 0 10648 580 wait_o D+ pts/28 0:00
rm -rf 15tb3
Sun May 7 05:01:12 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
1 04016 1 20 0 161136 1900 usbhid Dsl ? 1:39
/sbin/apcupsd
4 0 1423283 11939 20 0 10648 580 wait_o D+ pts/28 0:00
rm -rf 15tb3
Sun May 7 05:01:13 EDT 2023
The above lines showing those processes in uninterruptible sleep repeat
over and over each second as the "rm -r" continues. I then start up
"hdparm -t /dev/sda" on the internal SSD disk, and it also appears in
uninterruptible sleep and doesn't finish even after minutes of waiting:
Sun May 7 05:01:25 EDT 2023
1 0 368 2 20 0 0 0 md_sup D? 2:57
[md0_raid5]
1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[kworker/u16:2+flush-8:144]
4 0 1423283 11939 20 0 11260 2544 wait_o D+ pts/28 0:00
rm -rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:26 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[kworker/u16:2+flush-8:144]
4 0 1423283 11939 20 0 11260 2544 wait_o D+ pts/28 0:00
rm -rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:27 EDT 2023
[...]
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:35 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
4 0 1423283 11939 20 0 11260 2544 blk_mq D+ pts/28 0:00
rm -rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:36 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
1 04985 2 20 0 0 0 rq_qos D? 0:24
[jbd2/sdj1-8]
1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[kworker/u16:2+flush-8:144]
4 0 1423283 11939 20 0 11260 2544 wait_o D+ pts/28 0:00
rm -rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:37 EDT 2023
I keep waiting. The above lines repeat over and over and the hdparm is
blocked and doesn't finish.
Sun May 7 05:03:32 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:18
[usb-storage]
1 0 1366783 2 20
[Kernel-packages] [Bug 2018687] [NEW] rm -r dir on USB disk locks up hdparm on different disk
Public bug reported:
Description:Ubuntu 20.04.6 LTS
Linux 5.15.0-72-generic #79~20.04.1-Ubuntu SMP Thu Apr 20 22:12:07 UTC 2023
x86_64 GNU/Linux
Intel(R) Xeon(R) CPU E5-1620 v4 @ 3.50GHz
Running a "rm -r dir" on a directory with millions of files that resides
on a disk in an external USB-3 hard drive dock locks up an unrelated
hdparm processes running on an internal disk such that the kernel says:
May 7 04:24:02 kernel: [163606.041862] INFO: task hdparm:1391162 blocked
for more than 120 seconds.
[...]
May 7 04:26:03 kernel: [163726.876357] INFO: task hdparm:1391162 blocked
for more than 241 seconds.
[...]
May 7 04:28:04 kernel: [163847.702980] INFO: task hdparm:1391162 blocked
for more than 362 seconds.
First a normal run of "hdparm -t /dev/sda" with the offending "rm -r"
SIGSTOPped so that
it doesn't affect anything:
#Â \time hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 1128 MB in 3.00 seconds = 375.50 MB/sec
0.01user 0.67system 0:06.21elapsed 11%CPU (0avgtext+0avgdata
4584maxresident)k
2312704inputs+8outputs (0major+664minor)pagefaults 0swaps
Elapsed time is about six seconds, as expected. /dev/sda is an internal
SSD drive.
I now run this loop to show the timings and process states below:
#Â while sleep 1 ; do date ; ps laxww | grep '[ ]D' | grep -v refrig
; done
(I have some processes stopped in a freezer cgroup ("refrig") that I
don't want to see in the grep output.) I SIGCONT the offending "rm -r"
running on the drive in the USB3 drive dock and you see the rm appear
in uninterruptible sleep along with a couple of kernel processes:
Sun May 7 05:01:07 EDT 2023
Sun May 7 05:01:08 EDT 2023
Sun May 7 05:01:09 EDT 2023
Sun May 7 05:01:10 EDT 2023
Sun May 7 05:01:11 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
4 0 1423283 11939 20 0 10648 580 wait_o D+ pts/28 0:00 rm
-rf 15tb3
Sun May 7 05:01:12 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
1 04016 1 20 0 161136 1900 usbhid Dsl ? 1:39
/sbin/apcupsd
4 0 1423283 11939 20 0 10648 580 wait_o D+ pts/28 0:00 rm
-rf 15tb3
Sun May 7 05:01:13 EDT 2023
The above lines showing those processes in uninterruptible sleep repeat
over and over each second as the "rm -r" continues. I then start up
"hdparm -t /dev/sda" on the internal SSD disk, and it also appears in
uninterruptible sleep and doesn't finish even after minutes of waiting:
Sun May 7 05:01:25 EDT 2023
1 0 368 2 20 0 0 0 md_sup D? 2:57
[md0_raid5]
1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[kworker/u16:2+flush-8:144]
4 0 1423283 11939 20 0 11260 2544 wait_o D+ pts/28 0:00 rm
-rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:26 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[kworker/u16:2+flush-8:144]
4 0 1423283 11939 20 0 11260 2544 wait_o D+ pts/28 0:00 rm
-rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:27 EDT 2023
[...]
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:35 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
4 0 1423283 11939 20 0 11260 2544 blk_mq D+ pts/28 0:00 rm
-rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:36 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:17
[usb-storage]
1 04985 2 20 0 0 0 rq_qos D? 0:24
[jbd2/sdj1-8]
1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[kworker/u16:2+flush-8:144]
4 0 1423283 11939 20 0 11260 2544 wait_o D+ pts/28 0:00 rm
-rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:01:37 EDT 2023
I keep waiting. The above lines repeat over and over and the hdparm is
blocked and doesn't finish.
Sun May 7 05:03:32 EDT 2023
1 0 447 2 20 0 0 0 usb_sg D? 3:18
[usb-storage]
1 0 1366783 2 20 0 0 0 blk_mq D? 0:02
[kworker/u16:2+flush-8:144]
4 0 1423283 11939 20 0 11260 2544 wait_o D+ pts/28 0:03 rm
-rf 15tb3
4 0 14235019975 20 0 4680 4584 wb_wai DL+ pts/4 0:00
hdparm -t /dev/sda
Sun May 7 05:03:34 EDT
[Kernel-packages] [Bug 2007473] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648110/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648101/+files/PaInfo.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/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648100/+files/Lsusb-v.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/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648109/+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/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648108/+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/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648107/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648105/+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/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648106/+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/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648104/+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/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648103/+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/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648102/+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/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648099/+files/Lsusb-t.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/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648098/+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/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648097/+files/Lspci-vt.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/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648096/+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/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648095/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648094/+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/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648093/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-11 (67 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 00KRKP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007473] Re: Bug In Intel Mesa Graphics From Latest Linux Headers
apport information ** Tags added: apport-collected jammy wayland-session ** Description changed: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.> End-Date: 2023-02-15 14:14:59 Start-Date: 2023-02-15 14:16:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin> End-Date: 2023-02-15 14:16:06 These are some of the latest upgrades from my logs. Please note that this issue did not exist in the LTS release until this recent update. I have been using it since December. It was immediately present on 22.10 and why I went back to 22.04. Seems updates finally caught up to what is in 22.10. Best Regards, Daniel + + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.3 + Architecture: amd64 + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-12-11 (67 days ago) + InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) + MachineType: Dell Inc. XPS 9315 + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + 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 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 + RelatedPackageVersions: + linux-restricted-modules-5.19.0-32-generic N/A + linux-backports-modules-5.19.0-32-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.10 + Tags: jammy wayland-session + Uname: Linux 5.19.0-32-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/04/2023 + dmi.bios.release: 1.7 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.7.1 + dmi.board.name: 00KRKP + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: + dmi.product.family: XPS + dmi.product.name: XPS 9315 + dmi.product.sku: 0B14 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2007473/+attachment/5648092/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007473 Title: Bug In Intel Mesa Graphics From Latest Linux Headers Status in linux package in Ubuntu: Confirmed Bug description: affects Ubuntu 22.04.1 Hello, I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I stayed away from the latest non LTS release because this issue already existed there. The problem I have is that every so often in the display I will get rainbow horizontal lines that run from one side of the display to the other and it flashes for like a second or 2 and then disappears. It seems to be triggered by mouse movements. It will be anywhere from 2 to 6 lines of pixels. Start-Date: 2023-02-15 11:18:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.125' Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu> End-Date: 2023-02-15 11:18:04 Start-Date: 2023-02-15 14:14:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.162' Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3> Upgrade:
[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Confirmed for me 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse:  USERPID ACCESS COMMAND  /dev/snd/controlC0: vodka 1819 F pulseaudio  /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb:  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub  Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub  Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device  Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro 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.15.0-48-generic N/A  linux-backports-modules-5.15.0-48-generic N/A  linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 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.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804592] Re: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
Description:Ubuntu 20.04.4 LTS Linux linux 5.13.0-35-generic #40~20.04.1-Ubuntu SMP Mon Mar 7 09:18:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Mar 11 10:43:28 linux kernel: [1.578010] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM. Mar 11 10:43:28 linux kernel: [1.578061] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.13 Mar 11 10:43:28 linux kernel: [1.578066] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Mar 11 10:43:28 linux kernel: [1.578070] usb usb6: Product: xHCI Host Controller Mar 11 10:43:28 linux kernel: [1.578074] usb usb6: Manufacturer: Linux 5.13.0-35-generic xhci-hcd Mar 11 10:43:28 linux kernel: [1.578077] usb usb6: SerialNumber: :08:00.0 Mar 11 10:43:28 linux kernel: [1.578207] hub 6-0:1.0: USB hub found Mar 11 10:43:28 linux kernel: [1.578223] hub 6-0:1.0: 4 ports detected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804592 Title: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. Status in linux package in Ubuntu: Confirmed Bug description: [0.876087] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [0.876099] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.18 [0.876100] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.876101] usb usb2: Product: xHCI Host Controller [0.876102] usb usb2: Manufacturer: Linux 4.18.0-10-generic xhci-hcd [0.876103] usb usb2: SerialNumber: :15:00.0 [0.876206] hub 2-0:1.0: USB hub found [0.876215] hub 2-0:1.0: 4 ports detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895202] Re: touchpad suddenly not detected, appearing as PS/2 mouse in devices
This problem persists with Ubuntu 20.10 released today. The modprobe/rmmod/modprobe method above still works there, however it is very inconvenient to have to perform those steps after each reboot. Unfortunate, as Ubuntu has been the distro that I've used and recommended to others for the last four years based on "it just works". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895202 Title: touchpad suddenly not detected, appearing as PS/2 mouse in devices Status in linux package in Ubuntu: Confirmed Bug description: I can't even recall making any upgrades. Lenovo X1 Extreme. ~ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Synaptics TM3418-002id=12 [slave pointer (2)] ⎜ ↳ PS/2 Generic Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=9[slave keyboard (3)] ↳ AT Raw Set 2 keyboard id=10 [slave keyboard (3)] ↳ ThinkPad Extra Buttons id=11 [slave keyboard (3)] ➜ ~ cat /var/log/Xorg.0.log | grep -i synaptics [12.190] (II) config/udev: Adding input device Synaptics TM3418-002 (/dev/input/event7) [12.190] (**) Synaptics TM3418-002: Applying InputClass "libinput touchpad catchall" [12.190] (II) Using input driver 'libinput' for 'Synaptics TM3418-002' [12.190] (**) Synaptics TM3418-002: always reports core events [12.192] (II) event7 - Synaptics TM3418-002: is tagged by udev as: Touchpad [12.193] (II) event7 - Synaptics TM3418-002: device is a touchpad [12.194] (II) event7 - Synaptics TM3418-002: device removed [12.194] (II) XINPUT: Adding extended input device "Synaptics TM3418-002" (type: TOUCHPAD, id 12) [12.194] (**) Synaptics TM3418-002: (accel) selected scheme none/0 [12.194] (**) Synaptics TM3418-002: (accel) acceleration factor: 2.000 [12.194] (**) Synaptics TM3418-002: (accel) acceleration threshold: 4 [12.195] (II) event7 - Synaptics TM3418-002: is tagged by udev as: Touchpad [12.195] (II) event7 - Synaptics TM3418-002: device is a touchpad [12.196] (II) config/udev: Adding input device Synaptics TM3418-002 (/dev/input/mouse0) [34.235] (II) event7 - Synaptics TM3418-002: device removed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ole2093 F pulseaudio /dev/snd/controlC0: ole2093 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 10 21:45:53 2020 InstallationDate: Installed on 2019-03-30 (530 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=37b4f683-cd0d-4eb9-b05a-973790230aa4 ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET48W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET48W(1.30):bd05/15/2020:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1586195] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327760/+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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327758/+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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327759/+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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327756/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327757/+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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327752/+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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327749/+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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327751/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327754/+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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327750/+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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327753/+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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327748/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327755/+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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug
ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: idallen 30789 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-04-28 (1751 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=5a875d56-b2fd-43bd-b9a4-ecf90aced5fa ro ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-76-generic N/A linux-backports-modules-4.15.0-76-generic N/A linux-firmware 1.173.14 RfKill: Tags: bionic Uname: Linux 4.15.0-76-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-09-02 (528 days ago) UserGroups: adm audio cdrom davfs2 dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1303 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79T Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1303:bd06/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79TDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Tags added: apport-collected bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug
USB 3 Gigabit Ethernet device (Realtek) disconnect/reconnect repeats randomly. $Â lsb_release -a [...] Description:Ubuntu 18.04.4 LTS $Â uname -a Linux linux 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ lsusb [...] Bus 009 Device 003: ID 0bda:8153 Realtek Semiconductor Corp. Bus 009 Device 054: ID 0bda:8153 Realtek Semiconductor Corp. Syslog (two incidents of many): Feb 10 05:38:56 idallen-oak kernel: [1148004.410285] r8152 9-3.4:1.0 eth3: Stop submitting intr, status -71 Feb 10 05:38:56 idallen-oak kernel: [1148004.578733] usb 9-3: USB disconnect, device number 39 Feb 10 05:38:56 idallen-oak kernel: [1148004.578741] usb 9-3.4: USB disconnect, device number 40 Feb 10 05:38:56 idallen-oak NetworkManager[1403]: [1581331136.8384] devices removed (path: /sys/devices/pci:00/:00:05.0/:05:00.0/usb9/9-3/9-3.4/9-3.4:1.0/net/eth3, iface: eth3) Feb 10 05:38:56 idallen-oak NetworkManager[1403]: [1581331136.8564] get unmanaged devices count: 2 Feb 10 05:38:56 idallen-oak kernel: [1148004.908306] usb 9-3: new SuperSpeed USB device number 41 using xhci_hcd Feb 10 05:38:56 idallen-oak kernel: [1148004.944551] usb 9-3: New USB device found, idVendor=0bda, idProduct=0411 Feb 10 05:38:56 idallen-oak kernel: [1148004.944558] usb 9-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 10 05:38:56 idallen-oak kernel: [1148004.944563] usb 9-3: Product: 4-Port USB 3.0 Hub Feb 10 05:38:56 idallen-oak kernel: [1148004.944566] usb 9-3: Manufacturer: Generic Feb 10 05:38:57 idallen-oak kernel: [1148004.949495] hub 9-3:1.0: USB hub found Feb 10 05:38:57 idallen-oak kernel: [1148004.951169] hub 9-3:1.0: 4 ports detected Feb 10 05:38:57 idallen-oak upowerd[4883]: unhandled action 'bind' on /sys/devices/pci:00/:00:05.0/:05:00.0/usb9/9-3/9-3:1.0 Feb 10 05:38:57 idallen-oak upowerd[4883]: unhandled action 'bind' on /sys/devices/pci:00/:00:05.0/:05:00.0/usb9/9-3 Feb 10 05:38:57 idallen-oak kernel: [1148005.247277] usb 9-3.4: new SuperSpeed USB device number 42 using xhci_hcd Feb 10 05:38:57 idallen-oak kernel: [1148005.277094] usb 9-3.4: New USB device found, idVendor=0bda, idProduct=8153 Feb 10 05:38:57 idallen-oak kernel: [1148005.277102] usb 9-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=6 Feb 10 05:38:57 idallen-oak kernel: [1148005.277107] usb 9-3.4: Product: USB 10/100/1000 LAN Feb 10 05:38:57 idallen-oak kernel: [1148005.277111] usb 9-3.4: Manufacturer: CMI Feb 10 05:38:57 idallen-oak kernel: [1148005.277114] usb 9-3.4: SerialNumber: 01 Feb 10 05:38:57 idallen-oak kernel: [1148005.373123] usb 9-3.4: reset SuperSpeed USB device number 42 using xhci_hcd Feb 10 05:38:57 idallen-oak kernel: [1148005.752039] r8152 9-3.4:1.0 eth3: renamed from eth1 Feb 10 05:38:58 idallen-oak NetworkManager[1403]: [1581331138.2100] devices added (path: /sys/devices/pci:00/:00:05.0/:05:00.0/usb9/9-3/9-3.4/9-3.4:1.0/net/eth3, iface: eth3) Feb 10 05:39:00 idallen-oak kernel: [1148008.501102] r8152 9-3.4:1.0 eth3: carrier on A few minutes later, it repeats: Feb 10 10:56:43 idallen-oak kernel: [1167071.434329] r8152 9-3.4:1.0 eth3: Stop submitting intr, status -71 Feb 10 10:56:43 idallen-oak kernel: [1167071.597275] usb 9-3: USB disconnect, device number 41 Feb 10 10:56:43 idallen-oak kernel: [1167071.597283] usb 9-3.4: USB disconnect, device number 42 Feb 10 10:56:43 idallen-oak NetworkManager[1403]: [1581350203.5700] devices removed (path: /sys/devices/pci:00/:00:05.0/:05:00.0/usb9/9-3/9-3.4/9-3.4:1.0/net/eth3, iface: eth3) Feb 10 10:56:43 idallen-oak NetworkManager[1403]: [1581350203.5720] get unmanaged devices count: 2 Feb 10 10:56:43 idallen-oak kernel: [1167071.930010] usb 9-3: new SuperSpeed USB device number 43 using xhci_hcd Feb 10 10:56:43 idallen-oak kernel: [1167071.964334] usb 9-3: New USB device found, idVendor=0bda, idProduct=0411 Feb 10 10:56:43 idallen-oak kernel: [1167071.964341] usb 9-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 10 10:56:43 idallen-oak kernel: [1167071.964346] usb 9-3: Product: 4-Port USB 3.0 Hub Feb 10 10:56:43 idallen-oak kernel: [1167071.964349] usb 9-3: Manufacturer: Generic Feb 10 10:56:43 idallen-oak kernel: [1167071.969105] hub 9-3:1.0: USB hub found Feb 10 10:56:43 idallen-oak kernel: [1167071.970389] hub 9-3:1.0: 4 ports detected Feb 10 10:56:43 idallen-oak upowerd[4883]: unhandled action 'bind' on /sys/devices/pci:00/:00:05.0/:05:00.0/usb9/9-3/9-3:1.0 Feb 10 10:56:43 idallen-oak upowerd[4883]: unhandled action 'bind' on /sys/devices/pci:00/:00:05.0/:05:00.0/usb9/9-3 Feb 10 10:56:44 idallen-oak kernel: [1167072.269853] usb 9-3.4: new SuperSpeed USB device number 44 using xhci_hcd Feb 10 10:56:44 idallen-oak kernel: [1167072.295017] usb 9-3.4: New USB device found, idVendor=0bda, idProduct=8153 Feb 10 10:56:44 idallen-oak kernel: [1167072.295025] usb 9-3.4: New USB device
[Kernel-packages] [Bug 1760545] Re: [18.04] GLK hang after a while
What is the timeline for having this fix backported to the 4.15 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/1760545 Title: [18.04] GLK hang after a while Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: SRU Justification Impact: i915 lacks information about the glk_dmc_ver1_04.bin firmware file in modinfo, so it is not included in the initrd along with the i915 driver. Thus the firmware does not get loaded. Loading the firmware is said to prevent a hang. Fix: Add a MODULE_FIRMWARE statement for the firmware. Test Case: Without the firmware there will be a "Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2" line in dmesg. With the firmware there is no such message. Regression Potential: Minimal. Will only be loaded by i915 for specific hardware, and loading the firmware is known to fix a hang. --- Description: Platform information: Label: GLK02SDP Processor: Silver N5000 Bios: GELKRVPA.X64.0083.B30.1801162142 OS: Ubuntu 18.04 Kernel: 4.15.0-10-generic Details: Power on, and enter into the system; After a period, sometimes about 20 minutes, sometimes 1 hour, the machine will hang. We can only power it off manually, then power on to enter into OS again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1506817] Re: left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04)
Dear Antti, I am still having the problem today, which I previously described as the "random mouse" problem. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506817 https://answers.launchpad.net/ubuntu-certification/+question/272142 Presently I'm using an X260 with 18.04 ubuntu. The problem is still very serious, but I have various workarounds, that help reduce the magnitude of the problem. It seems like a bug in the synaptic driver that comes with linux. If you ask, I can share the various work-arounds I have developed over the years to deal with this very serious bug. Previous bug reports I suggest you look at to see if these match what your observing: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506817 https://answers.launchpad.net/ubuntu-certification/+question/272142 My present OS on my X260 as of Sep 30, 2018: cat /etc/os-release NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1506817 Title: left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04) Status in linux package in Ubuntu: Confirmed Bug description: I have reported the details of this problem at https://answers.launchpad.net/ubuntu-certification/+question/272142 As summarized on that question: X250 analysis: I used the command on the X250 evtest /dev/input/event15 | grep EV_KEY I can see the bug, as follows: I click on button 1 (left) over and over. When I push the button down, I see it register as 1, and when I let go of the key, it registers as a 0. The bug is that every now and then (once every 20 clicks), when I let go of the left mouse button (BIN_LEFT), it does not return to state 0 (it stays in state 1). This is highly random, but cant be triggered more often, by dragging a window, which I do with BIN_LEFT. I am using a brand new X250, purchased in late July 2015. The system was returned 3 times to IBM repair as I assumed this was a hardware error. Now with the above, it seems clear that this is a software issue. Ubuntu 15.04 apt-cache policy xserver-xorg-input-synaptics xserver-xorg-input-synaptics: Installed: 1.8.1-1ubuntu1 Candidate: 1.8.1-1ubuntu1 Version table: *** 1.8.1-1ubuntu1 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-input-synaptics 1.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 16 04:52:03 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu InstallationDate: Installed on 2015-08-15 (61 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20CMCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed root=UUID=5718b40f-944e-47a3-acda-04e29336d0bc ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET36W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET36W(1.15):bd06/19/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Oct 16 03:31:10 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1079 vendor LGD xserver.version: 2:1.17.1-0ubuntu3.1 To manage notifications
[Kernel-packages] [Bug 1791545] Re: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838]
It stopped since the last 4.17 kernel update via apt so I think it's been resolved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791545 Title: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838] Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: FYI, getting this error message on my gemini-lake-based laptop when running the daily 18.10 build ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.17.0-9-generic 4.17.0-9.10 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callen 1691 F pulseaudio Date: Sun Sep 9 13:13:25 2018 Failure: oops InstallationDate: Installed on 2018-08-16 (23 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723) MachineType: Acer Swift SF114-32 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=6f91c64c-cc9a-40f5-9813-9d1c329cfaeb ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Sapporo_GL_S dmi.board.vendor: GLK dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd05/02/2018:svnAcer:pnSwiftSF114-32:pvrV1.03:rvnGLK:rnSapporo_GL_S:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 1 dmi.product.name: Swift SF114-32 dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791545] [NEW] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838]
Public bug reported: FYI, getting this error message on my gemini-lake-based laptop when running the daily 18.10 build ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.17.0-9-generic 4.17.0-9.10 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callen 1691 F pulseaudio Date: Sun Sep 9 13:13:25 2018 Failure: oops InstallationDate: Installed on 2018-08-16 (23 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723) MachineType: Acer Swift SF114-32 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=6f91c64c-cc9a-40f5-9813-9d1c329cfaeb ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Sapporo_GL_S dmi.board.vendor: GLK dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd05/02/2018:svnAcer:pnSwiftSF114-32:pvrV1.03:rvnGLK:rnSapporo_GL_S:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 1 dmi.product.name: Swift SF114-32 dmi.product.version: V1.03 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops cosmic kernel-oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791545 Title: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838] Status in linux package in Ubuntu: Confirmed Bug description: FYI, getting this error message on my gemini-lake-based laptop when running the daily 18.10 build ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.17.0-9-generic 4.17.0-9.10 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callen 1691 F pulseaudio Date: Sun Sep 9 13:13:25 2018 Failure: oops InstallationDate: Installed on 2018-08-16 (23 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723) MachineType: Acer Swift SF114-32 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=6f91c64c-cc9a-40f5-9813-9d1c329cfaeb ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Sapporo_GL_S dmi.board.vendor: GLK dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd05/02/2018:svnAcer:pnSwiftSF114-32:pvrV1.03:rvnGLK:rnSapporo_GL_S:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 1 dmi.product.name: Swift SF114-32 dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
** Description changed: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: - * BIOS settings cannot be saved - * USB Boot impossible - * EFI entries read-only. + Â * BIOS settings cannot be saved + Â * USB Boot impossible + Â * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: Â Â $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G - Dell Inspiron 15-3531 (not fixed by 4.14.9) + Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ -f25l32pa, 0x8c2016 -f25l32qa, 0x8c4116 -f25l64qa, 0x8c4117 + Â Â Â f25l32pa, 0x8c2016 + Â Â Â f25l32qa, 0x8c4116 + Â Â Â f25l64qa, 0x8c4117 /* GigaDevice */ -gd25q16, 0xc84015 -gd25q32, 0xc84016 -gd25lq32, 0xc86016 -gd25q64, 0xc84017 -gd25lq64c, 0xc86017 -gd25q128, 0xc84018 -gd25q256, 0xc84019 + Â Â Â gd25q16, 0xc84015 + Â Â Â gd25q32, 0xc84016 + Â Â Â gd25lq32, 0xc86016 + Â Â Â gd25q64, 0xc84017 + Â Â Â gd25lq64c, 0xc86017 + Â Â Â gd25q128, 0xc84018 + Â Â Â gd25q256, 0xc84019 /* Winbond */ -w25q16dw, 0xef6015 -w25q32dw, 0xef6016 -w25q64dw, 0xef6017 -w25q128fw, 0xef6018 + Â Â Â w25q16dw, 0xef6015 + Â Â Â w25q32dw, 0xef6016 + Â Â Â w25q64dw, 0xef6017 + Â Â Â w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.
[Kernel-packages] [Bug 1739678] Re: HDMI audio makes loud popping noises while playing audio
I've just discovered that, despite my earlier testing, the bug is now also happening on linux-image-4.9.71-040971-generic. I'm going to mark as incomplete once more until I can further narrow down the issue. One other element that might be relevant is that I'm using two video ports: an HDMI port for video, and a DisplayPort cable for audio. In my current round of tests, running both streams over one cable seems to address the issue (but has not always done so), and changing to an interlaced resolution (1080 to 1080i) also seems to fix it (the regular screen is jittery, but YouTube video is clear). I will test for a few days and with different kernels to see if I can isolate the problem and update the bug with my results. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739678 Title: HDMI audio makes loud popping noises while playing audio Status in linux package in Ubuntu: Incomplete Bug description: When playing audio via HDMI, I get very loud pops and/or periods of silence. The frequency of this behaviour seems to go way up while playing video with a lot of motion, and especially YouTube videos. I can reliably reproduce the problem by playing the video https://www.youtube.com/watch?v=vt9UZo32KMk and maximising/minimising the video size rapidly. Testing older kernels, I can reproduce the problem on the linux- image-4.10.0-041000rc1-generic from http://kernel.ubuntu.com/~kernel- ppa/mainline/, but the previous version, linux- image-4.9.71-040971-generic, plays audio without any problems. The problem didn't exist on 17.04; it only started happening after I upgraded to 17.10. (I know 17.04 had a 4.10 kernel; I'm at a loss to explain the difference unless the zesty kernel was patched.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic 4.13.0-21.24 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: tim2079 F...m pulseaudio /dev/snd/controlC0: tim2079 F pulseaudio CurrentDesktop: GNOME Date: Thu Dec 21 23:15:07 2017 HibernationDevice: RESUME=UUID=3f719428-d2ac-4d3b-aa21-db3cd21940a5 InstallationDate: Installed on 2015-09-30 (812 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ZOTAC ZBOX-CI527/CI547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=bfa21ce0-9f16-44a7-9177-80e2a6ef6de8 ro quiet splash pci=noaer RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (61 days ago) dmi.bios.date: 03/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B331P205 dmi.board.asset.tag: NA dmi.board.name: ZBOX-CI527/CI547 dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB331P205:bd03/15/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: NA dmi.product.name: ZBOX-CI527/CI547 dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739678] Re: HDMI audio makes loud popping noises while playing audio
Thank you. The bug still exists on the latest mainline PPA kernel, 4.15.0-041500rc6-generic. ** Tags added: kernel-bug-exists-upstream ** 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/1739678 Title: HDMI audio makes loud popping noises while playing audio Status in linux package in Ubuntu: Confirmed Bug description: When playing audio via HDMI, I get very loud pops and/or periods of silence. The frequency of this behaviour seems to go way up while playing video with a lot of motion, and especially YouTube videos. I can reliably reproduce the problem by playing the video https://www.youtube.com/watch?v=vt9UZo32KMk and maximising/minimising the video size rapidly. Testing older kernels, I can reproduce the problem on the linux- image-4.10.0-041000rc1-generic from http://kernel.ubuntu.com/~kernel- ppa/mainline/, but the previous version, linux- image-4.9.71-040971-generic, plays audio without any problems. The problem didn't exist on 17.04; it only started happening after I upgraded to 17.10. (I know 17.04 had a 4.10 kernel; I'm at a loss to explain the difference unless the zesty kernel was patched.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic 4.13.0-21.24 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: tim2079 F...m pulseaudio /dev/snd/controlC0: tim2079 F pulseaudio CurrentDesktop: GNOME Date: Thu Dec 21 23:15:07 2017 HibernationDevice: RESUME=UUID=3f719428-d2ac-4d3b-aa21-db3cd21940a5 InstallationDate: Installed on 2015-09-30 (812 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ZOTAC ZBOX-CI527/CI547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=bfa21ce0-9f16-44a7-9177-80e2a6ef6de8 ro quiet splash pci=noaer RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (61 days ago) dmi.bios.date: 03/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B331P205 dmi.board.asset.tag: NA dmi.board.name: ZBOX-CI527/CI547 dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB331P205:bd03/15/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: NA dmi.product.name: ZBOX-CI527/CI547 dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
** Description changed: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read-only. Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous affected machines still suffered from a broken BIOS. Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into Linux and BIOS should be restored to a working state. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G - Dell Inspiron 15-3531 + Dell Inspiron 15-3531 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous affected machines still suffered from a broken BIOS. Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into Linux and BIOS should be restored to a working state. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I haven't seen the original kernel mod that caused the problem, but from a vulnerability stand-point, here is my take from reading the 261 comments. Temporary kernel mode access (in any Operating System) allows an attacker to permanently put the BIOS in a default state without ability to perform full operating system re-installs. I expect some panic to start happening as soon as corporate IT types figure this out. The degree of the problem will be determined if it is only Insyde Software, or if it also impacts corporate quality BIOS developed by Dell and other major vendors. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (22/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 Bug may effect machines from any manufacturer that uses BIOS based on Insyde Software. Insyde is responding to emails acknowledging that they are aware of issue but are not providing details. --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: Â linux-restricted-modules-4.13.0-17-generic N/A Â linux-backports-modules-4.13.0-17-generic N/A Â linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Mran, Does your Dell come up with "Insyde Software" in the BIOS or the more traditional Dell BIOS found in corporate desktops and laptops. If it the second, this is a much bigger deal in the vulnerability community. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (22/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 Bug may effect machines from any manufacturer that uses BIOS based on Insyde Software. Insyde is responding to emails acknowledging that they are aware of issue but are not providing details. --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: Â linux-restricted-modules-4.13.0-17-generic N/A Â linux-backports-modules-4.13.0-17-generic N/A Â linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I added the Dell. Mainline Dell BIOS laptops are probably fine, my low end Inspiron with Insyde Software had the same exact thing happen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (22/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 Bug may effect machines from any manufacturer that uses BIOS based on Insyde Software. Insyde is responding to emails acknowledging that they are aware of issue but are not providing details. --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: Â linux-restricted-modules-4.13.0-17-generic N/A Â linux-backports-modules-4.13.0-17-generic N/A Â linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
** Description changed: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! - UPDATE (20/12/2017) + UPDATE (22/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G + Dell Inspiron 15-3531 Bug may effect machines from any manufacturer that uses BIOS based on - Insyde Software + Insyde Software. Insyde is responding to emails acknowledging that they + are aware of issue but are not providing details. --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: Â linux-restricted-modules-4.13.0-17-generic N/A Â linux-backports-modules-4.13.0-17-generic N/A Â linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I contacted Insyde, here is the response, no details "We appreciate you reaching out to us. We are aware of 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (20/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Bug may effect machines from any manufacturer that uses BIOS based on Insyde Software --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: Â linux-restricted-modules-4.13.0-17-generic N/A Â linux-backports-modules-4.13.0-17-generic N/A Â linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739678] [NEW] HDMI audio makes loud popping noises while playing audio
Public bug reported: When playing audio via HDMI, I get very loud pops and/or periods of silence. The frequency of this behaviour seems to go way up while playing video with a lot of motion, and especially YouTube videos. I can reliably reproduce the problem by playing the video https://www.youtube.com/watch?v=vt9UZo32KMk and maximising/minimising the video size rapidly. Testing older kernels, I can reproduce the problem on the linux- image-4.10.0-041000rc1-generic from http://kernel.ubuntu.com/~kernel- ppa/mainline/, but the previous version, linux- image-4.9.71-040971-generic, plays audio without any problems. The problem didn't exist on 17.04; it only started happening after I upgraded to 17.10. (I know 17.04 had a 4.10 kernel; I'm at a loss to explain the difference unless the zesty kernel was patched.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic 4.13.0-21.24 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: tim2079 F...m pulseaudio /dev/snd/controlC0: tim2079 F pulseaudio CurrentDesktop: GNOME Date: Thu Dec 21 23:15:07 2017 HibernationDevice: RESUME=UUID=3f719428-d2ac-4d3b-aa21-db3cd21940a5 InstallationDate: Installed on 2015-09-30 (812 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ZOTAC ZBOX-CI527/CI547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=bfa21ce0-9f16-44a7-9177-80e2a6ef6de8 ro quiet splash pci=noaer RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (61 days ago) dmi.bios.date: 03/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B331P205 dmi.board.asset.tag: NA dmi.board.name: ZBOX-CI527/CI547 dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB331P205:bd03/15/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: NA dmi.product.name: ZBOX-CI527/CI547 dmi.product.version: XX dmi.sys.vendor: ZOTAC ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739678 Title: HDMI audio makes loud popping noises while playing audio Status in linux package in Ubuntu: Confirmed Bug description: When playing audio via HDMI, I get very loud pops and/or periods of silence. The frequency of this behaviour seems to go way up while playing video with a lot of motion, and especially YouTube videos. I can reliably reproduce the problem by playing the video https://www.youtube.com/watch?v=vt9UZo32KMk and maximising/minimising the video size rapidly. Testing older kernels, I can reproduce the problem on the linux- image-4.10.0-041000rc1-generic from http://kernel.ubuntu.com/~kernel- ppa/mainline/, but the previous version, linux- image-4.9.71-040971-generic, plays audio without any problems. The problem didn't exist on 17.04; it only started happening after I upgraded to 17.10. (I know 17.04 had a 4.10 kernel; I'm at a loss to explain the difference unless the zesty kernel was patched.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic 4.13.0-21.24 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: tim2079 F...m pulseaudio /dev/snd/controlC0: tim2079 F pulseaudio CurrentDesktop: GNOME Date: Thu Dec 21 23:15:07 2017 HibernationDevice: RESUME=UUID=3f719428-d2ac-4d3b-aa21-db3cd21940a5 InstallationDate: Installed on 2015-09-30 (812 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ZOTAC ZBOX-CI527/CI547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=bfa21ce0-9f16-44a7-9177-80e2a6ef6de8 ro quiet splash pci=noaer RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (61 days ago) dmi.bios.date: 03/15/2017
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
** Description changed: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! - UPDATE (01/12/2017) + UPDATE (20/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer TravelMate B113 Toshiba Satellite S55T-B5233 - Dell Insperion (with Insyde Software BIOS) + Dell Insperion + + Bug may effect machines from any manufacturer that uses BIOS based on + Insyde Software --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: Â linux-restricted-modules-4.13.0-17-generic N/A Â linux-backports-modules-4.13.0-17-generic N/A Â linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (20/12/2017) LENOVO machines affected so far (please add your affected model to this list):
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I think we are off on the wrong track. This is fundamentally a CVE against Insyde Software BIOS and possibly other vendors. Any attacker with kernel mode access could do the same thing, regardless of Linux install. I am not sure, but it is possible someone with admin access to Windows could create a driver to do the same thing. Any brave pentesters out there want to give it a try and write it up? If Paul Sladen in #173 is correct, this is definitely a CVE against the BIOS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer TravelMate B113 Toshiba Satellite S55T-B5233 Dell Insperion (with Insyde Software BIOS) --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: Â linux-restricted-modules-4.13.0-17-generic N/A Â linux-backports-modules-4.13.0-17-generic N/A Â linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Can anyone confirm whether this only happens with laptops with Insyde Software based BIOS? Or does it effect BIOS derived from AMI/Pheonix? My Dell had Insyde Software BIOS instead of normal Dell AMI based BIOS seen on business class laptops/desktops. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer TravelMate B113 Toshiba Satellite S55T-B5233 Dell Insperion (with Insyde Software BIOS) --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: Â linux-restricted-modules-4.13.0-17-generic N/A Â linux-backports-modules-4.13.0-17-generic N/A Â linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
** Description changed: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer TravelMate B113 Toshiba Satellite S55T-B5233 + Dell Insperion (with Insyde Software BIOS) --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: Â linux-restricted-modules-4.13.0-17-generic N/A Â linux-backports-modules-4.13.0-17-generic N/A Â linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo
[Kernel-packages] [Bug 1716747] Re: linux 4.12 - high system load and mouse delays - pipe A vblank wait timed out
It seems that the PCI Express card was the culprit. When I removed my PCI Express USB 3.0 card everything worked fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716747 Title: linux 4.12 - high system load and mouse delays - pipe A vblank wait timed out Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: This issue has been observed on a Lenovo X220i laptop: 1. Booting the laptop with artful's 4.12 kernel results in a very sluggish system performance (mouse pointer delays) and a high system load. 2. /var/log/kern.log indicates a problem with the display driver (see below) 3. The system works without any issues if the zesty kernel (4.10) is used instead. Ubuntu release: Artful Aardvark (development branch) Kernel package version: 4.12.0.13.14 Sep 12 20:22:45 trinity kernel: [ 155.491074] pipe A vblank wait timed out Sep 12 20:22:45 trinity kernel: [ 155.491117] [ cut here ] Sep 12 20:22:45 trinity kernel: [ 155.491171] WARNING: CPU: 0 PID: 203 at /build/linux-cK2WUa/linux-4.12.0/drivers/gpu/drm/i915/intel_display.c:12636 intel_atomic_commit_tail+0x1010/0x1020 [i915] Sep 12 20:22:45 trinity kernel: [ 155.491172] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter aufs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter binfmt_misc snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm_intel snd_seq_midi kvm snd_seq_midi_event irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd intel_cstate snd_rawmidi intel_rapl_perf arc4 uvcvideo videobuf2_vmalloc iwldvm videobuf2_memops videobuf2_v4l2 mac80211 Sep 12 20:22:45 trinity kernel: [ 155.491215] videobuf2_core videodev joydev input_leds media iwlwifi serio_raw cfg80211 snd_seq snd_seq_device snd_timer thinkpad_acpi nvram snd mac_hid mei_me mei soundcore lpc_ich shpchp parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c mmc_block i915 sdhci_pci uas usb_storage sdhci i2c_algo_bit drm_kms_helper psmouse syscopyarea ahci sysfillrect libahci sysimgblt e1000e fb_sys_fops drm ptp pps_core wmi video Sep 12 20:22:45 trinity kernel: [ 155.491251] CPU: 0 PID: 203 Comm: kworker/u16:5 Not tainted 4.12.0-13-generic #14-Ubuntu Sep 12 20:22:45 trinity kernel: [ 155.491253] Hardware name: LENOVO 4290W1A/4290W1A, BIOS 8DET69WW (1.39 ) 07/18/2013 Sep 12 20:22:45 trinity kernel: [ 155.491292] Workqueue: events_unbound intel_atomic_commit_work [i915] Sep 12 20:22:45 trinity kernel: [ 155.491295] task: 8842c14a8000 task.stack: ae8f0217c000 Sep 12 20:22:45 trinity kernel: [ 155.491330] RIP: 0010:intel_atomic_commit_tail+0x1010/0x1020 [i915] Sep 12 20:22:45 trinity kernel: [ 155.491331] RSP: 0018:ae8f0217fd88 EFLAGS: 00010282 Sep 12 20:22:45 trinity kernel: [ 155.491333] RAX: 001c RBX: RCX: Sep 12 20:22:45 trinity kernel: [ 155.491334] RDX: RSI: 8842de20dcc8 RDI: 8842de20dcc8 Sep 12 20:22:45 trinity kernel: [ 155.491336] RBP: ae8f0217fe40 R08: 0001 R09: 039a Sep 12 20:22:45 trinity kernel: [ 155.491337] R10: ae8f0217fd88 R11: R12: 2359 Sep 12 20:22:45 trinity kernel: [ 155.491338] R13: 8842c150 R14: 8842c15e6000 R15: 0001 Sep 12 20:22:45 trinity kernel: [ 155.491340] FS: () GS:8842de20() knlGS: Sep 12 20:22:45 trinity kernel: [ 155.491342] CS: 0010 DS: ES: CR0: 80050033 Sep 12 20:22:45 trinity kernel: [ 155.491343] CR2: 00c420921000 CR3: 0003a0409000 CR4: 000406f0 Sep 12 20:22:45 trinity kernel: [ 155.491345] Call Trace: Sep 12 20:22:45 trinity kernel: [ 155.491352] ? wake_bit_function+0x60/0x60 Sep 12 20:22:45 trinity kernel: [ 155.491386] intel_atomic_commit_work+0x12/0x20 [i915] Sep 12 20:22:45 trinity kernel: [ 155.491390] process_one_work+0x1e7/0x410 Sep 12 20:22:45 trinity kernel: [ 155.491393] worker_thread+0x4a/0x410 Sep 12 20:22:45 trinity kernel: [ 155.491396] kthread+0x125/0x140 Sep 12 20:22:45 trinity kernel: [ 155.491398] ? process_one_work+0x410/0x410 Sep 12 20:22:45 trinity kernel: [ 155.491400] ? kthread_create_on_node+0x70/0x70 Sep 12 20:22:45 trinity kernel: [ 155.491403] ret_from_fork+0x25/0x30 Sep 12 20:22:45 trinity kernel: [ 155.491405]
[Kernel-packages] [Bug 1716747] Re: linux 4.12 - high system load and mouse delays - pipe A vblank wait timed out
Thanks so much for working on this. I am unable to install 17.10 as a result of this 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/1716747 Title: linux 4.12 - high system load and mouse delays - pipe A vblank wait timed out Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: This issue has been observed on a Lenovo X220i laptop: 1. Booting the laptop with artful's 4.12 kernel results in a very sluggish system performance (mouse pointer delays) and a high system load. 2. /var/log/kern.log indicates a problem with the display driver (see below) 3. The system works without any issues if the zesty kernel (4.10) is used instead. Ubuntu release: Artful Aardvark (development branch) Kernel package version: 4.12.0.13.14 Sep 12 20:22:45 trinity kernel: [ 155.491074] pipe A vblank wait timed out Sep 12 20:22:45 trinity kernel: [ 155.491117] [ cut here ] Sep 12 20:22:45 trinity kernel: [ 155.491171] WARNING: CPU: 0 PID: 203 at /build/linux-cK2WUa/linux-4.12.0/drivers/gpu/drm/i915/intel_display.c:12636 intel_atomic_commit_tail+0x1010/0x1020 [i915] Sep 12 20:22:45 trinity kernel: [ 155.491172] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter aufs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter binfmt_misc snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm_intel snd_seq_midi kvm snd_seq_midi_event irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd intel_cstate snd_rawmidi intel_rapl_perf arc4 uvcvideo videobuf2_vmalloc iwldvm videobuf2_memops videobuf2_v4l2 mac80211 Sep 12 20:22:45 trinity kernel: [ 155.491215] videobuf2_core videodev joydev input_leds media iwlwifi serio_raw cfg80211 snd_seq snd_seq_device snd_timer thinkpad_acpi nvram snd mac_hid mei_me mei soundcore lpc_ich shpchp parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c mmc_block i915 sdhci_pci uas usb_storage sdhci i2c_algo_bit drm_kms_helper psmouse syscopyarea ahci sysfillrect libahci sysimgblt e1000e fb_sys_fops drm ptp pps_core wmi video Sep 12 20:22:45 trinity kernel: [ 155.491251] CPU: 0 PID: 203 Comm: kworker/u16:5 Not tainted 4.12.0-13-generic #14-Ubuntu Sep 12 20:22:45 trinity kernel: [ 155.491253] Hardware name: LENOVO 4290W1A/4290W1A, BIOS 8DET69WW (1.39 ) 07/18/2013 Sep 12 20:22:45 trinity kernel: [ 155.491292] Workqueue: events_unbound intel_atomic_commit_work [i915] Sep 12 20:22:45 trinity kernel: [ 155.491295] task: 8842c14a8000 task.stack: ae8f0217c000 Sep 12 20:22:45 trinity kernel: [ 155.491330] RIP: 0010:intel_atomic_commit_tail+0x1010/0x1020 [i915] Sep 12 20:22:45 trinity kernel: [ 155.491331] RSP: 0018:ae8f0217fd88 EFLAGS: 00010282 Sep 12 20:22:45 trinity kernel: [ 155.491333] RAX: 001c RBX: RCX: Sep 12 20:22:45 trinity kernel: [ 155.491334] RDX: RSI: 8842de20dcc8 RDI: 8842de20dcc8 Sep 12 20:22:45 trinity kernel: [ 155.491336] RBP: ae8f0217fe40 R08: 0001 R09: 039a Sep 12 20:22:45 trinity kernel: [ 155.491337] R10: ae8f0217fd88 R11: R12: 2359 Sep 12 20:22:45 trinity kernel: [ 155.491338] R13: 8842c150 R14: 8842c15e6000 R15: 0001 Sep 12 20:22:45 trinity kernel: [ 155.491340] FS: () GS:8842de20() knlGS: Sep 12 20:22:45 trinity kernel: [ 155.491342] CS: 0010 DS: ES: CR0: 80050033 Sep 12 20:22:45 trinity kernel: [ 155.491343] CR2: 00c420921000 CR3: 0003a0409000 CR4: 000406f0 Sep 12 20:22:45 trinity kernel: [ 155.491345] Call Trace: Sep 12 20:22:45 trinity kernel: [ 155.491352] ? wake_bit_function+0x60/0x60 Sep 12 20:22:45 trinity kernel: [ 155.491386] intel_atomic_commit_work+0x12/0x20 [i915] Sep 12 20:22:45 trinity kernel: [ 155.491390] process_one_work+0x1e7/0x410 Sep 12 20:22:45 trinity kernel: [ 155.491393] worker_thread+0x4a/0x410 Sep 12 20:22:45 trinity kernel: [ 155.491396] kthread+0x125/0x140 Sep 12 20:22:45 trinity kernel: [ 155.491398] ? process_one_work+0x410/0x410 Sep 12 20:22:45 trinity kernel: [ 155.491400] ? kthread_create_on_node+0x70/0x70 Sep 12 20:22:45 trinity kernel: [ 155.491403] ret_from_fork+0x25/0x30 Sep 12 20:22:45 trinity kernel: [ 155.491405] Code: ff ff ff 48 83 c7 08 e8
[Kernel-packages] [Bug 1670356] Re: i2c-hid and hid-multitouch drivers wake computer during suspend
Thanks; I had been looking at the hid-multitouch and i2c-hid source and was increasingly wondering if it was a BIOS/hardware issue. I'll raise the issue with Dell. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670356 Title: i2c-hid and hid-multitouch drivers wake computer during suspend Status in linux package in Ubuntu: Confirmed Bug description: Using the latest 16.04 LTS (Ubuntu 4.4.0-64.85-generic 4.4.44), my Dell Inspiron 7548 wakes everytime the Elan touchpad registers a touch. This causes the machine to wake when the lid is closed, and renders the suspend/hibernate function useless. The only way in which the suspend doesn't respond to the touchpad is if the touchpad is manipulated *during* the suspend process. This is true when removing the drivers or unbinding the hardware in /etc/pm/sleep.d; removing or unbinding will still cause the laptop to wake from sleep unless the touchpad has been touched between removing the driver and suspending the laptop. Disabling everything in /proc/acpi/wakeup has no effect on the issue. The relevant lines from dmesg: [ 174.627776] input: MSFT0001:00 06CB:75BD Touchpad as /devices/pci:00/INT3 433:00/i2c-5/i2c-MSFT0001:00/0018:06CB:75BD.0001/input/input13 [ 174.627923] hid-multitouch 0018:06CB:75BD.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:75BD] on i2c-MSFT0001:00 lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 8087:07dc Intel Corp. Bus 002 Device 003: ID 04f3:2098 Elan Microelectronics Corp. Bus 002 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (04f3:2098 is the device in question.) lsmod: Module Size Used by i2c_hid20480 0 hid_multitouch 20480 0 hid 118784 2 i2c_hid,hid_multitouch joydev 20480 0 rfcomm 69632 2 drbg 32768 1 ansi_cprng 16384 0 ctr16384 2 ccm20480 2 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 3 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack_ipv4 16384 2 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 1 nf_conntrack 106496 5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 16384 6 bridge126976 0 stp16384 1 bridge llc16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 1 ip_tables 24576 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 11 ip6table_filter,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables bnep 20480 2 nls_iso8859_1 16384 1 dell_laptop20480 0 dell_wmi 16384 0 dcdbas 16384 1 dell_laptop sparse_keymap 16384 1 dell_wmi dell_smm_hwmon 16384 0 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 arc4 16384 2 dell_led 16384 1 media 24576 2 uvcvideo,videodev iwlmvm311296 0 snd_hda_codec_hdmi 53248 1 snd_hda_codec_realtek86016 1 snd_hda_codec_generic77824 1 snd_hda_codec_realtek mac80211 737280 1 iwlmvm intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 snd_hda_intel 40960 12 coretemp 16384 0 snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel kvm_intel 172032 0 kvm 544768 1 kvm_intel snd_hda_core 73728 5
[Kernel-packages] [Bug 1670356] Re: i2c-hid and hid-multitouch drivers wake computer during suspend
That's correct; the screen presumably touches the touchpad when closing the lid. I've been testing by simply suspending and then touching the touchpad to wake the laptop (it doesn't require pressing the touchpad button; simply registering a touch works). As I say, the exception is if the touchpad is touched _during_ the suspend process (then the touchpad doesn't wake the laptop), or if the touchpad is touched after unloading the hid-multitouch or i2c-hid drivers. (I initially tried to resolve the issue by forcing removal of the drivers during the suspend processes, but this would also require that I touch the touchpad during the suspend process.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670356 Title: i2c-hid and hid-multitouch drivers wake computer during suspend Status in linux package in Ubuntu: Confirmed Bug description: Using the latest 16.04 LTS (Ubuntu 4.4.0-64.85-generic 4.4.44), my Dell Inspiron 7548 wakes everytime the Elan touchpad registers a touch. This causes the machine to wake when the lid is closed, and renders the suspend/hibernate function useless. The only way in which the suspend doesn't respond to the touchpad is if the touchpad is manipulated *during* the suspend process. This is true when removing the drivers or unbinding the hardware in /etc/pm/sleep.d; removing or unbinding will still cause the laptop to wake from sleep unless the touchpad has been touched between removing the driver and suspending the laptop. Disabling everything in /proc/acpi/wakeup has no effect on the issue. The relevant lines from dmesg: [ 174.627776] input: MSFT0001:00 06CB:75BD Touchpad as /devices/pci:00/INT3 433:00/i2c-5/i2c-MSFT0001:00/0018:06CB:75BD.0001/input/input13 [ 174.627923] hid-multitouch 0018:06CB:75BD.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:75BD] on i2c-MSFT0001:00 lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 8087:07dc Intel Corp. Bus 002 Device 003: ID 04f3:2098 Elan Microelectronics Corp. Bus 002 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (04f3:2098 is the device in question.) lsmod: Module Size Used by i2c_hid20480 0 hid_multitouch 20480 0 hid 118784 2 i2c_hid,hid_multitouch joydev 20480 0 rfcomm 69632 2 drbg 32768 1 ansi_cprng 16384 0 ctr16384 2 ccm20480 2 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 3 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack_ipv4 16384 2 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 1 nf_conntrack 106496 5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 16384 6 bridge126976 0 stp16384 1 bridge llc16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 1 ip_tables 24576 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 11 ip6table_filter,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables bnep 20480 2 nls_iso8859_1 16384 1 dell_laptop20480 0 dell_wmi 16384 0 dcdbas 16384 1 dell_laptop sparse_keymap 16384 1 dell_wmi dell_smm_hwmon 16384 0 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 arc4 16384 2 dell_led 16384 1 media 24576 2 uvcvideo,videodev iwlmvm311296 0 snd_hda_codec_hdmi 53248 1 snd_hda_codec_realtek86016 1 snd_hda_codec_generic77824 1 snd_hda_codec_realtek mac80211
[Kernel-packages] [Bug 1670356] Re: i2c-hid and hid-multitouch drivers wake computer during suspend
Thank you. Testing on 4.11.0-041100rc1-generic yields exactly the same result, testing with various values of /proc/acpi/wakeup and removed/inserted i2c-hid and hid-multitouch modules: the laptop wakes from suspend upon touching the touchpad unless the touchpad was manipulated between removing the modules and suspending, or during the suspend process. ** Tags added: kernel-bug-exists-upstream ** 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/1670356 Title: i2c-hid and hid-multitouch drivers wake computer during suspend Status in linux package in Ubuntu: Confirmed Bug description: Using the latest 16.04 LTS (Ubuntu 4.4.0-64.85-generic 4.4.44), my Dell Inspiron 7548 wakes everytime the Elan touchpad registers a touch. This causes the machine to wake when the lid is closed, and renders the suspend/hibernate function useless. The only way in which the suspend doesn't respond to the touchpad is if the touchpad is manipulated *during* the suspend process. This is true when removing the drivers or unbinding the hardware in /etc/pm/sleep.d; removing or unbinding will still cause the laptop to wake from sleep unless the touchpad has been touched between removing the driver and suspending the laptop. Disabling everything in /proc/acpi/wakeup has no effect on the issue. The relevant lines from dmesg: [ 174.627776] input: MSFT0001:00 06CB:75BD Touchpad as /devices/pci:00/INT3 433:00/i2c-5/i2c-MSFT0001:00/0018:06CB:75BD.0001/input/input13 [ 174.627923] hid-multitouch 0018:06CB:75BD.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:75BD] on i2c-MSFT0001:00 lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 8087:07dc Intel Corp. Bus 002 Device 003: ID 04f3:2098 Elan Microelectronics Corp. Bus 002 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (04f3:2098 is the device in question.) lsmod: Module Size Used by i2c_hid20480 0 hid_multitouch 20480 0 hid 118784 2 i2c_hid,hid_multitouch joydev 20480 0 rfcomm 69632 2 drbg 32768 1 ansi_cprng 16384 0 ctr16384 2 ccm20480 2 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 3 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack_ipv4 16384 2 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 1 nf_conntrack 106496 5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 16384 6 bridge126976 0 stp16384 1 bridge llc16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 1 ip_tables 24576 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 11 ip6table_filter,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables bnep 20480 2 nls_iso8859_1 16384 1 dell_laptop20480 0 dell_wmi 16384 0 dcdbas 16384 1 dell_laptop sparse_keymap 16384 1 dell_wmi dell_smm_hwmon 16384 0 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 arc4 16384 2 dell_led 16384 1 media 24576 2 uvcvideo,videodev iwlmvm311296 0 snd_hda_codec_hdmi 53248 1 snd_hda_codec_realtek86016 1 snd_hda_codec_generic77824 1 snd_hda_codec_realtek mac80211 737280 1 iwlmvm intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 snd_hda_intel 40960 12 coretemp 16384
[Kernel-packages] [Bug 1670356] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1670356/+attachment/4832316/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670356 Title: i2c-hid and hid-multitouch drivers wake computer during suspend Status in linux package in Ubuntu: Confirmed Bug description: Using the latest 16.04 LTS (Ubuntu 4.4.0-64.85-generic 4.4.44), my Dell Inspiron 7548 wakes everytime the Elan touchpad registers a touch. This causes the machine to wake when the lid is closed, and renders the suspend/hibernate function useless. The only way in which the suspend doesn't respond to the touchpad is if the touchpad is manipulated *during* the suspend process. This is true when removing the drivers or unbinding the hardware in /etc/pm/sleep.d; removing or unbinding will still cause the laptop to wake from sleep unless the touchpad has been touched between removing the driver and suspending the laptop. Disabling everything in /proc/acpi/wakeup has no effect on the issue. The relevant lines from dmesg: [ 174.627776] input: MSFT0001:00 06CB:75BD Touchpad as /devices/pci:00/INT3 433:00/i2c-5/i2c-MSFT0001:00/0018:06CB:75BD.0001/input/input13 [ 174.627923] hid-multitouch 0018:06CB:75BD.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:75BD] on i2c-MSFT0001:00 lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 8087:07dc Intel Corp. Bus 002 Device 003: ID 04f3:2098 Elan Microelectronics Corp. Bus 002 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (04f3:2098 is the device in question.) lsmod: Module Size Used by i2c_hid20480 0 hid_multitouch 20480 0 hid 118784 2 i2c_hid,hid_multitouch joydev 20480 0 rfcomm 69632 2 drbg 32768 1 ansi_cprng 16384 0 ctr16384 2 ccm20480 2 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 3 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack_ipv4 16384 2 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 1 nf_conntrack 106496 5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 16384 6 bridge126976 0 stp16384 1 bridge llc16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 1 ip_tables 24576 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 11 ip6table_filter,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables bnep 20480 2 nls_iso8859_1 16384 1 dell_laptop20480 0 dell_wmi 16384 0 dcdbas 16384 1 dell_laptop sparse_keymap 16384 1 dell_wmi dell_smm_hwmon 16384 0 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 arc4 16384 2 dell_led 16384 1 media 24576 2 uvcvideo,videodev iwlmvm311296 0 snd_hda_codec_hdmi 53248 1 snd_hda_codec_realtek86016 1 snd_hda_codec_generic77824 1 snd_hda_codec_realtek mac80211 737280 1 iwlmvm intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 snd_hda_intel 40960 12 coretemp 16384 0 snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel kvm_intel 172032 0 kvm 544768 1 kvm_intel snd_hda_core 73728 5
[Kernel-packages] [Bug 1670356] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1670356/+attachment/4832303/+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/1670356 Title: i2c-hid and hid-multitouch drivers wake computer during suspend Status in linux package in Ubuntu: Confirmed Bug description: Using the latest 16.04 LTS (Ubuntu 4.4.0-64.85-generic 4.4.44), my Dell Inspiron 7548 wakes everytime the Elan touchpad registers a touch. This causes the machine to wake when the lid is closed, and renders the suspend/hibernate function useless. The only way in which the suspend doesn't respond to the touchpad is if the touchpad is manipulated *during* the suspend process. This is true when removing the drivers or unbinding the hardware in /etc/pm/sleep.d; removing or unbinding will still cause the laptop to wake from sleep unless the touchpad has been touched between removing the driver and suspending the laptop. Disabling everything in /proc/acpi/wakeup has no effect on the issue. The relevant lines from dmesg: [ 174.627776] input: MSFT0001:00 06CB:75BD Touchpad as /devices/pci:00/INT3 433:00/i2c-5/i2c-MSFT0001:00/0018:06CB:75BD.0001/input/input13 [ 174.627923] hid-multitouch 0018:06CB:75BD.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:75BD] on i2c-MSFT0001:00 lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 8087:07dc Intel Corp. Bus 002 Device 003: ID 04f3:2098 Elan Microelectronics Corp. Bus 002 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (04f3:2098 is the device in question.) lsmod: Module Size Used by i2c_hid20480 0 hid_multitouch 20480 0 hid 118784 2 i2c_hid,hid_multitouch joydev 20480 0 rfcomm 69632 2 drbg 32768 1 ansi_cprng 16384 0 ctr16384 2 ccm20480 2 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 3 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack_ipv4 16384 2 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 1 nf_conntrack 106496 5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 16384 6 bridge126976 0 stp16384 1 bridge llc16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 1 ip_tables 24576 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 11 ip6table_filter,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables bnep 20480 2 nls_iso8859_1 16384 1 dell_laptop20480 0 dell_wmi 16384 0 dcdbas 16384 1 dell_laptop sparse_keymap 16384 1 dell_wmi dell_smm_hwmon 16384 0 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 arc4 16384 2 dell_led 16384 1 media 24576 2 uvcvideo,videodev iwlmvm311296 0 snd_hda_codec_hdmi 53248 1 snd_hda_codec_realtek86016 1 snd_hda_codec_generic77824 1 snd_hda_codec_realtek mac80211 737280 1 iwlmvm intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 snd_hda_intel 40960 12 coretemp 16384 0 snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel kvm_intel 172032 0 kvm 544768 1 kvm_intel snd_hda_core 73728 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel irqbypass
[Kernel-packages] [Bug 1670356] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1670356/+attachment/4832306/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670356 Title: i2c-hid and hid-multitouch drivers wake computer during suspend Status in linux package in Ubuntu: Confirmed Bug description: Using the latest 16.04 LTS (Ubuntu 4.4.0-64.85-generic 4.4.44), my Dell Inspiron 7548 wakes everytime the Elan touchpad registers a touch. This causes the machine to wake when the lid is closed, and renders the suspend/hibernate function useless. The only way in which the suspend doesn't respond to the touchpad is if the touchpad is manipulated *during* the suspend process. This is true when removing the drivers or unbinding the hardware in /etc/pm/sleep.d; removing or unbinding will still cause the laptop to wake from sleep unless the touchpad has been touched between removing the driver and suspending the laptop. Disabling everything in /proc/acpi/wakeup has no effect on the issue. The relevant lines from dmesg: [ 174.627776] input: MSFT0001:00 06CB:75BD Touchpad as /devices/pci:00/INT3 433:00/i2c-5/i2c-MSFT0001:00/0018:06CB:75BD.0001/input/input13 [ 174.627923] hid-multitouch 0018:06CB:75BD.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:75BD] on i2c-MSFT0001:00 lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 8087:07dc Intel Corp. Bus 002 Device 003: ID 04f3:2098 Elan Microelectronics Corp. Bus 002 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (04f3:2098 is the device in question.) lsmod: Module Size Used by i2c_hid20480 0 hid_multitouch 20480 0 hid 118784 2 i2c_hid,hid_multitouch joydev 20480 0 rfcomm 69632 2 drbg 32768 1 ansi_cprng 16384 0 ctr16384 2 ccm20480 2 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 3 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack_ipv4 16384 2 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 1 nf_conntrack 106496 5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 16384 6 bridge126976 0 stp16384 1 bridge llc16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 1 ip_tables 24576 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 11 ip6table_filter,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables bnep 20480 2 nls_iso8859_1 16384 1 dell_laptop20480 0 dell_wmi 16384 0 dcdbas 16384 1 dell_laptop sparse_keymap 16384 1 dell_wmi dell_smm_hwmon 16384 0 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 arc4 16384 2 dell_led 16384 1 media 24576 2 uvcvideo,videodev iwlmvm311296 0 snd_hda_codec_hdmi 53248 1 snd_hda_codec_realtek86016 1 snd_hda_codec_generic77824 1 snd_hda_codec_realtek mac80211 737280 1 iwlmvm intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 snd_hda_intel 40960 12 coretemp 16384 0 snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel kvm_intel 172032 0 kvm 544768 1 kvm_intel snd_hda_core 73728 5
[Kernel-packages] [Bug 1670356] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1670356/+attachment/4832312/+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/1670356 Title: i2c-hid and hid-multitouch drivers wake computer during suspend Status in linux package in Ubuntu: Confirmed Bug description: Using the latest 16.04 LTS (Ubuntu 4.4.0-64.85-generic 4.4.44), my Dell Inspiron 7548 wakes everytime the Elan touchpad registers a touch. This causes the machine to wake when the lid is closed, and renders the suspend/hibernate function useless. The only way in which the suspend doesn't respond to the touchpad is if the touchpad is manipulated *during* the suspend process. This is true when removing the drivers or unbinding the hardware in /etc/pm/sleep.d; removing or unbinding will still cause the laptop to wake from sleep unless the touchpad has been touched between removing the driver and suspending the laptop. Disabling everything in /proc/acpi/wakeup has no effect on the issue. The relevant lines from dmesg: [ 174.627776] input: MSFT0001:00 06CB:75BD Touchpad as /devices/pci:00/INT3 433:00/i2c-5/i2c-MSFT0001:00/0018:06CB:75BD.0001/input/input13 [ 174.627923] hid-multitouch 0018:06CB:75BD.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:75BD] on i2c-MSFT0001:00 lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 8087:07dc Intel Corp. Bus 002 Device 003: ID 04f3:2098 Elan Microelectronics Corp. Bus 002 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (04f3:2098 is the device in question.) lsmod: Module Size Used by i2c_hid20480 0 hid_multitouch 20480 0 hid 118784 2 i2c_hid,hid_multitouch joydev 20480 0 rfcomm 69632 2 drbg 32768 1 ansi_cprng 16384 0 ctr16384 2 ccm20480 2 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 3 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack_ipv4 16384 2 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 1 nf_conntrack 106496 5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 16384 6 bridge126976 0 stp16384 1 bridge llc16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 1 ip_tables 24576 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 11 ip6table_filter,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables bnep 20480 2 nls_iso8859_1 16384 1 dell_laptop20480 0 dell_wmi 16384 0 dcdbas 16384 1 dell_laptop sparse_keymap 16384 1 dell_wmi dell_smm_hwmon 16384 0 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 arc4 16384 2 dell_led 16384 1 media 24576 2 uvcvideo,videodev iwlmvm311296 0 snd_hda_codec_hdmi 53248 1 snd_hda_codec_realtek86016 1 snd_hda_codec_generic77824 1 snd_hda_codec_realtek mac80211 737280 1 iwlmvm intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 snd_hda_intel 40960 12 coretemp 16384 0 snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel kvm_intel 172032 0 kvm 544768 1 kvm_intel snd_hda_core 73728 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
[Kernel-packages] [Bug 1670356] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1670356/+attachment/4832311/+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/1670356 Title: i2c-hid and hid-multitouch drivers wake computer during suspend Status in linux package in Ubuntu: Confirmed Bug description: Using the latest 16.04 LTS (Ubuntu 4.4.0-64.85-generic 4.4.44), my Dell Inspiron 7548 wakes everytime the Elan touchpad registers a touch. This causes the machine to wake when the lid is closed, and renders the suspend/hibernate function useless. The only way in which the suspend doesn't respond to the touchpad is if the touchpad is manipulated *during* the suspend process. This is true when removing the drivers or unbinding the hardware in /etc/pm/sleep.d; removing or unbinding will still cause the laptop to wake from sleep unless the touchpad has been touched between removing the driver and suspending the laptop. Disabling everything in /proc/acpi/wakeup has no effect on the issue. The relevant lines from dmesg: [ 174.627776] input: MSFT0001:00 06CB:75BD Touchpad as /devices/pci:00/INT3 433:00/i2c-5/i2c-MSFT0001:00/0018:06CB:75BD.0001/input/input13 [ 174.627923] hid-multitouch 0018:06CB:75BD.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:75BD] on i2c-MSFT0001:00 lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 8087:07dc Intel Corp. Bus 002 Device 003: ID 04f3:2098 Elan Microelectronics Corp. Bus 002 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (04f3:2098 is the device in question.) lsmod: Module Size Used by i2c_hid20480 0 hid_multitouch 20480 0 hid 118784 2 i2c_hid,hid_multitouch joydev 20480 0 rfcomm 69632 2 drbg 32768 1 ansi_cprng 16384 0 ctr16384 2 ccm20480 2 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 3 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack_ipv4 16384 2 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 1 nf_conntrack 106496 5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 16384 6 bridge126976 0 stp16384 1 bridge llc16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 1 ip_tables 24576 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 11 ip6table_filter,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables bnep 20480 2 nls_iso8859_1 16384 1 dell_laptop20480 0 dell_wmi 16384 0 dcdbas 16384 1 dell_laptop sparse_keymap 16384 1 dell_wmi dell_smm_hwmon 16384 0 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 arc4 16384 2 dell_led 16384 1 media 24576 2 uvcvideo,videodev iwlmvm311296 0 snd_hda_codec_hdmi 53248 1 snd_hda_codec_realtek86016 1 snd_hda_codec_generic77824 1 snd_hda_codec_realtek mac80211 737280 1 iwlmvm intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 snd_hda_intel 40960 12 coretemp 16384 0 snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel kvm_intel 172032 0 kvm 544768 1 kvm_intel snd_hda_core 73728 5
[Kernel-packages] [Bug 1670356] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1670356/+attachment/4832315/+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/1670356 Title: i2c-hid and hid-multitouch drivers wake computer during suspend Status in linux package in Ubuntu: Confirmed Bug description: Using the latest 16.04 LTS (Ubuntu 4.4.0-64.85-generic 4.4.44), my Dell Inspiron 7548 wakes everytime the Elan touchpad registers a touch. This causes the machine to wake when the lid is closed, and renders the suspend/hibernate function useless. The only way in which the suspend doesn't respond to the touchpad is if the touchpad is manipulated *during* the suspend process. This is true when removing the drivers or unbinding the hardware in /etc/pm/sleep.d; removing or unbinding will still cause the laptop to wake from sleep unless the touchpad has been touched between removing the driver and suspending the laptop. Disabling everything in /proc/acpi/wakeup has no effect on the issue. The relevant lines from dmesg: [ 174.627776] input: MSFT0001:00 06CB:75BD Touchpad as /devices/pci:00/INT3 433:00/i2c-5/i2c-MSFT0001:00/0018:06CB:75BD.0001/input/input13 [ 174.627923] hid-multitouch 0018:06CB:75BD.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:75BD] on i2c-MSFT0001:00 lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 8087:07dc Intel Corp. Bus 002 Device 003: ID 04f3:2098 Elan Microelectronics Corp. Bus 002 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (04f3:2098 is the device in question.) lsmod: Module Size Used by i2c_hid20480 0 hid_multitouch 20480 0 hid 118784 2 i2c_hid,hid_multitouch joydev 20480 0 rfcomm 69632 2 drbg 32768 1 ansi_cprng 16384 0 ctr16384 2 ccm20480 2 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 3 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack_ipv4 16384 2 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 1 nf_conntrack 106496 5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 16384 6 bridge126976 0 stp16384 1 bridge llc16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 1 ip_tables 24576 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 11 ip6table_filter,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables bnep 20480 2 nls_iso8859_1 16384 1 dell_laptop20480 0 dell_wmi 16384 0 dcdbas 16384 1 dell_laptop sparse_keymap 16384 1 dell_wmi dell_smm_hwmon 16384 0 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 arc4 16384 2 dell_led 16384 1 media 24576 2 uvcvideo,videodev iwlmvm311296 0 snd_hda_codec_hdmi 53248 1 snd_hda_codec_realtek86016 1 snd_hda_codec_generic77824 1 snd_hda_codec_realtek mac80211 737280 1 iwlmvm intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 snd_hda_intel 40960 12 coretemp 16384 0 snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel kvm_intel 172032 0 kvm 544768 1 kvm_intel snd_hda_core 73728 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel irqbypass
[Kernel-packages] [Bug 1670356] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1670356/+attachment/4832305/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670356 Title: i2c-hid and hid-multitouch drivers wake computer during suspend Status in linux package in Ubuntu: Confirmed Bug description: Using the latest 16.04 LTS (Ubuntu 4.4.0-64.85-generic 4.4.44), my Dell Inspiron 7548 wakes everytime the Elan touchpad registers a touch. This causes the machine to wake when the lid is closed, and renders the suspend/hibernate function useless. The only way in which the suspend doesn't respond to the touchpad is if the touchpad is manipulated *during* the suspend process. This is true when removing the drivers or unbinding the hardware in /etc/pm/sleep.d; removing or unbinding will still cause the laptop to wake from sleep unless the touchpad has been touched between removing the driver and suspending the laptop. Disabling everything in /proc/acpi/wakeup has no effect on the issue. The relevant lines from dmesg: [ 174.627776] input: MSFT0001:00 06CB:75BD Touchpad as /devices/pci:00/INT3 433:00/i2c-5/i2c-MSFT0001:00/0018:06CB:75BD.0001/input/input13 [ 174.627923] hid-multitouch 0018:06CB:75BD.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:75BD] on i2c-MSFT0001:00 lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 8087:07dc Intel Corp. Bus 002 Device 003: ID 04f3:2098 Elan Microelectronics Corp. Bus 002 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (04f3:2098 is the device in question.) lsmod: Module Size Used by i2c_hid20480 0 hid_multitouch 20480 0 hid 118784 2 i2c_hid,hid_multitouch joydev 20480 0 rfcomm 69632 2 drbg 32768 1 ansi_cprng 16384 0 ctr16384 2 ccm20480 2 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 3 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack_ipv4 16384 2 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 1 nf_conntrack 106496 5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 16384 6 bridge126976 0 stp16384 1 bridge llc16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 1 ip_tables 24576 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 11 ip6table_filter,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables bnep 20480 2 nls_iso8859_1 16384 1 dell_laptop20480 0 dell_wmi 16384 0 dcdbas 16384 1 dell_laptop sparse_keymap 16384 1 dell_wmi dell_smm_hwmon 16384 0 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 arc4 16384 2 dell_led 16384 1 media 24576 2 uvcvideo,videodev iwlmvm311296 0 snd_hda_codec_hdmi 53248 1 snd_hda_codec_realtek86016 1 snd_hda_codec_generic77824 1 snd_hda_codec_realtek mac80211 737280 1 iwlmvm intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 snd_hda_intel 40960 12 coretemp 16384 0 snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel kvm_intel 172032 0 kvm 544768 1 kvm_intel snd_hda_core 73728 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
[Kernel-packages] [Bug 1670356] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1670356/+attachment/4832309/+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/1670356 Title: i2c-hid and hid-multitouch drivers wake computer during suspend Status in linux package in Ubuntu: Confirmed Bug description: Using the latest 16.04 LTS (Ubuntu 4.4.0-64.85-generic 4.4.44), my Dell Inspiron 7548 wakes everytime the Elan touchpad registers a touch. This causes the machine to wake when the lid is closed, and renders the suspend/hibernate function useless. The only way in which the suspend doesn't respond to the touchpad is if the touchpad is manipulated *during* the suspend process. This is true when removing the drivers or unbinding the hardware in /etc/pm/sleep.d; removing or unbinding will still cause the laptop to wake from sleep unless the touchpad has been touched between removing the driver and suspending the laptop. Disabling everything in /proc/acpi/wakeup has no effect on the issue. The relevant lines from dmesg: [ 174.627776] input: MSFT0001:00 06CB:75BD Touchpad as /devices/pci:00/INT3 433:00/i2c-5/i2c-MSFT0001:00/0018:06CB:75BD.0001/input/input13 [ 174.627923] hid-multitouch 0018:06CB:75BD.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:75BD] on i2c-MSFT0001:00 lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 8087:07dc Intel Corp. Bus 002 Device 003: ID 04f3:2098 Elan Microelectronics Corp. Bus 002 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (04f3:2098 is the device in question.) lsmod: Module Size Used by i2c_hid20480 0 hid_multitouch 20480 0 hid 118784 2 i2c_hid,hid_multitouch joydev 20480 0 rfcomm 69632 2 drbg 32768 1 ansi_cprng 16384 0 ctr16384 2 ccm20480 2 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 3 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack_ipv4 16384 2 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 1 nf_conntrack 106496 5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 16384 6 bridge126976 0 stp16384 1 bridge llc16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 1 ip_tables 24576 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 11 ip6table_filter,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables bnep 20480 2 nls_iso8859_1 16384 1 dell_laptop20480 0 dell_wmi 16384 0 dcdbas 16384 1 dell_laptop sparse_keymap 16384 1 dell_wmi dell_smm_hwmon 16384 0 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 arc4 16384 2 dell_led 16384 1 media 24576 2 uvcvideo,videodev iwlmvm311296 0 snd_hda_codec_hdmi 53248 1 snd_hda_codec_realtek86016 1 snd_hda_codec_generic77824 1 snd_hda_codec_realtek mac80211 737280 1 iwlmvm intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 snd_hda_intel 40960 12 coretemp 16384 0 snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel kvm_intel 172032 0 kvm 544768 1 kvm_intel snd_hda_core 73728 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
[Kernel-packages] [Bug 1670356] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1670356/+attachment/4832313/+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/1670356 Title: i2c-hid and hid-multitouch drivers wake computer during suspend Status in linux package in Ubuntu: Confirmed Bug description: Using the latest 16.04 LTS (Ubuntu 4.4.0-64.85-generic 4.4.44), my Dell Inspiron 7548 wakes everytime the Elan touchpad registers a touch. This causes the machine to wake when the lid is closed, and renders the suspend/hibernate function useless. The only way in which the suspend doesn't respond to the touchpad is if the touchpad is manipulated *during* the suspend process. This is true when removing the drivers or unbinding the hardware in /etc/pm/sleep.d; removing or unbinding will still cause the laptop to wake from sleep unless the touchpad has been touched between removing the driver and suspending the laptop. Disabling everything in /proc/acpi/wakeup has no effect on the issue. The relevant lines from dmesg: [ 174.627776] input: MSFT0001:00 06CB:75BD Touchpad as /devices/pci:00/INT3 433:00/i2c-5/i2c-MSFT0001:00/0018:06CB:75BD.0001/input/input13 [ 174.627923] hid-multitouch 0018:06CB:75BD.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:75BD] on i2c-MSFT0001:00 lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 8087:07dc Intel Corp. Bus 002 Device 003: ID 04f3:2098 Elan Microelectronics Corp. Bus 002 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (04f3:2098 is the device in question.) lsmod: Module Size Used by i2c_hid20480 0 hid_multitouch 20480 0 hid 118784 2 i2c_hid,hid_multitouch joydev 20480 0 rfcomm 69632 2 drbg 32768 1 ansi_cprng 16384 0 ctr16384 2 ccm20480 2 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 3 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack_ipv4 16384 2 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 1 nf_conntrack 106496 5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 16384 6 bridge126976 0 stp16384 1 bridge llc16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 1 ip_tables 24576 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 11 ip6table_filter,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables bnep 20480 2 nls_iso8859_1 16384 1 dell_laptop20480 0 dell_wmi 16384 0 dcdbas 16384 1 dell_laptop sparse_keymap 16384 1 dell_wmi dell_smm_hwmon 16384 0 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 arc4 16384 2 dell_led 16384 1 media 24576 2 uvcvideo,videodev iwlmvm311296 0 snd_hda_codec_hdmi 53248 1 snd_hda_codec_realtek86016 1 snd_hda_codec_generic77824 1 snd_hda_codec_realtek mac80211 737280 1 iwlmvm intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 snd_hda_intel 40960 12 coretemp 16384 0 snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel kvm_intel 172032 0 kvm 544768 1 kvm_intel snd_hda_core 73728 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
[Kernel-packages] [Bug 1670356] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1670356/+attachment/4832304/+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/1670356 Title: i2c-hid and hid-multitouch drivers wake computer during suspend Status in linux package in Ubuntu: Confirmed Bug description: Using the latest 16.04 LTS (Ubuntu 4.4.0-64.85-generic 4.4.44), my Dell Inspiron 7548 wakes everytime the Elan touchpad registers a touch. This causes the machine to wake when the lid is closed, and renders the suspend/hibernate function useless. The only way in which the suspend doesn't respond to the touchpad is if the touchpad is manipulated *during* the suspend process. This is true when removing the drivers or unbinding the hardware in /etc/pm/sleep.d; removing or unbinding will still cause the laptop to wake from sleep unless the touchpad has been touched between removing the driver and suspending the laptop. Disabling everything in /proc/acpi/wakeup has no effect on the issue. The relevant lines from dmesg: [ 174.627776] input: MSFT0001:00 06CB:75BD Touchpad as /devices/pci:00/INT3 433:00/i2c-5/i2c-MSFT0001:00/0018:06CB:75BD.0001/input/input13 [ 174.627923] hid-multitouch 0018:06CB:75BD.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:75BD] on i2c-MSFT0001:00 lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 8087:07dc Intel Corp. Bus 002 Device 003: ID 04f3:2098 Elan Microelectronics Corp. Bus 002 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub (04f3:2098 is the device in question.) lsmod: Module Size Used by i2c_hid20480 0 hid_multitouch 20480 0 hid 118784 2 i2c_hid,hid_multitouch joydev 20480 0 rfcomm 69632 2 drbg 32768 1 ansi_cprng 16384 0 ctr16384 2 ccm20480 2 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 3 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack_ipv4 16384 2 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 1 nf_conntrack 106496 5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 16384 6 bridge126976 0 stp16384 1 bridge llc16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 1 ip_tables 24576 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 11 ip6table_filter,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables bnep 20480 2 nls_iso8859_1 16384 1 dell_laptop20480 0 dell_wmi 16384 0 dcdbas 16384 1 dell_laptop sparse_keymap 16384 1 dell_wmi dell_smm_hwmon 16384 0 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 arc4 16384 2 dell_led 16384 1 media 24576 2 uvcvideo,videodev iwlmvm311296 0 snd_hda_codec_hdmi 53248 1 snd_hda_codec_realtek86016 1 snd_hda_codec_generic77824 1 snd_hda_codec_realtek mac80211 737280 1 iwlmvm intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 snd_hda_intel 40960 12 coretemp 16384 0 snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel kvm_intel 172032 0 kvm 544768 1 kvm_intel snd_hda_core 73728 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
