[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
Actually zfs-2.0.2-1ubuntu5, zfs-kmod-2.0.3-8ubuntu5. I'm not sure who to create corruption, but I have plenty of it causing processes to kernel panic. https://github.com/openzfs/zfs/issues/11474 contains some instructions on how to create a corrupted file using wine. Even after this fixed zfs hits, those of us with scrambled file systems are going to need help in clearing out the mess :( So please don't close this bug until there is a mitigation process as well as a fix to zfs to stop it happening further. Does using an encrypted pool have any impact on this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in zfs-linux package in Ubuntu: In Progress Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+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 1931660] Re: PANIC at zfs_znode.c:339:zfs_znode_sa_init()
Does the fact that this is an encrypted pool have any impact on this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931660 Title: PANIC at zfs_znode.c:339:zfs_znode_sa_init() Status in linux package in Ubuntu: Confirmed Bug description: I'm seeing a non-deterministic panic in the ZFS code. Last boot, this occurred in systemd-udevd, resulting in a failed boot. The boot before that, firefox hit the same thing, and this boot it looks like it's hit an Evolution component. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.11.0-18-generic 5.11.0-18.19+21.10.1 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 4988 F pulseaudio /dev/snd/controlC1: chris 4988 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 11:49:47 2021 InstallationDate: Installed on 2021-05-13 (28 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_z8j7yc@/vmlinuz-5.11.0-18-generic root=ZFS=rpool/ROOT/ubuntu_z8j7yc ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.198 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-05-13 (28 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931660/+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 1939460] Re: Unable to play media from Google Chrome with Bluetooth headeset in HSP/HFP profile
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14-rc5/amd64/ Headers are not needed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939460 Title: Unable to play media from Google Chrome with Bluetooth headeset in HSP/HFP profile Status in linux package in Ubuntu: New Bug description: Tried to use the microphone of my bluetooth headset. No audio while using my bluetooth headset in HSP/HFP profile. Media gets forzeen. My goal is to use the headset with A2DP Sink while using the microphone. This is possible on the same system in Windows. Listing information from the system, used audio card and bluetooth information. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 /etc/bluetooth$ pacmd list-cards index: 12 name: driver: owner module: 51 properties: device.description = "PXC 550" device.string = "00:16:94:23:D1:27" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "headset" bluez.path = "/org/bluez/hci0/dev_00_16_94_23_D1_27" bluez.class = "0x240404" bluez.alias = "PXC 550" device.icon_name = "audio-headset-bluetooth" device.intended_roles = "phone" profiles: headset_head_unit: Headset head unit (HSP/HFP) (priority 30, available: yes) a2dp_sink: High fidelity playback (A2DP Sink) (priority 40, available: unknown) off: Av (priority 0, available: yes) active profile: sinks: bluez_sink.00_16_94_23_D1_27.headset_head_unit/#44: PXC 550 sources: bluez_sink.00_16_94_23_D1_27.headset_head_unit.monitor/#53: Monitor of PXC 550 bluez_source.00_16_94_23_D1_27.headset_head_unit/#54: PXC 550 ports: headset-output: Headset (priority 0, latency offset 0 usec, available: yes) properties: headset-input: Headset (priority 0, latency offset 0 usec, available: yes) properties: /etc/bluetooth$ sudo dmesg | grep -i bluetooth [ 10.913222] Bluetooth: Core ver 2.22 [ 10.913242] Bluetooth: HCI device and connection manager initialized [ 10.913245] Bluetooth: HCI socket layer initialized [ 10.913246] Bluetooth: L2CAP socket layer initialized [ 10.913249] Bluetooth: SCO socket layer initialized [ 11.031423] Bluetooth: hci0: BCM: chip id 63 [ 11.032420] Bluetooth: hci0: BCM: features 0x07 [ 11.048478] Bluetooth: hci0: fredrik [ 11.048486] Bluetooth: hci0: BCM20702A1 (001.002.014) build [ 11.049496] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 11.049499] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0b05-17cb.hcd' [ 11.049500] Bluetooth: hci0: BCM: 'brcm/BCM-0b05-17cb.hcd' [ 11.599665] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.599668] Bluetooth: BNEP filters: protocol multicast [ 11.599672] Bluetooth: BNEP socket layer initialized [ 12.734502] Bluetooth: RFCOMM TTY layer initialized [ 12.734507] Bluetooth: RFCOMM socket layer initialized [ 12.734511] Bluetooth: RFCOMM ver 1.11 [27256.450493] Bluetooth: hci0: urb 7dc40568 submission failed (90) [27256.450505] Bluetooth: hci0: sending frame failed (-90) [27256.450511] Bluetooth: hci0: urb 7dc40568 submission failed (90) [27256.450515] Bluetooth: hci0: sending frame failed (-90) [28116.001485] Bluetooth: hci0: urb cbbd81d7 submission failed (90) [28116.001498] Bluetooth: hci0: sending frame failed (-90) [28116.001504] Bluetooth: hci0: urb cbbd81d7 submission failed (90) [28116.001508] Bluetooth: hci0: sending frame failed (-90) [28125.939480] Bluetooth: hci0: urb 508f2223 submission failed (90) [28125.939494] Bluetooth: hci0: sending frame failed (-90) [28125.939501] Bluetooth: hci0: urb 508f2223 submission failed (90) [28125.939505] Bluetooth: hci0: sending frame failed (-90) 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fredrik1324 F pulseaudio /dev/snd/controlC1: fredrik1324 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 11 01:23:14 2021 MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color
[Kernel-packages] [Bug 1939173] Re: [HP 120-1100eo AIO] Screen flickering white horizontal lines
Is it similar to LP: #1936708? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939173 Title: [HP 120-1100eo AIO] Screen flickering white horizontal lines Status in linux-hwe-5.11 package in Ubuntu: New Bug description: The screen on my HP AIO computer flickers. I'm able to browse the computer, but it's giving me headache. Flickering consists pattern of 2cm height white vertical pixel lines (1*Wpx white and 1*Wpx transparent lines) and 2cm transparent section. Flicker also has 1px lines with dashes ending them about 10cm from left of the screen and 2cm from right of the screen. Mathematically letter W being 100% of screen width in above description. Flickering seems to be consistent to screen refresh state (~60Hz). Changing refresh rate does not affect in to amount of flickering. Same thing not happening in Windows nor BIOS. Even though this looks a LOT like a hardware/wiring issue. Also the problem is visible in Ubuntu installer, but not in graphic safe one. Best regards, korho. $ lsb_release -rd: Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 23:04:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] InstallationDate: Installed on 2021-08-06 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard 120-1100eo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=bf3dba7e-429f-455e-ac68-c016e272a4d9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: LEO_707 dmi.board.name: 2AC5 dmi.board.vendor: Quanta dmi.board.version: 100 dmi.chassis.asset.tag: CZC2128RP3 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-1100eo:pvr:rvnQuanta:rn2AC5:rvr100:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 120-1100eo dmi.product.sku: H1E79EA#UUW dmi.sys.vendor: Hewlett-Packard 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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-hwe-5.11/+bug/1939173/+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 1814393] Re: "make: write error: stdout" on parallel builds
Sorry, operation error. The problem is not solved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1814393 Title: "make: write error: stdout" on parallel builds Status in linux-signed package in Ubuntu: Fix Released Bug description: - Release of Ubuntu: 18.04.1 LTS (Kubuntu). - Package version: linux-image-4.15.0-44-generic, linux-image-4.15.0-45-generic. - Expected outcome: Large parallel make build completing properly. - What happened instead: Build stops with "make: write error: stdout". Full explanation: Since the update to kernel 4.15.0-44 (linux-image-4.15.0-44-generic) in Kubuntu Bionic I'm experiencing issues in my ThinkPad P52 laptop during large parallel builds of source code (eg: a buildroot full rebuild for a work project). Note that this reports isn't about kernel builds, but about large project builds in general. I don't think it's relevant, but I'm running those builds in an schroot with the same Ubuntu Bionic distro I'm also using as main host distro. The specific error I get is this (in Spanish): make[4]: error al escribir: stdout I call Buildroot's make like this from KDE Konsole with "infinite history buffer" enabled (uses a tmp file to store the logs): V=1 make ...some stuff... 2>&1 However, the error is reproducible in Konsole even if I call make without options and also if I use "limited (in-memory) history buffer" as well as "no history buffer". Buildroot autoselects a parallelization level (-j) automatically. In my case, I'm using a Xeon E-2176 CPU with 12 threads. Searching on the Internet I found a thread[1] where people from the GNU Make project say that the error may be coming from the C runtime library (and I suspect originating from the kernel). I can NOT reproduce the issue on linux-image-4.15.0-43-generic (selected from grub at boot), but I experience it with linux- image-4.15.0-44-generic and linux-image-4.15.0-45-generic. That's why I'm reporting this bug against the linux package. Interestingly enough, I can NOT reproduce the issue on linux- image-4.15.0-45-generic (haven't tried previous versions) when building from xterm instead of Konsole. Unfortunately, this laptop has a 4K screen and xterm isn't an option for me. If I build redirecting stdout and stderr to different files to avoid terminal output and then watching the stdout file with tail -f, the tail command eventually finishes although the build continues and I can keep watching it by running tail again. An infinite build loop never finishes with this redirection (error not reproducible). Same results with the 2>&1 redirection to a single file. All this looks a bit like a poltergeist, but the only thing I'm sure about is that it all started with the upgrade from 4.15.0-43 to -44 and it continues on -45. Thank you. [1] http://gnu-make.2324884.n4.nabble.com/Spurious-quot-write-error-quot-on-parallel-builds-td15695.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1814393/+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 1939473] Re: mute/micmute LEDs no function on HP ProBook 650 G8
** Tags added: oem-priority originate-from-1938756 stella ** Tags added: originate-from-1938757 ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Triaged ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939473 Title: mute/micmute LEDs no function on HP ProBook 650 G8 Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook 650 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1939473/+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 1814393] Re: "make: write error: stdout" on parallel builds
** Changed in: linux-signed (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1814393 Title: "make: write error: stdout" on parallel builds Status in linux-signed package in Ubuntu: Fix Released Bug description: - Release of Ubuntu: 18.04.1 LTS (Kubuntu). - Package version: linux-image-4.15.0-44-generic, linux-image-4.15.0-45-generic. - Expected outcome: Large parallel make build completing properly. - What happened instead: Build stops with "make: write error: stdout". Full explanation: Since the update to kernel 4.15.0-44 (linux-image-4.15.0-44-generic) in Kubuntu Bionic I'm experiencing issues in my ThinkPad P52 laptop during large parallel builds of source code (eg: a buildroot full rebuild for a work project). Note that this reports isn't about kernel builds, but about large project builds in general. I don't think it's relevant, but I'm running those builds in an schroot with the same Ubuntu Bionic distro I'm also using as main host distro. The specific error I get is this (in Spanish): make[4]: error al escribir: stdout I call Buildroot's make like this from KDE Konsole with "infinite history buffer" enabled (uses a tmp file to store the logs): V=1 make ...some stuff... 2>&1 However, the error is reproducible in Konsole even if I call make without options and also if I use "limited (in-memory) history buffer" as well as "no history buffer". Buildroot autoselects a parallelization level (-j) automatically. In my case, I'm using a Xeon E-2176 CPU with 12 threads. Searching on the Internet I found a thread[1] where people from the GNU Make project say that the error may be coming from the C runtime library (and I suspect originating from the kernel). I can NOT reproduce the issue on linux-image-4.15.0-43-generic (selected from grub at boot), but I experience it with linux- image-4.15.0-44-generic and linux-image-4.15.0-45-generic. That's why I'm reporting this bug against the linux package. Interestingly enough, I can NOT reproduce the issue on linux- image-4.15.0-45-generic (haven't tried previous versions) when building from xterm instead of Konsole. Unfortunately, this laptop has a 4K screen and xterm isn't an option for me. If I build redirecting stdout and stderr to different files to avoid terminal output and then watching the stdout file with tail -f, the tail command eventually finishes although the build continues and I can keep watching it by running tail again. An infinite build loop never finishes with this redirection (error not reproducible). Same results with the 2>&1 redirection to a single file. All this looks a bit like a poltergeist, but the only thing I'm sure about is that it all started with the upgrade from 4.15.0-43 to -44 and it continues on -45. Thank you. [1] http://gnu-make.2324884.n4.nabble.com/Spurious-quot-write-error-quot-on-parallel-builds-td15695.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1814393/+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 1931660] Re: PANIC at zfs_znode.c:339:zfs_znode_sa_init()
Downgrading these libraries did not fix it for me. One canary is to look at the state of the updatedb.mlocate process which goes into live hang as it hits the file that is currently faulty. Thus for example: 2728 ?DNs0:01 /usr/bin/updatedb.mlocate Using lsof one can find out which is the faulty file but, if you try to ls the directory with the file in, then you terminal live hangs. And if you try to delete the directory containing the faulty file, then that silently fails, leaving the directory and the live hang should you try to read it. It's said that this bug relates to 1906476 and via that to https://github.com/openzfs/zfs/issues/11474 but I think I have that one fixed with zfs_recover=1. But the syslog message is very similar: Aug 11 10:13:45 silmh9 kernel: [ 242.531205] INFO: task updatedb.mlocat:2728 blocked for more than 120 seconds. Aug 11 10:13:45 silmh9 kernel: [ 242.531211] Tainted: P U O 5.13.0-13-generic #13-Ubuntu Aug 11 10:13:45 silmh9 kernel: [ 242.531212] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 11 10:13:45 silmh9 kernel: [ 242.531213] task:updatedb.mlocat state:D stack:0 pid: 2728 ppid: 1 flags:0x4220 Aug 11 10:13:45 silmh9 kernel: [ 242.531216] Call Trace: Aug 11 10:13:45 silmh9 kernel: [ 242.531221] __schedule+0x268/0x680 Aug 11 10:13:45 silmh9 kernel: [ 242.531225] ? arch_local_irq_enable+0xb/0xd Aug 11 10:13:45 silmh9 kernel: [ 242.531228] schedule+0x4f/0xc0 Aug 11 10:13:45 silmh9 kernel: [ 242.531231] spl_panic+0xfa/0xfc [spl] Aug 11 10:13:45 silmh9 kernel: [ 242.531238] ? queued_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531287] ? do_raw_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531313] ? __raw_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531339] ? dmu_buf_replace_user+0x65/0x80 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531367] ? dmu_buf_set_user+0x13/0x20 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531393] ? dmu_buf_set_user_ie+0x15/0x20 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531420] zfs_znode_sa_init+0xd9/0xe0 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531479] zfs_znode_alloc+0x101/0x560 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531536] ? dmu_buf_unlock_parent+0x5d/0x90 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531564] ? do_raw_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531590] ? dbuf_read_impl.constprop.0+0x316/0x3e0 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531616] ? __cond_resched+0x1a/0x50 Aug 11 10:13:45 silmh9 kernel: [ 242.531618] ? __raw_callee_save___native_queued_spin_unlock+0x15/0x23 Aug 11 10:13:45 silmh9 kernel: [ 242.531620] ? queued_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531642] ? __cond_resched+0x1a/0x50 Aug 11 10:13:45 silmh9 kernel: [ 242.531644] ? down_read+0x13/0x90 Aug 11 10:13:45 silmh9 kernel: [ 242.531645] ? __raw_callee_save___native_queued_spin_unlock+0x15/0x23 Aug 11 10:13:45 silmh9 kernel: [ 242.531646] ? queued_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531680] ? do_raw_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531712] ? __raw_callee_save___native_queued_spin_unlock+0x15/0x23 Aug 11 10:13:45 silmh9 kernel: [ 242.531713] ? dmu_object_info_from_dnode+0x8e/0xa0 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531742] zfs_zget+0x237/0x280 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531796] zfs_dirent_lock+0x42a/0x570 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531850] zfs_dirlook+0x91/0x2a0 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531902] zfs_lookup+0x1fb/0x3f0 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531954] zpl_lookup+0xcb/0x230 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.532007] __lookup_slow+0x84/0x150 Aug 11 10:13:45 silmh9 kernel: [ 242.532009] walk_component+0x141/0x1b0 Aug 11 10:13:45 silmh9 kernel: [ 242.532010] ? dput+0x5c/0x180 Aug 11 10:13:45 silmh9 kernel: [ 242.532012] path_lookupat+0x6e/0x1c0 Aug 11 10:13:45 silmh9 kernel: [ 242.532013] filename_lookup+0xbb/0x1c0 Aug 11 10:13:45 silmh9 kernel: [ 242.532015] ? __check_object_size.part.0+0x128/0x150 Aug 11 10:13:45 silmh9 kernel: [ 242.532017] ? __check_object_size+0x1c/0x20 Aug 11 10:13:45 silmh9 kernel: [ 242.532018] ? strncpy_from_user+0x44/0x150 Aug 11 10:13:45 silmh9 kernel: [ 242.532020] ? __raw_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.532066] user_path_at_empty+0x59/0x90 Aug 11 10:13:45 silmh9 kernel: [ 242.532068] vfs_statx+0x7a/0x120 Aug 11 10:13:45 silmh9 kernel: [ 242.532070] __do_sys_newlstat+0x3e/0x70 Aug 11 10:13:45 silmh9 kernel: [ 242.532072] ? __secure_computing+0x42/0xe0 Aug 11 10:13:45 silmh9 kernel: [ 242.532073] ? syscall_trace_enter.constprop.0+0xa0/0x1c0 Aug 11 10:13:45 silmh9 kernel: [ 242.532075] __x64_sys_newlstat+0x16/0x20 Aug 11 10:13:45 silmh9 kernel: [ 242.532076]
[Kernel-packages] [Bug 1939473] [NEW] mute/micmute LEDs no function on HP ProBook 650 G8
Public bug reported: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook 650 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939473 Title: mute/micmute LEDs no function on HP ProBook 650 G8 Status in linux package in Ubuntu: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook 650 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939473/+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 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
Can anyone please confirm the #57 works without any major problem? If yes, I request someone please write the instructions comprehensively. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1939173] Re: [HP 120-1100eo API] Screen flickering white horizontal lines
Thanks. I've reassigned this to the kernel because that video shows the problem happening before mutter/gnome-shell is even running. ** Summary changed: - [HP 120-1100eo API] Screen flickering white vertical lines + [HP 120-1100eo API] Screen flickering white horizontal lines ** Package changed: mutter (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Summary changed: - [HP 120-1100eo API] Screen flickering white horizontal lines + [HP 120-1100eo AIO] Screen flickering white horizontal lines ** Package changed: linux (Ubuntu) => linux-hwe-5.11 (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/1939173 Title: [HP 120-1100eo AIO] Screen flickering white horizontal lines Status in linux-hwe-5.11 package in Ubuntu: New Bug description: The screen on my HP AIO computer flickers. I'm able to browse the computer, but it's giving me headache. Flickering consists pattern of 2cm height white vertical pixel lines (1*Wpx white and 1*Wpx transparent lines) and 2cm transparent section. Flicker also has 1px lines with dashes ending them about 10cm from left of the screen and 2cm from right of the screen. Mathematically letter W being 100% of screen width in above description. Flickering seems to be consistent to screen refresh state (~60Hz). Changing refresh rate does not affect in to amount of flickering. Same thing not happening in Windows nor BIOS. Even though this looks a LOT like a hardware/wiring issue. Also the problem is visible in Ubuntu installer, but not in graphic safe one. Best regards, korho. $ lsb_release -rd: Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 23:04:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] InstallationDate: Installed on 2021-08-06 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard 120-1100eo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=bf3dba7e-429f-455e-ac68-c016e272a4d9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: LEO_707 dmi.board.name: 2AC5 dmi.board.vendor: Quanta dmi.board.version: 100 dmi.chassis.asset.tag: CZC2128RP3 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-1100eo:pvr:rvnQuanta:rn2AC5:rvr100:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 120-1100eo dmi.product.sku: H1E79EA#UUW dmi.sys.vendor: Hewlett-Packard 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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-hwe-5.11/+bug/1939173/+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 1939221] Re: [amdgpu] Screen freeze then system without response
Also the kernel version you have looks outdated: 5.4.0-7634.38~1592497129~20.04~9a1ea2e-generic Please try installing the latest version with: sudo apt update sudo apt install linux-generic-hwe-20.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/1939221 Title: [amdgpu] Screen freeze then system without response Status in linux package in Ubuntu: New Bug description: It seems that I install a new graphic cart AMD Radeon R7 240, it was blinking at first i watch video then put it on full screen (especially in browser chrome). it suddenly no response for any keys. even i press "Ctrl+alt+delete" or try "Ctrl+alt+F2" to text mode. then I search google and install amd's opencl driver to replace intel. but, it just better then previous. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.9-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-7634.38~1592497129~20.04~9a1ea2e-generic 5.4.41 Uname: Linux 5.4.0-7634-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 13:48:50 2021 InstallationDate: Installed on 2019-11-23 (623 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939221/+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 1939221] Re: Screen Freeze then system without response
Thanks. It looks like there is a recurring problem with the amdgpu kernel driver: 8月 10 22:35:10 peter-ubuntu kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=4929676, emitted seq=4929678 8月 10 22:35:10 peter-ubuntu kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1266 thread Xorg:cs0 pid 1374 8月 10 22:35:10 peter-ubuntu kernel: [drm] GPU recovery disabled. ** Tags added: amdgpu ** Summary changed: - Screen Freeze then system without response + [amdgpu] Screen freeze then system without response ** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939221 Title: [amdgpu] Screen freeze then system without response Status in linux package in Ubuntu: New Bug description: It seems that I install a new graphic cart AMD Radeon R7 240, it was blinking at first i watch video then put it on full screen (especially in browser chrome). it suddenly no response for any keys. even i press "Ctrl+alt+delete" or try "Ctrl+alt+F2" to text mode. then I search google and install amd's opencl driver to replace intel. but, it just better then previous. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.9-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-7634.38~1592497129~20.04~9a1ea2e-generic 5.4.41 Uname: Linux 5.4.0-7634-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 13:48:50 2021 InstallationDate: Installed on 2019-11-23 (623 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939221/+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 1939173] [NEW] [HP 120-1100eo API] Screen flickering white horizontal lines
You have been subscribed to a public bug: The screen on my HP AIO computer flickers. I'm able to browse the computer, but it's giving me headache. Flickering consists pattern of 2cm height white vertical pixel lines (1*Wpx white and 1*Wpx transparent lines) and 2cm transparent section. Flicker also has 1px lines with dashes ending them about 10cm from left of the screen and 2cm from right of the screen. Mathematically letter W being 100% of screen width in above description. Flickering seems to be consistent to screen refresh state (~60Hz). Changing refresh rate does not affect in to amount of flickering. Same thing not happening in Windows nor BIOS. Even though this looks a LOT like a hardware/wiring issue. Also the problem is visible in Ubuntu installer, but not in graphic safe one. Best regards, korho. $ lsb_release -rd: Description:Ubuntu 20.04.2 LTS Release:20.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 23:04:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] InstallationDate: Installed on 2021-08-06 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard 120-1100eo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=bf3dba7e-429f-455e-ac68-c016e272a4d9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: LEO_707 dmi.board.name: 2AC5 dmi.board.vendor: Quanta dmi.board.version: 100 dmi.chassis.asset.tag: CZC2128RP3 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-1100eo:pvr:rvnQuanta:rn2AC5:rvr100:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 120-1100eo dmi.product.sku: H1E79EA#UUW dmi.sys.vendor: Hewlett-Packard 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu wayland-session -- [HP 120-1100eo API] Screen flickering white horizontal lines https://bugs.launchpad.net/bugs/1939173 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)
If you experience lockups with kernel 5.11 then please: 1. Wait 10 seconds. 2. Reboot. 3. Run this command: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-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: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-ef1xxx dmi.product.sku: 27A48UA#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-hwe-5.8/+bug/1937321/+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 1939221] [NEW] [amdgpu] Screen freeze then system without response
You have been subscribed to a public bug: It seems that I install a new graphic cart AMD Radeon R7 240, it was blinking at first i watch video then put it on full screen (especially in browser chrome). it suddenly no response for any keys. even i press "Ctrl+alt+delete" or try "Ctrl+alt+F2" to text mode. then I search google and install amd's opencl driver to replace intel. but, it just better then previous. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.9-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-7634.38~1592497129~20.04~9a1ea2e-generic 5.4.41 Uname: Linux 5.4.0-7634-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 13:48:50 2021 InstallationDate: Installed on 2019-11-23 (623 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 amdgpu apport-bug focal third-party-packages -- [amdgpu] Screen freeze then system without response https://bugs.launchpad.net/bugs/1939221 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1939402] Re: Touchpad not working correctly after Ubuntu Update
Please run this command: sudo dmesg > dmesg.txt and attach the resulting text file here. We need to know more details about the model of machine. ** Changed in: linux-signed-hwe-5.11 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939402 Title: Touchpad not working correctly after Ubuntu Update Status in linux-signed-hwe-5.11 package in Ubuntu: Incomplete Bug description: xinput list When I run this command I do not see the touchpad listed. cat /proc/bus/input/devices In this command too I do not see the Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 10 18:04:56 2021 InstallationDate: Installed on 2021-06-26 (45 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939402/+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 1901350] Re: [Lenovo ThinkPad T450s] Touchpad stops working after sleep
Please try a newer kernel by downloading: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.9/amd64/linux- image- unsigned-5.13.9-051309-generic_5.13.9-051309.202108080438_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.9/amd64/linux- modules-5.13.9-051309-generic_5.13.9-051309.202108080438_amd64.deb and then install them together with: sudo dpkg -i linux*.deb and reboot. ** Tags removed: groovy ** Tags added: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901350 Title: [Lenovo ThinkPad T450s] Touchpad stops working after sleep Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 and 20.10, the touchpad stops working after sleep. Restarting with rmmod psmouse and modprobe psmouse is not working anymore, the touchpad reloads but with the wrong settings. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 13:42:39 2020 DistUpgraded: 2020-10-24 12:59:49,175 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] MachineType: LENOVO 20BWS1D61J ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=UUID=09cc0657-0a94-4a6c-9043-2df6132cd821 ro SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago) dmi.bios.date: 02/23/2019 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: JBET72WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS1D61J dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrJBET72WW(1.36):bd02/23/2019:br1.36:efr1.4:svnLENOVO:pn20BWS1D61J:pvrThinkPadT450s:rvnLENOVO:rn20BWS1D61J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS1D61J dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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/1901350/+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 1939285] Re: [Lenovo ThinkBook-15-IML] touchpad not recognised from the beginning
** Summary changed: - touchpad not recognised from the beginning + [Lenovo ThinkBook-15-IML] touchpad not recognised from the beginning -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939285 Title: [Lenovo ThinkBook-15-IML] touchpad not recognised from the beginning Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I recently dual-booted my windows 10 machine with ubuntu 20.04.2 LTS, even during my installation, the touchpad didnt work but mouse works. I tried modifying the grub file as given in some previous help requests but it didnt work. My laptop is Lenovo ThinkBook-15-IML ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 9 14:50:34 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939285/+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 1876632] Re: [nvidia] Corrupted shell textures when switching users or resuming from suspend
** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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/gnome-shell/+bug/1876632/+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 1936009] Re: [SRU] The internal mic of Dell Precision 5750 can't record sound
Oh, forgot to add testing info of 2 kernels: With hirsute: the old kernel is linux-5.10.0-1027-oem, the new kernel is linux-5.11.0-26.28-generic. With focal: the old kernel is linux-5.10.0-1027-oem, the new kernel is linux-5.10.0-1042-oem. The internal mic could work well with all kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1936009 Title: [SRU] The internal mic of Dell Precision 5750 can't record sound Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Released Bug description: [Impact] After upgrade the linux kernel, the mixer names of rt715 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't record sound from internal mic since the internal mic is routed to the codec rt715. [Fix] Backport 3 upstream commits, after applying these 3 commits, the ucm conf file dosn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec. [Test] run 'alsactl init 1' on the precision 5750 with old and new kernel, there is no error logs, use the internal mic to record sound, it could record successfully. [Where problems will occur] The change only affects the rt715 codec, so far, that codec only connects to the internal mic on Dell soundwire audio machines, so it could introduce regression on the internal mic like users can't record sound via internal mic anymore on the Dell soundwire audio machines. But this possibility is very low since we already tested these 3 commits on different Dell soundwire audio machines (latitude and precision). We tested it with old kernel and new kernel, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936009/+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 1939460] Re: Unable to play media from Google Chrome with Bluetooth headeset in HSP/HFP profile
** 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/1939460 Title: Unable to play media from Google Chrome with Bluetooth headeset in HSP/HFP profile Status in linux package in Ubuntu: New Bug description: Tried to use the microphone of my bluetooth headset. No audio while using my bluetooth headset in HSP/HFP profile. Media gets forzeen. My goal is to use the headset with A2DP Sink while using the microphone. This is possible on the same system in Windows. Listing information from the system, used audio card and bluetooth information. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 /etc/bluetooth$ pacmd list-cards index: 12 name: driver: owner module: 51 properties: device.description = "PXC 550" device.string = "00:16:94:23:D1:27" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "headset" bluez.path = "/org/bluez/hci0/dev_00_16_94_23_D1_27" bluez.class = "0x240404" bluez.alias = "PXC 550" device.icon_name = "audio-headset-bluetooth" device.intended_roles = "phone" profiles: headset_head_unit: Headset head unit (HSP/HFP) (priority 30, available: yes) a2dp_sink: High fidelity playback (A2DP Sink) (priority 40, available: unknown) off: Av (priority 0, available: yes) active profile: sinks: bluez_sink.00_16_94_23_D1_27.headset_head_unit/#44: PXC 550 sources: bluez_sink.00_16_94_23_D1_27.headset_head_unit.monitor/#53: Monitor of PXC 550 bluez_source.00_16_94_23_D1_27.headset_head_unit/#54: PXC 550 ports: headset-output: Headset (priority 0, latency offset 0 usec, available: yes) properties: headset-input: Headset (priority 0, latency offset 0 usec, available: yes) properties: /etc/bluetooth$ sudo dmesg | grep -i bluetooth [ 10.913222] Bluetooth: Core ver 2.22 [ 10.913242] Bluetooth: HCI device and connection manager initialized [ 10.913245] Bluetooth: HCI socket layer initialized [ 10.913246] Bluetooth: L2CAP socket layer initialized [ 10.913249] Bluetooth: SCO socket layer initialized [ 11.031423] Bluetooth: hci0: BCM: chip id 63 [ 11.032420] Bluetooth: hci0: BCM: features 0x07 [ 11.048478] Bluetooth: hci0: fredrik [ 11.048486] Bluetooth: hci0: BCM20702A1 (001.002.014) build [ 11.049496] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 11.049499] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0b05-17cb.hcd' [ 11.049500] Bluetooth: hci0: BCM: 'brcm/BCM-0b05-17cb.hcd' [ 11.599665] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.599668] Bluetooth: BNEP filters: protocol multicast [ 11.599672] Bluetooth: BNEP socket layer initialized [ 12.734502] Bluetooth: RFCOMM TTY layer initialized [ 12.734507] Bluetooth: RFCOMM socket layer initialized [ 12.734511] Bluetooth: RFCOMM ver 1.11 [27256.450493] Bluetooth: hci0: urb 7dc40568 submission failed (90) [27256.450505] Bluetooth: hci0: sending frame failed (-90) [27256.450511] Bluetooth: hci0: urb 7dc40568 submission failed (90) [27256.450515] Bluetooth: hci0: sending frame failed (-90) [28116.001485] Bluetooth: hci0: urb cbbd81d7 submission failed (90) [28116.001498] Bluetooth: hci0: sending frame failed (-90) [28116.001504] Bluetooth: hci0: urb cbbd81d7 submission failed (90) [28116.001508] Bluetooth: hci0: sending frame failed (-90) [28125.939480] Bluetooth: hci0: urb 508f2223 submission failed (90) [28125.939494] Bluetooth: hci0: sending frame failed (-90) [28125.939501] Bluetooth: hci0: urb 508f2223 submission failed (90) [28125.939505] Bluetooth: hci0: sending frame failed (-90) 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fredrik1324 F pulseaudio /dev/snd/controlC1: fredrik1324 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 11 01:23:14 2021 MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB:
[Kernel-packages] [Bug 1939460] [NEW] Unable to play media from Google Chrome with Bluetooth headeset in HSP/HFP profile
You have been subscribed to a public bug: Tried to use the microphone of my bluetooth headset. No audio while using my bluetooth headset in HSP/HFP profile. Media gets forzeen. My goal is to use the headset with A2DP Sink while using the microphone. This is possible on the same system in Windows. Listing information from the system, used audio card and bluetooth information. lsb_release -rd Description:Ubuntu 21.04 Release:21.04 /etc/bluetooth$ pacmd list-cards index: 12 name: driver: owner module: 51 properties: device.description = "PXC 550" device.string = "00:16:94:23:D1:27" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "headset" bluez.path = "/org/bluez/hci0/dev_00_16_94_23_D1_27" bluez.class = "0x240404" bluez.alias = "PXC 550" device.icon_name = "audio-headset-bluetooth" device.intended_roles = "phone" profiles: headset_head_unit: Headset head unit (HSP/HFP) (priority 30, available: yes) a2dp_sink: High fidelity playback (A2DP Sink) (priority 40, available: unknown) off: Av (priority 0, available: yes) active profile: sinks: bluez_sink.00_16_94_23_D1_27.headset_head_unit/#44: PXC 550 sources: bluez_sink.00_16_94_23_D1_27.headset_head_unit.monitor/#53: Monitor of PXC 550 bluez_source.00_16_94_23_D1_27.headset_head_unit/#54: PXC 550 ports: headset-output: Headset (priority 0, latency offset 0 usec, available: yes) properties: headset-input: Headset (priority 0, latency offset 0 usec, available: yes) properties: /etc/bluetooth$ sudo dmesg | grep -i bluetooth [ 10.913222] Bluetooth: Core ver 2.22 [ 10.913242] Bluetooth: HCI device and connection manager initialized [ 10.913245] Bluetooth: HCI socket layer initialized [ 10.913246] Bluetooth: L2CAP socket layer initialized [ 10.913249] Bluetooth: SCO socket layer initialized [ 11.031423] Bluetooth: hci0: BCM: chip id 63 [ 11.032420] Bluetooth: hci0: BCM: features 0x07 [ 11.048478] Bluetooth: hci0: fredrik [ 11.048486] Bluetooth: hci0: BCM20702A1 (001.002.014) build [ 11.049496] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 11.049499] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0b05-17cb.hcd' [ 11.049500] Bluetooth: hci0: BCM: 'brcm/BCM-0b05-17cb.hcd' [ 11.599665] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.599668] Bluetooth: BNEP filters: protocol multicast [ 11.599672] Bluetooth: BNEP socket layer initialized [ 12.734502] Bluetooth: RFCOMM TTY layer initialized [ 12.734507] Bluetooth: RFCOMM socket layer initialized [ 12.734511] Bluetooth: RFCOMM ver 1.11 [27256.450493] Bluetooth: hci0: urb 7dc40568 submission failed (90) [27256.450505] Bluetooth: hci0: sending frame failed (-90) [27256.450511] Bluetooth: hci0: urb 7dc40568 submission failed (90) [27256.450515] Bluetooth: hci0: sending frame failed (-90) [28116.001485] Bluetooth: hci0: urb cbbd81d7 submission failed (90) [28116.001498] Bluetooth: hci0: sending frame failed (-90) [28116.001504] Bluetooth: hci0: urb cbbd81d7 submission failed (90) [28116.001508] Bluetooth: hci0: sending frame failed (-90) [28125.939480] Bluetooth: hci0: urb 508f2223 submission failed (90) [28125.939494] Bluetooth: hci0: sending frame failed (-90) [28125.939501] Bluetooth: hci0: urb 508f2223 submission failed (90) [28125.939505] Bluetooth: hci0: sending frame failed (-90) 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fredrik1324 F pulseaudio /dev/snd/controlC1: fredrik1324 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 11 01:23:14 2021 MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=7e1152b7-0334-4bac-80c2-b45697d9beff ro quiet splash 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: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2019 dmi.bios.release: 5.11
[Kernel-packages] [Bug 1901350] Re: [Lenovo ThinkPad T450s] Touchpad stops working after sleep
How can we get this problem fixed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901350 Title: [Lenovo ThinkPad T450s] Touchpad stops working after sleep Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 and 20.10, the touchpad stops working after sleep. Restarting with rmmod psmouse and modprobe psmouse is not working anymore, the touchpad reloads but with the wrong settings. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 13:42:39 2020 DistUpgraded: 2020-10-24 12:59:49,175 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] MachineType: LENOVO 20BWS1D61J ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=UUID=09cc0657-0a94-4a6c-9043-2df6132cd821 ro SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago) dmi.bios.date: 02/23/2019 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: JBET72WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS1D61J dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrJBET72WW(1.36):bd02/23/2019:br1.36:efr1.4:svnLENOVO:pn20BWS1D61J:pvrThinkPadT450s:rvnLENOVO:rn20BWS1D61J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS1D61J dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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/1901350/+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 1939424] Re: FTBFS with Linux 5.13/GCC 11
Thanks for the review, Lucas. I added the proper "LP: #" snippet to the d/changelog entry, and uploaded the package now: $ dput llvm-toolchain-11_11.0.1-2ubuntu5_source.changes Trying to upload package to ubuntu Checking signature on .changes gpg: /home/sergio/work/llvm-toolchain/llvm-toolchain-11_11.0.1-2ubuntu5_source.changes: Valid signature from 106DA1C8C3CBBF14 Checking signature on .dsc gpg: /home/sergio/work/llvm-toolchain/llvm-toolchain-11_11.0.1-2ubuntu5.dsc: Valid signature from 106DA1C8C3CBBF14 Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading llvm-toolchain-11_11.0.1-2ubuntu5.dsc: done. Uploading llvm-toolchain-11_11.0.1-2ubuntu5.debian.tar.xz: done. Uploading llvm-toolchain-11_11.0.1-2ubuntu5_source.buildinfo: done. Uploading llvm-toolchain-11_11.0.1-2ubuntu5_source.changes: done. Successfully uploaded packages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to llvm-toolchain-11 in Ubuntu. https://bugs.launchpad.net/bugs/1939424 Title: FTBFS with Linux 5.13/GCC 11 Status in llvm-toolchain-11 package in Ubuntu: Confirmed Bug description: llvm-toolchain-11 is FTBFS'ing with Linux 5.13 because of: [ 8%] Building CXX object projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_posix.cpp.o cd /<>/build-llvm/projects/compiler-rt/lib/sanitizer_common && /usr/bin/g++-11 -DHAVE_RPC_XDR_H=0 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/projects/compiler-rt/lib/sanitizer_common -I/<>/compiler-rt/lib/sanitizer_common -I/<>/build-llvm/include -I/<>/llvm/include -I/<>/compiler-rt/lib/sanitizer_common/.. -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wno-comment -ffunction-sections -fdata-sections -Wall -std=c++14 -Wno-unused-parameter -O2 -DNDEBUG -g1 -m64 -fPIC -fno-builtin -fno-exceptions -fomit-frame-pointer -funwind-tables -fno-stack-protector -fvisibility=hidden -fno-lto -O3 -g -Wno-variadic-macros -Wno-non-virtual-dtor -fno-rtti -Wframe-larger-than=570 -std=c++14 -o CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_posix.cpp.o -c /<>/compiler-rt/lib/sanitizer_common/sanitizer_posix.cpp /<>/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.cpp:133:10: fatal error: linux/cyclades.h: No such file or directory 133 | #include | ^~ compilation terminated. make[5]: *** [projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/build.make:358: projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_platform_limits_posix.cpp.o] Error 1 make[5]: *** Waiting for unfinished jobs make -f projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommonCoverage.x86_64.dir/build.make projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommonCoverage.x86_64.dir/depend make[5]: Entering directory '/<>/build-llvm' This is happening because the Cyclades driver has been finally removed from Linux (after being orphaned 13 years ago): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/include/uapi/linux?h=v5.12=f76edd8f7ce06cdff2fe5b6b39a49644c684a161 LLVM includes cyclades.h when building libsanitizer, and therefore the FTBFS occurs. Upstream has fixed this by removing support for Cyclades from libsanitizer: https://github.com/llvm/llvm- project/commit/884040db086936107ec81656aa5b4c607235fb9a As for the GCC 11 failure, the problem is: [ 19%] Building CXX object tools/clang/utils/TableGen/CMakeFiles/obj.clang-tblgen.dir/ClangDiagnosticsEmitter.cpp.o cd /<>/build-llvm/tools/clang/stage2-bins/tools/clang/utils/TableGen && /<>/build-llvm/./bin/clang++ -DCLANG_VENDOR="\"Ubuntu \"" -D_GNU_SOURCE -D__STDC_CONSTANT_M ACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/utils/TableGen -I/<>/clang/utils/TableGen -I/< >/clang/include -I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/include -I/<>/build-llvm/tools/clang/stage2-bins/include -I/<>/llvm/include -fuse -ld=gold -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused -parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default -Wno-class-memaccess -Wno-noexcept-type -Wnon-vi rtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion
[Kernel-packages] [Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
Same issue with Lenovo Thinkpad P70 w Quadro M600M -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: After a recent update to nvidia-460, suspend then resume results in a black screen, then a hang for around 120 seconds, and then the text: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer dmesg shows: [ 188.352670] ACPI: Waking up from system sleep state S3 ... [ 309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.151885] acpi LNXPOWER:08: Turning OFF [ 313.151898] acpi LNXPOWER:04: Turning OFF [ 313.152351] acpi LNXPOWER:03: Turning OFF [ 313.153064] acpi LNXPOWER:02: Turning OFF ... [ 325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DELL 2209WA (HDMI-0) [ 325.010577] BUG: kernel NULL pointer dereference, address: 0050 [ 325.010579] #PF: supervisor read access in kernel mode [ 325.010580] #PF: error_code(0x) - not-present page [ 325.010580] PGD 0 P4D 0 [ 325.010582] Oops: [#1] SMP PTI [ 325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P O 5.4.0-60-generic #67-Ubuntu [ 325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018 [ 325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset] [ 325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10 [ 325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246 [ 325.010598] RAX: 0280 RBX: 0038 RCX: 03ff [ 325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 0038 [ 325.010599] RBP: b89542e5b9c8 R08: R09: c379e440 [ 325.010600] R10: R11: R12: b89542e5b948 [ 325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: c3a50e60 [ 325.010601] FS: 7feb4c09ea80() GS:8e46ada4() knlGS: [ 325.010602] CS: 0010 DS: ES: CR0: 80050033 [ 325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 003606e0 [ 325.010603] Call Trace: [ 325.010610] ? _nv002768kms+0x96/0xd0 [nvidia_modeset] [ 325.010616] ? _nv002328kms+0xb5/0x110 [nvidia_modeset] [ 325.010624] ? _nv000742kms+0x168/0x370 [nvidia_modeset] [ 325.010823] ? _nv036002rm+0x62/0x70 [nvidia] [ 325.010910] ? os_get_current_tick+0x2c/0x50 [nvidia] [ 325.010921] ? _nv002771kms+0x433/0x600 [nvidia_modeset] [ 325.010928] ? _nv002771kms+0x3fc/0x600 [nvidia_modeset] [ 325.010930] ? __schedule+0x2eb/0x740 [ 325.010935] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010939] ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset] [ 325.010944] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010948] ? _nv000744kms+0x2a/0x40 [nvidia_modeset] [ 325.010952] ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset] [ 325.010957] ? nvkms_ioctl_common+0x42/0x80 [nvidia_modeset] [ 325.010961] ? nvkms_ioctl+0xc4/0x100 [nvidia_modeset] [ 325.011016] ? nvidia_frontend_unlocked_ioctl+0x3b/0x50 [nvidia] [ 325.011017] ? do_vfs_ioctl+0x407/0x670 [ 325.011019] ? do_user_addr_fault+0x216/0x450 [ 325.011020] ? ksys_ioctl+0x67/0x90 [ 325.011021] ? __x64_sys_ioctl+0x1a/0x20 [ 325.011023] ? do_syscall_64+0x57/0x190 [ 325.011024] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 325.011025] Modules linked in: rfcomm ccm aufs overlay cmac algif_hash algif_skcipher af_alg bnep snd_sof_pci snd_sof_intel_hda_common nvidia_uvm(O) snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match nvidia_drm(PO) snd_soc_acpi nvidia_modeset(PO) snd_soc_core snd_compress
[Kernel-packages] [Bug 1939424] Re: FTBFS with Linux 5.13/GCC 11
Thanks for the patch Sergio! Also for the well explained reason why those patches are needed. I did not build the package since it takes too long but I see it built fine in the PPA so far (I'd wait until the builds end in all architectures before uploading it to the archive). One thing that you need to fix before uploading is adding a reference to this LP bug in the changelog to close it automatically. After that, feel free to upload the package once it builds in all architectures. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to llvm-toolchain-11 in Ubuntu. https://bugs.launchpad.net/bugs/1939424 Title: FTBFS with Linux 5.13/GCC 11 Status in llvm-toolchain-11 package in Ubuntu: Confirmed Bug description: llvm-toolchain-11 is FTBFS'ing with Linux 5.13 because of: [ 8%] Building CXX object projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_posix.cpp.o cd /<>/build-llvm/projects/compiler-rt/lib/sanitizer_common && /usr/bin/g++-11 -DHAVE_RPC_XDR_H=0 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/projects/compiler-rt/lib/sanitizer_common -I/<>/compiler-rt/lib/sanitizer_common -I/<>/build-llvm/include -I/<>/llvm/include -I/<>/compiler-rt/lib/sanitizer_common/.. -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wno-comment -ffunction-sections -fdata-sections -Wall -std=c++14 -Wno-unused-parameter -O2 -DNDEBUG -g1 -m64 -fPIC -fno-builtin -fno-exceptions -fomit-frame-pointer -funwind-tables -fno-stack-protector -fvisibility=hidden -fno-lto -O3 -g -Wno-variadic-macros -Wno-non-virtual-dtor -fno-rtti -Wframe-larger-than=570 -std=c++14 -o CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_posix.cpp.o -c /<>/compiler-rt/lib/sanitizer_common/sanitizer_posix.cpp /<>/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.cpp:133:10: fatal error: linux/cyclades.h: No such file or directory 133 | #include | ^~ compilation terminated. make[5]: *** [projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/build.make:358: projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_platform_limits_posix.cpp.o] Error 1 make[5]: *** Waiting for unfinished jobs make -f projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommonCoverage.x86_64.dir/build.make projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommonCoverage.x86_64.dir/depend make[5]: Entering directory '/<>/build-llvm' This is happening because the Cyclades driver has been finally removed from Linux (after being orphaned 13 years ago): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/include/uapi/linux?h=v5.12=f76edd8f7ce06cdff2fe5b6b39a49644c684a161 LLVM includes cyclades.h when building libsanitizer, and therefore the FTBFS occurs. Upstream has fixed this by removing support for Cyclades from libsanitizer: https://github.com/llvm/llvm- project/commit/884040db086936107ec81656aa5b4c607235fb9a As for the GCC 11 failure, the problem is: [ 19%] Building CXX object tools/clang/utils/TableGen/CMakeFiles/obj.clang-tblgen.dir/ClangDiagnosticsEmitter.cpp.o cd /<>/build-llvm/tools/clang/stage2-bins/tools/clang/utils/TableGen && /<>/build-llvm/./bin/clang++ -DCLANG_VENDOR="\"Ubuntu \"" -D_GNU_SOURCE -D__STDC_CONSTANT_M ACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/utils/TableGen -I/<>/clang/utils/TableGen -I/< >/clang/include -I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/include -I/<>/build-llvm/tools/clang/stage2-bins/include -I/<>/llvm/include -fuse -ld=gold -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused -parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default -Wno-class-memaccess -Wno-noexcept-type -Wnon-vi rtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -ffunction-sections -fdata-sections -fno-common -Woverloaded-virtual -Wno-nested-anon-types -O2 -DNDEBUG -g1 -fno-exceptions -std=c ++14 -o CMakeFiles/obj.clang-tblgen.dir/ClangDiagnosticsEmitter.cpp.o -c /<>/clang/utils/TableGen/ClangDiagnosticsEmitter.cpp In file included from /<>/llvm/utils/benchmark/src/benchmark_register.cc:15:
[Kernel-packages] [Bug 1934548] Re: RISC-V: Illegal instruction
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1934548 Title: RISC-V: Illegal instruction Status in linux-riscv package in Ubuntu: Confirmed Status in linux-riscv-5.11 package in Ubuntu: Confirmed Bug description: When booting the Ubuntu Server image on the SiFive HiFive Unmatched I am getting the following error. The last known working version was 1012. The issue is being tracked on the SiFive forums at https://forums.sifive.com/t/u-boot-says-unhandled-exception-illegal-instruction/4898 ``` Starting kernel ... [0.00] Linux version 5.11.0-1014-generic (buildd@riscv64-qemu-lcy01-084) (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #14-Ubuntu SMP Wed Jun 30 17:56:50 UTC 2021 (Ubuntu 5.11.0-1014.14-generic 5.11.22) [0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020 [0.00] earlycon: sifive0 at MMIO 0x1001 (options '') [0.00] printk: bootconsole [sifive0] enabled [0.00] efi: UEFI not found. [0.00] Initial ramdisk at: 0x(ptrval) (183422976 bytes) [0.00] cma: Reserved 32 MiB at 0xfe00 [0.00] Zone ranges: [0.00] DMA32[mem 0x8020-0x] [0.00] Normal [mem 0x0001-0x00047fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x8020-0x00047fff] [0.00] Initmem setup node 0 [mem 0x8020-0x00047fff] [0.00] DMA32 zone: 512 pages in unavailable ranges [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=/dev/nvme0n1p1 ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16165452K/16775168K available (9854K kernel code, 5763K rwdata, 8192K rodata, 2519K init, 997K bss, 576948K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38893 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1014-generic #14-Ubuntu [0.00] epc: ffe0920e ra : ffe09384 sp : ffe001803d30 [0.00] gp : ffe001a14240 tp : ffe00180f440 t0 : ffe07fe38000 [0.00] t1 : ffe0019cd338 t2 : s0 : ffe001803d70 [0.00] s1 : a0 : ffe095aa a1 : 0001 [0.00] a2 : 0002 a3 : a4 : [0.00] a5 : a6 : 0004 a7 : 52464e43 [0.00] s2 : 0002 s3 : 0001 s4 : [0.00] s5 : s6 : s7 : [0.00] s8 : ffe001a170c0 s9 : 0001 s10: 0001 [0.00] s11: fffcc5d0 t3 : 0068 t4 : 000b [0.00] t5 : ffe0019cd3e0 t6 : ffe001803cd8 [0.00] status: 00020100 badaddr: 0513f187 cause: 0002 [0.00] ---[ end trace f67eb9af4d8d492b ]--- [0.00] Kernel panic - not syncing: Attempted to kill the idle task! [0.00] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]--- ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1934548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1939424] Re: FTBFS with Linux 5.13/GCC 11
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to llvm-toolchain-11 in Ubuntu. https://bugs.launchpad.net/bugs/1939424 Title: FTBFS with Linux 5.13/GCC 11 Status in llvm-toolchain-11 package in Ubuntu: Confirmed Bug description: llvm-toolchain-11 is FTBFS'ing with Linux 5.13 because of: [ 8%] Building CXX object projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_posix.cpp.o cd /<>/build-llvm/projects/compiler-rt/lib/sanitizer_common && /usr/bin/g++-11 -DHAVE_RPC_XDR_H=0 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/projects/compiler-rt/lib/sanitizer_common -I/<>/compiler-rt/lib/sanitizer_common -I/<>/build-llvm/include -I/<>/llvm/include -I/<>/compiler-rt/lib/sanitizer_common/.. -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wno-comment -ffunction-sections -fdata-sections -Wall -std=c++14 -Wno-unused-parameter -O2 -DNDEBUG -g1 -m64 -fPIC -fno-builtin -fno-exceptions -fomit-frame-pointer -funwind-tables -fno-stack-protector -fvisibility=hidden -fno-lto -O3 -g -Wno-variadic-macros -Wno-non-virtual-dtor -fno-rtti -Wframe-larger-than=570 -std=c++14 -o CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_posix.cpp.o -c /<>/compiler-rt/lib/sanitizer_common/sanitizer_posix.cpp /<>/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.cpp:133:10: fatal error: linux/cyclades.h: No such file or directory 133 | #include | ^~ compilation terminated. make[5]: *** [projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/build.make:358: projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_platform_limits_posix.cpp.o] Error 1 make[5]: *** Waiting for unfinished jobs make -f projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommonCoverage.x86_64.dir/build.make projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommonCoverage.x86_64.dir/depend make[5]: Entering directory '/<>/build-llvm' This is happening because the Cyclades driver has been finally removed from Linux (after being orphaned 13 years ago): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/include/uapi/linux?h=v5.12=f76edd8f7ce06cdff2fe5b6b39a49644c684a161 LLVM includes cyclades.h when building libsanitizer, and therefore the FTBFS occurs. Upstream has fixed this by removing support for Cyclades from libsanitizer: https://github.com/llvm/llvm- project/commit/884040db086936107ec81656aa5b4c607235fb9a As for the GCC 11 failure, the problem is: [ 19%] Building CXX object tools/clang/utils/TableGen/CMakeFiles/obj.clang-tblgen.dir/ClangDiagnosticsEmitter.cpp.o cd /<>/build-llvm/tools/clang/stage2-bins/tools/clang/utils/TableGen && /<>/build-llvm/./bin/clang++ -DCLANG_VENDOR="\"Ubuntu \"" -D_GNU_SOURCE -D__STDC_CONSTANT_M ACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/utils/TableGen -I/<>/clang/utils/TableGen -I/< >/clang/include -I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/include -I/<>/build-llvm/tools/clang/stage2-bins/include -I/<>/llvm/include -fuse -ld=gold -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused -parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default -Wno-class-memaccess -Wno-noexcept-type -Wnon-vi rtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -ffunction-sections -fdata-sections -fno-common -Woverloaded-virtual -Wno-nested-anon-types -O2 -DNDEBUG -g1 -fno-exceptions -std=c ++14 -o CMakeFiles/obj.clang-tblgen.dir/ClangDiagnosticsEmitter.cpp.o -c /<>/clang/utils/TableGen/ClangDiagnosticsEmitter.cpp In file included from /<>/llvm/utils/benchmark/src/benchmark_register.cc:15: /<>/llvm/utils/benchmark/src/benchmark_register.h:17:30: error: no member named 'numeric_limits' in namespace 'std' static const T kmax = std::numeric_limits::max(); ~^ /<>/llvm/utils/benchmark/src/benchmark_register.h:17:45: error: 'T' does not refer to a value static const T kmax = std::numeric_limits::max(); ^ /<>/llvm/utils/benchmark/src/benchmark_register.h:8:20: note: declared here template
[Kernel-packages] [Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740
Thanks for the suggestion. However, this does not make any difference. I ran also "watch -n1 cat /proc/interrupts", "acpi_listen" and "sudo showkey -s" and no reaction to brightness hotkeys whereas volume hotkeys work and that also shows up when running these commands. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872311 Title: Brightness hotkeys not working on Lenovo S740 Status in linux package in Ubuntu: Incomplete Bug description: Brightness hotkeys (Fn + F11 for decrease and Fn + F12 for increase) do not work on Ubuntu 20.04 and Lenovo S740 laptop. The brightness hotkeys did not work on 19.10 either. I followed the guide here: https://wiki.ubuntu.com/Hotkeys/Troubleshooting In "Step-by-step Troubleshooting", none of the steps (1-7) did produce any reaction to brightness change key combinations. However, I am able to change the laptop screen brightness through the brightness applet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: elias 1447 F pulseaudio /dev/snd/controlC0: elias 1447 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 16:12:01 2020 InstallationDate: Installed on 2019-11-19 (144 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81RS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (7 days ago) dmi.bios.date: 03/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BYCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S740-14IIL dmi.modalias: dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL: dmi.product.family: Yoga S740-14IIL dmi.product.name: 81RS dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL dmi.product.version: Lenovo Yoga S740-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+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 1939301] Re: REGRESSION: shiftfs lets sendfile fail with EINVAL
I've verified on my end that with the patch from https://paste.ubuntu.com/p/TPsjfCpnD5/ the failing sendfile syscall on top of shiftfs is gone. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939301 Title: REGRESSION: shiftfs lets sendfile fail with EINVAL Status in linux package in Ubuntu: New Status in linux-meta-hwe-5.11 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-meta-hwe-5.11 source package in Focal: Confirmed Status in linux source package in Hirsute: In Progress Status in linux-meta-hwe-5.11 source package in Hirsute: Invalid Status in linux source package in Impish: New Status in linux-meta-hwe-5.11 source package in Impish: Invalid Bug description: With the 5.11 HWE kernel landing for Ubuntu 20.04 we noticed that LXC tools we're using in bionic containers as part of Anbox Cloud start to fail when executed on the 5.11 kernel. A simple reproducer looks like this: 1. Run Ubuntu 20.04 with HWE kernel (linux-generic-hwe-20.04, 5.11.0-25-generic #27~20.04.1-Ubuntu) 2. Install LXD and enable shiftfs $ snap install lxd $ snap set lxd shiftfs.enable true $ snap restart --reload lxd 3. Launch bionic container and run `lxc-info` $ lxc launch ubuntu:b c0 $ lxc shell c0 c0$ apt update c0$ apt install -y lxc-utils root@c1:~# apt show lxc-utils | grep Version Version: 3.0.3-0ubuntu1~18.04.1 c0$ mkdir -p containers/test c0$ touch containers/test/config c0$ lxc-info -P containers -n test Failed to load config for test Failure to retrieve information on containers:test Looking into the failing `lxc-info` call with strace reveals: ... memfd_create(".lxc_config_file", MFD_CLOEXEC) = 4 openat(AT_FDCWD, "containers/test/config", O_RDONLY|O_CLOEXEC) = 5 sendfile(4, 5, NULL, 2147479552)= -1 EINVAL (Invalid argument ... LXC >= 4.0.0 doesn't use sendfile anymore and with that isn't affected. Any other tool using sendfile however is affected and will fail. Bionic is affected as the 3.0.3 version of LXC it includes still uses sendfile. Disabling shiftfs makes things work again and can be considered as a workaround to a certain degree, but not be applicable in all cases. Further analysis with Christian (cbrauner) from the LXD team this morning showed that shiftfs is missing an implementation for the now required slice_read handler in the file_operations structure. So whenever shiftfs is being used, all calls to sendfile will fail because of the missing implementation. The generic handler for this got removed in the following upstream change: https://lore.kernel.org/lkml/20200626075836.1998185-10-...@lst.de/ Christian implemented a quick fix: https://paste.ubuntu.com/p/TPsjfCpnD5/ As of today I don't know of any customer of Anbox Cloud who is affected by this as most of them run with one of our cloud kernels. However as soon as 5.11 rolls out to the cloud kernels, we will hit production systems and cause them to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939301/+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 1939450] Re: Hirsute update: upstream stable patchset 2021-08-10
** Description changed: - - SRU Justification - - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: - -upstream stable patchset 2021-08-10 -from git://git.kernel.org/ + SRU Justification + + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: + + upstream stable patchset 2021-08-10 + + Ported from the following upstream stable releases: + v5.10.51, v5.12.18 + + from git://git.kernel.org/ + + drm/mxsfb: Don't select DRM_KMS_FB_HELPER + drm/zte: Don't select DRM_KMS_FB_HELPER + drm/ast: Fixed CVE for DP501 + drm/amd/display: fix HDCP reset sequence on reinitialize + drm/amd/amdgpu/sriov disable all ip hw status by default + drm/vc4: fix argument ordering in vc4_crtc_get_margins() + drm/bridge: nwl-dsi: Force a full modeset when crtc_state->active is changed to be true + net: pch_gbe: Use proper accessors to BE data in pch_ptp_match() + drm/amd/display: fix use_max_lb flag for 420 pixel formats + clk: renesas: rcar-usb2-clock-sel: Fix error handling in .probe() + hugetlb: clear huge pte during flush function on mips platform + atm: iphase: fix possible use-after-free in ia_module_exit() + mISDN: fix possible use-after-free in HFC_cleanup() + atm: nicstar: Fix possible use-after-free in nicstar_cleanup() + net: Treat __napi_schedule_irqoff() as __napi_schedule() on PREEMPT_RT + drm/mediatek: Fix PM reference leak in mtk_crtc_ddp_hw_init() + net: mdio: ipq8064: add regmap config to disable REGCACHE + drm/bridge: lt9611: Add missing MODULE_DEVICE_TABLE + reiserfs: add check for invalid 1st journal block + drm/virtio: Fix double free on probe failure + net: mdio: provide shim implementation of devm_of_mdiobus_register + net/sched: cls_api: increase max_reclassify_loop + pinctrl: equilibrium: Add missing MODULE_DEVICE_TABLE + drm/scheduler: Fix hang when sched_entity released + drm/sched: Avoid data corruptions + udf: Fix NULL pointer dereference in udf_symlink function + drm/vc4: Fix clock source for VEC PixelValve on BCM2711 + drm/vc4: hdmi: Fix PM reference leak in vc4_hdmi_encoder_pre_crtc_co() + e100: handle eeprom as little endian + igb: handle vlan types with checker enabled + igb: fix assignment on big endian machines + drm/bridge: cdns: Fix PM reference leak in cdns_dsi_transfer() + clk: renesas: r8a77995: Add ZA2 clock + net/mlx5e: IPsec/rep_tc: Fix rep_tc_update_skb drops IPsec packet + net/mlx5: Fix lag port remapping logic + drm: rockchip: add missing registers for RK3188 + drm: rockchip: add missing registers for RK3066 + net: stmmac: the XPCS obscures a potential "PHY not found" error + RDMA/rtrs: Change MAX_SESS_QUEUE_DEPTH + clk: tegra: Fix refcounting of gate clocks + clk: tegra: Ensure that PLLU configuration is applied properly + drm: bridge: cdns-mhdp8546: Fix PM reference leak in + virtio-net: Add validation for used length + ipv6: use prandom_u32() for ID generation + MIPS: cpu-probe: Fix FPU detection on Ingenic JZ4760(B) + MIPS: ingenic: Select CPU_SUPPORTS_CPUFREQ && MIPS_EXTERNAL_TIMER + drm/amd/display: Avoid HDCP over-read and corruption + drm/amdgpu: remove unsafe optimization to drop preamble ib + net: tcp better handling of reordering then loss cases + RDMA/cxgb4: Fix missing error code in create_qp() + dm space maps: don't reset space map allocation cursor when committing + dm writecache: don't split bios when overwriting contiguous cache content + dm: Fix dm_accept_partial_bio() relative to zone management commands + net: bridge: mrp: Update ring transitions. + pinctrl: mcp23s08: fix race condition in irq handler + ice: set the value of global config lock timeout longer + ice: fix clang warning regarding deadcode.DeadStores + virtio_net: Remove BUG() to avoid machine dead + net: mscc: ocelot: check return value after calling platform_get_resource() + net: bcmgenet: check return value after calling platform_get_resource() + net: mvpp2: check return value after calling platform_get_resource() + net: micrel: check return value after calling platform_get_resource() + net: moxa: Use devm_platform_get_and_ioremap_resource() + drm/amd/display: Fix DCN 3.01 DSCCLK validation + drm/amd/display: Update scaling settings on modeset +
[Kernel-packages] [Bug 1939450] [NEW] Hirsute update: upstream stable patchset 2021-08-10
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-08-10 Ported from the following upstream stable releases: v5.10.51, v5.12.18 from git://git.kernel.org/ drm/mxsfb: Don't select DRM_KMS_FB_HELPER drm/zte: Don't select DRM_KMS_FB_HELPER drm/ast: Fixed CVE for DP501 drm/amd/display: fix HDCP reset sequence on reinitialize drm/amd/amdgpu/sriov disable all ip hw status by default drm/vc4: fix argument ordering in vc4_crtc_get_margins() drm/bridge: nwl-dsi: Force a full modeset when crtc_state->active is changed to be true net: pch_gbe: Use proper accessors to BE data in pch_ptp_match() drm/amd/display: fix use_max_lb flag for 420 pixel formats clk: renesas: rcar-usb2-clock-sel: Fix error handling in .probe() hugetlb: clear huge pte during flush function on mips platform atm: iphase: fix possible use-after-free in ia_module_exit() mISDN: fix possible use-after-free in HFC_cleanup() atm: nicstar: Fix possible use-after-free in nicstar_cleanup() net: Treat __napi_schedule_irqoff() as __napi_schedule() on PREEMPT_RT drm/mediatek: Fix PM reference leak in mtk_crtc_ddp_hw_init() net: mdio: ipq8064: add regmap config to disable REGCACHE drm/bridge: lt9611: Add missing MODULE_DEVICE_TABLE reiserfs: add check for invalid 1st journal block drm/virtio: Fix double free on probe failure net: mdio: provide shim implementation of devm_of_mdiobus_register net/sched: cls_api: increase max_reclassify_loop pinctrl: equilibrium: Add missing MODULE_DEVICE_TABLE drm/scheduler: Fix hang when sched_entity released drm/sched: Avoid data corruptions udf: Fix NULL pointer dereference in udf_symlink function drm/vc4: Fix clock source for VEC PixelValve on BCM2711 drm/vc4: hdmi: Fix PM reference leak in vc4_hdmi_encoder_pre_crtc_co() e100: handle eeprom as little endian igb: handle vlan types with checker enabled igb: fix assignment on big endian machines drm/bridge: cdns: Fix PM reference leak in cdns_dsi_transfer() clk: renesas: r8a77995: Add ZA2 clock net/mlx5e: IPsec/rep_tc: Fix rep_tc_update_skb drops IPsec packet net/mlx5: Fix lag port remapping logic drm: rockchip: add missing registers for RK3188 drm: rockchip: add missing registers for RK3066 net: stmmac: the XPCS obscures a potential "PHY not found" error RDMA/rtrs: Change MAX_SESS_QUEUE_DEPTH clk: tegra: Fix refcounting of gate clocks clk: tegra: Ensure that PLLU configuration is applied properly drm: bridge: cdns-mhdp8546: Fix PM reference leak in virtio-net: Add validation for used length ipv6: use prandom_u32() for ID generation MIPS: cpu-probe: Fix FPU detection on Ingenic JZ4760(B) MIPS: ingenic: Select CPU_SUPPORTS_CPUFREQ && MIPS_EXTERNAL_TIMER drm/amd/display: Avoid HDCP over-read and corruption drm/amdgpu: remove unsafe optimization to drop preamble ib net: tcp better handling of reordering then loss cases RDMA/cxgb4: Fix missing error code in create_qp() dm space maps: don't reset space map allocation cursor when committing dm writecache: don't split bios when overwriting contiguous cache content dm: Fix dm_accept_partial_bio() relative to zone management commands net: bridge: mrp: Update ring transitions. pinctrl: mcp23s08: fix race condition in irq handler ice: set the value of global config lock timeout longer ice: fix clang warning regarding deadcode.DeadStores virtio_net: Remove BUG() to avoid machine dead net: mscc: ocelot: check return value after calling platform_get_resource() net: bcmgenet: check return value after calling platform_get_resource() net: mvpp2: check return value after calling platform_get_resource() net: micrel: check return value after calling platform_get_resource() net: moxa: Use devm_platform_get_and_ioremap_resource() drm/amd/display: Fix DCN 3.01 DSCCLK validation drm/amd/display: Update scaling settings on modeset drm/amd/display: Release MST resources on switch from MST to SST drm/amd/display: Set DISPCLK_MAX_ERRDET_CYCLES to 7 drm/amd/display: Fix off-by-one error in DML net: phy: realtek: add delay to fix RXC generation issue selftests: Clean forgotten resources as part of cleanup() net: sgi: ioc3-eth: check return value after calling platform_get_resource() drm/amdkfd: use allowed domain for vmbo validation fjes: check return value after calling platform_get_resource() selinux: use __GFP_NOWARN with GFP_NOWAIT in the AVC r8169: avoid link-up interrupt issue on RTL8106e if user enables ASPM drm/amd/display: Verify Gamma & Degamma LUT sizes in amdgpu_dm_atomic_check xfrm: Fix error reporting in xfrm_state_construct. dm writecache:
[Kernel-packages] [Bug 1934548] Re: RISC-V: Illegal instruction
Hey, @xnox. Can you try the attached patch and see if that works out? It's possible that other functions need to be marked notrace. Cascardo. ** Patch added: "fix for hirsute:linux-riscv" https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.11/+bug/1934548/+attachment/5517152/+files/0001-UBUNTU-SAUCE-RISC-V-prevent-sbi_send_cpumask_ipi-rac.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1934548 Title: RISC-V: Illegal instruction Status in linux-riscv package in Ubuntu: Confirmed Status in linux-riscv-5.11 package in Ubuntu: Confirmed Bug description: When booting the Ubuntu Server image on the SiFive HiFive Unmatched I am getting the following error. The last known working version was 1012. The issue is being tracked on the SiFive forums at https://forums.sifive.com/t/u-boot-says-unhandled-exception-illegal-instruction/4898 ``` Starting kernel ... [0.00] Linux version 5.11.0-1014-generic (buildd@riscv64-qemu-lcy01-084) (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #14-Ubuntu SMP Wed Jun 30 17:56:50 UTC 2021 (Ubuntu 5.11.0-1014.14-generic 5.11.22) [0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020 [0.00] earlycon: sifive0 at MMIO 0x1001 (options '') [0.00] printk: bootconsole [sifive0] enabled [0.00] efi: UEFI not found. [0.00] Initial ramdisk at: 0x(ptrval) (183422976 bytes) [0.00] cma: Reserved 32 MiB at 0xfe00 [0.00] Zone ranges: [0.00] DMA32[mem 0x8020-0x] [0.00] Normal [mem 0x0001-0x00047fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x8020-0x00047fff] [0.00] Initmem setup node 0 [mem 0x8020-0x00047fff] [0.00] DMA32 zone: 512 pages in unavailable ranges [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=/dev/nvme0n1p1 ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16165452K/16775168K available (9854K kernel code, 5763K rwdata, 8192K rodata, 2519K init, 997K bss, 576948K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38893 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1014-generic #14-Ubuntu [0.00] epc: ffe0920e ra : ffe09384 sp : ffe001803d30 [0.00] gp : ffe001a14240 tp : ffe00180f440 t0 : ffe07fe38000 [0.00] t1 : ffe0019cd338 t2 : s0 : ffe001803d70 [0.00] s1 : a0 : ffe095aa a1 : 0001 [0.00] a2 : 0002 a3 : a4 : [0.00] a5 : a6 : 0004 a7 : 52464e43 [0.00] s2 : 0002 s3 : 0001 s4 : [0.00] s5 : s6 : s7 : [0.00] s8 : ffe001a170c0 s9 : 0001 s10: 0001 [0.00] s11: fffcc5d0 t3 : 0068 t4 : 000b [0.00] t5 : ffe0019cd3e0 t6 : ffe001803cd8 [0.00] status: 00020100 badaddr: 0513f187 cause: 0002 [0.00] ---[ end trace f67eb9af4d8d492b ]--- [0.00] Kernel panic - not syncing: Attempted to kill the idle task! [0.00] ---[ end Kernel panic - not
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
** Changed in: linux (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933980 Title: NVIDIA CVE-2021-{1093|1094|1094} Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: In Progress Status in nvidia-settings package in Ubuntu: Fix Released Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-460 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in linux source package in Bionic: Triaged Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: Fix Released Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-460 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in linux source package in Focal: Triaged Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: In Progress Status in nvidia-settings source package in Focal: Fix Released Status in fabric-manager-450 source package in Groovy: Fix Released Status in fabric-manager-460 source package in Groovy: Fix Released Status in libnvidia-nscq-450 source package in Groovy: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux-restricted-modules source package in Groovy: Won't Fix Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Won't Fix Status in nvidia-settings source package in Groovy: Fix Released Status in fabric-manager-450 source package in Hirsute: Fix Released Status in fabric-manager-460 source package in Hirsute: Fix Released Status in libnvidia-nscq-450 source package in Hirsute: Fix Released Status in linux source package in Hirsute: Triaged Status in linux-restricted-modules source package in Hirsute: Triaged Status in nvidia-graphics-drivers-390 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: In Progress Status in nvidia-settings source package in Hirsute: Fix Released Bug description: As per the subject, the update includes fixes for the following CVEs: CVE-2021-1093 CVE-2021-1094 CVE-2021-1095 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1933980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
crash continued. Now trying the /etc/modprobe.d/rtw88_pci.conf method -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927808 Title: rtw88_8821ce causes freeze Status in linux package in Ubuntu: Confirmed Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+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 1934548] Re: RISC-V: Illegal instruction
The alternative theory here is that this is always breaking at sbi_send_cpumask_ipi, which is being patched at: ffe091e2: f097auipc ra,0xf ffe091e6: dfe080e7jalr-514(ra) # ffe07fe0 I even found ffe091e2 as one of the addresses being patched (look at __start_mcount_loc). And it happens that the patching code will end up calling flush_icache_range (which is really flush_icache_all). That, in turn, will end up doing some form of IPI. So, possibly there is a race involved here, where the IPI code is being executed after it is patched, but before icache is flushed. It's hard to think that this segment lies inside a cache boundary, but there is certainly something else necessary for the sync here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1934548 Title: RISC-V: Illegal instruction Status in linux-riscv package in Ubuntu: Confirmed Status in linux-riscv-5.11 package in Ubuntu: Confirmed Bug description: When booting the Ubuntu Server image on the SiFive HiFive Unmatched I am getting the following error. The last known working version was 1012. The issue is being tracked on the SiFive forums at https://forums.sifive.com/t/u-boot-says-unhandled-exception-illegal-instruction/4898 ``` Starting kernel ... [0.00] Linux version 5.11.0-1014-generic (buildd@riscv64-qemu-lcy01-084) (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #14-Ubuntu SMP Wed Jun 30 17:56:50 UTC 2021 (Ubuntu 5.11.0-1014.14-generic 5.11.22) [0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020 [0.00] earlycon: sifive0 at MMIO 0x1001 (options '') [0.00] printk: bootconsole [sifive0] enabled [0.00] efi: UEFI not found. [0.00] Initial ramdisk at: 0x(ptrval) (183422976 bytes) [0.00] cma: Reserved 32 MiB at 0xfe00 [0.00] Zone ranges: [0.00] DMA32[mem 0x8020-0x] [0.00] Normal [mem 0x0001-0x00047fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x8020-0x00047fff] [0.00] Initmem setup node 0 [mem 0x8020-0x00047fff] [0.00] DMA32 zone: 512 pages in unavailable ranges [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=/dev/nvme0n1p1 ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16165452K/16775168K available (9854K kernel code, 5763K rwdata, 8192K rodata, 2519K init, 997K bss, 576948K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38893 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1014-generic #14-Ubuntu [0.00] epc: ffe0920e ra : ffe09384 sp : ffe001803d30 [0.00] gp : ffe001a14240 tp : ffe00180f440 t0 : ffe07fe38000 [0.00] t1 : ffe0019cd338 t2 : s0 : ffe001803d70 [0.00] s1 : a0 : ffe095aa a1 : 0001 [0.00] a2 : 0002 a3 : a4 : [0.00] a5 : a6 : 0004 a7 : 52464e43 [0.00] s2 : 0002 s3 : 0001 s4 : [0.00] s5 : s6 : s7 : [0.00] s8 : ffe001a170c0 s9 : 0001
[Kernel-packages] [Bug 1936009] Re: [SRU] The internal mic of Dell Precision 5750 can't record sound
Comments #9 and #10 don't indicate which versions of the kernel were tested while the description specifically mentions testing with "the old and new kernel". Was this tested with both kernels? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1936009 Title: [SRU] The internal mic of Dell Precision 5750 can't record sound Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Released Bug description: [Impact] After upgrade the linux kernel, the mixer names of rt715 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't record sound from internal mic since the internal mic is routed to the codec rt715. [Fix] Backport 3 upstream commits, after applying these 3 commits, the ucm conf file dosn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec. [Test] run 'alsactl init 1' on the precision 5750 with old and new kernel, there is no error logs, use the internal mic to record sound, it could record successfully. [Where problems will occur] The change only affects the rt715 codec, so far, that codec only connects to the internal mic on Dell soundwire audio machines, so it could introduce regression on the internal mic like users can't record sound via internal mic anymore on the Dell soundwire audio machines. But this possibility is very low since we already tested these 3 commits on different Dell soundwire audio machines (latitude and precision). We tested it with old kernel and new kernel, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936009/+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 1934548] Re: RISC-V: Illegal instruction
Looking at the crashing address (by doing objdump on the vmlinux from the ddeb), it lands on the middle of an instruction. ffe09204: 99c080e7jalr-1636(ra) # ffe06b9c ffe09208: 0180e797auipc a5,0x180e ffe0920c: f187b783ld a5,-232(a5) # ffe001817120 <__sbi_send_ipi> ffe09210: fd040513addia0,s0,-48 ffe09214: 9782jalra5 ffe09216: fd843703ld a4,-40(s0) Perhaps, the patching done by ftrace is causing this. There is afc76b8b80112189b6f11e67e19cf58301944814 ("riscv: Using PATCHABLE_FUNCTION_ENTRY instead of MCOUNT"), which doesn't refer to any bug that is fixed, but changes the way patches are applied. So, perhaps, this would help fix the issue. Possibly worth the try until this is properly debugged. I can't test it, otherwise, so @xnox, would you be able to try this upstream commit? Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1934548 Title: RISC-V: Illegal instruction Status in linux-riscv package in Ubuntu: Confirmed Status in linux-riscv-5.11 package in Ubuntu: Confirmed Bug description: When booting the Ubuntu Server image on the SiFive HiFive Unmatched I am getting the following error. The last known working version was 1012. The issue is being tracked on the SiFive forums at https://forums.sifive.com/t/u-boot-says-unhandled-exception-illegal-instruction/4898 ``` Starting kernel ... [0.00] Linux version 5.11.0-1014-generic (buildd@riscv64-qemu-lcy01-084) (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #14-Ubuntu SMP Wed Jun 30 17:56:50 UTC 2021 (Ubuntu 5.11.0-1014.14-generic 5.11.22) [0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020 [0.00] earlycon: sifive0 at MMIO 0x1001 (options '') [0.00] printk: bootconsole [sifive0] enabled [0.00] efi: UEFI not found. [0.00] Initial ramdisk at: 0x(ptrval) (183422976 bytes) [0.00] cma: Reserved 32 MiB at 0xfe00 [0.00] Zone ranges: [0.00] DMA32[mem 0x8020-0x] [0.00] Normal [mem 0x0001-0x00047fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x8020-0x00047fff] [0.00] Initmem setup node 0 [mem 0x8020-0x00047fff] [0.00] DMA32 zone: 512 pages in unavailable ranges [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=/dev/nvme0n1p1 ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16165452K/16775168K available (9854K kernel code, 5763K rwdata, 8192K rodata, 2519K init, 997K bss, 576948K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38893 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1014-generic #14-Ubuntu [0.00] epc: ffe0920e ra : ffe09384 sp : ffe001803d30 [0.00] gp : ffe001a14240 tp : ffe00180f440 t0 : ffe07fe38000 [0.00] t1 : ffe0019cd338 t2 : s0 : ffe001803d70 [0.00] s1 : a0 : ffe095aa a1 : 0001 [0.00] a2 : 0002 a3 : a4 : [0.00] a5 : a6 : 0004 a7 : 52464e43 [
[Kernel-packages] [Bug 1939442] [NEW] Focal update: v5.4.135 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.135 upstream stable release from git://git.kernel.org/ ARM: dts: gemini: rename mdio to the right name ARM: dts: gemini: add device_type on pci ARM: dts: rockchip: fix pinctrl sleep nodename for rk3036-kylin and rk3288 arm64: dts: rockchip: fix pinctrl sleep nodename for rk3399.dtsi ARM: dts: rockchip: Fix the timer clocks order ARM: dts: rockchip: Fix IOMMU nodes properties on rk322x ARM: dts: rockchip: Fix power-controller node names for rk3066a ARM: dts: rockchip: Fix power-controller node names for rk3188 ARM: dts: rockchip: Fix power-controller node names for rk3288 arm64: dts: rockchip: Fix power-controller node names for px30 arm64: dts: rockchip: Fix power-controller node names for rk3328 reset: ti-syscon: fix to_ti_syscon_reset_data macro ARM: brcmstb: dts: fix NAND nodes names ARM: Cygnus: dts: fix NAND nodes names ARM: NSP: dts: fix NAND nodes names ARM: dts: BCM63xx: Fix NAND nodes names ARM: dts: Hurricane 2: Fix NAND nodes names ARM: dts: imx6: phyFLEX: Fix UART hardware flow control ARM: imx: pm-imx5: Fix references to imx5_cpu_suspend_info rtc: mxc_v2: add missing MODULE_DEVICE_TABLE kbuild: sink stdout from cmd for silent build ARM: dts: am57xx-cl-som-am57x: fix ti,no-reset-on-init flag for gpios ARM: dts: am437x-gp-evm: fix ti,no-reset-on-init flag for gpios ARM: dts: stm32: fix gpio-keys node on STM32 MCU boards ARM: dts: stm32: fix RCC node name on stm32f429 MCU ARM: dts: stm32: fix timer nodes on STM32 MCU to prevent warnings arm64: dts: juno: Update SCPI nodes as per the YAML schema ARM: dts: rockchip: fix supply properties in io-domains nodes ARM: dts: stm32: fix i2c node name on stm32f746 to prevent warnings ARM: dts: stm32: move stmmac axi config in ethernet node on stm32mp15 soc/tegra: fuse: Fix Tegra234-only builds firmware: tegra: bpmp: Fix Tegra234-only builds arm64: dts: ls208xa: remove bus-num from dspi node arm64: dts: imx8mq: assign PCIe clocks thermal/core: Correct function name thermal_zone_device_unregister() kbuild: mkcompile_h: consider timestamp if KBUILD_BUILD_TIMESTAMP is set rtc: max77686: Do not enforce (incorrect) interrupt trigger type scsi: aic7xxx: Fix unintentional sign extension issue on left shift of u8 scsi: libsas: Add LUN number check in .slave_alloc callback scsi: libfc: Fix array index out of bound exception scsi: qedf: Add check to synchronize abort and flush sched/fair: Fix CFS bandwidth hrtimer expiry type s390: introduce proper type handling call_on_stack() macro cifs: prevent NULL deref in cifs_compose_mount_options() arm64: dts: armada-3720-turris-mox: add firmware node firmware: turris-mox-rwtm: add marvell,armada-3700-rwtm-firmware compatible string arm64: dts: marvell: armada-37xx: move firmware node to generic dtsi file f2fs: Show casefolding support only when supported usb: cdns3: Enable TDL_CHK only for OUT ep Revert "UBUNTU: SAUCE: Revert "mm: memcg/slab: fix memory leak at non-root kmem_cache destroy"" mm: slab: fix kmem_cache_create failed when sysfs node not destroyed dm writecache: return the exact table values that were set net: dsa: mv88e6xxx: enable .port_set_policy() on Topaz net: dsa: mv88e6xxx: enable .rmu_disable() on Topaz net: ipv6: fix return value of ip6_skb_dst_mtu netfilter: ctnetlink: suspicious RCU usage in ctnetlink_dump_helpinfo net/sched: act_ct: fix err check for nf_conntrack_confirm net: bridge: sync fdb to new unicast-filtering ports net: bcmgenet: Ensure all TX/RX queues DMAs are disabled net: ip_tunnel: fix mtu calculation for ETHER tunnel devices net: moxa: fix UAF in moxart_mac_probe net: qcom/emac: fix UAF in emac_remove net: ti: fix UAF in tlan_remove_one net: send SYNACK packet with accepted fwmark net: validate lwtstate->data before returning from skb_tunnel_info() net: fddi: fix UAF in fza_probe dma-buf/sync_file: Don't leak fences on merge failure tcp: annotate data races around tp->mtu_info ipv6: tcp: drop silly ICMPv6 packet too big messages bpftool: Properly close va_list 'ap' by va_end() on error perf test bpf: Free obj_buf udp: annotate data races around unix_sk(sk)->gso_size Linux 5.4.135 UBUNTU: upstream stable to v5.4.135 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal)
[Kernel-packages] [Bug 1938626] Re: PPS API broken
According to linux/drivers/pps/clients/Kconfig config PPS_CLIENT_LDISC tristate "PPS line discipline" depends on TTY help If you say yes here you get support for a PPS source connected with the CD (Carrier Detect) pin of your serial port. If this is true, CTS needs to be added for modern devices. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938626 Title: PPS API broken Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: The kernel PPS API appears to be broken. I have a serial GPS with PPS attached to /dev/ttyS4. If I use gpsd to create /dev/pps0, gpsd fails to see PPS data. If I disable gpsd and create /dev/pps0 with ldattach, any app or tool run against ttyS4 works fine and does see the CTS transitions every second, i.e. gpsmon and ppscheck. Anything run against pps0 fails, i.e. ppstest, ppswatch. ntpd gets data from ttyS4 but not pps0. There are some issues with stock apparmor with gpsd and ntpd, but I have solved those. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-80-generic 5.4.0-80.90 ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 Uname: Linux 5.4.0-80-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jimp 6811 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Sat Jul 31 16:41:32 2021 HibernationDevice: RESUME=UUID=90289c8f-5a00-46c4-8f1f-79dd26128f39 InstallationDate: Installed on 2016-08-05 (1820 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=389dcb0d-84f2-4340-ad6c-e4f1dbe55b67 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-09 (264 days ago) dmi.bios.date: 11/26/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: TYG4110H.86A.0036.2009.1126.2047 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41TY dmi.board.vendor: Intel Corporation dmi.board.version: AAE47335-302 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTYG4110H.86A.0036.2009.1126.2047:bd11/26/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41TY:rvrAAE47335-302:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938626/+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 1939440] Re: Focal update: v5.4.134 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.134 upstream stable release + from git://git.kernel.org/ -v5.4.134 upstream stable release -from git://git.kernel.org/ + KVM: mmio: Fix use-after-free Read in kvm_vm_ioctl_unregister_coalesced_mmio + KVM: x86: Use guest MAXPHYADDR from CPUID.0x8000_0008 iff TDP is enabled + KVM: X86: Disable hardware breakpoints unconditionally before kvm_x86->run() + scsi: core: Fix bad pointer dereference when ehandler kthread is invalid + tracing: Do not reference char * as a string in histograms + cgroup: verify that source is a string + fbmem: Do not delete the mode that is still in use + net: moxa: Use devm_platform_get_and_ioremap_resource() + dmaengine: fsl-qdma: check dma_set_mask return value + srcu: Fix broken node geometry after early ssp init + tty: serial: fsl_lpuart: fix the potential risk of division or modulo by zero + misc/libmasm/module: Fix two use after free in ibmasm_init_one + misc: alcor_pci: fix null-ptr-deref when there is no PCI bridge + iio: gyro: fxa21002c: Balance runtime pm + use pm_runtime_resume_and_get(). + iio: magn: bmc150: Balance runtime pm + use pm_runtime_resume_and_get() + ALSA: usx2y: Don't call free_pages_exact() with NULL address + Revert "ALSA: bebob/oxfw: fix Kconfig entry for Mackie d.2 Pro" + w1: ds2438: fixing bug that would always get page0 + scsi: hisi_sas: Propagate errors in interrupt_init_v1_hw() + scsi: lpfc: Fix "Unexpected timeout" error in direct attach topology + scsi: lpfc: Fix crash when lpfc_sli4_hba_setup() fails to initialize the SGLs + scsi: core: Cap scsi_host cmd_per_lun at can_queue + ALSA: ac97: fix PM reference leak in ac97_bus_remove() + tty: serial: 8250: serial_cs: Fix a memory leak in error handling path + scsi: scsi_dh_alua: Check for negative result value + fs/jfs: Fix missing error code in lmLogInit() + scsi: megaraid_sas: Fix resource leak in case of probe failure + scsi: megaraid_sas: Early detection of VD deletion through RaidMap update + scsi: megaraid_sas: Handle missing interrupts while re-enabling IRQs + scsi: iscsi: Add iscsi_cls_conn refcount helpers + scsi: iscsi: Fix conn use after free during resets + scsi: iscsi: Fix shost->max_id use + scsi: qedi: Fix null ref during abort handling + mfd: da9052/stmpe: Add and modify MODULE_DEVICE_TABLE + mfd: cpcap: Fix cpcap dmamask not set warnings + ASoC: img: Fix PM reference leak in img_i2s_in_probe() + serial: tty: uartlite: fix console setup + s390/sclp_vt220: fix console name to match device + ALSA: sb: Fix potential double-free of CSP mixer elements + powerpc/ps3: Add dma_mask to ps3_dma_region + iommu/arm-smmu: Fix arm_smmu_device refcount leak when arm_smmu_rpm_get fails + iommu/arm-smmu: Fix arm_smmu_device refcount leak in address translation + gpio: zynq: Check return value of pm_runtime_get_sync + ALSA: ppc: fix error return code in snd_pmac_probe() + selftests/powerpc: Fix "no_handler" EBB selftest + gpio: pca953x: Add support for the On Semi pca9655 + ASoC: soc-core: Fix the error return code in snd_soc_of_parse_audio_routing() + s390/processor: always inline stap() and __load_psw_mask() + s390/ipl_parm: fix program check new psw handling + s390/mem_detect: fix diag260() program check new psw handling + s390/mem_detect: fix tprot() program check new psw handling + Input: hideep - fix the uninitialized use in hideep_nvm_unlock() + ALSA: bebob: add support for ToneWeal FW66 + ALSA: usb-audio: scarlett2: Fix 18i8 Gen 2 PCM Input count + ALSA: usb-audio: scarlett2: Fix data_mutex lock + ALSA: usb-audio: scarlett2: Fix scarlett2_*_ctl_put() return values + usb: gadget: f_hid: fix endianness issue with descriptors + usb: gadget: hid: fix error return code in hid_bind() + powerpc/boot: Fixup device-tree on little endian + ASoC: Intel: kbl_da7219_max98357a: shrink platform_id below 20 characters + backlight: lm3630a: Fix return code of .update_status() callback + ALSA: hda: Add IRQ check for platform_get_irq() + ALSA: usb-audio: scarlett2: Fix 6i6 Gen 2 line out descriptions + staging: rtl8723bs: fix macro value
[Kernel-packages] [Bug 1939440] [NEW] Focal update: v5.4.134 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.134 upstream stable release from git://git.kernel.org/ KVM: mmio: Fix use-after-free Read in kvm_vm_ioctl_unregister_coalesced_mmio KVM: x86: Use guest MAXPHYADDR from CPUID.0x8000_0008 iff TDP is enabled KVM: X86: Disable hardware breakpoints unconditionally before kvm_x86->run() scsi: core: Fix bad pointer dereference when ehandler kthread is invalid tracing: Do not reference char * as a string in histograms cgroup: verify that source is a string fbmem: Do not delete the mode that is still in use net: moxa: Use devm_platform_get_and_ioremap_resource() dmaengine: fsl-qdma: check dma_set_mask return value srcu: Fix broken node geometry after early ssp init tty: serial: fsl_lpuart: fix the potential risk of division or modulo by zero misc/libmasm/module: Fix two use after free in ibmasm_init_one misc: alcor_pci: fix null-ptr-deref when there is no PCI bridge iio: gyro: fxa21002c: Balance runtime pm + use pm_runtime_resume_and_get(). iio: magn: bmc150: Balance runtime pm + use pm_runtime_resume_and_get() ALSA: usx2y: Don't call free_pages_exact() with NULL address Revert "ALSA: bebob/oxfw: fix Kconfig entry for Mackie d.2 Pro" w1: ds2438: fixing bug that would always get page0 scsi: hisi_sas: Propagate errors in interrupt_init_v1_hw() scsi: lpfc: Fix "Unexpected timeout" error in direct attach topology scsi: lpfc: Fix crash when lpfc_sli4_hba_setup() fails to initialize the SGLs scsi: core: Cap scsi_host cmd_per_lun at can_queue ALSA: ac97: fix PM reference leak in ac97_bus_remove() tty: serial: 8250: serial_cs: Fix a memory leak in error handling path scsi: scsi_dh_alua: Check for negative result value fs/jfs: Fix missing error code in lmLogInit() scsi: megaraid_sas: Fix resource leak in case of probe failure scsi: megaraid_sas: Early detection of VD deletion through RaidMap update scsi: megaraid_sas: Handle missing interrupts while re-enabling IRQs scsi: iscsi: Add iscsi_cls_conn refcount helpers scsi: iscsi: Fix conn use after free during resets scsi: iscsi: Fix shost->max_id use scsi: qedi: Fix null ref during abort handling mfd: da9052/stmpe: Add and modify MODULE_DEVICE_TABLE mfd: cpcap: Fix cpcap dmamask not set warnings ASoC: img: Fix PM reference leak in img_i2s_in_probe() serial: tty: uartlite: fix console setup s390/sclp_vt220: fix console name to match device ALSA: sb: Fix potential double-free of CSP mixer elements powerpc/ps3: Add dma_mask to ps3_dma_region iommu/arm-smmu: Fix arm_smmu_device refcount leak when arm_smmu_rpm_get fails iommu/arm-smmu: Fix arm_smmu_device refcount leak in address translation gpio: zynq: Check return value of pm_runtime_get_sync ALSA: ppc: fix error return code in snd_pmac_probe() selftests/powerpc: Fix "no_handler" EBB selftest gpio: pca953x: Add support for the On Semi pca9655 ASoC: soc-core: Fix the error return code in snd_soc_of_parse_audio_routing() s390/processor: always inline stap() and __load_psw_mask() s390/ipl_parm: fix program check new psw handling s390/mem_detect: fix diag260() program check new psw handling s390/mem_detect: fix tprot() program check new psw handling Input: hideep - fix the uninitialized use in hideep_nvm_unlock() ALSA: bebob: add support for ToneWeal FW66 ALSA: usb-audio: scarlett2: Fix 18i8 Gen 2 PCM Input count ALSA: usb-audio: scarlett2: Fix data_mutex lock ALSA: usb-audio: scarlett2: Fix scarlett2_*_ctl_put() return values usb: gadget: f_hid: fix endianness issue with descriptors usb: gadget: hid: fix error return code in hid_bind() powerpc/boot: Fixup device-tree on little endian ASoC: Intel: kbl_da7219_max98357a: shrink platform_id below 20 characters backlight: lm3630a: Fix return code of .update_status() callback ALSA: hda: Add IRQ check for platform_get_irq() ALSA: usb-audio: scarlett2: Fix 6i6 Gen 2 line out descriptions staging: rtl8723bs: fix macro value for 2.4Ghz only device intel_th: Wait until port is in reset before programming it i2c: core: Disable client irq on reboot/shutdown power: supply: sc27xx: Add missing MODULE_DEVICE_TABLE power: supply: sc2731_charger: Add missing MODULE_DEVICE_TABLE pwm: spear: Don't modify HW state in .remove callback power: supply: ab8500: Avoid NULL pointers power: supply: max17042: Do not enforce (incorrect) interrupt trigger type power: reset: gpio-poweroff: add missing MODULE_DEVICE_TABLE ARM: 9087/1: kprobes: test-thumb: fix for LLVM_IAS=1 PCI/P2PDMA: Avoid pci_get_slot(), which may sleep watchdog: Fix possible use-after-free in wdt_startup() watchdog: sc520_wdt: Fix possible use-after-free in
[Kernel-packages] [Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
** 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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: New Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [
[Kernel-packages] [Bug 1939417] [NEW] Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
You have been subscribed to a public bug: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009d3ff] usable [0.00] BIOS-e820: [mem 0x0009d400-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x09d01fff] usable [0.00] BIOS-e820:
[Kernel-packages] [Bug 1939424] Re: FTBFS with Linux 5.13/GCC 11
This is the patch to fix the current llvm-toolchain FTBFS. I explained everything on the description already, but feel free to ask questions. There's a PPA with the proposed change here: https://launchpad.net/~sergiodj/+archive/ubuntu/ftbfs-impish/+packages This PPA depends on the "volatile" PPA that doko is using to build the packages. Unfortunately, the llvm-toolchain package takes a long time to build, but I did verify locally that the build is passing. One of the dep8 tests is failing locally, but the failure is not related to this change. IMO, fixing the FTBFS is orthogonal to fixing the dep8 failure, which should be done later. ** Patch added: "fix-llvm-toolchain-ftbfs.patch" https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1939424/+attachment/5517140/+files/fix-llvm-toolchain-ftbfs.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to llvm-toolchain-11 in Ubuntu. https://bugs.launchpad.net/bugs/1939424 Title: FTBFS with Linux 5.13/GCC 11 Status in llvm-toolchain-11 package in Ubuntu: Confirmed Bug description: llvm-toolchain-11 is FTBFS'ing with Linux 5.13 because of: [ 8%] Building CXX object projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_posix.cpp.o cd /<>/build-llvm/projects/compiler-rt/lib/sanitizer_common && /usr/bin/g++-11 -DHAVE_RPC_XDR_H=0 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/projects/compiler-rt/lib/sanitizer_common -I/<>/compiler-rt/lib/sanitizer_common -I/<>/build-llvm/include -I/<>/llvm/include -I/<>/compiler-rt/lib/sanitizer_common/.. -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wno-comment -ffunction-sections -fdata-sections -Wall -std=c++14 -Wno-unused-parameter -O2 -DNDEBUG -g1 -m64 -fPIC -fno-builtin -fno-exceptions -fomit-frame-pointer -funwind-tables -fno-stack-protector -fvisibility=hidden -fno-lto -O3 -g -Wno-variadic-macros -Wno-non-virtual-dtor -fno-rtti -Wframe-larger-than=570 -std=c++14 -o CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_posix.cpp.o -c /<>/compiler-rt/lib/sanitizer_common/sanitizer_posix.cpp /<>/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.cpp:133:10: fatal error: linux/cyclades.h: No such file or directory 133 | #include | ^~ compilation terminated. make[5]: *** [projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/build.make:358: projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_platform_limits_posix.cpp.o] Error 1 make[5]: *** Waiting for unfinished jobs make -f projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommonCoverage.x86_64.dir/build.make projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommonCoverage.x86_64.dir/depend make[5]: Entering directory '/<>/build-llvm' This is happening because the Cyclades driver has been finally removed from Linux (after being orphaned 13 years ago): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/include/uapi/linux?h=v5.12=f76edd8f7ce06cdff2fe5b6b39a49644c684a161 LLVM includes cyclades.h when building libsanitizer, and therefore the FTBFS occurs. Upstream has fixed this by removing support for Cyclades from libsanitizer: https://github.com/llvm/llvm- project/commit/884040db086936107ec81656aa5b4c607235fb9a As for the GCC 11 failure, the problem is: [ 19%] Building CXX object tools/clang/utils/TableGen/CMakeFiles/obj.clang-tblgen.dir/ClangDiagnosticsEmitter.cpp.o cd /<>/build-llvm/tools/clang/stage2-bins/tools/clang/utils/TableGen && /<>/build-llvm/./bin/clang++ -DCLANG_VENDOR="\"Ubuntu \"" -D_GNU_SOURCE -D__STDC_CONSTANT_M ACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/utils/TableGen -I/<>/clang/utils/TableGen -I/< >/clang/include -I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/include -I/<>/build-llvm/tools/clang/stage2-bins/include -I/<>/llvm/include -fuse -ld=gold -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused -parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default -Wno-class-memaccess -Wno-noexcept-type -Wnon-vi rtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -ffunction-sections
Re: [Kernel-packages] [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)
Thanks Daniel. I think 5.11 kernel locks up as well but I'll test it again to be sure. Duane On Monday, August 9, 2021, 10:55:35 PM CDT, Daniel van Vugt <1937...@bugs.launchpad.net> wrote: Please run: sudo dpkg -P \ linux-headers-5.10.56-051056 \ linux-headers-5.13.7-051307 \ linux-image-unsigned-5.10.56-051056-generic \ linux-image-unsigned-5.13.7-051307-generic \ linux-modules-5.10.56-051056-generic \ linux-modules-5.13.7-051307-generic then reboot. You should be left with a working 5.11 kernel. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-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: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-ef1xxx dmi.product.sku: 27A48UA#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-hwe-5.8/+bug/1937321/+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 1930275] Re: [nvidia] System does not wake up after suspend
Can you please enable systemd-pstore: $ sudo systemctl enable systemd-pstore Reproduce the problem, reboot and see if there's any file in /var/lib/systemd/pstore? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930275 Title: [nvidia] System does not wake up after suspend Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Ubuntu 20.10 suspend is not working. After suspend it does not wake up. And I have to hard reboot machine. It is happening since last few days. Here is error message I see from logs: "Failed to start Application launched by gnome-session-binary. A start job for unit UNIT has finished with a failure. The job identifier is 368 and the job result is failed. Failed to start LSB: OpenIPMI Driver init script. A start job for unit openipmi.service has finished with a failure. The job identifier is 151 and the job result is failed. " ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 09:04:06 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.73.01, 5.8.0-50-generic, x86_64: installed nvidia, 460.73.01, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU106 [GeForce RTX 2060 SUPER] [3842:3061] InstallationDate: Installed on 2020-02-15 (471 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=ae47d531-67a5-47ff-ba8c-fd3928cd4cad ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7b:bd09/17/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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/1930275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1900388] Re: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Can the optical drive read CD/DVD/BD correctly? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1900388 Title: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Status in linux package in Ubuntu: Confirmed Bug description: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 PIONEER BD-RW BDR-205 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-23-generic 5.8.0-23.24 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2032 F pulseaudio /dev/snd/controlC0: navycat2032 F pulseaudio /dev/snd/controlC1: navycat2032 F pulseaudio CasperMD5CheckResult: skip Date: Mon Oct 19 10:11:53 2020 InstallationDate: Installed on 2020-10-07 (11 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-23-generic N/A linux-backports-modules-5.8.0-23-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900388/+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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws
Please file a bug against Intel graphics: https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws Status in linux package in Ubuntu: Triaged Status in linux-hwe-5.11 package in Ubuntu: Triaged Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1934548] Re: RISC-V: Illegal instruction
https://people.canonical.com/~xnox/lp1934548/ findings published at above location. I am giving up at this point and need to handover to someone else. Is there a way to attach gdb over jtag to unmatched board whilst it is attempting to boot? Is there a way to analyze the vmlinuz image to figure out what is supposed to be at the crashing addresses? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1934548 Title: RISC-V: Illegal instruction Status in linux-riscv package in Ubuntu: Confirmed Status in linux-riscv-5.11 package in Ubuntu: Confirmed Bug description: When booting the Ubuntu Server image on the SiFive HiFive Unmatched I am getting the following error. The last known working version was 1012. The issue is being tracked on the SiFive forums at https://forums.sifive.com/t/u-boot-says-unhandled-exception-illegal-instruction/4898 ``` Starting kernel ... [0.00] Linux version 5.11.0-1014-generic (buildd@riscv64-qemu-lcy01-084) (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #14-Ubuntu SMP Wed Jun 30 17:56:50 UTC 2021 (Ubuntu 5.11.0-1014.14-generic 5.11.22) [0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020 [0.00] earlycon: sifive0 at MMIO 0x1001 (options '') [0.00] printk: bootconsole [sifive0] enabled [0.00] efi: UEFI not found. [0.00] Initial ramdisk at: 0x(ptrval) (183422976 bytes) [0.00] cma: Reserved 32 MiB at 0xfe00 [0.00] Zone ranges: [0.00] DMA32[mem 0x8020-0x] [0.00] Normal [mem 0x0001-0x00047fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x8020-0x00047fff] [0.00] Initmem setup node 0 [mem 0x8020-0x00047fff] [0.00] DMA32 zone: 512 pages in unavailable ranges [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=/dev/nvme0n1p1 ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16165452K/16775168K available (9854K kernel code, 5763K rwdata, 8192K rodata, 2519K init, 997K bss, 576948K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38893 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1014-generic #14-Ubuntu [0.00] epc: ffe0920e ra : ffe09384 sp : ffe001803d30 [0.00] gp : ffe001a14240 tp : ffe00180f440 t0 : ffe07fe38000 [0.00] t1 : ffe0019cd338 t2 : s0 : ffe001803d70 [0.00] s1 : a0 : ffe095aa a1 : 0001 [0.00] a2 : 0002 a3 : a4 : [0.00] a5 : a6 : 0004 a7 : 52464e43 [0.00] s2 : 0002 s3 : 0001 s4 : [0.00] s5 : s6 : s7 : [0.00] s8 : ffe001a170c0 s9 : 0001 s10: 0001 [0.00] s11: fffcc5d0 t3 : 0068 t4 : 000b [0.00] t5 : ffe0019cd3e0 t6 : ffe001803cd8 [0.00] status: 00020100 badaddr: 0513f187 cause: 0002 [0.00] ---[ end trace f67eb9af4d8d492b ]--- [0.00] Kernel panic - not syncing: Attempted to kill the idle task! [0.00] ---[ end Kernel panic - not
[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown
Nolt, is your laptop also AMD based? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
Thanks for the testing. The kernel power cycle the ACPI part of the touchpad, but it doesn't work :( I guess it's better to stick to s2idle for now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend Status in linux package in Ubuntu: New Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from the impish repos. To recreate: 1. Reboot a X1C9 machine and see that the touchpad works fine 2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a software suspend) 3. Resume from suspend and see that touchpad acts differently and less responsive than right after a clean boot What is expected: 1. Same responsive touchpad experience after resuming from suspend as right after a clean boot. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Pop!_OS 21.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] MachineType: LENOVO 20XW005PMX Package: libinput10 1.18.0-1 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet systemd.show_status=false loglevel=0 splash Tags: hirsute third-party-packages ubuntu Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: This does not seem to be an official Pop!_OS package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 06/15/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET66W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW005PMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW005PMX dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938096/+subscriptions -- 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 1939142] Re: linux-riscv-5.11 1015 panics on unmatched
*** This bug is a duplicate of bug 1934548 *** https://bugs.launchpad.net/bugs/1934548 ** This bug has been marked a duplicate of bug 1934548 RISC-V: Illegal instruction -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939142 Title: linux-riscv-5.11 1015 panics on unmatched Status in linux-riscv-5.11 package in Ubuntu: New Bug description: linux-riscv-5.11 1015 panics on unmatched [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=LABEL=cloudimg-rootfs ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16175136K/16775168K available (9852K kernel code, 5762K rwdata, 6144K rodata, 2519K init, 997K bss, 567264K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38886 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1015-generic #16~20.04.1-Ubuntu [0.00] epc: ffe0920e ra : ffe09384 sp : ffe001603d30 [0.00] gp : ffe0018141c0 tp : ffe00160f440 t0 : ffe07fe38000 [0.00] t1 : ffe0017cd2b8 t2 : s0 : ffe001603d70 [0.00] s1 : a0 : ffe095aa a1 : 0001 [0.00] a2 : 0003 a3 : a4 : [0.00] a5 : a6 : 0008 a7 : 52464e43 [0.00] s2 : 0003 s3 : 0001 s4 : [0.00] s5 : s6 : s7 : [0.00] s8 : ffe0018170c0 s9 : 0001 s10: 0001 [0.00] s11: fffcc4e0 t3 : 0068 t4 : 000b [0.00] t5 : ffe0017cd360 t6 : ffe001603cd8 [0.00] status: 00020100 badaddr: 0513f187 cause: 0002 [0.00] ---[ end trace f67eb9af4d8d492b ]--- [0.00] Kernel panic - not syncing: Attempted to kill the idle task! [0.00] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.11/+bug/1939142/+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 1938650] Re: iwd on Ubuntu 20.04 stopped working since update to kernel 5.11
@Lukas Märdian (slyon), I've understand that, but since 20.04 is the defacto LTS release right now I think a fix, besides using an untrusted repository, would be much appreciated by the mainstream users. Cheers! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1938650 Title: iwd on Ubuntu 20.04 stopped working since update to kernel 5.11 Status in iwd package in Ubuntu: Confirmed Status in linux-meta-hwe-5.11 package in Ubuntu: New Bug description: I was using iwd on my Acer aspire v17 nitro with Ubuntu 20.04, and it was working great. But after the last update to kernel 5.11 it suddenly had stopped working. I’ve tried to reinstall it but that didn’t help. I've tried back with kernel 5.8 and iwd was working again. Quick google search showed that this is actually a wide spread problem since kernel 5.9.x, so I wish to ask is there going to be a solution of any kind? Regards! I.Ivanov --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-28 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) NonfreeKernelModules: nvidia_modeset nvidia Package: iwd 1.5-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Tags: focal 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 _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1938650/+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 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: New Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-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.187.15 Tags: focal 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 _MarkForUpload: True dmi.bios.date: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+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 1939424] [NEW] FTBFS with Linux 5.13/GCC 11
Public bug reported: llvm-toolchain-11 is FTBFS'ing with Linux 5.13 because of: [ 8%] Building CXX object projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_posix.cpp.o cd /<>/build-llvm/projects/compiler-rt/lib/sanitizer_common && /usr/bin/g++-11 -DHAVE_RPC_XDR_H=0 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/projects/compiler-rt/lib/sanitizer_common -I/<>/compiler-rt/lib/sanitizer_common -I/<>/build-llvm/include -I/<>/llvm/include -I/<>/compiler-rt/lib/sanitizer_common/.. -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wno-comment -ffunction-sections -fdata-sections -Wall -std=c++14 -Wno-unused-parameter -O2 -DNDEBUG -g1 -m64 -fPIC -fno-builtin -fno-exceptions -fomit-frame-pointer -funwind-tables -fno-stack-protector -fvisibility=hidden -fno-lto -O3 -g -Wno-variadic-macros -Wno-non-virtual-dtor -fno-rtti -Wframe-larger-than=570 -std=c++14 -o CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_posix.cpp.o -c /<>/compiler-rt/lib/sanitizer_common/sanitizer_posix.cpp /<>/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.cpp:133:10: fatal error: linux/cyclades.h: No such file or directory 133 | #include | ^~ compilation terminated. make[5]: *** [projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/build.make:358: projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_platform_limits_posix.cpp.o] Error 1 make[5]: *** Waiting for unfinished jobs make -f projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommonCoverage.x86_64.dir/build.make projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommonCoverage.x86_64.dir/depend make[5]: Entering directory '/<>/build-llvm' This is happening because the Cyclades driver has been finally removed from Linux (after being orphaned 13 years ago): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/include/uapi/linux?h=v5.12=f76edd8f7ce06cdff2fe5b6b39a49644c684a161 LLVM includes cyclades.h when building libsanitizer, and therefore the FTBFS occurs. Upstream has fixed this by removing support for Cyclades from libsanitizer: https://github.com/llvm/llvm- project/commit/884040db086936107ec81656aa5b4c607235fb9a As for the GCC 11 failure, the problem is: [ 19%] Building CXX object tools/clang/utils/TableGen/CMakeFiles/obj.clang-tblgen.dir/ClangDiagnosticsEmitter.cpp.o cd /<>/build-llvm/tools/clang/stage2-bins/tools/clang/utils/TableGen && /<>/build-llvm/./bin/clang++ -DCLANG_VENDOR="\"Ubuntu \"" -D_GNU_SOURCE -D__STDC_CONSTANT_M ACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/utils/TableGen -I/<>/clang/utils/TableGen -I/< >/clang/include >-I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/include >-I/<>/build-llvm/tools/clang/stage2-bins/include >-I/<>/llvm/include -fuse -ld=gold -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused -parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default -Wno-class-memaccess -Wno-noexcept-type -Wnon-vi rtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -ffunction-sections -fdata-sections -fno-common -Woverloaded-virtual -Wno-nested-anon-types -O2 -DNDEBUG -g1 -fno-exceptions -std=c ++14 -o CMakeFiles/obj.clang-tblgen.dir/ClangDiagnosticsEmitter.cpp.o -c /<>/clang/utils/TableGen/ClangDiagnosticsEmitter.cpp In file included from /<>/llvm/utils/benchmark/src/benchmark_register.cc:15: /<>/llvm/utils/benchmark/src/benchmark_register.h:17:30: error: no member named 'numeric_limits' in namespace 'std' static const T kmax = std::numeric_limits::max(); ~^ /<>/llvm/utils/benchmark/src/benchmark_register.h:17:45: error: 'T' does not refer to a value static const T kmax = std::numeric_limits::max(); ^ /<>/llvm/utils/benchmark/src/benchmark_register.h:8:20: note: declared here template ^ /<>/llvm/utils/benchmark/src/benchmark_register.h:17:47: error: no member named 'max' in the global namespace; did you mean 'kmax'? static const T kmax = std::numeric_limits::max(); ^ kmax /<>/llvm/utils/benchmark/src/benchmark_register.h:17:18: note:
Re: [Kernel-packages] [E] [Bug 1939333] Re: package linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-25-generic package post-installation scri
Yes, the previous version of the Virtualbox Guest Additions was 6.1.22 and I did not have issues with that install. I actually did attempt to reinstall Virtualbox Guest Additions 6.1.26 and it succeeded. Not sure where the issue was exactly, but it seems to be OK now. Evgueni-- On Tue, Aug 10, 2021 at 9:45 AM Kleber Sacilotto de Souza < 1939...@bugs.launchpad.net> wrote: > Hello Evgueni, > > The HWE kernel in Focal Fossa 20.04 has recently been updated from 5.8 > to 5.11. Reading the logs attached, it seems your system is trying to > install the new 5.11 kernel packages and is failing at this stage: > > Processing triggers for linux-image-5.11.0-25-generic > (5.11.0-25.27~20.04.1) ... > /etc/kernel/postinst.d/initramfs-tools: > update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic > run-parts: failed to stat component /etc/kernel/postinst.d/vboxadd: No > such file or directory > > The file '/etc/kernel/postinst.d/vboxadd' was likely supposed to be > installed by Virtualbox Guest Additions but it's either empty or not > present. You mentioned that you are trying to install the newest > Virtualbox Guest Additions. Was a previous version already installed > before? If yes, could you try removing it and installing again? > > -- > You received this bug notification because you are subscribed to the bug > report. > > https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_bugs_1939333=DwIFaQ=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ=EP9zXakUoez-ZfjYKLUXmujwh2UKQiETx9TU-8GvDoJSb_I5Tz03P3n66M7yKrDz=ZBOMlrWbrZtPauStHwxFSMGdpiGSiTx76rEHRpjHfLo=XQ_M8KsPzHk2QwveC2OR6_zWFJg5RRPVD-N1yNsM8k4= > > Title: > package linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to > install/upgrade: installed linux-image-5.11.0-25-generic package post- > installation script subprocess returned error exit status 1 > > Status in linux-signed-hwe-5.11 package in Ubuntu: > New > > Bug description: > This issue appeared while VirtualBox kernel modules were being > compiled for installation of the newest Guest Additions > > ProblemType: Package > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 > ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-63-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > CasperMD5CheckResult: skip > Date: Mon Aug 9 13:57:45 2021 > ErrorMessage: installed linux-image-5.11.0-25-generic package > post-installation script subprocess returned error exit status 1 > InstallationDate: Installed on 2021-02-13 (177 days ago) > InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 > (20210209.1) > Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, > 3.8.2-0ubuntu2 > PythonDetails: N/A > RelatedPackageVersions: >dpkg 1.19.7ubuntu3 >apt 2.0.6 > SourcePackage: linux-signed-hwe-5.11 > Title: package linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed > to install/upgrade: installed linux-image-5.11.0-25-generic package > post-installation script subprocess returned error exit status 1 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_ubuntu_-2Bsource_linux-2Dsigned-2Dhwe-2D5.11_-2Bbug_1939333_-2Bsubscriptions=DwIFaQ=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ=EP9zXakUoez-ZfjYKLUXmujwh2UKQiETx9TU-8GvDoJSb_I5Tz03P3n66M7yKrDz=ZBOMlrWbrZtPauStHwxFSMGdpiGSiTx76rEHRpjHfLo=NGi4GKrbhGeJA8NLPioD9nFyeSqnNGL-8HR2xyk91zM= > > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939333 Title: package linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-25-generic package post- installation script subprocess returned error exit status 1 Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: This issue appeared while VirtualBox kernel modules were being compiled for installation of the newest Guest Additions ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 9 13:57:45 2021 ErrorMessage: installed linux-image-5.11.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-02-13 (177 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3
[Kernel-packages] [Bug 1939333] Re: package linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-25-generic package post-installation script subpr
Hello Evgueni, The HWE kernel in Focal Fossa 20.04 has recently been updated from 5.8 to 5.11. Reading the logs attached, it seems your system is trying to install the new 5.11 kernel packages and is failing at this stage: Processing triggers for linux-image-5.11.0-25-generic (5.11.0-25.27~20.04.1) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic run-parts: failed to stat component /etc/kernel/postinst.d/vboxadd: No such file or directory The file '/etc/kernel/postinst.d/vboxadd' was likely supposed to be installed by Virtualbox Guest Additions but it's either empty or not present. You mentioned that you are trying to install the newest Virtualbox Guest Additions. Was a previous version already installed before? If yes, could you try removing it and installing again? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939333 Title: package linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-25-generic package post- installation script subprocess returned error exit status 1 Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: This issue appeared while VirtualBox kernel modules were being compiled for installation of the newest Guest Additions ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 9 13:57:45 2021 ErrorMessage: installed linux-image-5.11.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-02-13 (177 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-signed-hwe-5.11 Title: package linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939333/+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 1939349] Re: frequent hangs with latest hirsute kernel (nvidia graphics)
If you want to try going back to 5.11.0-16-generic, you can install the nvidia-dkms-$flavour package for your NVIDIA driver, and, assuming you are using secure boot, let DKMS enroll its own key. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939349 Title: frequent hangs with latest hirsute kernel (nvidia graphics) Status in linux package in Ubuntu: New Bug description: After upgrading to the latest kernel, I am experiencing frequent kernel hangs. The system does not respond to Alt+SysRq, and I have to power it off. In some cases the hang happens before X has even been launched at boot. When it hangs, the fan spins up to full speed. 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 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vorlon10452 F pulseaudio /dev/snd/controlC0: vorlon10452 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 9 14:15:58 2021 InstallationDate: Installed on 2019-12-23 (594 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_di672m@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_di672m ro quiet splash vt.handoff=1 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: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2019 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET40W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 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.19 dmi.modalias: dmi:bvnLENOVO:bvrN2OET40W(1.27):bd10/17/2019:br1.27:efr1.19:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939349/+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 1939402] [NEW] Touchpad not working correctly after Ubuntu Update
Public bug reported: xinput list When I run this command I do not see the touchpad listed. cat /proc/bus/input/devices In this command too I do not see the Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 10 18:04:56 2021 InstallationDate: Installed on 2021-06-26 (45 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939402 Title: Touchpad not working correctly after Ubuntu Update Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: xinput list When I run this command I do not see the touchpad listed. cat /proc/bus/input/devices In this command too I do not see the Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 10 18:04:56 2021 InstallationDate: Installed on 2021-06-26 (45 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939402/+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 1912935] Re: battery drain while notebook off / shutdown
@asgard2 Didn't tried that but I will today. Rebooting to another OS only to shut it down is horror, I needed Windows only to upgrade BIOS (had a hope maybe this resolve mine issue). And yea I live with this bug since October 2020, back then I upgraded to alpha Ubuntu 21.04 because I thought maybe in new kernel issue has been fixed but unfortunately nope. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1933415] Re: Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0.
** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1933415 Title: Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0. Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Bug description: [SRU Justification] [Impact] iwlwifi may encounter firmware crash when running 5.13 kernel with outdated firmware. [Fix] Commit 2b13afc1a0ff82 ("iwlwifi: add new FWs from core60-51 release") added new rev -63 firmware. [Test Case] 1. disconnect/connect stress $ sudo add-apt-repository ppa:checkbox-dev/ppa $ sudo apt install plainbox-provider-checkbox $ checkbox-cli run com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress ignore connect bluetooth part, and set the SSID and password to proceed. 2. suspend/resume stress $ for i in $(seq 200); do \ echo "Round $i..."; \ nmcli d; \ sleep 15; \ rtcwake -m mem -s 15; \ done [Where problems could occur] Rev -63 firmware is only used by 5.13 kernel or newer. [Other Info] While 5.13 kernel is only available in Focal and Impish, only Focal is nominated here. == original bug description == [Reproduce steps] 1. disconnect/connect stress $ sudo add-apt-repository ppa:checkbox-dev/ppa $ sudo apt install plainbox-provider-checkbox $ checkbox-cli run com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress ignore connect bluetooth part, and set the SSID and password to proceed. 2. suspend/resume stress $ for i in $(seq 200); do \ echo "Round $i..."; \ nmcli d; \ sleep 15; \ rtcwake -m mem -s 15; \ done kernel: iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x0. [100/1757] kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: kernel: iwlwifi :03:00.0: Status: 0x0040, count: 6 kernel: iwlwifi :03:00.0: Loaded firmware version: 59.601f3a66.0 ty-a0-gf-a0-59.ucode kernel: iwlwifi :03:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL kernel: iwlwifi :03:00.0: 0x00A08200 | trm_hw_status0 kernel: iwlwifi :03:00.0: 0x | trm_hw_status1 kernel: iwlwifi :03:00.0: 0x004D9BDC | branchlink2 kernel: iwlwifi :03:00.0: 0x922A | interruptlink1 kernel: iwlwifi :03:00.0: 0x922A | interruptlink2 kernel: iwlwifi :03:00.0: 0x000161C4 | data1 kernel: iwlwifi :03:00.0: 0x0010 | data2 kernel: iwlwifi :03:00.0: 0x | data3 kernel: iwlwifi :03:00.0: 0x1C405003 | beacon time kernel: iwlwifi :03:00.0: 0x72B40004 | tsf low kernel: iwlwifi :03:00.0: 0x03E4 | tsf hi kernel: iwlwifi :03:00.0: 0x | time gp1 kernel: iwlwifi :03:00.0: 0x00EF1CDC | time gp2 kernel: iwlwifi :03:00.0: 0x0001 | uCode revision type kernel: iwlwifi :03:00.0: 0x003B | uCode version major kernel: iwlwifi :03:00.0: 0x601F3A66 | uCode version minor kernel: iwlwifi :03:00.0: 0x0420 | hw version kernel: iwlwifi :03:00.0: 0x00489002 | board version kernel: iwlwifi :03:00.0: 0x8011001C | hcmd kernel: iwlwifi :03:00.0: 0xE6863000 | isr0 kernel: iwlwifi :03:00.0: 0x0104 | isr1 kernel: iwlwifi :03:00.0: 0x68FA | isr2 kernel: iwlwifi :03:00.0: 0x00C44C4F | isr3 kernel: iwlwifi :03:00.0: 0x0020 | isr4 kernel: iwlwifi :03:00.0: 0x007C019C | last cmd Id kernel: iwlwifi :03:00.0: 0x000161C4 | wait_event kernel: iwlwifi :03:00.0: 0x00D0 | l2p_control kernel: iwlwifi :03:00.0: 0x00018034 | l2p_duration kernel: iwlwifi :03:00.0: 0x003F | l2p_mhvalid kernel: iwlwifi :03:00.0: 0x00CF00F8 | l2p_addr_match kernel: iwlwifi :03:00.0: 0x0009 | lmpm_pmg_sel kernel: iwlwifi :03:00.0: 0x | timestamp kernel: iwlwifi :03:00.0: 0x9890 | flow_handler kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: kernel: iwlwifi :03:00.0: Status: 0x0040, count: 7 kernel: iwlwifi :03:00.0: 0x2000345A | ADVANCED_SYSASSERT kernel: iwlwifi :03:00.0: 0x | umac branchlink1 kernel: iwlwifi :03:00.0: 0x8045D8DE | umac branchlink2 kernel: iwlwifi :03:00.0: 0xC0085288 | umac interruptlink1 kernel: iwlwifi :03:00.0: 0x | umac interruptlink2 kernel: iwlwifi :03:00.0: 0x0007 | umac data1 [55/1757] kernel: iwlwifi :03:00.0: 0x0006 | umac data2 kernel: iwlwifi
[Kernel-packages] [Bug 1938149] Re: To support AMD W6600 and W6700
** Tags added: verification-needed-focal verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1938149 Title: To support AMD W6600 and W6700 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Bug description: [Impact] To support AMD Radeon Pro W6600/W6700 graphic card, we need some new firmware. [Fix] AMD suggests us to include below 2 commits, and to avoid conflicts I cherry pick sienna cichlid firmware from the beginning when it's been added. Impish already have both commits. amdgpu: add initial dimgrey cavefish firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=87619e4114cc631efcb6868dca54d481dc467034 amdgpu: update sienna cichlid firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=4043da4f77f84b75a0f818ab7e83ead187ebf441 [Test] Verified on AMD Radeon Pro W6600 graphic card. [Where problems could occur] This series of patches introduce dimgrey cavefish and sienna cichlid firmware. The 2 GPUs are still new and have little chance to affect old platforms, should be safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1938149/+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 1938530] Re: arm64: virtio_blk is not included in the initramfs
Something like this https://github.com/snapcore/core- initrd/pull/34/files should do it. Plus respinning the pc-kernel arm64 & armhf kernel snaps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1938530 Title: arm64: virtio_blk is not included in the initramfs Status in linux-meta package in Ubuntu: New Bug description: The virtio_blk module is not included by default in the initramfs for arm64, so UC20 cannot boot as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1938530/+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 1912935] Re: battery drain while notebook off / shutdown
@Nolt Booting to Windows is not required, your can press the power button from grub menu. @kaihengfeng I'm concerned, no update in months and it seems to affect a lot of devices. Most of the users may not notice the increased energy consumption with daily use in home office. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1939205] Re: sound dummy output 21.04
not sure what you mean by stock, it was the 21.04 pushed from dist- upgrade with the 5.11.0.26 kernel how do i "debug" pulseaudio and the "pa" exactly ? :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939205 Title: sound dummy output 21.04 Status in linux package in Ubuntu: New Bug description: no more sound device /output since dist upgrade from 20.10 to 21.04 tried both official ubuntu kernel 5.11.0.26 and newer 5.13.8-051308-generic alsa log: http://alsa-project.org/db/?f=07dfaad1d5d30948449dc36f0caaf39c99145cce lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 apt-cache policy pkgname N: Unable to locate package pkgname ubuntu-bug linux: package not installed cat /proc/version_signature > version.log cat: /proc/version_signature: No such file or directory sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error be descriptive in helping as im a newbie to linux troubleshoot :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939205/+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 1924624] Re: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable
New bug against 5.11 opened https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe-5.11/+bug/1939296 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1924624 Title: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe-5.8 package in Ubuntu: Fix Released Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+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 1938650] Re: iwd on Ubuntu 20.04 stopped working since update to kernel 5.11
This seems to be a regression (deprecated AF_ALG RC4 support) in the linux-hwe-5.11 stack: https://lkml.org/lkml/2020/8/4/512 A workaround exists by either using Linux 5.8 or using a newer iwd version (e.g. from https://launchpad.net/~slyon/+archive/ubuntu/iwd+nm ) Unfortunately, we cannot easily backport a big version jump of iwd into the 20.04 stable series, but we would need a small patch that only backports the required iwd RC4 implementation on top of iwd-1.5. ** Also affects: linux-meta-hwe-5.11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1938650 Title: iwd on Ubuntu 20.04 stopped working since update to kernel 5.11 Status in iwd package in Ubuntu: Confirmed Status in linux-meta-hwe-5.11 package in Ubuntu: New Bug description: I was using iwd on my Acer aspire v17 nitro with Ubuntu 20.04, and it was working great. But after the last update to kernel 5.11 it suddenly had stopped working. I’ve tried to reinstall it but that didn’t help. I've tried back with kernel 5.8 and iwd was working again. Quick google search showed that this is actually a wide spread problem since kernel 5.9.x, so I wish to ask is there going to be a solution of any kind? Regards! I.Ivanov --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-28 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) NonfreeKernelModules: nvidia_modeset nvidia Package: iwd 1.5-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Tags: focal 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 _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1938650/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
Tested the kernel provided now and it seems to still act the same. Attaching GIF with output of the `watch -n0 cat /proc/interrupts` command. I also tried switching the sleep mode back to the default (S0ix) yesterday and this seems to work a lot better with 5.13 kernels than the 5.11 one and preserves battery very well now. I had it set back to "Linux S3" again for this kernel test though. `uname -a` output: Linux lomez 5.13.0-2010-oem #11 SMP Tue Aug 10 13:37:12 CST 2021 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "Peek 2021-08-10 12-37.gif" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938096/+attachment/5517063/+files/Peek%202021-08-10%2012-37.gif -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend Status in linux package in Ubuntu: New Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from the impish repos. To recreate: 1. Reboot a X1C9 machine and see that the touchpad works fine 2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a software suspend) 3. Resume from suspend and see that touchpad acts differently and less responsive than right after a clean boot What is expected: 1. Same responsive touchpad experience after resuming from suspend as right after a clean boot. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Pop!_OS 21.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] MachineType: LENOVO 20XW005PMX Package: libinput10 1.18.0-1 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet systemd.show_status=false loglevel=0 splash Tags: hirsute third-party-packages ubuntu Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: This does not seem to be an official Pop!_OS package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 06/15/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET66W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW005PMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW005PMX dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Kernel-packages] [Bug 1939222] Re: DisplayPort over USB-C not working after release update
Referring to bug #1938999 It seems that the underlying problem is the same, However, please be aware that Thomas (Bug 1938999) worked on Thunderbolt3 DP and reported: "Without the dock and one external display it is okay, ..." whereas the Thinkpad e15 (bug 1939222) has USB-C GEN1 and DP alt mode only. The E15 fails with a single external display - (attached via usb-c/dp adapter). The same applies to your test on a T590: T590 has usb-c gen2 / Thunderbolt3 and a second usb-c gen1 Could that be the reason why you can't reproduce the issue on T590 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939222 Title: DisplayPort over USB-C not working after release update Status in linux package in Ubuntu: Confirmed Bug description: After (automated) update from 5.8.0-63 to 5.11.0.-25 the displayport over usb-c (Thinkpad e15gen2 i5-1135G7 / GeForce MX450/PCIe/SSE2) is not working properly. Revert to 5.8.0-63 resolves the problem. The problem is independent of nvdia-drivers (tried 470, 460 and intel only drivers). Same Monitors connected over HDMI work properly. Problem is limited to displayport over usb-c. Problem symptoms: Monitor atttached over displayport allows only VGA resolution(1024 * 768) and flickers (on/off periodically). no special error messages found in dmesg except for abundance of "i915 :00:02.0: [drm] *ERROR* failed to enable link training" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.35 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 09:12:10 2021 InstallationDate: Installed on 2021-06-14 (54 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IL:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939222/+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 1938530] Re: arm64: virtio_blk is not included in the initramfs
$ git grep virtio_blk features/server/usr/lib/modules-load.d/ubuntu-core-server.conf:virtio_blk When building initrd into the generic arm64 kernel snap, we should enable feature "server" like we do on x86. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1938530 Title: arm64: virtio_blk is not included in the initramfs Status in linux-meta package in Ubuntu: New Bug description: The virtio_blk module is not included by default in the initramfs for arm64, so UC20 cannot boot as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1938530/+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 1938530] Re: arm64: virtio_blk is not included in the initramfs
Doing this in "kernel-snaps-uc20" git repo would be tricky, as at the moment we don't pass any option when making kernel snaps. Otherwise core-initd itself defaults to "main server" on x86, but just "main" on all other arches. Maybe we should enable "server" features for "generic" kernel flavours always. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1938530 Title: arm64: virtio_blk is not included in the initramfs Status in linux-meta package in Ubuntu: New Bug description: The virtio_blk module is not included by default in the initramfs for arm64, so UC20 cannot boot as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1938530/+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 1876632] Re: [nvidia] Corrupted shell textures when switching users or resuming from suspend
Same problem occurs for me with nvidia-driver-470. The graphical effect / issue is a bit different, yet. See attached pic... My Ubuntu 20.04 is as up-to-date as possible. The last suggested solution is working for me (restarting gnome-shell), but this is still annoying... I've just read this : https://www.reddit.com/r/gnome/comments/k5ea3g/text_and_icon_glitching_out_after_resuming_from/ so it seems we won't have any solution before quite a long time... Fed up with nvidia ! ** Attachment added: "Capture d’écran de 2021-08-09 12-53-14.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1876632/+attachment/5517062/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202021-08-09%2012-53-14.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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/gnome-shell/+bug/1876632/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1939222] Re: DisplayPort over USB-C not working after release update
Probably it's duplicated bug of #1938999 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939222 Title: DisplayPort over USB-C not working after release update Status in linux package in Ubuntu: Confirmed Bug description: After (automated) update from 5.8.0-63 to 5.11.0.-25 the displayport over usb-c (Thinkpad e15gen2 i5-1135G7 / GeForce MX450/PCIe/SSE2) is not working properly. Revert to 5.8.0-63 resolves the problem. The problem is independent of nvdia-drivers (tried 470, 460 and intel only drivers). Same Monitors connected over HDMI work properly. Problem is limited to displayport over usb-c. Problem symptoms: Monitor atttached over displayport allows only VGA resolution(1024 * 768) and flickers (on/off periodically). no special error messages found in dmesg except for abundance of "i915 :00:02.0: [drm] *ERROR* failed to enable link training" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.35 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 09:12:10 2021 InstallationDate: Installed on 2021-06-14 (54 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IL:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939222/+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 1938999] Re: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock
I didn't reproduce this issue on T590 with 5.11.0-25 kernel. Please try dock or DP again. And the 5.13 kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13/amd64/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938999 Title: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock Status in linux package in Ubuntu: Confirmed Bug description: I have two external displays chained via Display port connected to the ThinkPad Thunderbolt 3 Dock. They are working with kernel 5.8.0-63 but not with the new 5.11.0-25 kernel. I could reproduce this behavior several times for both kernels, as follows: I booted up with disconnected dock, logged in, then I connected it, disconnected it, and connected it again. With the 5.11.0-25 kernel the external displays go black; the main screen turns off and on several times. Sometimes the main screen remains working, but UI is lagging. I'm attaching the logs. Two separate boots for each variant are marked 'a'/'b'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938999/+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 1939301] Re: REGRESSION: shiftfs lets sendfile fail with EINVAL
** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939301 Title: REGRESSION: shiftfs lets sendfile fail with EINVAL Status in linux package in Ubuntu: New Status in linux-meta-hwe-5.11 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-meta-hwe-5.11 source package in Focal: Confirmed Status in linux source package in Hirsute: In Progress Status in linux-meta-hwe-5.11 source package in Hirsute: Invalid Status in linux source package in Impish: New Status in linux-meta-hwe-5.11 source package in Impish: Invalid Bug description: With the 5.11 HWE kernel landing for Ubuntu 20.04 we noticed that LXC tools we're using in bionic containers as part of Anbox Cloud start to fail when executed on the 5.11 kernel. A simple reproducer looks like this: 1. Run Ubuntu 20.04 with HWE kernel (linux-generic-hwe-20.04, 5.11.0-25-generic #27~20.04.1-Ubuntu) 2. Install LXD and enable shiftfs $ snap install lxd $ snap set lxd shiftfs.enable true $ snap restart --reload lxd 3. Launch bionic container and run `lxc-info` $ lxc launch ubuntu:b c0 $ lxc shell c0 c0$ apt update c0$ apt install -y lxc-utils root@c1:~# apt show lxc-utils | grep Version Version: 3.0.3-0ubuntu1~18.04.1 c0$ mkdir -p containers/test c0$ touch containers/test/config c0$ lxc-info -P containers -n test Failed to load config for test Failure to retrieve information on containers:test Looking into the failing `lxc-info` call with strace reveals: ... memfd_create(".lxc_config_file", MFD_CLOEXEC) = 4 openat(AT_FDCWD, "containers/test/config", O_RDONLY|O_CLOEXEC) = 5 sendfile(4, 5, NULL, 2147479552)= -1 EINVAL (Invalid argument ... LXC >= 4.0.0 doesn't use sendfile anymore and with that isn't affected. Any other tool using sendfile however is affected and will fail. Bionic is affected as the 3.0.3 version of LXC it includes still uses sendfile. Disabling shiftfs makes things work again and can be considered as a workaround to a certain degree, but not be applicable in all cases. Further analysis with Christian (cbrauner) from the LXD team this morning showed that shiftfs is missing an implementation for the now required slice_read handler in the file_operations structure. So whenever shiftfs is being used, all calls to sendfile will fail because of the missing implementation. The generic handler for this got removed in the following upstream change: https://lore.kernel.org/lkml/20200626075836.1998185-10-...@lst.de/ Christian implemented a quick fix: https://paste.ubuntu.com/p/TPsjfCpnD5/ As of today I don't know of any customer of Anbox Cloud who is affected by this as most of them run with one of our cloud kernels. However as soon as 5.11 rolls out to the cloud kernels, we will hit production systems and cause them to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939301/+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 1768777] Re: libnvpair1linux doc contents have busted symlinks
Also affects Ubuntu/Focal: # readlink /usr/share/doc/zfs-zed/changelog.Debian.gz ../libnvpair1linux/changelog.Debian.gz # readlink /usr/share/doc/zfsutils-linux/changelog.Debian.gz ../libnvpair1linux/changelog.Debian.gz # readlink /usr/share/doc/zfsutils-linux/../libnvpair1linux/changelog.Debian.gz ../libnvpair1linux/changelog.Debian.gz So.. no changelog then. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal # apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.12 Candidate: 0.8.3-1ubuntu12.12 Version table: *** 0.8.3-1ubuntu12.12 500 This is also an upgraded system. I tried removing a stale 'rc' zfs-doc (0.7.5-1ubuntu16.4), and then --reinstall'ing zfsutil-linux and libnvpair1linux, but I still have no docs, only broken symlinks. Any ideas? Cheers, Walter -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1768777 Title: libnvpair1linux doc contents have busted symlinks Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Justification [BIONIC] == Upgrading from Xenial to Bionic causes broken symlinked changelog, COPYRIGHT and OPENSOLARIS.LICENSE.gz files because the zfs-doc file is missing. == Fix == Add back the missing zfs-doc package, with this package the upgrade works correctly. == Regression Potential == Minimal, this adds just a bunch of missing files that are missing from the default Bionic zfsutils-linux installation. --- % apt-cache policy libnvpair1linux libnvpair1linux: Installed: 0.7.5-1ubuntu15 Candidate: 0.7.5-1ubuntu15 Version table: *** 0.7.5-1ubuntu15 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status % lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 The symlinks are busted: % ls -al total 108 drwxr-xr-x3 root root 4096 Apr 23 08:33 ./ drwxr-xr-x 1120 root root 36864 May 2 07:36 ../ lrwxrwxrwx1 root root38 Apr 17 04:18 changelog.Debian.gz -> ../libnvpair1linux/changelog.Debian.gz -rw-r--r--1 root root 53854 Oct 6 2017 copyright lrwxrwxrwx1 root root28 Apr 17 04:18 COPYRIGHT -> ../libnvpair1linux/COPYRIGHT drwxr-xr-x2 root root 4096 Apr 23 08:33 examples/ lrwxrwxrwx1 root root41 Apr 17 04:18 OPENSOLARIS.LICENSE.gz -> ../libnvpair1linux/OPENSOLARIS.LICENSE.gz -rw-r--r--1 root root 684 Oct 6 2017 README.Debian % zcat changelog.Debian.gz gzip: changelog.Debian.gz: Too many levels of symbolic links ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libnvpair1linux 0.7.5-1ubuntu15 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 03:47:57 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1768777/+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 1768777] Re: libnvpair1linux doc contents have busted symlinks
Ok. I stand corrected. I reinstall of libnvpair1linux _did_ fix it. (After removing zfs-doc.) # apt-get install --reinstall libnvpair1linux # ls -l /usr/share/doc/libnvpair1linux/ total 76 -rw-r--r-- 1 root root 1615 jul 12 16:36 changelog.Debian.gz Move along.. nothing to see here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1768777 Title: libnvpair1linux doc contents have busted symlinks Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Justification [BIONIC] == Upgrading from Xenial to Bionic causes broken symlinked changelog, COPYRIGHT and OPENSOLARIS.LICENSE.gz files because the zfs-doc file is missing. == Fix == Add back the missing zfs-doc package, with this package the upgrade works correctly. == Regression Potential == Minimal, this adds just a bunch of missing files that are missing from the default Bionic zfsutils-linux installation. --- % apt-cache policy libnvpair1linux libnvpair1linux: Installed: 0.7.5-1ubuntu15 Candidate: 0.7.5-1ubuntu15 Version table: *** 0.7.5-1ubuntu15 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status % lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 The symlinks are busted: % ls -al total 108 drwxr-xr-x3 root root 4096 Apr 23 08:33 ./ drwxr-xr-x 1120 root root 36864 May 2 07:36 ../ lrwxrwxrwx1 root root38 Apr 17 04:18 changelog.Debian.gz -> ../libnvpair1linux/changelog.Debian.gz -rw-r--r--1 root root 53854 Oct 6 2017 copyright lrwxrwxrwx1 root root28 Apr 17 04:18 COPYRIGHT -> ../libnvpair1linux/COPYRIGHT drwxr-xr-x2 root root 4096 Apr 23 08:33 examples/ lrwxrwxrwx1 root root41 Apr 17 04:18 OPENSOLARIS.LICENSE.gz -> ../libnvpair1linux/OPENSOLARIS.LICENSE.gz -rw-r--r--1 root root 684 Oct 6 2017 README.Debian % zcat changelog.Debian.gz gzip: changelog.Debian.gz: Too many levels of symbolic links ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libnvpair1linux 0.7.5-1ubuntu15 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 03:47:57 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1768777/+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 1939349] Re: frequent hangs with latest hirsute kernel (nvidia graphics)
I didn't reproduce this issue on another X1 2nd. Reboot for 10 times, all good. Verified OS version: Focal $ uname -a Linux u-ThinkPad-X1-Extreme-Gen2 5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux NVRM: loading NVIDIA UNIX x86_64 Kernel Module 460.91.03 The error I found in dmesg is: [ 14.291240] loop0: detected capacity change from 0 to 226816 [ 14.328998] loop1: detected capacity change from 0 to 231360 It could be related to ZFS raid, It's better to backup everything and scan your partition. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939349 Title: frequent hangs with latest hirsute kernel (nvidia graphics) Status in linux package in Ubuntu: New Bug description: After upgrading to the latest kernel, I am experiencing frequent kernel hangs. The system does not respond to Alt+SysRq, and I have to power it off. In some cases the hang happens before X has even been launched at boot. When it hangs, the fan spins up to full speed. 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 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vorlon10452 F pulseaudio /dev/snd/controlC0: vorlon10452 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 9 14:15:58 2021 InstallationDate: Installed on 2019-12-23 (594 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_di672m@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_di672m ro quiet splash vt.handoff=1 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: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2019 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET40W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 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.19 dmi.modalias: dmi:bvnLENOVO:bvrN2OET40W(1.27):bd10/17/2019:br1.27:efr1.19:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939349/+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 1912935] Re: battery drain while notebook off / shutdown
Same here I have HP 15s-eq0057nw, tried almost everything and battery drain exist while I shutdown laptop from Ubuntu. If I reboot to Windows and shutdown from Windows there is no battery drain. So for now I unfortunately have to dualboot to Windows and shutdown from Windows. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1934282] Re: Some test in kselftest/net on focal source tree were not tested at all
Thanks for the verification, Kleber! ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934282 Title: Some test in kselftest/net on focal source tree were not tested at all Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: [Impact] Found this issue while debugging devlink_port_split.py test issue in bug 1928889. There are some tests like icmp_redirect.sh, ip6_gre_headroom.sh and etc are not in the Makefile of the net directory, thus they are not tested at all. [Fix] * 919a23e9d6ccf8 selftests/net: add missing tests to Makefile Backport needed for Focal as we only have these tests unadded: $ for file in $(ls *.sh); do grep -q $file Makefile || echo $file; done fib_nexthop_multiprefix.sh fib_nexthops.sh icmp_redirect.sh ip6_gre_headroom.sh route_localnet.sh [Test] Run the "net" test suite in the kselftest directory from a patched source tree. These tests will be executed. [Where problems could occur] This change will bring in more tests for our SRU, we might see new failures because of these test in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934282/+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 1936899] Re: [IoTG] [TGL-H] TPM tests fail
For the tpm2_clockrateadjust test fail, + tpm2_clockrateadjust s WARNING:esys:src/tss2-esys/api/Esys_ClockRateAdjust.c:287:Esys_ClockRateAdjust_Finish() Received TPM Error ERROR:esys:src/tss2-esys/api/Esys_ClockRateAdjust.c:100:Esys_ClockRateAdjust() Esys Finish ErrorCode (0x01c4) ERROR: Esys_ClockRateAdjust(0x1C4) - tpm:parameter(1):value is out of range or is not correct for the context ERROR: Unable to run tpm2_clockrateadjust it occurred on the tpm2_clockrateadjust to slow down the clock period one fine increment and got the "value is out of range or is not correct for the context" from TPM. It is due to the platform unsupported the clock rate adjust, it is known that some firmware TPM do not support this function, please check if this platform is firmware TPM, and check with your TPM vendors. -- 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/1936899 Title: [IoTG] [TGL-H] TPM tests fail Status in intel: New Status in linux-intel package in Ubuntu: New Bug description: [Summary]TPM tests from CDTS 20 automated fail [Steps to reproduce]Run cdts.odm_certification, select TPM [Expected result]All tests should pass. [Actual result] Failed Jobs (TPM 2.0): tpm2.0_4.1.1/tpm2_clockratedadjust tpm2.0_4.1.1/tpm2_createprimary tpm2.0_4.1.1/tpm2_import tpm2.0_4.1.1/tpm2_loadexternal Jobs with failed dependencies tpm2.0_4.1.1/tpm2_rc_decode [Failure rate]100% [Additional information] CID: 202106-29175 SKU: system-manufacturer: Intel Corporation system-product-name: Tiger Lake Client Platform bios-version: TGLIFUI1.R00.3455.A03.2011281547 CPU: Genuine Intel(R) CPU @ 2.60GHz (16x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a60] kernel-version: 5.11.0-1009-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1936899/+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 1923113] Re: mem-on-off-test from memory-hotplug in ubuntu_kernel_selftests fails with blocked task on B/F/G/H
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: mem-on-off-test from memory-hotplug fails with timeout and blocked task, although visible is also invalid argument/unexpected success on Bionic 4.15.0-141.145 This is not a regression as it happened on 4.15.0-139.143 too, though passed all tests on 4.15.0-140.144. This same test is reported as failing, though with different output on: + lp:1897764 and lp:1891003 - https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1897764 - https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1891003 - + --- 03/26 11:09:12 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > /proc/sys/net/ipv4/conf/all/accept_local'' 03/26 11:09:12 DEBUG| utils:0116| Running 'sudo make -C linux/tools/testing/selftests TARGETS=memory-hotplug run_tests' 03/26 11:09:12 DEBUG| utils:0153| [stdout] make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' 03/26 11:09:12 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memory-hotplug' 03/26 11:09:12 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done for 'all'. 03/26 11:09:12 DEBUG| utils:0153| [stdout] make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memory-hotplug' 03/26 11:09:12 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memory-hotplug' 03/26 11:09:12 DEBUG| utils:0153| [stdout] ./mem-on-off-test.sh -r 2 && echo "selftests: memory-hotplug [PASS]" || echo "selftests: memory-hotplug [FAIL]" 03/26 11:09:12 DEBUG| utils:0153| [stdout] Test scope: 2% hotplug memory 03/26 11:09:16 DEBUG| utils:0153| [stdout] online all hot-pluggable memory in offline state: 03/26 11:09:16 DEBUG| utils:0153| [stdout] SKIPPED - no hot-pluggable memory in offline state 03/26 11:09:20 DEBUG| utils:0153| [stdout] offline 2% hot-pluggable memory in online state 03/26 11:09:20 DEBUG| utils:0153| [stdout] trying to offline 15 out of 748 memory block(s): 03/26 11:09:23 DEBUG| utils:0153| [stdout] online->offline memory10 03/26 11:09:24 DEBUG| utils:0153| [stdout] online->offline memory100 03/26 11:09:24 DEBUG| utils:0153| [stdout] online->offline memory101 03/26 11:09:24 DEBUG| utils:0153| [stdout] online->offline memory102 03/26 11:09:24 DEBUG| utils:0153| [stdout] online->offline memory103 03/26 11:09:24 DEBUG| utils:0153| [stdout] online->offline memory104 03/26 11:09:24 DEBUG| utils:0153| [stdout] online->offline memory105 03/26 11:09:24 DEBUG| utils:0153| [stdout] online->offline memory106 03/26 11:09:24 DEBUG| utils:0153| [stdout] online->offline memory107 03/26 11:09:24 DEBUG| utils:0153| [stdout] online->offline memory108 03/26 11:09:24 DEBUG| utils:0153| [stdout] online->offline memory109 03/26 11:09:24 DEBUG| utils:0153| [stdout] online->offline memory11 03/26 11:09:24 DEBUG| utils:0153| [stdout] online->offline memory110 03/26 11:09:24 DEBUG| utils:0153| [stdout] online->offline memory111 03/26 11:09:24 DEBUG| utils:0153| [stdout] online->offline memory112 03/26 11:09:28 DEBUG| utils:0153| [stdout] online all hot-pluggable memory in offline state: 03/26 11:09:32 DEBUG| utils:0153| [stdout] offline->online memory10 03/26 11:09:32 DEBUG| utils:0153| [stdout] offline->online memory100 03/26 11:09:32 DEBUG| utils:0153| [stdout] offline->online memory101 03/26 11:09:32 DEBUG| utils:0153| [stdout] offline->online memory102 03/26 11:09:32 DEBUG| utils:0153| [stdout] offline->online memory103 03/26 11:09:32 DEBUG| utils:0153| [stdout] offline->online memory104 03/26 11:09:32 DEBUG| utils:0153| [stdout] offline->online memory105 03/26 11:09:32 DEBUG| utils:0153| [stdout] offline->online memory106 03/26 11:09:32 DEBUG| utils:0153| [stdout] offline->online memory107 03/26 11:09:32 DEBUG| utils:0153| [stdout] offline->online memory108 03/26 11:09:32 DEBUG| utils:0153| [stdout] offline->online memory109 03/26 11:09:32 DEBUG| utils:0153| [stdout] offline->online memory11 03/26 11:09:33 DEBUG| utils:0153| [stdout] offline->online memory110 03/26 11:09:33 DEBUG| utils:0153| [stdout] offline->online memory111 03/26 11:09:33 DEBUG| utils:0153| [stdout] offline->online memory112 03/26 11:09:33 DEBUG| utils:0153| [stdout] Test with memory notifier error injection 03/26 11:09:37 ERROR| utils:0153| [stderr] ./mem-on-off-test.sh: line 263: echo:
[Kernel-packages] [Bug 1939384] Re: Blocked task of memory-hotplug test from ubuntu_kernel_selftests on Bionic ibm-gt
*** This bug is a duplicate of bug 1923113 *** https://bugs.launchpad.net/bugs/1923113 ** This bug has been marked a duplicate of bug 1923113 mem-on-off-test from memory-hotplug in ubuntu_kernel_selftests fails with blocked task on B/F/G/H -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939384 Title: Blocked task of memory-hotplug test from ubuntu_kernel_selftests on Bionic ibm-gt Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: Bionic ibm-gt v4.15 kernel only on amd64 metal nodes rizzo and rumford has a timeout of memory-hotplug from ubuntu_kernel_selftests: --- 14121 14:49:30 ERROR| [stderr] offline_memory_expect_fail 5: unexpected success 14122 14:56:12 ERROR| [stderr] offline_memory_expect_fail 62: unexpected success 14123 14:56:12 ERROR| [stderr] offline_memory_expect_fail 63: unexpected success 14124 15:19:22 INFO | Timer expired (1800 sec.), nuking pid 17231 14125 15:19:23 INFO | ERROR ubuntu_kernel_selftests.memory-hotplug ubuntu_kernel_selftests.memory-hotplugtimestamp=1625066363localtime=Jun 30 15:19:23 --- In dmesg from next test: --- [ 583.473311] Offlined Pages 32768 [ 583.476247] Offlined Pages 32768 [ 583.479028] Offlined Pages 32768 [ 583.481876] Offlined Pages 32768 [ 1088.798252] INFO: task systemd:1 blocked for more than 120 seconds. [ 1088.798310] Not tainted 4.15.0-1098-ibm-gt #108-Ubuntu [ 1088.798360] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1088.798410] systemd D0 1 0 0x [ 1088.798413] Call Trace: [ 1088.798422] __schedule+0x24e/0x890 [ 1088.798426] schedule+0x2c/0x80 [ 1088.798428] schedule_preempt_disabled+0xe/0x10 [ 1088.798431] __mutex_lock.isra.5+0x276/0x4e0 [ 1088.798435] __mutex_lock_slowpath+0x13/0x20 [ 1088.798437] ? __mutex_lock_slowpath+0x13/0x20 [ 1088.798439] mutex_lock+0x2f/0x40 [ 1088.798444] proc_cgroup_show+0x4c/0x2a0 [ 1088.798449] proc_single_show+0x56/0x80 [ 1088.798453] seq_read+0xe5/0x450 [ 1088.798459] __vfs_read+0x1b/0x40 [ 1088.798462] vfs_read+0x8e/0x130 [ 1088.798466] SyS_read+0x5c/0xe0 [ 1088.798470] do_syscall_64+0x73/0x130 [ 1088.798474] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 1088.798477] RIP: 0033:0x7fb5b16cf184 [ 1088.798478] RSP: 002b:7fff21894aa0 EFLAGS: 0246 ORIG_RAX: [ 1088.798481] RAX: ffda RBX: 0012 RCX: 7fb5b16cf184 [ 1088.798482] RDX: 0400 RSI: 56544b965d80 RDI: 0012 [ 1088.798484] RBP: 56544b965d80 R08: R09: 7fb5b12cc9ba [ 1088.798485] R10: R11: 0246 R12: 0400 [ 1088.798486] R13: 7fb5b19a72a0 R14: 56544b8ad570 R15: 07ff [ 1088.798497] INFO: task kworker/11:1:179 blocked for more than 120 seconds. --- This was found on: 2021.06.21: bionic linux-ibm-gt 4.15.0-1095.104 (rizzo) 2021.07.19: bionic linux-ibm-gt 4.15.0-1098.108 (rumford) Not found on: 2021.06.21: bionic linux-ibm-gt 4.15.0-1096.105 (ricolli) 2021.06.21: bionic linux 4.15.0-150.155 (rumford) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939384/+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 1939384] [NEW] Blocked task of memory-hotplug test from ubuntu_kernel_selftests on Bionic ibm-gt
Public bug reported: Bionic ibm-gt v4.15 kernel only on amd64 metal nodes rizzo and rumford has a timeout of memory-hotplug from ubuntu_kernel_selftests: --- 14121 14:49:30 ERROR| [stderr] offline_memory_expect_fail 5: unexpected success 14122 14:56:12 ERROR| [stderr] offline_memory_expect_fail 62: unexpected success 14123 14:56:12 ERROR| [stderr] offline_memory_expect_fail 63: unexpected success 14124 15:19:22 INFO | Timer expired (1800 sec.), nuking pid 17231 14125 15:19:23 INFO | ERROR ubuntu_kernel_selftests.memory-hotplug ubuntu_kernel_selftests.memory-hotplugtimestamp=1625066363localtime=Jun 30 15:19:23 --- In dmesg from next test: --- [ 583.473311] Offlined Pages 32768 [ 583.476247] Offlined Pages 32768 [ 583.479028] Offlined Pages 32768 [ 583.481876] Offlined Pages 32768 [ 1088.798252] INFO: task systemd:1 blocked for more than 120 seconds. [ 1088.798310] Not tainted 4.15.0-1098-ibm-gt #108-Ubuntu [ 1088.798360] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1088.798410] systemd D0 1 0 0x [ 1088.798413] Call Trace: [ 1088.798422] __schedule+0x24e/0x890 [ 1088.798426] schedule+0x2c/0x80 [ 1088.798428] schedule_preempt_disabled+0xe/0x10 [ 1088.798431] __mutex_lock.isra.5+0x276/0x4e0 [ 1088.798435] __mutex_lock_slowpath+0x13/0x20 [ 1088.798437] ? __mutex_lock_slowpath+0x13/0x20 [ 1088.798439] mutex_lock+0x2f/0x40 [ 1088.798444] proc_cgroup_show+0x4c/0x2a0 [ 1088.798449] proc_single_show+0x56/0x80 [ 1088.798453] seq_read+0xe5/0x450 [ 1088.798459] __vfs_read+0x1b/0x40 [ 1088.798462] vfs_read+0x8e/0x130 [ 1088.798466] SyS_read+0x5c/0xe0 [ 1088.798470] do_syscall_64+0x73/0x130 [ 1088.798474] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 1088.798477] RIP: 0033:0x7fb5b16cf184 [ 1088.798478] RSP: 002b:7fff21894aa0 EFLAGS: 0246 ORIG_RAX: [ 1088.798481] RAX: ffda RBX: 0012 RCX: 7fb5b16cf184 [ 1088.798482] RDX: 0400 RSI: 56544b965d80 RDI: 0012 [ 1088.798484] RBP: 56544b965d80 R08: R09: 7fb5b12cc9ba [ 1088.798485] R10: R11: 0246 R12: 0400 [ 1088.798486] R13: 7fb5b19a72a0 R14: 56544b8ad570 R15: 07ff [ 1088.798497] INFO: task kworker/11:1:179 blocked for more than 120 seconds. --- This was found on: 2021.06.21: bionic linux-ibm-gt 4.15.0-1095.104 (rizzo) 2021.07.19: bionic linux-ibm-gt 4.15.0-1098.108 (rumford) Not found on: 2021.06.21: bionic linux-ibm-gt 4.15.0-1096.105 (ricolli) 2021.06.21: bionic linux 4.15.0-150.155 (rumford) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939384 Title: Blocked task of memory-hotplug test from ubuntu_kernel_selftests on Bionic ibm-gt Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: Bionic ibm-gt v4.15 kernel only on amd64 metal nodes rizzo and rumford has a timeout of memory-hotplug from ubuntu_kernel_selftests: --- 14121 14:49:30 ERROR| [stderr] offline_memory_expect_fail 5: unexpected success 14122 14:56:12 ERROR| [stderr] offline_memory_expect_fail 62: unexpected success 14123 14:56:12 ERROR| [stderr] offline_memory_expect_fail 63: unexpected success 14124 15:19:22 INFO | Timer expired (1800 sec.), nuking pid 17231 14125 15:19:23 INFO | ERROR ubuntu_kernel_selftests.memory-hotplug ubuntu_kernel_selftests.memory-hotplugtimestamp=1625066363localtime=Jun 30 15:19:23 --- In dmesg from next test: --- [ 583.473311] Offlined Pages 32768 [ 583.476247] Offlined Pages 32768 [ 583.479028] Offlined Pages 32768 [ 583.481876] Offlined Pages 32768 [ 1088.798252] INFO: task systemd:1 blocked for more than 120 seconds. [ 1088.798310] Not tainted 4.15.0-1098-ibm-gt #108-Ubuntu [ 1088.798360] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1088.798410] systemd D0 1 0 0x [ 1088.798413] Call Trace: [ 1088.798422] __schedule+0x24e/0x890 [ 1088.798426] schedule+0x2c/0x80 [ 1088.798428] schedule_preempt_disabled+0xe/0x10 [ 1088.798431] __mutex_lock.isra.5+0x276/0x4e0 [ 1088.798435]
[Kernel-packages] [Bug 1936899] Re: [IoTG] [TGL-H] TPM tests fail
** Also affects: linux-intel (Ubuntu) Importance: Undecided Status: New -- 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/1936899 Title: [IoTG] [TGL-H] TPM tests fail Status in intel: New Status in linux-intel package in Ubuntu: New Bug description: [Summary]TPM tests from CDTS 20 automated fail [Steps to reproduce]Run cdts.odm_certification, select TPM [Expected result]All tests should pass. [Actual result] Failed Jobs (TPM 2.0): tpm2.0_4.1.1/tpm2_clockratedadjust tpm2.0_4.1.1/tpm2_createprimary tpm2.0_4.1.1/tpm2_import tpm2.0_4.1.1/tpm2_loadexternal Jobs with failed dependencies tpm2.0_4.1.1/tpm2_rc_decode [Failure rate]100% [Additional information] CID: 202106-29175 SKU: system-manufacturer: Intel Corporation system-product-name: Tiger Lake Client Platform bios-version: TGLIFUI1.R00.3455.A03.2011281547 CPU: Genuine Intel(R) CPU @ 2.60GHz (16x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a60] kernel-version: 5.11.0-1009-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1936899/+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 1939376] Re: 'Synaptics Touchpad' suddenly stopped working without any update on 'Lenovo Thinkbook IML 15'
** Package changed: ubuntu => linux-signed-hwe-5.11 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939376 Title: 'Synaptics Touchpad' suddenly stopped working without any update on 'Lenovo Thinkbook IML 15' Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: My touchpad has suddenly stopped working on 'Lenovo Thinkbook IML 15'. Its not a hardware issue because touchpad is working on my Windows OS. I didn't install any update when this issue appeared. Touchpad device is also not showing up in `xinput --list` and `/proc/bus/input/devices`. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 10 11:42:39 2021 InstallationDate: Installed on 2020-12-09 (243 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939376/+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 1935017] Re: Possible io_uring regression with QEMU on Ubuntu's kernel
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1935017 Title: Possible io_uring regression with QEMU on Ubuntu's kernel Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: Fix Released Bug description: Hi everyone. Possible io_uring regression with QEMU on Ubuntu's kernel With the latest Ubuntu 20.04's HWE kernel 5.8.0-59, I'm noticing some weirdness when using QEMU/libvirt with the following storage configuration: QEMU version is 5.2+dfsg-9ubuntu3 and libvirt version is 7.0.0-2ubuntu2. The guest VM is unable to handle I/O properly with io_uring, and nuking io="io_uring" fixes the issue. On one machine (EPYC 7742), the partition table cannot be read and on another (Ryzen 9 3950X), ext4 detects weirdness with journaling and ultimately remounts the guest disk to R/O: [2.712321] virtio_blk virtio5: [vda] 3906519775 512-byte logical blocks (2.00 TB/1.82 TiB) [2.714054] vda: detected capacity change from 0 to 2000138124800 [2.963671] blk_update_request: I/O error, dev vda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [2.964909] Buffer I/O error on dev vda, logical block 0, async page read [2.966021] blk_update_request: I/O error, dev vda, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [2.967177] Buffer I/O error on dev vda, logical block 1, async page read [2.968330] blk_update_request: I/O error, dev vda, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [2.969504] Buffer I/O error on dev vda, logical block 2, async page read [2.970767] blk_update_request: I/O error, dev vda, sector 3 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [2.971624] Buffer I/O error on dev vda, logical block 3, async page read [2.972170] blk_update_request: I/O error, dev vda, sector 4 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [2.972728] Buffer I/O error on dev vda, logical block 4, async page read [2.973308] blk_update_request: I/O error, dev vda, sector 5 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [2.973920] Buffer I/O error on dev vda, logical block 5, async page read [2.974496] blk_update_request: I/O error, dev vda, sector 6 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [2.975093] Buffer I/O error on dev vda, logical block 6, async page read [2.975685] blk_update_request: I/O error, dev vda, sector 7 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [2.976295] Buffer I/O error on dev vda, logical block 7, async page read [2.980074] blk_update_request: I/O error, dev vda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [2.981104] Buffer I/O error on dev vda, logical block 0, async page read [2.981786] blk_update_request: I/O error, dev vda, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [2.982083] ixgbe :06:00.0: Multiqueue Enabled: Rx Queue count = 63, Tx Queue count = 63 XDP Queue count = 0 [2.982442] Buffer I/O error on dev vda, logical block 1, async page read [2.983642] ldm_validate_partition_table(): Disk read failed. Kernel 5.8.0-55 is fine, and the only io_uring-related change between 5.8.0-55 and 5.8.0-59 is the commit 4b982bd0f383 ("io_uring: don't mark S_ISBLK async work as unbounded"). I'm hesitant to run lspci -vnvn and post other bug reporting logs as the machine includes some proprietary hardware (quite unrelated to this specific issue), but this issue is reproducible on multiple machines. The another machine that I was able to reproduce this is running a production software that needs to run 24/7, so I'm also hesitant to gather logs there too. Thanks, Regards Update: It was the commit 87c9cfe0fa1fb ("block: don't ignore REQ_NOWAIT for direct IO"). (Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5) I've double checked by resetting the Git to Ubuntu-hwe-5.8-5.8.0-59.66_20.04.1 and reverting that patch alone. It fixes the issue. It seems like this patch was backported to multiple stable trees, so I'm not exactly sure why only Canonical's 5.8 is affected. FWIW, 5.8.0-61 is also affected. To manage notifications
[Kernel-packages] [Bug 1939376] [NEW] 'Synaptics Touchpad' suddenly stopped working without any update on 'Lenovo Thinkbook IML 15'
You have been subscribed to a public bug: My touchpad has suddenly stopped working on 'Lenovo Thinkbook IML 15'. Its not a hardware issue because touchpad is working on my Windows OS. I didn't install any update when this issue appeared. Touchpad device is also not showing up in `xinput --list` and `/proc/bus/input/devices`. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 10 11:42:39 2021 InstallationDate: Installed on 2020-12-09 (243 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 'Synaptics Touchpad' suddenly stopped working without any update on 'Lenovo Thinkbook IML 15' https://bugs.launchpad.net/bugs/1939376 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. -- 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 1937144] Re: The front mic can't be detected on a lenovo thinkstation machine
Installed the proposed kernel on the machine, reboot, and plug a headest to the front mic audio jack, the mic could be detected and could record sound via it. Verified done. ** 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-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1937144 Title: The front mic can't be detected on a lenovo thinkstation machine Status in HWE Next: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: The patch is sent to oem-5.10 first, and other ubuntu kernels will merge this patch with stable update since this patch was already CCed to stable. [Impact] Users plug a headset or microphone to the front mic jack, but the system can't detect the plug and will not set the mic to be the active input device. [Fix] Backport a upstream patch, this will change the front mic jack's name from Front Mic to Mic, then the pulseaudio could handle the plug/unplug. [Test] Plug a headset to the front mic jack, open the gnome-sound-setting, the front mic is the active input device, use this device to record sound, it could record the sound successfully. [Where problems could occur] It could make the other mic can't be detected, but this possibility is very low and I alreaed tested all audio jacks on that machine, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937144/+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 1935853] Re: Fix second monitor hotplug on Intel TGP PCH
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1935853 Title: Fix second monitor hotplug on Intel TGP PCH Status in HWE Next: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: [Impact] Intel TGP dekstop cannot detect second monitor. [Fix] Remove an IRQ setup routine and re-order some other IRQ setups. [Test] 1. Boot up the system with single monitor connected. 2. Hotplug second monitor. With the fix applied, the system can detect the 2nd monitor correctly. [Where problems could occur] This fix removed some special handling for early gen Core, so HPD on those old Core systems might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1935853/+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 1936921] Re: While screen while vt switching with AMD W5700 or W5500
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1936921 Title: While screen while vt switching with AMD W5700 or W5500 Status in HWE Next: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: [Impact] Ubuntu-oem-5.10-5.10.0-1027.28 includes some amdgpu patches to support s2idle feature, but it leads to the white screen while vt switching during booting up. [Fix] After bisect the kernel, we need below commit to fix this issue. 0b08c54bb7a37 drm/amd/display: Fix the display corruption issue on Navi10 [Test] Verified on Dell machine with AMD W5700 graphics card. [Where problems could occur] Hard to evaluate, but there is no further code modification on this part since 10/20/2020, and no "Fixes:" on this commit, so it should be stable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936921/+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 1937144] Re: The front mic can't be detected on a lenovo thinkstation machine
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1937144 Title: The front mic can't be detected on a lenovo thinkstation machine Status in HWE Next: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: The patch is sent to oem-5.10 first, and other ubuntu kernels will merge this patch with stable update since this patch was already CCed to stable. [Impact] Users plug a headset or microphone to the front mic jack, but the system can't detect the plug and will not set the mic to be the active input device. [Fix] Backport a upstream patch, this will change the front mic jack's name from Front Mic to Mic, then the pulseaudio could handle the plug/unplug. [Test] Plug a headset to the front mic jack, open the gnome-sound-setting, the front mic is the active input device, use this device to record sound, it could record the sound successfully. [Where problems could occur] It could make the other mic can't be detected, but this possibility is very low and I alreaed tested all audio jacks on that machine, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937144/+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 1939349] Re: frequent hangs with latest hirsute kernel (nvidia graphics)
I probably would first suggest to try the proposed 5.11.0-26 from this cycle. The other path which might be useful (but I do not know whether this is possible with the HW) would be to attempt a bit with the nouveau driver. That might separate whether this is in Nvidia or the kernel. Generally fast spinning fans sound like a spinlock problem. But this could as well be caused by a crash somewhere with a lock taken. Or a hand for other reasons, again while being in a lock section. I suspect Steve already checked previous boot logs and did not find any useful message. That makes it hard to put a finger somewhere. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939349 Title: frequent hangs with latest hirsute kernel (nvidia graphics) Status in linux package in Ubuntu: New Bug description: After upgrading to the latest kernel, I am experiencing frequent kernel hangs. The system does not respond to Alt+SysRq, and I have to power it off. In some cases the hang happens before X has even been launched at boot. When it hangs, the fan spins up to full speed. 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 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vorlon10452 F pulseaudio /dev/snd/controlC0: vorlon10452 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 9 14:15:58 2021 InstallationDate: Installed on 2019-12-23 (594 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_di672m@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_di672m ro quiet splash vt.handoff=1 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: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2019 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET40W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 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.19 dmi.modalias: dmi:bvnLENOVO:bvrN2OET40W(1.27):bd10/17/2019:br1.27:efr1.19:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939349/+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 1939178] Re: Bluetooth not working after an update
What was the last working kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939178 Title: Bluetooth not working after an update Status in linux package in Ubuntu: New Bug description: Bluetooth not working after an update. 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/controlC1: yinka 2369 F pulseaudio /dev/snd/controlC0: yinka 2369 F pulseaudio /dev/snd/controlC2: yinka 2369 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 22:29:07 2021 InstallationDate: Installed on 2021-04-16 (112 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=a4150dca-83c9-4b4d-8376-b13fbd5c172f ro quiet splash 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2020 dmi.bios.release: 1.49 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.49 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 21.89 dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.49:bd02/24/2020:br1.49:efr21.89:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.sku: K5T62UP#ABA dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939178/+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 1934410] Re: Second Monitor shuts off.
** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934410 Title: Second Monitor shuts off. Status in linux package in Ubuntu: Incomplete Bug description: I'm running two identical monitors daisy-chained via my DV port on my NUC10i7. The second monitor shuts down with a no signal error message, though the system still seems to see it. If I change it's refresh rate it will come back but, depending on the software I'm using, goes into low power mode and blanks off again. Sometimes randomly. Always when starting video conferencing software (e.g. zoom or webex). Today when using abd and fastboot from the command line in a terminal window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934410/+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 1939178] Re: Bluetooth not working after an update
I typed this in the terminal - ($ dpkg -l linux- modules-5.11.0-25-generic) this is the result Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=== ii linux-modules-5.11.0-25-generic 5.11.0-25.27 amd64Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939178 Title: Bluetooth not working after an update Status in linux package in Ubuntu: New Bug description: Bluetooth not working after an update. 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/controlC1: yinka 2369 F pulseaudio /dev/snd/controlC0: yinka 2369 F pulseaudio /dev/snd/controlC2: yinka 2369 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 22:29:07 2021 InstallationDate: Installed on 2021-04-16 (112 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=a4150dca-83c9-4b4d-8376-b13fbd5c172f ro quiet splash 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2020 dmi.bios.release: 1.49 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.49 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 21.89 dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.49:bd02/24/2020:br1.49:efr21.89:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.sku: K5T62UP#ABA dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939178/+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 1928878] Re: [ASUS X450L] Touchpad suddenly not responding
If possible, can you please give 5.4.0-80.90 a go? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1928878 Title: [ASUS X450L] Touchpad suddenly not responding Status in linux package in Ubuntu: Incomplete Bug description: After leaving my laptop on sleep mode for a while, then bringing it up again causes the touchpad to stop responding completely. Checked for it in the bus/input/devices folder and didn't see it. Laptop model: ASUS X450L Touchpad manufacturer: I presume to also be ASUS Symptom first appeared less than a week ago. EDIT: Forgot to mention, the touchpad comes back after a restart. Touchpad info is as follows: Bus=0011 Vendor=0002 Product=000e Version= Name="ETPS/2 Elantech Touchpad" Phys=isa0060/serio1/input0 Sysfs=/devices/platform/i8042/serio1/input/input5 Uniq= Handlers=mouse0 event4 PROP=5 EV=b KEY=e420 1 0 0 0 0 ABS=66180001103 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-73-generic 5.4.0-73.82 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: luiz 1541 F pulseaudio /dev/snd/controlC0: luiz 1541 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 18 21:15:53 2021 InstallationDate: Installed on 2018-10-11 (950 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. X450LCP ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=3aa08318-3527-4824-a97a-cc0084649c15 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-18 (181 days ago) dmi.bios.date: 02/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X450LCP.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X450LCP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX450LCP.206:bd02/20/2014:svnASUSTeKCOMPUTERINC.:pnX450LCP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX450LCP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X450LCP dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
Can you please give this kernel a try: https://people.canonical.com/~khfeng/lp1938096/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend Status in linux package in Ubuntu: New Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from the impish repos. To recreate: 1. Reboot a X1C9 machine and see that the touchpad works fine 2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a software suspend) 3. Resume from suspend and see that touchpad acts differently and less responsive than right after a clean boot What is expected: 1. Same responsive touchpad experience after resuming from suspend as right after a clean boot. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Pop!_OS 21.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] MachineType: LENOVO 20XW005PMX Package: libinput10 1.18.0-1 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet systemd.show_status=false loglevel=0 splash Tags: hirsute third-party-packages ubuntu Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: This does not seem to be an official Pop!_OS package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 06/15/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET66W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW005PMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW005PMX dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938096/+subscriptions -- 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