[Kernel-packages] [Bug 1919250] Re: [ASUS TUF Gaming FX505DT] [ELAN1200:00 04F3:30BA] touchpad freeze or disable itself after laptop go to suspend
Please try a newer kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D or just try live booting the latest preview of 21.10 from USB: http://cdimage.ubuntu.com/daily-live/current/ We would like to know if the issue is already fixed in some kernel version newer than 5.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/1919250 Title: [ASUS TUF Gaming FX505DT] [ELAN1200:00 04F3:30BA] touchpad freeze or disable itself after laptop go to suspend Status in linux package in Ubuntu: Incomplete Bug description: touchpad freeze or disable itself after laptop go to suspend... and non of the solutions like "modprobe -r psmouse"/ "modprobe psmouse" do work (doesn't work). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: MATE Date: Mon Mar 15 16:58:29 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev ff) (prog-if ff) Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1] InstallationDate: Installed on 2017-06-21 (1363 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=5a4a3b87-22ad-46cb-b313-e45f053e558e ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX505DT.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX505DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 12.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.310:bd12/24/2019:br5.14:efr12.0:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX505DT_FX505DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919250/+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 1938669] [NEW] Epiphan framegrabbers stream only once then need unbinding/rebinding to uvcvideo to work again
Public bug reported: Video capture devices made by Epiphan Systems (vendor id 0x2b77) work once, but as soon as the video device is closed (or even if it is kept open but the application issues a VIDIOC_STREAMOFF ioctl) it won't work again - subsequent calls to VIDOC_DQBUF simply hang - until the device is unbound from and rebound to the uvcvideo module. (modprobe -r uvcvideo; modprobe uvcvideo also works). For example: ffplay /dev/video0 -- works fine and shows the captured stream. ffplay /dev/video0 -- when run a second time: hangs and does not capture anything modprobe -r uvcvideo ; modprobe uvcvideo; ffplay /dev/video -- works fine again. Experimenting with the device and the uvcvideo module source code reveals that problem is the device is expecting SET_INTERFACE(0) to be sent to return it to a state where it can accept control requests and start streaming again. The code in uvc_video.c has several comments stating that some bulk- transfer devices require a SET_INTERFACE(0) call to be made before any control commands, even though 0 is already the default and only valid interface value. And, the function uvc_video_init makes such a call (which is why the device starts working again after rebinding to the uvcvideo module). But no such call is made when streaming is stopped then restarted. Furthermore, SET_INTERFACE(0) is the mechanism by which isochronous devices are told to stop streaming, and the comments in uvc_video_stop_streaming state that the UVC specification is unclear on how a bulk-based device should be told to stop streaming, so it is reasonable to expect this particular bulk-based device might be expecting the same SET_INTERFACE(0) call that an isochronous device would get as means of being told to stop streaming. The attached patch fixes the problem for these Epiphan devices by adding a SET_INTERFACE(0) call in two places. Either one by itself is sufficient to resolve the symptoms but I think it is probably safest to include both. The first hunk adds a SET_INTERFACE(0) call in uvc_video_start_streaming, but only in the bulk-based case where 0 is the only possible interface value (it won't mess with an isochronous device that might be set to a different interface). The second hunk modifies the behaviour of uvc_video_stop_streaming to call SET_INTERFACE(0) unconditionally instead of only calling it for isochronous devices. Since interface 0 should already be set on non- isochronous devices, it should be safe to set it again, and this way devices that are expecting it as a signal to stop streaming will get it. The patch is against 5.4.137 in the vanilla kernel.org source tree, but also applies cleanly to the 5.8.63 kernel in Ubuntu 20.4 LTS and to the 5.14-rc3 release candidate kernel. Since this is clearly an upstream issue unrelated to any vendor modifications, should I also submit an upstream bug report directly to bugzilla.kernel.org? ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Patch added: "uvc_video.patch" https://bugs.launchpad.net/bugs/1938669/+attachment/5515189/+files/uvc_video.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938669 Title: Epiphan framegrabbers stream only once then need unbinding/rebinding to uvcvideo to work again Status in linux package in Ubuntu: New Bug description: Video capture devices made by Epiphan Systems (vendor id 0x2b77) work once, but as soon as the video device is closed (or even if it is kept open but the application issues a VIDIOC_STREAMOFF ioctl) it won't work again - subsequent calls to VIDOC_DQBUF simply hang - until the device is unbound from and rebound to the uvcvideo module. (modprobe -r uvcvideo; modprobe uvcvideo also works). For example: ffplay /dev/video0 -- works fine and shows the captured stream. ffplay /dev/video0 -- when run a second time: hangs and does not capture anything modprobe -r uvcvideo ; modprobe uvcvideo; ffplay /dev/video -- works fine again. Experimenting with the device and the uvcvideo module source code reveals that problem is the device is expecting SET_INTERFACE(0) to be sent to return it to a state where it can accept control requests and start streaming again. The code in uvc_video.c has several comments stating that some bulk- transfer devices require a SET_INTERFACE(0) call to be made before any control commands, even though 0 is already the default and only valid interface value. And, the function uvc_video_init makes such a call (which is why the device starts working again after rebinding to the uvcvideo module). But no such call is made when streaming is stopped then restarted. Furthermore, SET_INTERFACE(0) is the mechanism by which isochronous devices are told to stop streaming, and the comments in uvc_video_stop_streaming state that the UVC specification
[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround
Same thing with 5.8.0-63-generic, on 20.04.2. Need a lot of rebooting to load the kernel. Adding kernel options: nolapic => loads the kernel, but disables multicore, making use impracticable intremap=off => loads the kernel, does not seem to have noticeable side effects -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808418 Title: Thinkpad T430u won't boot without noapic workaround Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: I've used Ubuntu on this specific machine for years without problems, but starting with the 4.13 kernel that came with the 17.10 HWE and continuing into 18.04 kernels my computer would no longer boot, hanging at various screens: - A blank screen with a flashing cursor - A screen with this message: Loading Linux 4.13.0.36-generic ... Loading initial ramdisk ... - A screen with kernel messages, ending in: APCI: EC: interrupt blocked I've encountered the bug in a number of kernels, including: - 4.13.0-32 - 4.13.0-36 - 4.13.0-37 - 4.15.0-24 - 4.15.0-34 - 4.15.0-36 - 4.15.0-38 - 4.15.0-42 - 4.20.0-rc7 I was able to work around the issue by adding noapic to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic" I'm not entirely sure of the consequences of this workaround, but one thing I've noticed is significantly reduced battery life. This bug seems very similar to what's described here for the Thinkpad E485/E585: https://evilazrael.de/node/401 I'll attach screenshots of various times I've encountered this bug over the last year. $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy linux-image-4.15.0-42-generic linux-image-4.15.0-42-generic: Installed: 4.15.0-42.45 Candidate: 4.15.0-42.45 Version table: *** 4.15.0-42.45 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bryan 2349 F pulseaudio CurrentDesktop: XFCE Date: Thu Dec 13 15:31:15 2018 HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac InstallationDate: Installed on 2014-05-08 (1680 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 3351CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago) dmi.bios.date: 06/01/2018 dmi.bios.vendor: LENOVO dmi.bios.version: H6ETA0WW (2.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 3351CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430u dmi.product.name: 3351CTO dmi.product.version: ThinkPad T430u dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1919250] Re: [ASUS TUF Gaming FX505DT] [ELAN1200:00 04F3:30BA] touchpad freeze or disable itself after laptop go to suspend
I knew my dear, 20.04 is older but more stable; exactly for this reason I got back to old one. It was unwise of me to upgrade distro to 20.10 (newer), usually it has more bugs. To answer your question, there is not any problem with 20.04 LTS, for now, but if start to add gnome extensions (I do not know which one) More probably is gone destabilize the system. I had this suspicious before that there are several conflicts when one add additional features of gnome with Ubuntu desktop vs without them, because before I was using LTS before upgrade and I found some instability when I started to add gnome extensions to Unity. I'm not gonna do that again. On Sun, Aug 1, 2021, 10:54 PM Daniel van Vugt <1919...@bugs.launchpad.net> wrote: > LTS is older than 20.10, not newer. Does 21.04 have the problem? > > https://ubuntu.com/download/desktop > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1919250 > > Title: > [ASUS TUF Gaming FX505DT] [ELAN1200:00 04F3:30BA] touchpad freeze or > disable itself after laptop go to suspend > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > touchpad freeze or disable itself after laptop go to suspend... and > non of the solutions like "modprobe -r psmouse"/ "modprobe psmouse" do > work (doesn't work). > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: xorg 1:7.7+19ubuntu15 > ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 > Uname: Linux 5.8.0-45-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.11-0ubuntu50.5 > Architecture: amd64 > BootLog: > > CasperMD5CheckResult: skip > CompizPlugins: > [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] > CompositorRunning: None > CurrentDesktop: MATE > Date: Mon Mar 15 16:58:29 2021 > DistUpgraded: Fresh install > DistroCodename: groovy > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GconfCompiz: >/apps/compiz-1/general: > /apps/compiz-1/general/screen0: > /apps/compiz-1/general/screen0/options: >active_plugins = > [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] > GraphicsCard: >NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] > (rev ff) (prog-if ff) >Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) > (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1] > InstallationDate: Installed on 2017-06-21 (1363 days ago) > InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 > (20170215.2) > MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic > root=UUID=5a4a3b87-22ad-46cb-b313-e45f053e558e ro > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 12/24/2019 > dmi.bios.release: 5.14 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: FX505DT.310 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: FX505DT > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.ec.firmware.release: 12.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.310:bd12/24/2019:br5.14:efr12.0:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: TUF Gaming > dmi.product.name: TUF Gaming FX505DT_FX505DT > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 > version.libdrm2: libdrm2 2.4.102-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200714-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919250/+subscriptions > > -- You received this bug
[Kernel-packages] [Bug 1934864] Re: [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934864 Title: [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: SRU justification: [Impact] When plugin HDMI cable, no HDMI output, kernel reported error: [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port [Fix] Legacy LSPCON chip from MCA and Parade is only used for platforms, Limit the support between GEN9 and GEN10. The commit is already in 5.13, so only SRU for oem-5.10 and hirsute. [Test] Verified on hardware, HDMI output works fine. [Where problems could occur] The HDMI output may break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1934864/+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 1936790] Re: [SRU][OEM-5.13/U] Fix firmware reload failure of MT7921
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936790 Title: [SRU][OEM-5.13/U] Fix firmware reload failure of MT7921 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: SRU justification: [Impact] MT7921 is supported on 5.13 kernel, mt76 driver failed to work when reboot. SRUed for 5.13+ kernel only. [Fix] MT7921 needs both driver and firmware, firmware is SRUed. When reboot, the firmware is already reloaded, driver probe breaks. Continue to probe if firmware status is OK. [Test] Verified on hardware, After reboot system wifi works fine. [Where problems could occur] The MT7921 wifi may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936790/+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 1938538] Re: Touchpad not working in Ubuntu 21.04
Hi, 5.11 hrisute kernel doesn't fully support this laptop. Please use 5.10-oem kernel or 5.13+ kernel instead. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938538 Title: Touchpad not working in Ubuntu 21.04 Status in linux package in Ubuntu: New Bug description: Lenovo Thinkpad X1 Yoga Titanium (Model: 20QBS02G00) Synaptics touchpad not working after Upgrade from 20.04 LTS to 21.04 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amelie 4095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 30 12:09:12 2021 InstallationDate: Installed on 2021-07-28 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20QBS02G00 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgubuntu-root ro nomodeset quiet splash acpi_backlight=vendor acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-07-29 (0 days ago) dmi.bios.date: 05/20/2021 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: N2MET49W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QBS02G00 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.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN2MET49W(1.14):bd05/20/2021:br1.14:efr1.9:svnLENOVO:pn20QBS02G00:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QBS02G00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Titanium Gen 1 dmi.product.name: 20QBS02G00 dmi.product.sku: LENOVO_MT_20QB_BU_Think_FM_ThinkPad X1 Titanium Gen 1 dmi.product.version: ThinkPad X1 Titanium Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938538/+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 1937914] Re: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work
** Tags added: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937914 Title: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work Status in linux package in Ubuntu: New Bug description: While starting the my laptop (Computer Model: HP Probook 450 G6 ProdID 5YH15UT#ABA Memory: 15.5 GB Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8 Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2) Disk Capacity: 256.1 GB) which runs (OS Name: Ubuntu 20.04.2 LTS OS Type: 64-bit GNOME Version: 3.36.8 Windowing System: X11) the monitor turns off as soon as Ubuntu loads. The OS loads as normal and my external monitor still works, but my laptop monitor does not. I was able to fix the problem by pressing ESC as soon as the HP logo appears during start-up, then selecting "Advanced Ubuntu Options", then choosing an older version of Ubuntu (currently that's ...5.4.0-48..., while I believe the latest version is ...5.8.0-66...). It seems clear that this problem is caused by a bug that was introduced in one of the more recent updates (...5.8.0-59..., maybe?). I am not at all sure that the problem is in xorg; the package identification webpage just suggested that, if the monitor is blank when I would expect to see the Ubuntu logo during startup, then I should say that the relevant package is xorg. I am more than happy to run additional diagnostics that you would recommend if that would help you diagnose and fix the problem. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 14:28:51 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8538] Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:8542] InstallationDate: Installed on 2021-07-06 (17 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00b7 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b66a Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 004: ID 0bda:b00b Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8bde40df-a693-4c3a-b5be-05611212add4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.11.01 dmi.board.name: 8538 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2A.00 dmi.chassis.asset.tag: 5CD9308H3X dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook450G6:pvr:rvnHP:rn8538:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 450 G6 dmi.product.sku: 5YH15UT#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937914/+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 1919250] Re: [ASUS TUF Gaming FX505DT] [ELAN1200:00 04F3:30BA] touchpad freeze or disable itself after laptop go to suspend
LTS is older than 20.10, not newer. Does 21.04 have the problem? https://ubuntu.com/download/desktop -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1919250 Title: [ASUS TUF Gaming FX505DT] [ELAN1200:00 04F3:30BA] touchpad freeze or disable itself after laptop go to suspend Status in linux package in Ubuntu: Incomplete Bug description: touchpad freeze or disable itself after laptop go to suspend... and non of the solutions like "modprobe -r psmouse"/ "modprobe psmouse" do work (doesn't work). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: MATE Date: Mon Mar 15 16:58:29 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev ff) (prog-if ff) Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1] InstallationDate: Installed on 2017-06-21 (1363 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=5a4a3b87-22ad-46cb-b313-e45f053e558e ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX505DT.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX505DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 12.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.310:bd12/24/2019:br5.14:efr12.0:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX505DT_FX505DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919250/+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 1919116] Re: Intel e1000e blocks the system to enter PC10 on TGL platform
Hirsute got this fixed through stable update since Ubuntu-5.11.0-18.19 ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1919116 Title: Intel e1000e blocks the system to enter PC10 on TGL platform Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Invalid Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] The deepest package cstate is PC9 and fails to enter low power mode during s2i on Tiger Lake platform. [Fix] Intel provides a fix for TGL platform https://patchwork.kernel.org/project/platform-driver-x86/patch/20210305190608.1834164-1-david.e@linux.intel.com/ [Test] Verified on Dell TGL platforms and it works as expected. [Where problem could occur] It actually adds a quirk for tgl platform to ignore Latency Tolerance Reporting (LTR) in pmc_core driver, that makes GBE on TGL won't block the system to enter deeper PC state. It should be safe for all TGL platforms. [Misc] Currently, this commit is not accepted and a v2 is expected. So, submit this commit to oem kernel only and will revert it and submit final version of this patch to ubuntu kernels later. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1919116/+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 1938408] Re: EHL board does not support soft reboot
** Changed in: linux-intel (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938408 Title: EHL board does not support soft reboot Status in intel: New Status in linux-intel package in Ubuntu: In Progress Bug description: [Summary]Telling the EHL board to reboot from within Ubuntu causes it to hang, forcing you to do a hard reboot. [Steps to reproduce] 1. Open terminal window. 2. $ reboot [Expected result] System should gracefullyl reboot. [Actual result] Screen goes blank except for a cursor. System does not reboot. You must hard reboot (pull the plug) [Failure rate]100% [Additional information] CID: 202105-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938408/+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 1938413] Re: Shutdown hangs on EHL board
** Changed in: linux-intel (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938413 Title: Shutdown hangs on EHL board Status in intel: New Status in linux-intel package in Ubuntu: In Progress Bug description: [Summary]Go to Power -> Shutdown and the screen goes blank, but the system does not shut down. You cannot recover and have to perform a hard reboot. [Steps to reproduce] 1. Boot up Ubuntu 2. Power -> Shutdown (click ok) [Expected result] System should cleanly shut down. [Actual result] Screen blanks with a blinking cursor, the system does not shut down, the fan is still on. System is unresponsive, forcing you to do a hard reset. [Failure rate]100% [Additional information] CID: 20215-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel [Stage] Device froze, issue reported and logs collected right after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938413/+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 1938647] Re: Suspend in kernel 5.11 causes the whole network to go down
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1938647 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided with Ubuntu by default, many require manual addition for some releases of downstream OSes based on Ubuntu (eg. Linux Mint). You should check with your distribution first. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-edge in Ubuntu. https://bugs.launchpad.net/bugs/1938647 Title: Suspend in kernel 5.11 causes the whole network to go down Status in focal package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Bug description: I am currently reporting on kernel 5.8 (HWE) on KDE Neon Testing Edition (Ubuntu 20.04). I was mainly on 5.11, tried both kernels from Ubuntu and Pop!_OS. Every time I put the PC on sleep, the whole network will go down after waking up. Only fix I managed is to fully reboot it. Operating System: KDE neon Testing Edition KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-63-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Kernels installed: * 5.8.0-63-generic * 5.11.0.25.27 * 5.11.0.7620.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/focal/+bug/1938647/+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 1938039] Re: Tongfang PH4TUX1 flickering with 3k eDP Display on 5.11
I have a PH4TRX but with a 16:10 screen (2880x1800) not the 'standard' display format you'll find when you search for this type (which is apparently 2560x1600, so a bit confusing). They seem very closely related (see: https://www.notebookcheck.net/Schenker-launches-the- Vision-14-a-light-new-16-10-ultrabook-with-3K-display-options-and- expandable-RAM-storage.544343.0.html ) When I wanted to upgrade from Ubuntu 20.04.2 to 21.04 it at first seemed a bit like flickering, but when installed it was completely unusable. I have not tried with the different boot parameters suggested in the post above, but it seems very comparable. Also maybe comparable with Dell XPS 13 troubles (the fix suggested there doesn't work) https://www.dell.com/community/XPS/Dell-XPS-13-9310-Display-issue-after- installing-update/td-p/7735493 I'll try the suggestion with a startup disk soon and U. 21.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/1938039 Title: Tongfang PH4TUX1 flickering with 3k eDP Display on 5.11 Status in linux package in Ubuntu: Confirmed Bug description: The Tongfang PH4TUX1 barebone has occasional display flickering with a 3k eDP display on 5.11 ubuntu kernel, but not on 5.8 ubuntu kernel. Setting i915.enable_psr=0 as a boot parameter fixes the issue, so my guess is that this patch missing on 5.11 is causing the regression: https://kernel.ubuntu.com/git/ubuntu/ubuntu- focal.git/commit/?h=hwe-5.8=c6625a005bd1a2e02773c7633df211be95fa0d09 Will this default disabled-behaviour be carried over to 5.11? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938039/+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 1938039] Re: Tongfang PH4TUX1 flickering with 3k eDP Display on 5.11
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938039 Title: Tongfang PH4TUX1 flickering with 3k eDP Display on 5.11 Status in linux package in Ubuntu: Confirmed Bug description: The Tongfang PH4TUX1 barebone has occasional display flickering with a 3k eDP display on 5.11 ubuntu kernel, but not on 5.8 ubuntu kernel. Setting i915.enable_psr=0 as a boot parameter fixes the issue, so my guess is that this patch missing on 5.11 is causing the regression: https://kernel.ubuntu.com/git/ubuntu/ubuntu- focal.git/commit/?h=hwe-5.8=c6625a005bd1a2e02773c7633df211be95fa0d09 Will this default disabled-behaviour be carried over to 5.11? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938039/+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 1931301] Re: NIC unavailable after suspend to RAM
Same problem on ubuntu 21.04 here: *-network description: Ethernet interface product: QCA8171 Gigabit Ethernet vendor: Qualcomm Atheros physical id: 0 bus info: pci@:08:00.0 logical name: enp8s0 version: 10 serial: 60:02:92:15:4f:ce size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=alx driverversion=5.11.0-25-generic duplex=full ip=192.168.0.101 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s resources: irq:18 memory:d140-d143 ioport:3000(size=128) I also noticed blueman only remembers "Recent Connections" after a reboot. After suspending it forgets them and I have to enter "Bluetooth Devices" and connect through there. Not a serious issue and i'm not sure it's related but just in case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931301 Title: NIC unavailable after suspend to RAM Status in linux package in Ubuntu: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: [SRU Justification] [Impact] The network card will be unavailable after system resume if the interface is not UP before suspend. [Fix] It's because we added the WOL support for this driver. The driver with WoL feature does detach the network interface even the interface is DOWN. However, it doesn't attach the network interface back on resume if it was DOWN. That's why it's unavailable after resume. Fix this by correctly netif_device_attach according to the interface status. [Test Case] 1. Plug the ethernet cable to the Atheros E220x ethernet adapter 2. Suspend the system and check if the ethernet interface available after resume 3. Unplug the ethernet cable 4. Suspend the system and check if the ethernet interface available after resume [Regression Potential] Low. The driver code would be identical to working Groovy version after fix. == Original Bug Description == Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+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 1937897] Re: GPIO error logs in start and dmesg after update of kernel
No, I can't, because there isn't a single module loaded with even the name "gpio" in it. So running: $ lsmod|grep gpio == No result It's in the kernel, not a module. I reverted to the GA kernel and although with that I've had some issue with on headless *Intel* NUC running Virtual Machines that use the more optimized Ubuntu KVM kernel, using libvirt (host uses the latest HWE), where both host and VMs slow down to a crawl randomly without errors. But on my Ryzen 9 workstation the GA kernel is super stable, fast and just works. A little slower in Vulkan *Benchmarks*, that's basically it. And yes, it runs a bunch of server services. Mainly does that like "22/7", for LAN and WAN. Biggest "drawback" is that the 5.4 kernel's k10temp module does not display the temperatures of my Corsair PCIe4 5.5 GB/s NVMEs (just running "sensors"), but well that doesn't matter. I've stressed them well enough before, to see that my cooling is absolutely enough (and they come with a built-in heatsink. Sure I could've reverted to the previous 5.8 kernel, but it's tied to HWE (metapackages), unless I uninstall them, and then, well no security 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/1937897 Title: GPIO error logs in start and dmesg after update of kernel Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error to gpio: 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with zero lines [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 On pc: description: Desktop Computer product: System Product Name (SKU) vendor: ASUS version: System Version serial: System Serial Number width: 64 bits capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32 configuration: boot=normal chassis=desktop family=To be filled by O.E.M. sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4 *-core description: Motherboard product: TUF GAMING B550M-PLUS (WI-FI) vendor: ASUSTeK COMPUTER INC. physical id: 0 version: Rev X.0x serial: 201176738701636 slot: Default string *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 2403 date: 06/16/2021 size: 64KiB capacity: 16MiB capabilities: pci apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi *-memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+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 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
I am having a similar issue with my Thinkpad L15 Gen2 (Intel), running Ubuntu 21.04 with Kernel 5.11.0-25-generic: After a suspend/resume cycle, the LAN interface only receives at very low speed (less than 1 MBit/sec reported by iperf). So far only rebooting brought back the full speed (approx. 950 MBits/sec.). It seems that using the MEI fix from #77 also fixes the problem in this scenario - after applying the fix the network speed was back to normal immediately, and I tried several suspend/resume cycles with no decrease in network speed anymore. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 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.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 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.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10
[Kernel-packages] [Bug 1938645] Re: Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman over USB using MTP protocol
I decided to have the Sony WalkMan reformat itself. MTP over USB working much better now. Very odd that I could play MP3 recordings with the player without issues... only issues was removing files, copying new files to it. The thing that tipped me off to try reformatting the device with itself is I was seeing traces of recordings I had deleted yet in the playlist. Some of the letters in the listings were missing, but the content would still play properly. That told me deletes were not being completed properly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938645 Title: Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman over USB using MTP protocol Status in linux package in Ubuntu: New Bug description: I use package Rhythembox as my MP3 player software. I also use Rhythebox to transfer audio to my Sony WalkMan MP3 player. Since moving to Xubuntu 20.04.2, it has gotten much harder to successfully transfer mp3 audio to the Sony WalkMan MP3 player. I checked in syslog... I see some errors I believe are related: Aug 1 10:39:54 jaakob kernel: [ 8079.675644] mtp[10045]: segfault at 8a ip 7f2754d6f623 sp 7f274cbb2f20 error 4 in libglib-2.0.so.0.6400.6[7f2754d1b000+84000] Aug 1 10:39:54 jaakob kernel: [ 8079.675648] Code: 0f 1f 80 00 00 00 00 48 c1 e8 04 4c 8b 3b 8d 48 ff 48 89 c5 49 89 ce 49 c1 e6 04 4d 01 f7 4d 8b 27 4d 85 e4 0f 84 cd 00 00 00 <49> 8b 44 24 08 48 85 c0 74 43 48 8b 10 49 89 54 24 08 49 89 c4 49 Aug 1 10:40:13 jaakob kernel: [ 8098.630114] usb 1-11.2: USB disconnect, device number 6 Aug 1 10:41:34 jaakob kernel: [ 8179.600470] usb 1-5: new high-speed USB device number 8 using xhci_hcd Aug 1 10:41:34 jaakob kernel: [ 8179.749115] usb 1-5: New USB device found, idVendor=054c, idProduct=0385, bcdDevice= 0.01 Aug 1 10:41:34 jaakob kernel: [ 8179.749121] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Aug 1 10:41:34 jaakob kernel: [ 8179.749124] usb 1-5: Product: WALKMAN Aug 1 10:41:34 jaakob kernel: [ 8179.749127] usb 1-5: Manufacturer: Sony Aug 1 10:41:34 jaakob kernel: [ 8179.749130] usb 1-5: SerialNumber: 10FA1355316092 Aug 1 10:41:34 jaakob kernel: [ 8179.750689] usb-storage 1-5:1.0: USB Mass Storage device detected Aug 1 10:41:34 jaakob kernel: [ 8179.751175] scsi host14: usb-storage 1-5:1.0 Aug 1 10:41:35 jaakob kernel: [ 8180.761332] scsi 14:0:0:0: Direct-Access SONY WALKMAN 1.00 PQ: 0 ANSI: 4 Aug 1 10:41:35 jaakob kernel: [ 8180.761875] sd 14:0:0:0: Attached scsi generic sg3 type 0 Aug 1 10:41:35 jaakob kernel: [ 8180.762889] sd 14:0:0:0: [sdb] 1917952 2048-byte logical blocks: (3.93 GB/3.66 GiB) Aug 1 10:41:35 jaakob kernel: [ 8180.763062] sd 14:0:0:0: [sdb] Write Protect is off Aug 1 10:41:35 jaakob kernel: [ 8180.763066] sd 14:0:0:0: [sdb] Mode Sense: 3e 00 00 00 Aug 1 10:41:35 jaakob kernel: [ 8180.763200] sd 14:0:0:0: [sdb] No Caching mode page found Aug 1 10:41:35 jaakob kernel: [ 8180.763206] sd 14:0:0:0: [sdb] Assuming drive cache: write through Aug 1 10:41:36 jaakob kernel: [ 8180.809779] sdb: sdb1 Aug 1 10:41:36 jaakob kernel: [ 8180.811198] sd 14:0:0:0: [sdb] Attached SCSI removable disk Aug 1 10:41:36 jaakob Thunar[7060]: Working directory "/home/mdlueck/[Invalid UTF-8]" does not exist. It won't be used when spawning "exo-open".Working directory "/home/mdlueck/[Invalid UTF-8]" does not exist. It won't be used when spawning "exo-open". Aug 1 10:41:36 jaakob Thunar[10184]: thunar-volman: Unknown block device type "disk". Aug 1 10:41:42 jaakob kernel: [ 8186.793656] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Aug 1 10:41:42 jaakob systemd[1]: Created slice system-clean\x2dmount\x2dpoint.slice. Aug 1 10:41:42 jaakob systemd[1]: Finished Clean the /media/mdlueck/WALKMAN mount point. Aug 1 10:41:42 jaakob udisksd[813]: Mounted /dev/sdb1 at /media/mdlueck/WALKMAN on behalf of uid 1000 Aug 1 10:41:42 jaakob dbus-daemon[1546]: [session uid=1000 pid=1546] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.83' (uid=1000 pid=7060 comm="/usr/bin/Thunar --daemon " label="unconfined") Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer atril-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer gnome-thumbnail-font --size %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob dbus-daemon[1546]: [session uid=1000 pid=1546] Successfully activated
[Kernel-packages] [Bug 1938013] Re: 4.15.0-151 is freezing various CPUs
Tested on Lenovo ThinkPad 13, i7-7500U, Intel Wireless 8265 / 8275. With 4.15.0-151 there was a freeze after 1-15 min. After 6 hours no issues with 4.15.0-153 kernel. Thank you Juerg. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938013 Title: 4.15.0-151 is freezing various CPUs Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: From: https://askubuntu.com/questions/1353859/ubuntu-18-04-05-lts- desktop-hangs-with-since-kernel-4-15-0-151-and-systemd-237-3 Several crashes in /var/crash, here's the last one:- ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Date: Fri Jul 23 18:10:54 2021 Failure: oops OopsText: BUG: Bad rss-counter state mm:c098a229 idx:2 val:-1 usblp0: removed usblp 1-5:1.0: usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04F9 pid 0x02EC <44>[ 18.329026] systemd-journald[358]: File /var/log/journal/b022dca21fd4480baeeb84f47ab439d3/user-1000.journal corrupted or uncleanly shut down, renaming and replacing. vboxdrv: loading out-of-tree module taints kernel. vboxdrv: module verification failed: signature and/or required key missing - tainting kernel vboxdrv: Found 8 processor cores vboxdrv: TSC mode is Invariant, tentative frequency 2303999142 Hz vboxdrv: Successfully loaded version 6.1.24 r145767 (interface 0x0030) VBoxNetFlt: Successfully started. VBoxNetAdp: Successfully started. Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 rfkill: input handler disabled [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 Package: linux-image-4.15.0-151-generic 4.15.0-151.157 SourcePackage: linux Tags: kernel-oops Uname: Linux 4.15.0-151-generic x86_64 --- The system is a laptop from Entroware based on Clevo and has 8 logical CPUs:- Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 158 Model name: Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz Stepping:10 CPU MHz: 2000.295 CPU max MHz: 4000. CPU min MHz: 800. BogoMIPS:4599.93 Virtualisation: VT-x L1d cache: 32K L1i cache: 32K L2 cache:256K L3 cache:8192K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d USB Config:- Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:2110 Acer, Inc Bus 001 Device 003: ID 04f9:02ec Brother Industries, Ltd MFC-J870DW Bus 001 Device 005: ID 8087:07dc Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0d8c:0104 C-Media Electronics, Inc. CM103+ Audio Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PCI Config:-
[Kernel-packages] [Bug 1928686] Re: Oracle kernel has Android related config options disabled
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Oracle kernel has Android related config options disabled + Some cloud kernels have Android related config options disabled -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1928686 Title: Some cloud kernels have Android related config options disabled Status in linux-gcp package in Ubuntu: New Status in linux-oracle package in Ubuntu: Confirmed Status in linux-gcp source package in Bionic: New Status in linux-oracle source package in Bionic: New Status in linux-gcp source package in Focal: New Status in linux-oracle source package in Focal: Fix Released Status in linux-gcp source package in Groovy: New Status in linux-oracle source package in Groovy: Fix Released Status in linux-gcp source package in Hirsute: New Status in linux-oracle source package in Hirsute: Fix Released Bug description: For Anbox Cloud we require certain CONFIG_ANDROID_* options to be enabled in the kernel. We do this already for most of our cloud kernels (GCE, AWS, Azure) and the generic kernel and should do so for the oracle (and possible others too). We have customers looking at running Anbox Cloud on OCI instances and having the ashmem and binder kernel modules available is a precondition for this to work. The following options are what we need CONFIG_ANDROID=y CONFIG_ANDROID_BINDER_IPC=m CONFIG_ANDROID_BINDERFS=m CONFIG_ANDROID_BINDER_DEVICES="" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set CONFIG_ASHMEM=m These should be the same across all our kernels where we're going to support Anbox Cloud. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1928686/+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 1938645] Re: Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman over USB using MTP protocol
** Tags added: focal ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938645 Title: Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman over USB using MTP protocol Status in linux package in Ubuntu: New Bug description: I use package Rhythembox as my MP3 player software. I also use Rhythebox to transfer audio to my Sony WalkMan MP3 player. Since moving to Xubuntu 20.04.2, it has gotten much harder to successfully transfer mp3 audio to the Sony WalkMan MP3 player. I checked in syslog... I see some errors I believe are related: Aug 1 10:39:54 jaakob kernel: [ 8079.675644] mtp[10045]: segfault at 8a ip 7f2754d6f623 sp 7f274cbb2f20 error 4 in libglib-2.0.so.0.6400.6[7f2754d1b000+84000] Aug 1 10:39:54 jaakob kernel: [ 8079.675648] Code: 0f 1f 80 00 00 00 00 48 c1 e8 04 4c 8b 3b 8d 48 ff 48 89 c5 49 89 ce 49 c1 e6 04 4d 01 f7 4d 8b 27 4d 85 e4 0f 84 cd 00 00 00 <49> 8b 44 24 08 48 85 c0 74 43 48 8b 10 49 89 54 24 08 49 89 c4 49 Aug 1 10:40:13 jaakob kernel: [ 8098.630114] usb 1-11.2: USB disconnect, device number 6 Aug 1 10:41:34 jaakob kernel: [ 8179.600470] usb 1-5: new high-speed USB device number 8 using xhci_hcd Aug 1 10:41:34 jaakob kernel: [ 8179.749115] usb 1-5: New USB device found, idVendor=054c, idProduct=0385, bcdDevice= 0.01 Aug 1 10:41:34 jaakob kernel: [ 8179.749121] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Aug 1 10:41:34 jaakob kernel: [ 8179.749124] usb 1-5: Product: WALKMAN Aug 1 10:41:34 jaakob kernel: [ 8179.749127] usb 1-5: Manufacturer: Sony Aug 1 10:41:34 jaakob kernel: [ 8179.749130] usb 1-5: SerialNumber: 10FA1355316092 Aug 1 10:41:34 jaakob kernel: [ 8179.750689] usb-storage 1-5:1.0: USB Mass Storage device detected Aug 1 10:41:34 jaakob kernel: [ 8179.751175] scsi host14: usb-storage 1-5:1.0 Aug 1 10:41:35 jaakob kernel: [ 8180.761332] scsi 14:0:0:0: Direct-Access SONY WALKMAN 1.00 PQ: 0 ANSI: 4 Aug 1 10:41:35 jaakob kernel: [ 8180.761875] sd 14:0:0:0: Attached scsi generic sg3 type 0 Aug 1 10:41:35 jaakob kernel: [ 8180.762889] sd 14:0:0:0: [sdb] 1917952 2048-byte logical blocks: (3.93 GB/3.66 GiB) Aug 1 10:41:35 jaakob kernel: [ 8180.763062] sd 14:0:0:0: [sdb] Write Protect is off Aug 1 10:41:35 jaakob kernel: [ 8180.763066] sd 14:0:0:0: [sdb] Mode Sense: 3e 00 00 00 Aug 1 10:41:35 jaakob kernel: [ 8180.763200] sd 14:0:0:0: [sdb] No Caching mode page found Aug 1 10:41:35 jaakob kernel: [ 8180.763206] sd 14:0:0:0: [sdb] Assuming drive cache: write through Aug 1 10:41:36 jaakob kernel: [ 8180.809779] sdb: sdb1 Aug 1 10:41:36 jaakob kernel: [ 8180.811198] sd 14:0:0:0: [sdb] Attached SCSI removable disk Aug 1 10:41:36 jaakob Thunar[7060]: Working directory "/home/mdlueck/[Invalid UTF-8]" does not exist. It won't be used when spawning "exo-open".Working directory "/home/mdlueck/[Invalid UTF-8]" does not exist. It won't be used when spawning "exo-open". Aug 1 10:41:36 jaakob Thunar[10184]: thunar-volman: Unknown block device type "disk". Aug 1 10:41:42 jaakob kernel: [ 8186.793656] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Aug 1 10:41:42 jaakob systemd[1]: Created slice system-clean\x2dmount\x2dpoint.slice. Aug 1 10:41:42 jaakob systemd[1]: Finished Clean the /media/mdlueck/WALKMAN mount point. Aug 1 10:41:42 jaakob udisksd[813]: Mounted /dev/sdb1 at /media/mdlueck/WALKMAN on behalf of uid 1000 Aug 1 10:41:42 jaakob dbus-daemon[1546]: [session uid=1000 pid=1546] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.83' (uid=1000 pid=7060 comm="/usr/bin/Thunar --daemon " label="unconfined") Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer atril-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer gnome-thumbnail-font --size %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob dbus-daemon[1546]: [session uid=1000 pid=1546] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1' Aug 1 10:43:07 jaakob kernel: [ 8272.638815] blk_update_request: I/O error, dev sdb, sector 32 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Aug 1 10:43:07 jaakob kernel: [ 8272.638818] Buffer I/O error on dev sdb1, logical block 1, lost async page write Aug 1 10:43:07 jaakob kernel: [ 8272.638822] blk_update_request: I/O error, dev sdb, sector 2176 op 0x1:(WRITE) flags 0x0 phys_seg 1
[Kernel-packages] [Bug 1938647] Re: Suspend in kernel 5.11 causes the whole network to go down
Related to this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301 ** Also affects: focal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-edge in Ubuntu. https://bugs.launchpad.net/bugs/1938647 Title: Suspend in kernel 5.11 causes the whole network to go down Status in focal package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Bug description: I am currently reporting on kernel 5.8 (HWE) on KDE Neon Testing Edition (Ubuntu 20.04). I was mainly on 5.11, tried both kernels from Ubuntu and Pop!_OS. Every time I put the PC on sleep, the whole network will go down after waking up. Only fix I managed is to fully reboot it. Operating System: KDE neon Testing Edition KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-63-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Kernels installed: * 5.8.0-63-generic * 5.11.0.25.27 * 5.11.0.7620.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/focal/+bug/1938647/+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 1938647] Re: Suspend in kernel 5.11 causes the whole network to go down
*-network description: Ethernet interface product: Killer E2400 Gigabit Ethernet Controller vendor: Qualcomm Atheros physical id: 0 bus info: pci@:06:00.0 logical name: enp6s0 version: 10 serial: d8:cb:8a:a3:f7:df size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=alx driverversion=5.8.0-63-generic duplex=full ip=192.168.100.13 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s resources: irq:19 memory:df10-df13 ioport:d000(size=128) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-edge in Ubuntu. https://bugs.launchpad.net/bugs/1938647 Title: Suspend in kernel 5.11 causes the whole network to go down Status in focal package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Bug description: I am currently reporting on kernel 5.8 (HWE) on KDE Neon Testing Edition (Ubuntu 20.04). I was mainly on 5.11, tried both kernels from Ubuntu and Pop!_OS. Every time I put the PC on sleep, the whole network will go down after waking up. Only fix I managed is to fully reboot it. Operating System: KDE neon Testing Edition KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-63-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Kernels installed: * 5.8.0-63-generic * 5.11.0.25.27 * 5.11.0.7620.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/focal/+bug/1938647/+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 1938647] Re: Suspend in kernel 5.11 causes the whole network to go down
This is my ethernet: 06:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-edge in Ubuntu. https://bugs.launchpad.net/bugs/1938647 Title: Suspend in kernel 5.11 causes the whole network to go down Status in focal package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Bug description: I am currently reporting on kernel 5.8 (HWE) on KDE Neon Testing Edition (Ubuntu 20.04). I was mainly on 5.11, tried both kernels from Ubuntu and Pop!_OS. Every time I put the PC on sleep, the whole network will go down after waking up. Only fix I managed is to fully reboot it. Operating System: KDE neon Testing Edition KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-63-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Kernels installed: * 5.8.0-63-generic * 5.11.0.25.27 * 5.11.0.7620.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/focal/+bug/1938647/+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 1938647] [NEW] Suspend in kernel 5.11 causes the whole network to go down
Public bug reported: I am currently reporting on kernel 5.8 (HWE) on KDE Neon Testing Edition (Ubuntu 20.04). I was mainly on 5.11, tried both kernels from Ubuntu and Pop!_OS. Every time I put the PC on sleep, the whole network will go down after waking up. Only fix I managed is to fully reboot it. Operating System: KDE neon Testing Edition KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-63-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Kernels installed: * 5.8.0-63-generic * 5.11.0.25.27 * 5.11.0.7620.21 ** Affects: focal (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe-edge (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-edge in Ubuntu. https://bugs.launchpad.net/bugs/1938647 Title: Suspend in kernel 5.11 causes the whole network to go down Status in focal package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Bug description: I am currently reporting on kernel 5.8 (HWE) on KDE Neon Testing Edition (Ubuntu 20.04). I was mainly on 5.11, tried both kernels from Ubuntu and Pop!_OS. Every time I put the PC on sleep, the whole network will go down after waking up. Only fix I managed is to fully reboot it. Operating System: KDE neon Testing Edition KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-63-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Kernels installed: * 5.8.0-63-generic * 5.11.0.25.27 * 5.11.0.7620.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/focal/+bug/1938647/+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 1938645] [NEW] Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman over USB using MTP protocol
You have been subscribed to a public bug: I use package Rhythembox as my MP3 player software. I also use Rhythebox to transfer audio to my Sony WalkMan MP3 player. Since moving to Xubuntu 20.04.2, it has gotten much harder to successfully transfer mp3 audio to the Sony WalkMan MP3 player. I checked in syslog... I see some errors I believe are related: Aug 1 10:39:54 jaakob kernel: [ 8079.675644] mtp[10045]: segfault at 8a ip 7f2754d6f623 sp 7f274cbb2f20 error 4 in libglib-2.0.so.0.6400.6[7f2754d1b000+84000] Aug 1 10:39:54 jaakob kernel: [ 8079.675648] Code: 0f 1f 80 00 00 00 00 48 c1 e8 04 4c 8b 3b 8d 48 ff 48 89 c5 49 89 ce 49 c1 e6 04 4d 01 f7 4d 8b 27 4d 85 e4 0f 84 cd 00 00 00 <49> 8b 44 24 08 48 85 c0 74 43 48 8b 10 49 89 54 24 08 49 89 c4 49 Aug 1 10:40:13 jaakob kernel: [ 8098.630114] usb 1-11.2: USB disconnect, device number 6 Aug 1 10:41:34 jaakob kernel: [ 8179.600470] usb 1-5: new high-speed USB device number 8 using xhci_hcd Aug 1 10:41:34 jaakob kernel: [ 8179.749115] usb 1-5: New USB device found, idVendor=054c, idProduct=0385, bcdDevice= 0.01 Aug 1 10:41:34 jaakob kernel: [ 8179.749121] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Aug 1 10:41:34 jaakob kernel: [ 8179.749124] usb 1-5: Product: WALKMAN Aug 1 10:41:34 jaakob kernel: [ 8179.749127] usb 1-5: Manufacturer: Sony Aug 1 10:41:34 jaakob kernel: [ 8179.749130] usb 1-5: SerialNumber: 10FA1355316092 Aug 1 10:41:34 jaakob kernel: [ 8179.750689] usb-storage 1-5:1.0: USB Mass Storage device detected Aug 1 10:41:34 jaakob kernel: [ 8179.751175] scsi host14: usb-storage 1-5:1.0 Aug 1 10:41:35 jaakob kernel: [ 8180.761332] scsi 14:0:0:0: Direct-Access SONY WALKMAN 1.00 PQ: 0 ANSI: 4 Aug 1 10:41:35 jaakob kernel: [ 8180.761875] sd 14:0:0:0: Attached scsi generic sg3 type 0 Aug 1 10:41:35 jaakob kernel: [ 8180.762889] sd 14:0:0:0: [sdb] 1917952 2048-byte logical blocks: (3.93 GB/3.66 GiB) Aug 1 10:41:35 jaakob kernel: [ 8180.763062] sd 14:0:0:0: [sdb] Write Protect is off Aug 1 10:41:35 jaakob kernel: [ 8180.763066] sd 14:0:0:0: [sdb] Mode Sense: 3e 00 00 00 Aug 1 10:41:35 jaakob kernel: [ 8180.763200] sd 14:0:0:0: [sdb] No Caching mode page found Aug 1 10:41:35 jaakob kernel: [ 8180.763206] sd 14:0:0:0: [sdb] Assuming drive cache: write through Aug 1 10:41:36 jaakob kernel: [ 8180.809779] sdb: sdb1 Aug 1 10:41:36 jaakob kernel: [ 8180.811198] sd 14:0:0:0: [sdb] Attached SCSI removable disk Aug 1 10:41:36 jaakob Thunar[7060]: Working directory "/home/mdlueck/[Invalid UTF-8]" does not exist. It won't be used when spawning "exo-open".Working directory "/home/mdlueck/[Invalid UTF-8]" does not exist. It won't be used when spawning "exo-open". Aug 1 10:41:36 jaakob Thunar[10184]: thunar-volman: Unknown block device type "disk". Aug 1 10:41:42 jaakob kernel: [ 8186.793656] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Aug 1 10:41:42 jaakob systemd[1]: Created slice system-clean\x2dmount\x2dpoint.slice. Aug 1 10:41:42 jaakob systemd[1]: Finished Clean the /media/mdlueck/WALKMAN mount point. Aug 1 10:41:42 jaakob udisksd[813]: Mounted /dev/sdb1 at /media/mdlueck/WALKMAN on behalf of uid 1000 Aug 1 10:41:42 jaakob dbus-daemon[1546]: [session uid=1000 pid=1546] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.83' (uid=1000 pid=7060 comm="/usr/bin/Thunar --daemon " label="unconfined") Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer atril-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer gnome-thumbnail-font --size %s %u %o Aug 1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Aug 1 10:41:42 jaakob dbus-daemon[1546]: [session uid=1000 pid=1546] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1' Aug 1 10:43:07 jaakob kernel: [ 8272.638815] blk_update_request: I/O error, dev sdb, sector 32 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Aug 1 10:43:07 jaakob kernel: [ 8272.638818] Buffer I/O error on dev sdb1, logical block 1, lost async page write Aug 1 10:43:07 jaakob kernel: [ 8272.638822] blk_update_request: I/O error, dev sdb, sector 2176 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Aug 1 10:43:07 jaakob kernel: [ 8272.638823] Buffer I/O error on dev sdb1, logical block 537, lost async page write Aug 1 10:43:07 jaakob kernel: [ 8272.638839] blk_update_request: I/O error, dev sdb, sector 793984 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Aug 1 10:43:07 jaakob kernel: [ 8272.638839] Buffer I/O error on dev sdb1, logical block 198489, lost async page write Aug 1 10:43:07 jaakob kernel: [
[Kernel-packages] [Bug 1931301] Re: NIC unavailable after suspend to RAM
This is my network card: *-network description: Ethernet interface product: Killer E2400 Gigabit Ethernet Controller vendor: Qualcomm Atheros physical id: 0 bus info: pci@:06:00.0 logical name: enp6s0 version: 10 serial: d8:cb:8a:a3:f7:df size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=alx driverversion=5.8.0-63-generic duplex=full ip=192.168.100.13 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s resources: irq:19 memory:df10-df13 ioport:d000(size=128) Currently running on 5.8 to test and see if it's a 5.11 issue or just my network card, and I stumbled onto this after I reported it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931301 Title: NIC unavailable after suspend to RAM Status in linux package in Ubuntu: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: [SRU Justification] [Impact] The network card will be unavailable after system resume if the interface is not UP before suspend. [Fix] It's because we added the WOL support for this driver. The driver with WoL feature does detach the network interface even the interface is DOWN. However, it doesn't attach the network interface back on resume if it was DOWN. That's why it's unavailable after resume. Fix this by correctly netif_device_attach according to the interface status. [Test Case] 1. Plug the ethernet cable to the Atheros E220x ethernet adapter 2. Suspend the system and check if the ethernet interface available after resume 3. Unplug the ethernet cable 4. Suspend the system and check if the ethernet interface available after resume [Regression Potential] Low. The driver code would be identical to working Groovy version after fix. == Original Bug Description == Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+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 1931301] Re: NIC unavailable after suspend to RAM
Also experienced the same thing on KDE Neon Testing Edition (Ubuntu 20.04) with HWE-edge kernels & Pop!_OS kernels. https://bugs.launchpad.net/ubuntu/+source/linux-hwe-edge/+bug/1938647 I have these kernels in my system right now, and only 5.11 is affected: * 5.8.0-63-generic * 5.11.0.25.27 * 5.11.0.7620.21 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931301 Title: NIC unavailable after suspend to RAM Status in linux package in Ubuntu: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: [SRU Justification] [Impact] The network card will be unavailable after system resume if the interface is not UP before suspend. [Fix] It's because we added the WOL support for this driver. The driver with WoL feature does detach the network interface even the interface is DOWN. However, it doesn't attach the network interface back on resume if it was DOWN. That's why it's unavailable after resume. Fix this by correctly netif_device_attach according to the interface status. [Test Case] 1. Plug the ethernet cable to the Atheros E220x ethernet adapter 2. Suspend the system and check if the ethernet interface available after resume 3. Unplug the ethernet cable 4. Suspend the system and check if the ethernet interface available after resume [Regression Potential] Low. The driver code would be identical to working Groovy version after fix. == Original Bug Description == Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+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 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Does this bug look like a duplicate https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937056? I have the same issue with touchpad not being detected, tried removing and adding i2c_hid back but does not help. Tried kernels 5.12.8, 5.12.11, 5.13.1 through 5.13.7, 5.14-rc2, 5.14-rc3 but no luck. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+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 1937056] Re: Touchpad not working with ASUS TUF F15
** Description changed: I am using Kubuntu 21.04 on my ASUS TUF F15 FX506HM_FX566HM. The touchpad isn't detected in Settings and neither in xinput, nor in cat /proc/bus/input/devices. Laptop model: ASUS TUF F15 FX506HM_FX566HM. Manufacturer of the Touchpad: Probably ELAN1203 When the symptom first appeared: From beginning Output of lsb_release -rd Description:Ubuntu 21.04 Release:21.04 Using kernel version 5.13.6. Also tried 5.11, 5.12.8, 5.12.15, 5.13.1, 5.13.2, 5.13.4, 5.13.5, 5.14-rc2, 5.14-rc3 Output of xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Asus Wireless Radio Control id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11 [slave keyboard (3)] ↳ Intel HID events id=12 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ Asus WMI hotkeys id=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)] Output of lspci :00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 05) :00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #1 (rev 05) :00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) :00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 05) :00:06.0 System peripheral: Intel Corporation Device 09ab :00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #0 (rev 05) :00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 05) :00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01) :00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB Controller (rev 05) :00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI #0 (rev 05) :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller :00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11) :00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11) :00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H Serial IO I2C Controller #0 (rev 11) :00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11) :00:1c.0 PCI bridge: Intel Corporation Device 43bf (rev 11) :00:1d.0 PCI bridge: Intel Corporation Device 43b6 (rev 11) :00:1f.0 ISA bridge: Intel Corporation Tiger Lake-H LPC/eSPI Controller (rev 11) :00:1f.3 Audio device: Intel Corporation Tiger Lake-H HD Audio Controller (rev 11) :00:1f.4 SMBus: Intel Corporation Tiger Lake-H SMBus Controller (rev 11) :00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H SPI Controller (rev 11) :01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1) :01:00.1 Audio device: NVIDIA Corporation Device 228e (rev a1) :2d:00.0 Network controller: MEDIATEK Corp. Device 7961 :2e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 1:e0:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #0 (rev 05) 1:e1:00.0 Non-Volatile memory controller: SK hynix Device 174a --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-25 (1 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to hirsute on 2021-07-25 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True + + + Logged a bug in the kernel as well https://bugzilla.kernel.org/show_bug.cgi?id=213857 -- You received
[Kernel-packages] [Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
The Internet is clogged with reports of this bug on AMD GPUs, but some
w/ Intel/nVidia (which I haven't followed).
Is your info from post 61 still valid? (This would be for a current,
unmodified update of any distro.)
It would interesting to plug in a Mint live device and check output of
'aplay -l'. Two reasons for Mint; the team does a great job debugging
and it seems to be the one you were running originally.
If same result, that means the kernel itself can't access the hardware
(to my understanding). Totally scwewed in that case.
The workaround relies on alsa being able to access and control the audio
hardware. If alsa can't enumerate the HDMI devices, there's no
convenient way to manually circumvent the defaults (that don't work).
But if the HDMI ports *are* listed, the workaround should get HDMI audio
playing. Note that it grabs 'HDMI 0', the first HDMI device listed. Just
checked and found the AMD cards here all show one device for each port,
but with Intel/nVidia, there's up to three shown for each. (!)
Someone may be able to shed some light on why this is but meanwhile, it
appears that a different device number may be required (not the device
number associated with HDMI 0).
So you could try, for example from post 61:
card=0
dev=7
Then paste inner part of script:
pulseaudio --kill
rm $HOME/.config/pulse/*
sleep 2
wait
pulseaudio --start
pacmd load-module module-alsa-sink device=hw:$card,$dev
pacmd set-default-sink alsa_output.hw_${card}_${dev}
pacmd set-sink-volume alsa_output.hw_${card}_${dev} 35000
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834771
Title:
No HDMI-audio after kernel 4.15.-0.50
Status in linux package in Ubuntu:
Confirmed
Bug description:
I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50.
In pavucontrol HDMI-audio shows unplugged. And also internal audio shows
unplugged, but it still works. I'm on linux mint 18.3.
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jouni 1859 F pulseaudio
/dev/snd/controlC1: jouni 1859 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux 18.3
HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36
InstallationDate: Installed on 2017-01-28 (883 days ago)
InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
IwConfig:
lono wireless extensions.
enp3s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic
root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash
vt.handoff=7
ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-54-generic N/A
linux-backports-modules-4.15.0-54-generic N/A
linux-firmware 1.157.21
RfKill:
Tags: sylvia
Uname: Linux 4.15.0-54-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
_MarkForUpload: True
dmi.bios.date: 02/26/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 970A-UD3P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+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 1936255] Re: New upstream release 2021.07.14
What about the trusty/xenial packages? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1936255 Title: New upstream release 2021.07.14 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Trusty: In Progress Status in wireless-regdb source package in Xenial: In Progress Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Won't Fix Status in wireless-regdb source package in Hirsute: Fix Committed Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+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 1936255] Re: New upstream release 2021.07.14
$ dpkg-query -W wireless-regdb wireless-regdb 2021.07.14-0ubuntu1~21.04.1 $ iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (6, 20), (N/A) (2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) $ sudo iw reg set US $ iw reg get global country US: DFS-FCC (2400 - 2472 @ 40), (N/A, 30), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN (57240 - 71000 @ 2160), (N/A, 40), (N/A) ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1936255 Title: New upstream release 2021.07.14 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Trusty: In Progress Status in wireless-regdb source package in Xenial: In Progress Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Won't Fix Status in wireless-regdb source package in Hirsute: Fix Committed Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+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 1936255] Re: New upstream release 2021.07.14
$ dpkg-query -W wireless-regdb wireless-regdb 2021.07.14-0ubuntu1~20.04.1 $ iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (N/A, 20), (N/A) (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) $ sudo iw reg set US $ iw reg get global country US: DFS-FCC (2400 - 2472 @ 40), (N/A, 30), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN (57240 - 71000 @ 2160), (N/A, 40), (N/A) ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1936255 Title: New upstream release 2021.07.14 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Trusty: In Progress Status in wireless-regdb source package in Xenial: In Progress Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Won't Fix Status in wireless-regdb source package in Hirsute: Fix Committed Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+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 1930754] Re: e1000e extremly slow
@Sebastian, did you check #14 and apply the workaround? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: Confirmed Bug description: We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1930754/+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 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
Thanks for the feedback Uriel, but on the Intel Graphics card, after i copy in that program from here (https://askubuntu.com/questions/1032811/ubuntu-18-04-no-hdmi-audio-with-amd-radeon-hd-7870/1207919#1207919) and then run $ $HOME/bin/fixHDMIaudio & It says . [1] 1967 Then returns "Sink alsa_output.hw__ does not exist. No sink found by this name or index." As you say, a cheap video card might be the solution in the long term :-) It's frustrating, but at least i can continue to use LMDE 4 using the 4.18.19 kernel for the minute though -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 Status in linux package in Ubuntu: Confirmed Bug description: I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. In pavucontrol HDMI-audio shows unplugged. And also internal audio shows unplugged, but it still works. I'm on linux mint 18.3. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jouni 1859 F pulseaudio /dev/snd/controlC1: jouni 1859 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36 InstallationDate: Installed on 2017-01-28 (883 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.157.21 RfKill: Tags: sylvia Uname: Linux 4.15.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+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 1938221] Re: Fail to resume after hibernate. Image mismatch: architecture specific data
Yet another issue: after resuming, the desktop is corrupted
** Attachment added: "Corrupted desktop after resuming from hibernate"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+attachment/5515080/+files/Schermata%20da%202021-08-01%2013-33-28.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1938221
Title:
Fail to resume after hibernate. Image mismatch: architecture specific
data
Status in linux package in Ubuntu:
New
Bug description:
I'm running Ubuntu 21.04 on a laptop and have been using hibernate flawlessly
for a couple of months.
More recently, resuming from hibernation stopped working and now falls back
to complete restart.
This is what I get from dmesg:
[ 17.407048] kernel: PM: hibernation: resume from hibernation
[ 17.409714] kernel: PM: hibernation: Marking nosave pages: [mem
0x-0x0fff]
[ 17.409717] kernel: PM: hibernation: Marking nosave pages: [mem
0x0004f000-0x0004]
[ 17.409718] kernel: PM: hibernation: Marking nosave pages: [mem
0x0009e000-0x000f]
[ 17.409721] kernel: PM: hibernation: Marking nosave pages: [mem
0xae6e9000-0xae6e]
[ 17.409723] kernel: PM: hibernation: Marking nosave pages: [mem
0xaf0cd000-0xaf5abfff]
[ 17.409744] kernel: PM: hibernation: Marking nosave pages: [mem
0xb1e4c000-0xb1ed3fff]
[ 17.409747] kernel: PM: hibernation: Marking nosave pages: [mem
0xb2698000-0xb2698fff]
[ 17.409748] kernel: PM: hibernation: Marking nosave pages: [mem
0xb54af000-0xb54a]
[ 17.409749] kernel: PM: hibernation: Marking nosave pages: [mem
0xb54d8000-0xb54d8fff]
[ 17.409751] kernel: PM: hibernation: Marking nosave pages: [mem
0xb7db3000-0xb7ff]
[ 17.409761] kernel: PM: hibernation: Marking nosave pages: [mem
0xb8759000-0xb87f]
[ 17.409765] kernel: PM: hibernation: Marking nosave pages: [mem
0xb8f9d000-0xb8ff]
[ 17.409767] kernel: PM: hibernation: Marking nosave pages: [mem
0xba6f5000-0xba7f]
[ 17.409773] kernel: PM: hibernation: Marking nosave pages: [mem
0xbbcec000-0x]
[ 17.410626] kernel: PM: hibernation: Basic memory bitmaps created
[ 17.481616] kernel: PM: Using 3 thread(s) for decompression
[ 17.481620] kernel: PM: Loading and decompressing image data (835177
pages)...
[ 17.481626] kernel: PM: hibernation: Image mismatch: architecture specific
data
[ 17.481627] kernel: PM: hibernation: Read 3340708 kbytes in 0.01 seconds
(334070.80 MB/s)
[ 17.482589] kernel: PM: Error -1 resuming
[ 17.482594] kernel: PM: hibernation: Failed to load image, recovering.
[ 17.482992] kernel: PM: hibernation: Basic memory bitmaps freed
[ 17.483572] kernel: PM: hibernation: resume failed (-1)
Here is some system information:
$ cat /proc/version_signature
Ubuntu 5.11.0-25.27-generic 5.11.22
$ cat /sys/power/state
freeze mem disk
$ cat /sys/power/disk
[platform] shutdown reboot suspend test_resume
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet
splash resume=UUID=a2be2098-* mem_sleep_default=deep
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: giacof 2186 F pulseaudio
/dev/snd/controlC2: giacof 2186 F pulseaudio
/dev/snd/controlC0: giacof 2186 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.04
InstallationDate: Installed on 2021-05-17 (71 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Dell Inc. Precision M4800
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic
root=/dev/mapper/vgubuntu-root ro quiet splash
resume=UUID=a2be2098-8e7d-4460-845d-c2b3b22def13 mem_sleep_default=deep
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
RelatedPackageVersions:
linux-restricted-modules-5.11.0-25-generic N/A
linux-backports-modules-5.11.0-25-generic N/A
linux-firmware 1.197.2
StagingDrivers: ashmem_linux
Tags: hirsute staging
Uname: Linux 5.11.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 10/08/2018
dmi.bios.release: 65.25
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A25
dmi.board.name: 0T3YTY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
[Kernel-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)
** Tags removed: disco disconnect down drop network wifi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> scanning Dec 01 21:15:49
[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
modprobe i2c_hid_acpi fixes the touchpad on Fujitsu U7x11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 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.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 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.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE 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.8 dmi.modalias:
[Kernel-packages] [Bug 1908139] Re: ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2
The issue persists on Ubuntu 21.04 with Linux kernel 5.11.0-25-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/1908139 Title: ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2 Status in linux package in Ubuntu: Confirmed Bug description: laptop: ThinkPad T14s Gen 1 - AMD Ryzen 7 PRO 4750U docking station: ThinkPad USB-C Dock 2. Gen. external display: NE MultiSync EA275UHD OS: Ubuntu 20.10 - kernel 5.8.0 Plugging the external display into one of the docking station's two DisplayPort connectors leads to the screen resolution changing on the laptop's builtin display and the external display waking up but showing no picture and displaying "no-signal" after a bit. Plugging the external display into the docking station's HDMI connector leads to no visible reaction on either the external nor the builtin display. Plugging the external display into the laptop's builtin HDMI connector works as expected. The external display is recognized and shows an image. I have recorded the output on `dmesg` during the steps mentioned above and inserted explanations using `echo MSG >/dev/kmsg`. The output follows at the end of the message. I believe `ubuntu-bug` should also attach the full log. All above modes of connection work as expected with the same laptop, dock, and display on Windows 10 (installed as dual boot along side Ubuntu). All above modes of connection also work as expected with an older laptop (ThinkPad T470s - Ubuntu 20.04 - kernel 5.4.0), and the same dock and display. This leads me to believe that this is not a hardware issue. The following bug seems related, but seems to have been observed on faulty hardware according to its author. Therefore, I decided to open a separate bug report. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899336 ``` [ 343.372511] plugging DisplayPort into dock port 1 [ 352.666113] [drm] DP Alt mode state on HPD: 1 [ 352.749192] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 352.858482] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.888400] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.892555] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.896719] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.900876] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.905596] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.910323] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.914485] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 377.353566] plugged in - no signal [ 396.728970] unplugging [ 403.001418] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id: 75] [ 415.576397] unplugged [ 431.500729] plugging DisplayPort into dock port 2 [ 437.607724] [drm] DP Alt mode state on HPD: 1 [ 437.681116] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 437.790303] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.820138] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.824305] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.828462] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.832619] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.837029] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.841984] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.846144] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 458.999849] plugged in - no signal [ 465.702949] unplugging [ 476.127418] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id: 75] [ 476.956491] [drm] Failed to add display topology, DTM TA is not initialized. [ 488.792533] unplugged [ 529.801179] plugging HDMI into dock [ 536.721076] [drm] DP Alt mode state on HPD: 1 [ 536.792947] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 536.901958] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.906123] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.910288] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.914611] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.919568] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.923725] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.927888] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.932047] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.936451] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.941486] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.945651] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.949808] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 537.010093] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 271ba325 port 1: DPCD read on addr 0x60 for 1 bytes NAKed [ 592.844147] plugged in - display does not react [ 597.998141] unplugging
[Kernel-packages] [Bug 1937056] Re: Touchpad not working with ASUS TUF F15
Output of udevadm info --export-db ** Attachment added: "udevdb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937056/+attachment/5515063/+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/1937056 Title: Touchpad not working with ASUS TUF F15 Status in linux package in Ubuntu: New Bug description: I am using Kubuntu 21.04 on my ASUS TUF F15 FX506HM_FX566HM. The touchpad isn't detected in Settings and neither in xinput, nor in cat /proc/bus/input/devices. Laptop model: ASUS TUF F15 FX506HM_FX566HM. Manufacturer of the Touchpad: Probably ELAN1203 When the symptom first appeared: From beginning Output of lsb_release -rd Description:Ubuntu 21.04 Release:21.04 Using kernel version 5.13.6. Also tried 5.11, 5.12.8, 5.12.15, 5.13.1, 5.13.2, 5.13.4, 5.13.5, 5.14-rc2, 5.14-rc3 Output of xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Asus Wireless Radio Control id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11 [slave keyboard (3)] ↳ Intel HID events id=12 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ Asus WMI hotkeys id=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)] Output of lspci :00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 05) :00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #1 (rev 05) :00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) :00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 05) :00:06.0 System peripheral: Intel Corporation Device 09ab :00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #0 (rev 05) :00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 05) :00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01) :00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB Controller (rev 05) :00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI #0 (rev 05) :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller :00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11) :00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11) :00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H Serial IO I2C Controller #0 (rev 11) :00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11) :00:1c.0 PCI bridge: Intel Corporation Device 43bf (rev 11) :00:1d.0 PCI bridge: Intel Corporation Device 43b6 (rev 11) :00:1f.0 ISA bridge: Intel Corporation Tiger Lake-H LPC/eSPI Controller (rev 11) :00:1f.3 Audio device: Intel Corporation Tiger Lake-H HD Audio Controller (rev 11) :00:1f.4 SMBus: Intel Corporation Tiger Lake-H SMBus Controller (rev 11) :00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H SPI Controller (rev 11) :01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1) :01:00.1 Audio device: NVIDIA Corporation Device 228e (rev a1) :2d:00.0 Network controller: MEDIATEK Corp. Device 7961 :2e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 1:e0:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #0 (rev 05) 1:e1:00.0 Non-Volatile memory controller: SK hynix Device 174a --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-25 (1 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: linux
[Kernel-packages] [Bug 1938538] Re: Touchpad not working in Ubuntu 21.04
I added "i8042.nopnp=1 pci=nocrs" to "GRUB_CMDLINE_LINUX_DEFAULT" (as suggested here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881322/comments/3), updated grub and rebooted. The touchpad still does not work (rather is not recognized). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938538 Title: Touchpad not working in Ubuntu 21.04 Status in linux package in Ubuntu: New Bug description: Lenovo Thinkpad X1 Yoga Titanium (Model: 20QBS02G00) Synaptics touchpad not working after Upgrade from 20.04 LTS to 21.04 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amelie 4095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 30 12:09:12 2021 InstallationDate: Installed on 2021-07-28 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20QBS02G00 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgubuntu-root ro nomodeset quiet splash acpi_backlight=vendor acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-07-29 (0 days ago) dmi.bios.date: 05/20/2021 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: N2MET49W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QBS02G00 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.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN2MET49W(1.14):bd05/20/2021:br1.14:efr1.9:svnLENOVO:pn20QBS02G00:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QBS02G00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Titanium Gen 1 dmi.product.name: 20QBS02G00 dmi.product.sku: LENOVO_MT_20QB_BU_Think_FM_ThinkPad X1 Titanium Gen 1 dmi.product.version: ThinkPad X1 Titanium Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938538/+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
