[Kernel-packages] [Bug 2060716] Re: Screen flickering again
I de-installed the nvidia driver completly and can confirm: This solves
the flickering issue.
Installing it again also adds flickering again.
(Using the 535 "tested" driver from the ubuntu distribution.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060716
Title:
Screen flickering again
Status in linux package in Ubuntu:
New
Bug description:
There is random screen flickering with the build of kernel 6.5.0-27.
Also other builds of 6.5.0 have this flickering.
The *only* build of this version that does work without flickering is
6.5.0-13
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bf 5114 F pipewire
bf 5119 F wireplumber
/dev/snd/controlC0: bf 5119 F wireplumber
/dev/snd/seq:bf 5114 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 9 18:48:35 2024
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=be4de94b-3fb1-44d1-875a-edcd620dc310
InstallationDate: Installed on 2016-03-18 (2944 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=17026de9-c699-420e-ae96-01ac290b69ef ro quiet splash
i915.enable_psr=0 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-27-generic N/A
linux-backports-modules-6.5.0-27-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2023
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N2VET45W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TK000AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN2VET45W(1.30):bd08/29/2023:br1.30:efr1.11:svnLENOVO:pn20TK000AGE:pvrThinkPadX1ExtremeGen3:rvnLENOVO:rn20TK000AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TK_BU_Think_FM_ThinkPadX1ExtremeGen3:
dmi.product.family: ThinkPad X1 Extreme Gen 3
dmi.product.name: 20TK000AGE
dmi.product.sku: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
dmi.product.version: ThinkPad X1 Extreme Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060716/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060716] Re: Screen flickering again
Thanks for your reply. I tested now both PSR settings, and the results
are
There is no screen flickering in 6.5.0-13, regardless of enable_psr=0 or
enable_psr=1
There is always screen flickering (every 1-2 minutes) in 6.5.0-27,
regardless of enable_psr=0 or enable_psr=1
So PSR seems to have no influence on this issue.
I Also attached the edid-Data from
/sys/devices/pci:00/:00:02.0/drm/card0/card0-eDP-1/edid
** Attachment added: "edid.dat"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060716/+attachment/5768138/+files/edid.dat
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060716
Title:
Screen flickering again
Status in linux package in Ubuntu:
New
Bug description:
There is random screen flickering with the build of kernel 6.5.0-27.
Also other builds of 6.5.0 have this flickering.
The *only* build of this version that does work without flickering is
6.5.0-13
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bf 5114 F pipewire
bf 5119 F wireplumber
/dev/snd/controlC0: bf 5119 F wireplumber
/dev/snd/seq:bf 5114 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 9 18:48:35 2024
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=be4de94b-3fb1-44d1-875a-edcd620dc310
InstallationDate: Installed on 2016-03-18 (2944 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=17026de9-c699-420e-ae96-01ac290b69ef ro quiet splash
i915.enable_psr=0 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-27-generic N/A
linux-backports-modules-6.5.0-27-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2023
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N2VET45W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TK000AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN2VET45W(1.30):bd08/29/2023:br1.30:efr1.11:svnLENOVO:pn20TK000AGE:pvrThinkPadX1ExtremeGen3:rvnLENOVO:rn20TK000AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TK_BU_Think_FM_ThinkPadX1ExtremeGen3:
dmi.product.family: ThinkPad X1 Extreme Gen 3
dmi.product.name: 20TK000AGE
dmi.product.sku: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
dmi.product.version: ThinkPad X1 Extreme Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060716/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060716] [NEW] Screen flickering again
Public bug reported:
There is random screen flickering with the build of kernel 6.5.0-27.
Also other builds of 6.5.0 have this flickering.
The *only* build of this version that does work without flickering is
6.5.0-13
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bf 5114 F pipewire
bf 5119 F wireplumber
/dev/snd/controlC0: bf 5119 F wireplumber
/dev/snd/seq:bf 5114 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 9 18:48:35 2024
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=be4de94b-3fb1-44d1-875a-edcd620dc310
InstallationDate: Installed on 2016-03-18 (2944 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=17026de9-c699-420e-ae96-01ac290b69ef ro quiet splash
i915.enable_psr=0 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-27-generic N/A
linux-backports-modules-6.5.0-27-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2023
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N2VET45W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TK000AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN2VET45W(1.30):bd08/29/2023:br1.30:efr1.11:svnLENOVO:pn20TK000AGE:pvrThinkPadX1ExtremeGen3:rvnLENOVO:rn20TK000AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TK_BU_Think_FM_ThinkPadX1ExtremeGen3:
dmi.product.family: ThinkPad X1 Extreme Gen 3
dmi.product.name: 20TK000AGE
dmi.product.sku: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
dmi.product.version: ThinkPad X1 Extreme Gen 3
dmi.sys.vendor: LENOVO
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060716
Title:
Screen flickering again
Status in linux package in Ubuntu:
New
Bug description:
There is random screen flickering with the build of kernel 6.5.0-27.
Also other builds of 6.5.0 have this flickering.
The *only* build of this version that does work without flickering is
6.5.0-13
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bf 5114 F pipewire
bf 5119 F wireplumber
/dev/snd/controlC0: bf 5119 F wireplumber
/dev/snd/seq:bf 5114 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 9 18:48:35 2024
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=be4de94b-3fb1-44d1-875a-edcd620dc310
InstallationDate: Installed on 2016-03-18 (2944 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=17026de9-c699-420e-ae96-01ac290b69ef ro quiet splash
i915.enable_psr=0 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-27-generic N/A
linux-backports-modules-6.5.0-27-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2023
dmi.bios.release: 1.30
[Kernel-packages] [Bug 1964586] [NEW] Mellanox Network Driver Bug Laser Wavelength
Public bug reported: Kernel Version 5.13.0 introduced a new bug. This bug was eventually fixed on Kernel Version 5.15.20. This Bug causes Mellanox Networking Adapters to a lot of errors, when connected over fibre. The standard laser wavelength of this transceivers is 850nm, with this error it increases to 22560nm and invalid information on "Vendor SN" etc. Initial change on Kernel 5.13.0 -> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e19b0a3474ab9ef90dd110af9f39fc87329755f1 Final fix on this Problem -> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=60c48abf62ca57428f66ed25b982593b57c656c3 Applying this fix to Kernel 5.13.0 solves the problem. We wrote an article on this matter with further details (in German) -> https://www.thomas- krenn.com/de/wiki/Mellanox_ConnectX-4/5/6_Bitfehler_ab_Linux_Kernel_5.13 Would it be possible to backport that fix? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 11 10:48:08 2022 InstallationDate: Installed on 2022-03-11 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1964586 Title: Mellanox Network Driver Bug Laser Wavelength Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Kernel Version 5.13.0 introduced a new bug. This bug was eventually fixed on Kernel Version 5.15.20. This Bug causes Mellanox Networking Adapters to a lot of errors, when connected over fibre. The standard laser wavelength of this transceivers is 850nm, with this error it increases to 22560nm and invalid information on "Vendor SN" etc. Initial change on Kernel 5.13.0 -> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e19b0a3474ab9ef90dd110af9f39fc87329755f1 Final fix on this Problem -> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=60c48abf62ca57428f66ed25b982593b57c656c3 Applying this fix to Kernel 5.13.0 solves the problem. We wrote an article on this matter with further details (in German) -> https://www.thomas- krenn.com/de/wiki/Mellanox_ConnectX-4/5/6_Bitfehler_ab_Linux_Kernel_5.13 Would it be possible to backport that fix? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 11 10:48:08 2022 InstallationDate: Installed on 2022-03-11 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1964586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952425] Re: SLUB freelist corruption with ceph
apport-collect fails with 401, so no logs available. ** 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/1952425 Title: SLUB freelist corruption with ceph Status in linux package in Ubuntu: Confirmed Bug description: Several different systems, both vm and bare metal, running Ubuntu 20.04 LTS and different Ubuntu kernel versions with the generic kernel, 5.4.0-91.81, a mainline 5.15 build from kernel.ubuntu.com, 5.11-hwe, show random panics. The crash dumps all show panics within the SLUB memory management stuff. Analyzing the kdump show invalid free list pointers: CACHE OBJSIZE ALLOCATED TOTAL SLABS SSIZE NAME kmem: kmalloc-256: slab: efc73e319900 invalid freepointer: d28996eab0548a12 8a863dc06f40 256 15454 76096 118916k kmalloc-256 The kernel log shows warnings about wrong slab cache: [148148.037307] cache_from_obj: Wrong slab cache. jbd2_journal_handle but object is from kmalloc-256 [148148.037348] WARNING: CPU: 20 PID: 4141624 at mm/slab.h:521 kmem_cache_free+0x260/0x2b0 This shows up if there are several hundred MB per second backup traffic via ceph (I think using rbd). Sometimes it only takes minutes for the system to panic. Hardware: HP DL380 Gen10 AMD EPYC 7502 32-Core Processor 256GB RAM Firmware and microcode are uptodate. I attached one backtraces, the warning message, the panic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952425] [NEW] SLUB freelist corruption with ceph
Public bug reported: Several different systems, both vm and bare metal, running Ubuntu 20.04 LTS and different Ubuntu kernel versions with the generic kernel, 5.4.0-91.81, a mainline 5.15 build from kernel.ubuntu.com, 5.11-hwe, show random panics. The crash dumps all show panics within the SLUB memory management stuff. Analyzing the kdump show invalid free list pointers: CACHE OBJSIZE ALLOCATED TOTAL SLABS SSIZE NAME kmem: kmalloc-256: slab: efc73e319900 invalid freepointer: d28996eab0548a12 8a863dc06f40 256 15454 76096 118916k kmalloc-256 The kernel log shows warnings about wrong slab cache: [148148.037307] cache_from_obj: Wrong slab cache. jbd2_journal_handle but object is from kmalloc-256 [148148.037348] WARNING: CPU: 20 PID: 4141624 at mm/slab.h:521 kmem_cache_free+0x260/0x2b0 This shows up if there are several hundred MB per second backup traffic via ceph (I think using rbd). Sometimes it only takes minutes for the system to panic. Hardware: HP DL380 Gen10 AMD EPYC 7502 32-Core Processor 256GB RAM Firmware and microcode are uptodate. I attached one backtraces, the warning message, the panic. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Panic 1" https://bugs.launchpad.net/bugs/1952425/+attachment/5543591/+files/out -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952425 Title: SLUB freelist corruption with ceph Status in linux package in Ubuntu: New Bug description: Several different systems, both vm and bare metal, running Ubuntu 20.04 LTS and different Ubuntu kernel versions with the generic kernel, 5.4.0-91.81, a mainline 5.15 build from kernel.ubuntu.com, 5.11-hwe, show random panics. The crash dumps all show panics within the SLUB memory management stuff. Analyzing the kdump show invalid free list pointers: CACHE OBJSIZE ALLOCATED TOTAL SLABS SSIZE NAME kmem: kmalloc-256: slab: efc73e319900 invalid freepointer: d28996eab0548a12 8a863dc06f40 256 15454 76096 118916k kmalloc-256 The kernel log shows warnings about wrong slab cache: [148148.037307] cache_from_obj: Wrong slab cache. jbd2_journal_handle but object is from kmalloc-256 [148148.037348] WARNING: CPU: 20 PID: 4141624 at mm/slab.h:521 kmem_cache_free+0x260/0x2b0 This shows up if there are several hundred MB per second backup traffic via ceph (I think using rbd). Sometimes it only takes minutes for the system to panic. Hardware: HP DL380 Gen10 AMD EPYC 7502 32-Core Processor 256GB RAM Firmware and microcode are uptodate. I attached one backtraces, the warning message, the panic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901755] Re: "btrfs subvolume list" sporadically segfaults with linux-image-5.4.0-52-generic
I'm still getting this error on Ubuntu 18.04 with kernel 5.4.0-54.60. Installed Mainline Kernel 5.9.10 as a workaround... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901755 Title: "btrfs subvolume list" sporadically segfaults with linux- image-5.4.0-52-generic Status in linux package in Ubuntu: Fix Committed Bug description: On a BTRFS volume with a lot of subvolumes, I get sporadic segfaults on "btrfs subvolume list", about 1/3 of the time. This is on Ubuntu 20.04. linux-image-5.4.0-48-generic does not experience those segfaults. On #btrfs on freenode, it was pointed out that 5.4.0-52.57 seems to have a regression but not the fix for it committed. To quote from the IRC message: > 5.4.0-52.57 has a regression (a48b73eca4ce btrfs: fix potential deadlock in the search ioctl) and not the fix (1c78544eaa46 btrfs: fix wrong address when faulting in pages in the search ioctl) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected
attached is a hcidump during connect. ** Attachment added: "hcidump -i hci0 -X -R" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1861063/+attachment/5329300/+files/debug_bluetooth.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1861063 Title: Dualshock4 controller doesn't stay connected Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Pairing the Dualshock4 controller works somehow, after several attempts. I expected this to work out of the box but it does not work well at all. Once the pairing is completed, if I try to connect it it doesn't stay connected. I have checked the dmesg and apparently there is a buffer overflow somewhere. I can pair a bluetooth headset to my laptop and the Dualshock4 pairs with my samsung tablet without problems but when I try to pair the dualshock4 to the laptop, running Ubuntu 19.10, it does not work. Dmesg output: [4.099796] Bluetooth: Core ver 2.22 [4.099833] Bluetooth: HCI device and connection manager initialized [4.099837] Bluetooth: HCI socket layer initialized [4.099839] Bluetooth: L2CAP socket layer initialized [4.099842] Bluetooth: SCO socket layer initialized [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018 [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.855413] Bluetooth: BNEP filters: protocol multicast [6.855416] Bluetooth: BNEP socket layer initialized [ 14.234706] Bluetooth: RFCOMM TTY layer initialized [ 14.234711] Bluetooth: RFCOMM socket layer initialized [ 14.234715] Bluetooth: RFCOMM ver 1.11 [ 117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow Release: Description: Ubuntu 19.10 Release: 19.10 Package Info: bluez: Installed: 5.50-0ubuntu4 Candidate: 5.50-0ubuntu4 Version table: *** 5.50-0ubuntu4 500 500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 14:11:19 2020 InstallationDate: Installed on 2019-11-26 (62 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FCS33A00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago) dmi.bios.date: 03/13/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET68W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FCS33A00 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:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 4th dmi.product.name: 20FCS33A00 dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:C6:7F:AE ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:8289 acl:41 sco:0 events:268 errors:0 TX bytes:9494 acl:44 sco:0 commands:163 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1861063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected
Same error during connect with kernel 5.6.0-rc2 When i press the "playstation"-button in the middle, the connect works for a very short time (gets "blue") and gets off with this message in kernel-log: "Dropping L2CAP data: receive buffer overflow" root@ryzen:/home/bastian# dmesg | grep Bluetooth [8.589275] Bluetooth: Core ver 2.22 [8.589293] Bluetooth: HCI device and connection manager initialized [8.589296] Bluetooth: HCI socket layer initialized [8.589298] Bluetooth: L2CAP socket layer initialized [8.589300] Bluetooth: SCO socket layer initialized [8.738524] Bluetooth: hci0: Firmware revision 0.1 build 216 week 27 2019 [8.846171] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [8.846173] Bluetooth: BNEP filters: protocol multicast [8.846179] Bluetooth: BNEP socket layer initialized [ 11.148265] Bluetooth: RFCOMM TTY layer initialized [ 11.148271] Bluetooth: RFCOMM socket layer initialized [ 11.148276] Bluetooth: RFCOMM ver 1.11 [...] [ 76.444821] Bluetooth: Dropping L2CAP data: receive buffer overflow I can apply kernel-patches and debug on advise. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1861063 Title: Dualshock4 controller doesn't stay connected Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Pairing the Dualshock4 controller works somehow, after several attempts. I expected this to work out of the box but it does not work well at all. Once the pairing is completed, if I try to connect it it doesn't stay connected. I have checked the dmesg and apparently there is a buffer overflow somewhere. I can pair a bluetooth headset to my laptop and the Dualshock4 pairs with my samsung tablet without problems but when I try to pair the dualshock4 to the laptop, running Ubuntu 19.10, it does not work. Dmesg output: [4.099796] Bluetooth: Core ver 2.22 [4.099833] Bluetooth: HCI device and connection manager initialized [4.099837] Bluetooth: HCI socket layer initialized [4.099839] Bluetooth: L2CAP socket layer initialized [4.099842] Bluetooth: SCO socket layer initialized [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018 [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.855413] Bluetooth: BNEP filters: protocol multicast [6.855416] Bluetooth: BNEP socket layer initialized [ 14.234706] Bluetooth: RFCOMM TTY layer initialized [ 14.234711] Bluetooth: RFCOMM socket layer initialized [ 14.234715] Bluetooth: RFCOMM ver 1.11 [ 117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow Release: Description: Ubuntu 19.10 Release: 19.10 Package Info: bluez: Installed: 5.50-0ubuntu4 Candidate: 5.50-0ubuntu4 Version table: *** 5.50-0ubuntu4 500 500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 14:11:19 2020 InstallationDate: Installed on 2019-11-26 (62 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FCS33A00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago) dmi.bios.date: 03/13/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET68W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FCS33A00 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:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 4th dmi.product.name: 20FCS33A00 dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:C6:7F:AE ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:8289 acl:41 sco:0 events:268 errors:0 TX bytes:9494 acl:44 sco:0 commands:163 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1861063/+subscriptions -- Mai
[Kernel-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected
Official specs say about den 2nd generation, that the weight is 209-210 grams. https://en.wikipedia.org/wiki/DualShock The Internet is full of people having problem to pair these, but it worked with older kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1861063 Title: Dualshock4 controller doesn't stay connected Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Pairing the Dualshock4 controller works somehow, after several attempts. I expected this to work out of the box but it does not work well at all. Once the pairing is completed, if I try to connect it it doesn't stay connected. I have checked the dmesg and apparently there is a buffer overflow somewhere. I can pair a bluetooth headset to my laptop and the Dualshock4 pairs with my samsung tablet without problems but when I try to pair the dualshock4 to the laptop, running Ubuntu 19.10, it does not work. Dmesg output: [4.099796] Bluetooth: Core ver 2.22 [4.099833] Bluetooth: HCI device and connection manager initialized [4.099837] Bluetooth: HCI socket layer initialized [4.099839] Bluetooth: L2CAP socket layer initialized [4.099842] Bluetooth: SCO socket layer initialized [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018 [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.855413] Bluetooth: BNEP filters: protocol multicast [6.855416] Bluetooth: BNEP socket layer initialized [ 14.234706] Bluetooth: RFCOMM TTY layer initialized [ 14.234711] Bluetooth: RFCOMM socket layer initialized [ 14.234715] Bluetooth: RFCOMM ver 1.11 [ 117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow Release: Description: Ubuntu 19.10 Release: 19.10 Package Info: bluez: Installed: 5.50-0ubuntu4 Candidate: 5.50-0ubuntu4 Version table: *** 5.50-0ubuntu4 500 500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 14:11:19 2020 InstallationDate: Installed on 2019-11-26 (62 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FCS33A00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago) dmi.bios.date: 03/13/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET68W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FCS33A00 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:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 4th dmi.product.name: 20FCS33A00 dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:C6:7F:AE ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:8289 acl:41 sco:0 events:268 errors:0 TX bytes:9494 acl:44 sco:0 commands:163 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1861063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected
@Goran: both of mine controllers have a weight of 202 grams... question: they where working on your machine earlier? I have an onboard Intel Wireless-AC 9260 (rev 29) with recent firmware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1861063 Title: Dualshock4 controller doesn't stay connected Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Pairing the Dualshock4 controller works somehow, after several attempts. I expected this to work out of the box but it does not work well at all. Once the pairing is completed, if I try to connect it it doesn't stay connected. I have checked the dmesg and apparently there is a buffer overflow somewhere. I can pair a bluetooth headset to my laptop and the Dualshock4 pairs with my samsung tablet without problems but when I try to pair the dualshock4 to the laptop, running Ubuntu 19.10, it does not work. Dmesg output: [4.099796] Bluetooth: Core ver 2.22 [4.099833] Bluetooth: HCI device and connection manager initialized [4.099837] Bluetooth: HCI socket layer initialized [4.099839] Bluetooth: L2CAP socket layer initialized [4.099842] Bluetooth: SCO socket layer initialized [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018 [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.855413] Bluetooth: BNEP filters: protocol multicast [6.855416] Bluetooth: BNEP socket layer initialized [ 14.234706] Bluetooth: RFCOMM TTY layer initialized [ 14.234711] Bluetooth: RFCOMM socket layer initialized [ 14.234715] Bluetooth: RFCOMM ver 1.11 [ 117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow Release: Description: Ubuntu 19.10 Release: 19.10 Package Info: bluez: Installed: 5.50-0ubuntu4 Candidate: 5.50-0ubuntu4 Version table: *** 5.50-0ubuntu4 500 500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 14:11:19 2020 InstallationDate: Installed on 2019-11-26 (62 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FCS33A00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago) dmi.bios.date: 03/13/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET68W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FCS33A00 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:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 4th dmi.product.name: 20FCS33A00 dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:C6:7F:AE ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:8289 acl:41 sco:0 events:268 errors:0 TX bytes:9494 acl:44 sco:0 commands:163 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1861063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected
Same issue for me with fresh mainline kernel 5.5.2 on debian. The controller model (the same) is: CUH-ZCT2U -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1861063 Title: Dualshock4 controller doesn't stay connected Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Pairing the Dualshock4 controller works somehow, after several attempts. I expected this to work out of the box but it does not work well at all. Once the pairing is completed, if I try to connect it it doesn't stay connected. I have checked the dmesg and apparently there is a buffer overflow somewhere. I can pair a bluetooth headset to my laptop and the Dualshock4 pairs with my samsung tablet without problems but when I try to pair the dualshock4 to the laptop, running Ubuntu 19.10, it does not work. Dmesg output: [4.099796] Bluetooth: Core ver 2.22 [4.099833] Bluetooth: HCI device and connection manager initialized [4.099837] Bluetooth: HCI socket layer initialized [4.099839] Bluetooth: L2CAP socket layer initialized [4.099842] Bluetooth: SCO socket layer initialized [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018 [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.855413] Bluetooth: BNEP filters: protocol multicast [6.855416] Bluetooth: BNEP socket layer initialized [ 14.234706] Bluetooth: RFCOMM TTY layer initialized [ 14.234711] Bluetooth: RFCOMM socket layer initialized [ 14.234715] Bluetooth: RFCOMM ver 1.11 [ 117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow Release: Description: Ubuntu 19.10 Release: 19.10 Package Info: bluez: Installed: 5.50-0ubuntu4 Candidate: 5.50-0ubuntu4 Version table: *** 5.50-0ubuntu4 500 500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 14:11:19 2020 InstallationDate: Installed on 2019-11-26 (62 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FCS33A00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago) dmi.bios.date: 03/13/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET68W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FCS33A00 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:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 4th dmi.product.name: 20FCS33A00 dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:C6:7F:AE ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:8289 acl:41 sco:0 events:268 errors:0 TX bytes:9494 acl:44 sco:0 commands:163 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1861063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829598] Re: GCC Update breaks CC checks with dkms and others because kernel compiled in old gcc version
No it's not, had 3 kernel updates from the stable release in the meantime - and needed to ignore cc version while installing Nvidia driver, dkms still does not work, thus I'm forced to install the driver manually every time the kernel updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829598 Title: GCC Update breaks CC checks with dkms and others because kernel compiled in old gcc version Status in linux package in Ubuntu: Confirmed Bug description: System: Xubuntu 18.04.02 due to an gcc update, several programs give errors. This includes DKMS as the GCC version installed is newer than the version the kernel was compiled with. This happens with the newest kernel from the stable channel GCC versions in question: Kernel GCC version 7.3.0-16ubuntu3 in my case installed 7.4.0-1ubuntu1~18.04 this may affect GPU Drivers (nvidia in my case) as they are not able to load properly - which results in a Forced resolution of 1024*768 at 78 hz Kernel versions prior to 4.15.0-50-generic are affected more or less too, as they are compiled with older gcc versions too. newer kernel version not available in stable channel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ebiko 2099 F pulseaudio /dev/snd/controlC2: ebiko 2099 F pulseaudio /dev/snd/controlC0: ebiko 2099 F pulseaudio CurrentDesktop: XFCE Date: Sat May 18 08:53:28 2019 InstallationDate: Installed on 2018-04-28 (384 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=587302e0-65e3-4866-b20a-666e71964992 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII GENE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/29/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIGENE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829598] [NEW] GCC Update breaks CC checks with dkms and others because kernel compiled in old gcc version
Public bug reported: System: Xubuntu 18.04.02 due to an gcc update, several programs give errors. This includes DKMS as the GCC version installed is newer than the version the kernel was compiled with. This happens with the newest kernel from the stable channel GCC versions in question: Kernel GCC version 7.3.0-16ubuntu3 in my case installed 7.4.0-1ubuntu1~18.04 this may affect GPU Drivers (nvidia in my case) as they are not able to load properly - which results in a Forced resolution of 1024*768 at 78 hz Kernel versions prior to 4.15.0-50-generic are affected more or less too, as they are compiled with older gcc versions too. newer kernel version not available in stable channel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ebiko 2099 F pulseaudio /dev/snd/controlC2: ebiko 2099 F pulseaudio /dev/snd/controlC0: ebiko 2099 F pulseaudio CurrentDesktop: XFCE Date: Sat May 18 08:53:28 2019 InstallationDate: Installed on 2018-04-28 (384 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=587302e0-65e3-4866-b20a-666e71964992 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII GENE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/29/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIGENE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dkms gcc nvidia -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829598 Title: GCC Update breaks CC checks with dkms and others because kernel compiled in old gcc version Status in linux package in Ubuntu: New Bug description: System: Xubuntu 18.04.02 due to an gcc update, several programs give errors. This includes DKMS as the GCC version installed is newer than the version the kernel was compiled with. This happens with the newest kernel from the stable channel GCC versions in question: Kernel GCC version 7.3.0-16ubuntu3 in my case installed 7.4.0-1ubuntu1~18.04 this may affect GPU Drivers (nvidia in my case) as they are not able to load properly - which results in a Forced resolution of 1024*768 at 78 hz Kernel versions prior to 4.15.0-50-generic are affected more or less too, as they are compiled with older gcc versions too. newer kernel version not available in stable channel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ebiko 2099 F pulseaudio /dev/snd/controlC2: ebiko 2099 F pulseaudio /dev/snd/controlC0: ebiko 2099 F pulseaudio CurrentDesktop: XFCE Date: Sat May 18 08:53:28 2019 InstallationDate: Installed on 2018-04-28 (384 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=587302e0-65e3-4866-b20a-666e71964992 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1723736] Re: Touchpad not detected - Lenovo ideapad 320-15IKB
Ok I tried the -proposed kernel for xenial and artful. Problem is, I'm using zesty. I installed the -proposed kernels and headers, and after a reboot neither my touchpad nor my wifi was working. I admit that I am a linux beginner, so I'm not sure if it is even possible to use those xenial and artful kernels with my zesty Ubuntu. ** Tags removed: verification-needed-artful verification-needed-xenial ** Tags added: verification-failed-artful verification-failed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723736 Title: Touchpad not detected - Lenovo ideapad 320-15IKB Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: Description: Ubuntu 17.04 Release: 17.04 Basically the same bug as described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852 I'm using a Lenovo ideapad 320-15IKB, though. I also tried the latest mainline kernel (4.13.7) which didn't help. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: boot/vmlinuz-4.10.0-19-generic] ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meradanis 1747 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 15 14:23:54 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=912e6e24-9770-4e44-914b-9d181193c23d InstallationDate: Installed on 2017-10-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 81BG ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic root=UUID=a7c89b92-6e62-49e5-a4b0-052b751a2d6e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 6JCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6JCN14WW:bd09/28/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.name: 81BG dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723736] Re: Touchpad not detected - Lenovo ideapad 320-15IKB
kernel-bug-exists-upstream I tried the mainline kerne 4.14 RC5. The touchpad was not recognized. ** 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/1723736 Title: Touchpad not detected - Lenovo ideapad 320-15IKB Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 17.04 Release: 17.04 Basically the same bug as described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852 I'm using a Lenovo ideapad 320-15IKB, though. I also tried the latest mainline kernel (4.13.7) which didn't help. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: boot/vmlinuz-4.10.0-19-generic] ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meradanis 1747 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 15 14:23:54 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=912e6e24-9770-4e44-914b-9d181193c23d InstallationDate: Installed on 2017-10-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 81BG ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic root=UUID=a7c89b92-6e62-49e5-a4b0-052b751a2d6e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 6JCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6JCN14WW:bd09/28/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.name: 81BG dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723736] Re: Touchpad not detected - Lenovo ideapad 320-15IKB
The kernel from khfeng did fix the issue. This is a snippet from cat /proc/bus/input/devices I: Bus=0018 Vendor=04f3 Product=005b Version= N: Name="Elan Touchpad" P: Phys= S: Sysfs=/devices/pci:00/:00:15.0/i2c_designware.0/i2c-4/i2c-ELAN0611:00/input/input15 U: Uniq= H: Handlers=mouse1 event15 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=66380001303 ** Attachment added: "cat /proc/bus/input/devices" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723736/+attachment/4973475/+files/report.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/1723736 Title: Touchpad not detected - Lenovo ideapad 320-15IKB Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 17.04 Release: 17.04 Basically the same bug as described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852 I'm using a Lenovo ideapad 320-15IKB, though. I also tried the latest mainline kernel (4.13.7) which didn't help. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: boot/vmlinuz-4.10.0-19-generic] ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meradanis 1747 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 15 14:23:54 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=912e6e24-9770-4e44-914b-9d181193c23d InstallationDate: Installed on 2017-10-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 81BG ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic root=UUID=a7c89b92-6e62-49e5-a4b0-052b751a2d6e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 6JCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6JCN14WW:bd09/28/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.name: 81BG dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723736] Re: Touchpad not detected - Lenovo ideapad 320-15IKB
I also tried this workaround, which didn't work: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852/comments/10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723736 Title: Touchpad not detected - Lenovo ideapad 320-15IKB Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 17.04 Release: 17.04 Basically the same bug as described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852 I'm using a Lenovo ideapad 320-15IKB, though. I also tried the latest mainline kernel (4.13.7) which didn't help. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: boot/vmlinuz-4.10.0-19-generic] ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meradanis 1747 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 15 14:23:54 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=912e6e24-9770-4e44-914b-9d181193c23d InstallationDate: Installed on 2017-10-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 81BG ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic root=UUID=a7c89b92-6e62-49e5-a4b0-052b751a2d6e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 6JCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6JCN14WW:bd09/28/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.name: 81BG dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723736] [NEW] Touchpad not detected - Lenovo ideapad 320-15IKB
Public bug reported: Description:Ubuntu 17.04 Release:17.04 Basically the same bug as described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852 I'm using a Lenovo ideapad 320-15IKB, though. I also tried the latest mainline kernel (4.13.7) which didn't help. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: boot/vmlinuz-4.10.0-19-generic] ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meradanis 1747 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 15 14:23:54 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=912e6e24-9770-4e44-914b-9d181193c23d InstallationDate: Installed on 2017-10-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 81BG ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic root=UUID=a7c89b92-6e62-49e5-a4b0-052b751a2d6e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 6JCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6JCN14WW:bd09/28/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.name: 81BG dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug zesty ** Attachment added: "cat /proc/bus/input/devices" https://bugs.launchpad.net/bugs/1723736/+attachment/4971639/+files/lala.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/1723736 Title: Touchpad not detected - Lenovo ideapad 320-15IKB Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 17.04 Release: 17.04 Basically the same bug as described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852 I'm using a Lenovo ideapad 320-15IKB, though. I also tried the latest mainline kernel (4.13.7) which didn't help. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: boot/vmlinuz-4.10.0-19-generic] ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meradanis 1747 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 15 14:23:54 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=912e6e24-9770-4e44-914b-9d181193c23d InstallationDate: Installed on 2017-10-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 81BG ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic root=UUID=a7c89b92-6e62-49e5-a4b0-052b751a2d6e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 6JCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6JCN14WW:bd09/28/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.name: 81BG dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723736/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card
For me, 4.4.0-78 actually made it worse on my Dell Latitude E7250 to the point where I had to downgrade to 4.4.0-72 in order to be able to use external monitors again. With versions prior to 4.4.0-78, running xrandr a couple of times would usually cycle through all kinds of weird broken setups with parts of what was supposed to be shown on one monitor being shown in the corner of a different monitor and similar problems. But after a few attempts, it used to somehow "get it right" and display the right layout. With 4.4.0-78, this workaround stopped working as even though the layout may be correct, there simply is "no signal" on external monitors. They are detected by xrandr as being present and connected, the window manager appears to recognize them but neither of them receives a video signal so they just go to sleep after a few seconds. The built-in notebook display keeps working all the time. External monitors appear to work up to the point at which the switch from "VESA VGA" to "inteldrmfb" occurs. After going back to 4.4.0-72, all issues went away. Even the layout options given to xrandr now work as expected. I looks like something is horribly wrong with Intel graphics support. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582823] Re: Text not rendering correctly after resume from suspend
Changed status to "Confirmed" since hackel seems to have executed the requested "apport-collect". This bug affects me too. I'm also running the i915 driver: $ sudo lshw -c video *-display description: VGA compatible controller product: 4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:28 memory:f000-f03f memory:e000-efff ioport:5000(size=64) ** 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/1582823 Title: Text not rendering correctly after resume from suspend Status in gtk+3.0 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04, I've been experiencing frequent difficulties resuming from suspend, causing text not to be displayed at all, or wrong characters to be displayed. Please see the attached screenshots. I don't know what part of the system this lies in. It seems to affect all gtk apps at least. Chromium renders just fine when this happens, other than the titlebar. Similarly, Cool Retro Term renders correctly, which obviously doesn't use gtk, while Gnome Terminal and Guake do not. This suggests it could be related to framebuffer corruption, but this report was made with a much earlier kernel, and I had no such problems under 15.10. http://askubuntu.com/questions/688306/text-missing- garbled-after-laptop-resumes-from-sleep-mode libgtk-3-0 3.18.9-1ubuntu3 linux-image-4.4.0-22-generic 4.4.0-22.40 xserver-xorg-core 2:1.18.3-1ubuntu2 xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 lshw -c video *-display description: VGA compatible controller product: 4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:30 memory:b200-b23f memory:a000-afff ioport:5000(size=64) dmesg | grep i915 [1.383957] [drm] Initialized i915 1.6.0 20151010 for :00:02.0 on minor 0 [1.534467] i915 :00:02.0: fb0: inteldrmfb frame buffer device [2.718041] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [2.718060] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun [2.733438] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B [2.733460] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun [4.137698] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 66.585338] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=4267 end=4268) time 282 us, min 1073, max 1079, scanline start 1059, end 1090 [ 277.577183] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=16480 end=16481) time 363 us, min 894, max 899, scanline start 875, end 900 [ 284.581315] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=16900 end=16901) time 358 us, min 894, max 899, scanline start 891, end 905 [ 300.589410] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=18424 end=18425) time 210 us, min 1073, max 1079, scanline start 1070, end 1084 [ 302.574085] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=18544 end=18545) time 338 us, min 1073, max 1079, scanline start 1061, end 1078 [ 470.560521] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=28707 end=28708) time 301 us, min 1073, max 1079, scanline start 1071, end 1091 [ 595.553386] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=36269 end=36270) time 107 us, min 1073, max 1079, scanline start 1056, end 1083 [ 1043.512803] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=63370 end=63371) time 402 us, min 1073, max 1079, scanline start 1058, end 1084 [ 1106.508551] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=66184 end=66185) time 424 us, min 894, max 899, scanline start 876, end 895 --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse:
[Kernel-packages] [Bug 1243693] Re: RT3290 12.04 new kernel
3.2.0-58 kernel works for me. everything is working again !! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1243693 Title: RT3290 12.04 new kernel Status in “linux” package in Ubuntu: Fix Released Bug description: The problem dates on 22. oct 2013 Linux Ubuntu 12.04 LTS 64 Bit - Update to Kernel 3.2.0-55 - rebboot and WLAN function gone the last Kernel 3.2.0-54 was no problem with the Ralink Corp RT3290 Wireless 802.11 n lspci still shows the chip iwconfig shows no wireless extentions The Ralink is in many HP Notebooks like the HP 655 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1243693] Re: RT3290 12.04 new kernel
I have the same problem. A kernel update in October screwed up the wireless card. When I boot the laptop ( HP 655 Ubuntu certified) I can choose which kernel I want to use. I choose for 3.2.0-32. It was installed when i bought the notebook. 3.2.0-55 and 3.2.0-56 kernels both screw the wireless driver or card up. https://answers.launchpad.net/ubuntu-certification/+question/238136 In this tread there is some additional information from myself and someone else. Personally I am not going to try the newest kernel. I wnat my card to work with the kernel that is installed by the update-manager. I bought this notebook especially because it has ubuntu certification but it is not working properly. A shame if you ask 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/1243693 Title: RT3290 12.04 new kernel Status in “linux” package in Ubuntu: Incomplete Bug description: The problem dates on 22. oct 2013 Linux Ubuntu 12.04 LTS 64 Bit - Update to Kernel 3.2.0-55 - rebboot and WLAN function gone the last Kernel 3.2.0-54 was no problem with the Ralink Corp RT3290 Wireless 802.11 n lspci still shows the chip iwconfig shows no wireless extentions The Ralink is in many HP Notebooks like the HP 655 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
