[Kernel-packages] [Bug 2008672] [NEW] focal linux-xilinx-zynqmp promote from universe to main
Public bug reported: focal linux-xilinx-zynqmp promote from universe to main new kernel published in the wrong component. ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2008672 Title: focal linux-xilinx-zynqmp promote from universe to main Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: focal linux-xilinx-zynqmp promote from universe to main new kernel published in the wrong component. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2008672/+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 2004491] Re: [23.04 FEAT] KVM: Enablement of device busid for subchannels
Since this got upstream accepted with v5.15 - this can be set to Fix Released already now - and btw. not only for lunar (planned target kernel 6.2), but also for kinetic (5.19) as well as for jammy (5.15). ** Also affects: linux (Ubuntu Lunar) Importance: High Assignee: Skipper Bug Screeners (skipper-screen-team) Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Released ** Changed in: ubuntu-z-systems Status: In Progress => Fix Released ** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004491 Title: [23.04 FEAT] KVM: Enablement of device busid for subchannels Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Feature Description Before kernel 5.15 and libvirt 8.4 it was not possible to know a CCW device bus ID (devno) if the device is unbound from its 'proper' device driver (e.g. dasd-eckd), which is the case if a CCW device is passed through to a KVM guest. This places an unnecessary burden on VM admins, as they have to keep track of the mapping between a subchannel id and the bus id manually, outside of the KVM management stack. Notes: With kernel 5.15 an additional sysfs property 'dev_busid' was added to the sysfs entry for subchannels which is exposed by libvirt 8.4 and higher. These changes were done in the context of maintainership activities, but with newer libvirt versions included, it makes sense to also include the patch in distro releases. The commit is https://github.com/torvalds/linux/commit/d3683c055212bf910d4e318f7944910ce10dbee6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2004491/+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 2008466] Re: [HP ENVY x360 Convertible 15-ee0xxx] Will not wake up from suspend using kernel 5.19 (but 5.15 works)
** Summary changed: - Will not wake up from suspend. + [HP ENVY x360 Convertible 15-ee0xxx] Will not wake up from suspend using kernel 5.19 (but 5.15 works) ** Package changed: linux (Ubuntu) => linux-hwe-5.19 (Ubuntu) ** Tags added: regression-release ** Tags added: suspend-resume -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008466 Title: [HP ENVY x360 Convertible 15-ee0xxx] Will not wake up from suspend using kernel 5.19 (but 5.15 works) Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: HP laptop Ryzen 7 4700 with Renoir graphics. Close lid which puts system into suspend. After say 20 mins open laptop, keyboard backlight comes on but system does not wake up. Have to force a power off. It works OK after only a few mins in suspend. Sames on mains or battery. Problem does not exist using kernel 5.15.0-60-generic. Problem started on upgrade to 5.19.0-32-generic. Tried switching between X-org and Wayland and disabled TPM in BIOS without any change. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 24 09:32:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:876f] InstallationDate: Installed on 2022-09-12 (164 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP ENVY x360 Convertible 15-ee0xxx ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-mono PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=d3454052-ab9f-432c-88bb-477464dd3c93 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2022 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 876F dmi.board.vendor: HP dmi.board.version: 13.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 13.47 dmi.modalias: dmi:bvnInsyde:bvrF.22:bd11/03/2022:br15.22:efr13.47:svnHP:pnHPENVYx360Convertible15-ee0xxx:pvrType1ProductConfigId:rvnHP:rn876F:rvr13.47:cvnHP:ct31:cvrChassisVersion:sku9QZ65EA#ABU: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-ee0xxx dmi.product.sku: 9QZ65EA#ABU dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2008466/+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 2006042] Re: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram
Ordinarily we would ask that a separate bug be opened for each model of laptop but it's suspicious this keeps being reported on ASUS ZenBooks: UX430UAR, UM425QA: bug 2006042 UX325EA: bug 2006038 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006042 Title: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram Status in linux package in Ubuntu: Confirmed Bug description: Hi, After waking up from suspend to RAM, my computer actually wakes up but can sometimes then hang on a black screen (no prompt, nothing displayed, screen is active). This issue happens quite frequently but seems rather random. I think certain circumstances lower the frequency (I'll elaborate in the report). First of all, I'm not exactly sure when it started but I would say first notable frequent occurrences were around summer 2021 (yes, I'm late, sorry for that). When this happens, Algr+SysRQ+[usb] is unresponsive. Or at least that's what I used to believe as it used to be true as I always tried from the laptop integrated keyboard. Until I connected an USB-C mechanical keyboard, from which I'm *sometimes* able to use the magic keys (not always, and with a lot of lag, but still). If magic keys are unresponsive, I need to hard reset/long press power. There is nothing unusual before that in syslog nor kern.log, at least not that I know of. Except the ^@^@^@ characters when I had to hard reset the computer. If I leave the laptop like that for a while, it eventually reboots by itself and stays on the FDE passphrase prompt (which is not nice as the screen can then stay on for a very long like that if I did not notice). I'm running KDE/Plasma desktop, and this issue has happened regardless of the display manager. I used to run Xorg but now I'm on wayland flavor (mostly to alleviate firefox rendering/compositing issues). This also seems unrelated to external screen being connected or not, as it happened in the past regardless of that parameter. Although, it *seems* frequency has lowered a bit since I changed the way I wake up my laptop. Higher frequency (almost every day): - no external screen or external screen connected to HDMI port - waking up from integrated keyboard power button short press Lower frequency (one to multiple times a week, but somewhat irregular, since ~ 2 months ago): - external screen connected to USB-C port - mechanical keyboard connected to USB-C port of screen - waking up from the mechanical keyboard It also seems to happen more frequently if I wake up the computer, do some very fast task and send it to sleep in under a few minutes. It's not guaranteed to happen, but seems to highly increase the probability. Also, this might be related so I'm adding that bit: I had to disable shutting the screen Off in energy saving settings, as enabling that option would trigger a similar behavior after a break long enough for that setting to trigger. I would come back on a laptop having self-rebooted and waiting for my input on the FDE passphrase prompt. During ACPI options testing, I noticed that setting might cause the sleep order to get cancelled. From that, I suspect in that case the laptop would go to sleep, then wake up immediately, which could have been triggering the bug as I described previously that rapid state changes would increase probability. Then as I described earlier, if I do nothing when this happens, the computer eventually reboots. This is only speculation as I'm usually not here to observe the behavior (this mostly happened during lunch breaks, which are long enough for all of these steps to happen). I disabled screen turn-off energy saving option a long while ago and have taken the habit of manually suspending to RAM when I intend on going away from the computer for more than a few minutes. As I described above, I've tried a few changes to check for behavior but that was a few months ago and I don't clearly remember all scenario. What I remember is that changing any of these did not resolve my issue and some even prevented my computer to even suspend to RAM properly (waking up immediately after). Among the options I tried is: - booting with a previous kernel, but then it's been happening for so long this would obviously not work (just for the sake of completion) - booting on latest mainstream kernel (tested linux-image-unsigned-6.0.9-060009-generic, this was the latest version when I tried a while ago) - booting with i915.enable_dpcd_backlight=3 (I think this one triggered the immediate wake up) - booting with nolapic, noapic (didn't try acpi=off nor acpi=ht as it seems to me it would disable suspend to RAM feature, right?) I think that's about it, and I'd be happy to try any suggestion. ProblemType: Bug
[Kernel-packages] [Bug 2007729] Re: HP Probook 450 G8 Intel i5-1135G7 with Intel Wireless-AC 9560 wifi driver not working
There appears to be a bug filed for kernel 5.15 aswell: https://bugs.launchpad.net/ubuntu/jammy/+source/linux- firmware/+bug/1966793, did i file for the wrong package? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007729 Title: HP Probook 450 G8 Intel i5-1135G7 with Intel Wireless-AC 9560 wifi driver not working Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: this forum post, https://community.intel.com/t5/Wireless/Linux-Intel- AC-9560-iwlwifi-fails-on-kernels-above-5-10/m-p/1377826#M41506, appears to mention that QuZ-a0-jf-b0-64.ucode has this problem but QuZ-a0-jf-b0-59.ucode does not. taking a look in /lib/firmware i see the following: iwlwifi-QuZ-a0-jf-b0-48.ucode iwlwifi-QuZ-a0-jf-b0-63.ucode iwlwifi-QuZ-a0-jf-b0-50.ucode iwlwifi-QuZ-a0-jf-b0-66.ucode iwlwifi-QuZ-a0-jf-b0-53.ucode iwlwifi-QuZ-a0-jf-b0-68.ucode iwlwifi-QuZ-a0-jf-b0-55.ucode iwlwifi-QuZ-a0-jf-b0-71.ucode iwlwifi-QuZ-a0-jf-b0-59.ucode iwlwifi-QuZ-a0-jf-b0-72.ucode iwlwifi-QuZ-a0-jf-b0-62.ucode it appears to be loading iwlwifi-QuZ-a0-jf-b0-72.ucode and failing. i have removed the these entries one by one, followed by modprobe -r iwlwifi && modprobe iwlwifi untill i have found a working one, which turns out to be iwlwifi-QuZ-a0-jf-b0-55.ucode ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 17:57:08 2023 InstallationDate: Installed on 2022-05-12 (281 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 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.19/+bug/2007729/+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 1966793] Re: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
This seems to be a an issue on 5.19 aswell jonathan's workaround works but doing that after every kernel upgrade, including within 5.15 is cumbersome. I have filed a separate bug report for 5.19 with ubuntu-bug linux, feedback if there's any additional information i can provide is appreciated So far i've found this is a regression from 5.10 -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi
[Kernel-packages] [Bug 2006994] Re: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep
UPDATE RE: i915.enable_psr=0 Yes, this kernel parameter solves the problem - WHEN - the laptop runs off it's internal battery. As soon as I plug the power cable in and issue a >> systemctl suspend << command, the screen will go blank, however, the system will not go into sleep: the keyboard backlight will stay on and will fade after a while; if I touch the touchpad or any key on the keyboard, the backlight will turn back on; moreover, sometimes the keyboard backlight just stays on constantly, does not fade away; the power button will have it's led on, won't turn off and I can hear the system is somewhat still running - as in: it does not become 100% quiet, some electricity is still in use. So, this kernel module is only a partial solution. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006994 Title: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Scenario: Fresh and clean Ubuntu 22.10 install on Latitude 7390, requiring nomodeset kernel boot option to be added in GRUB at boot time when booting from USB stick. This can be achieved by following instructions from here: https://www.dell.com/support/kbdoc/en-uk/000123893/manual- nomodeset-kernel-boot-line-option-for-linux-booting Then, nomodeset needs to be permanently added to /etc/default/grub Followed instructions from https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu If nomodeset is not added, Dell Latitude 7390 will freeze at one point or another, either before reaching the Gnome desktop, either little after. This is the case with both, installing Ubuntu 22.10 from Live USB and running Ubuntu 22.10 after install the install (and having the USB stick disconnected). The issue after having Ubuntu 22.10 installed on Dell Latitude 7390 and having nomodeset permanently added to GRUB for each boot is: If by chance the system goes into sleep, after waking up, there is a totally pitch-black screen; nothing shows up, no screen backlight either. However, caps-lock works and I am able to log in to the system via ssh and can see the system is up an running well. I can even issue a request to send the system to sleep by “sudo systemctl suspend” and then wake the the system up several times without loosing ssh access, however, the screen will remain pitch-black. Other tries to troubleshoot and see if the system can be brought back with a working display (while nomodeset kernel option is being used): 1. sudo systemctl suspend -i >>> this will result in an unusable system after waking up, again, with a pitch-black screen; moreover, the caps-lock would not work, the keyboard backlight won’t work, ssh won’t work; I need a hard reset to get the system back up. 2. start the system in single user mode by inserting “single” in GRUB at boot time; >>> the system will be unusable after waking up, same as in try 1. 3. after a normal boot into the GNOME desktop with kernel nomodeset option and investigating the dmesg for any acpi, no error could be found. Tried to read up on other possible solutions, while stumbled upon the ubuntu wiki page below: https://wiki.ubuntu.com/UnderstandingSuspend Unfortunately, to not much help so far. Other notes: N1. All the above were done by having the latest BIOS v1.30.0 N2. This laptop came with Windows 10 Pro which works fine: goes into suspend and wakes up fine, with working screen and display. N3. Dell Latitude 7390 was released on 15 Feb 2018 ( source: https://www.laptoparena.net/dell/notebook-dell-latitude-7390-n025l739013emea-black-12984 ) and the user manual states it has support for Ubuntu. Therefore, other older and major Ubuntu versions were given a try, along with a new version of Fedora: N3.1 – Ubuntu 22.04 N3.2 – Ubuntu 18.04.6 N3.3 – Ubuntu 16.04.7 N3.4 – Fedora-Workstation-Live-x86_64-37-1.7 Each of the above will freeze at one point or another if nomodeset is not used, except the Ubuntu 18.04.6 and Ubuntu 16.04.7 which will run well and install well from the USB Live stick and will also run fine after the install, until the system goes into sleep, after which, when the system is awake, the screen is black and will have nothing displayed. Any advice will be appreciated. Thank you! ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuser 2832 F
[Kernel-packages] [Bug 1960016] Re: | Kernel 5.15 Regression | ' Bluetooth: hci0: command tx timeout '
Not a huge fan of copy-pasta but this may be more useful here. +1 AX200 ``` 07:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084] Kernel driver in use: iwlwifi Kernel modules: iwlwifi ``` ``` [ 25.711840] Bluetooth: Core ver 2.22 [ 25.711860] NET: Registered PF_BLUETOOTH protocol family [ 25.711861] Bluetooth: HCI device and connection manager initialized [ 25.711864] Bluetooth: HCI socket layer initialized [ 25.711866] Bluetooth: L2CAP socket layer initialized [ 25.711869] Bluetooth: SCO socket layer initialized [ 25.788390] iwlwifi :07:00.0: loaded firmware version 66.f1c864e0.0 cc-a0-66.ucode op_mode iwlmvm [ 27.783372] Bluetooth: hci0: command 0xfc05 tx timeout [ 27.783378] Bluetooth: hci0: Reading Intel version command failed (-110) [ 28.785728] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 28.785731] Bluetooth: BNEP filters: protocol multicast [ 28.785733] Bluetooth: BNEP socket layer initialized ``` ``` celiyah@darkunicorn:~$ sudo systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2023-02-26 16:43:43 CST; 12min ago Docs: man:bluetoothd(8) Main PID: 28973 (bluetoothd) Status: "Running" Tasks: 1 (limit: 76959) Memory: 668.0K CPU: 38ms CGroup: /system.slice/bluetooth.service └─28973 /usr/lib/bluetooth/bluetoothd ``` ``` celiyah@darkunicorn:~$ bluetoothctl Agent registered [bluetooth]# scan on No default controller available quitetooth]# ``` It's popping up in Ubuntu forums e.g. https://askubuntu.com/questions/1448731/bluetooth-not-working-no-controller-available | Reloading `btusb` module several times makes it working. Any specific steps for this? I have not been able to get it to work. Issue persists despite reboots incl. hard power off/on. This happened suddenly. ``` celiyah@darkunicorn:~$ uname -a Linux darkunicorn 5.15.0-56-lowlatency #62-Ubuntu SMP PREEMPT Wed Nov 23 09:50:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux celiyah@darkunicorn:~$ lsmod | grep bt btusb 61440 0 btrtl 24576 1 btusb btbcm 24576 1 btusb btintel40960 1 btusb bluetooth 708608 12 btrtl,btintel,btbcm,bnep,btusb ``` (I believe the bleeding cutting edge 23.04.1 is the only available bunty release with a 6 kernel line. Could be wrong.) Note the workaround in the askubuntu question: https://askubuntu.com/a/1456898/253482 (for transparency, I'm linking to my own answer). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960016 Title: | Kernel 5.15 Regression | ' Bluetooth: hci0: command tx timeout ' Status in linux package in Ubuntu: Confirmed Bug description: With the current daily-build of 'jammy 22.04' it is not possible to enable Bluetooth with (some) Intel Bluetooth devices after reboot/warm boot. With a Cold boot it is working. My hardware: $ lsusb Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface This is because of a regression in Kernel 5.15 and was present in Fedora and other Distributions as well. https://bugzilla.redhat.com/show_bug.cgi?id=2027071 https://bugzilla.opensuse.org/show_bug.cgi?id=1193124 For example on Fedora35 my Bluetooth did not initialize correctly after warm boot between versions 5.14.18 > 5.15.14. After a cold boot it worked. (Turned off the desktop PC and disconnected it from power for a few seconds.) Kernel 5.15.15 changed that and since then everything went fine again. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848 The fix is mentioned there… https://lore.kernel.org/lkml/246bd180-4d8f-ae2b-1b51-90eaf1948...@leemhuis.info/T/#m77ab9e84eec72d1b3e16d6862ffb1a2670277d94 Direct-Link to commit mentioned in the above discussion… https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic-hwe-20.04 5.15.0.18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 4 12:26:46 2022 InstallationDate: Installed on 2022-02-02 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220201) MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1960016] Re: | Kernel 5.15 Regression | ' Bluetooth: hci0: command tx timeout '
Yes.. I'm a little confused. For example the previously mentioned thread (id=215167) is still very much ongoing, with some people reporting that certain kernel versions fix this and others reporting it showing up in regressions as late as 6.2. They referenced a message https://lore.kernel.org/all/20211202162256.31837-1-ti...@suse.de/ refers to commit 95655456e7cee858a23793f67025765b4c4c227b upstream, which was merged into 5.16 mainline last year. https://lkml.org/lkml/2022/1/14/195 -- I will post back in the bugzilla thread later that this seems to be unrelated. I believe on the Ubuntu side patching from 5.11 to 5.15 caused this problem for me. And it would appear that 5.19 has it as well. But needless to say in "stable LTS" (22.04.2/5.15) this is still happening, breaking bluetooth for Ubuntu users. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960016 Title: | Kernel 5.15 Regression | ' Bluetooth: hci0: command tx timeout ' Status in linux package in Ubuntu: Confirmed Bug description: With the current daily-build of 'jammy 22.04' it is not possible to enable Bluetooth with (some) Intel Bluetooth devices after reboot/warm boot. With a Cold boot it is working. My hardware: $ lsusb Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface This is because of a regression in Kernel 5.15 and was present in Fedora and other Distributions as well. https://bugzilla.redhat.com/show_bug.cgi?id=2027071 https://bugzilla.opensuse.org/show_bug.cgi?id=1193124 For example on Fedora35 my Bluetooth did not initialize correctly after warm boot between versions 5.14.18 > 5.15.14. After a cold boot it worked. (Turned off the desktop PC and disconnected it from power for a few seconds.) Kernel 5.15.15 changed that and since then everything went fine again. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848 The fix is mentioned there… https://lore.kernel.org/lkml/246bd180-4d8f-ae2b-1b51-90eaf1948...@leemhuis.info/T/#m77ab9e84eec72d1b3e16d6862ffb1a2670277d94 Direct-Link to commit mentioned in the above discussion… https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic-hwe-20.04 5.15.0.18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 4 12:26:46 2022 InstallationDate: Installed on 2022-02-02 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220201) MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=91d2d15b-9614-4498-bb5c-d3376034009f ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220124.git0c6a7b3b-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F51d dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF51d:bd12/13/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960016/+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 2000491] Re: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-recoverable after screen lock and screen completely fades to black or after system goes into slee
Hey everyone! For anyone who is experiencing these same issues, a handy solution has been found by Benjamin Renard, see his comment #6 on: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006994 Or, directly via https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006994/comments/6 Any updates and other ideas solutions are welcome here! :) Have a great week! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2000491 Title: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non- recoverable after screen lock and screen completely fades to black or after system goes into sleep Status in linux-hwe-5.4 package in Ubuntu: Invalid Bug description: This is a fresh install of Ubuntu 18.04.6 on Dell Latitude 7390. The system is non-recoverable after it goes into sleep. Or after the screen is locked by the user and after it fades to complete black. System becomes unresponsive, no mouse or keypress will get the system back on to work. If the systemctl suspend is issued, the system will not wake up again. Hard reset is needed. If Ubuntu 18.04.6 is booted from live USB, the same is happening. Sometimes, when the system is rendered unresponsive as a result of any of the above, the power led is sending the message of "processor failure" (2 x amber blinks followed by 1 x white blink). Any help is greatly appreciated! I will keep the system as is, without applying any updates for now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 27 01:13:12 2022 InstallationDate: Installed on 2022-12-26 (0 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2000491/+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 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
Thank you for this, Benjamin Renard! I have tried this and indeed, the problem is gone. I only have the laptop, no additional displays attached, however, it works fine! Until the problem is 100% solved by someone, I will just use the "i915.enable_psr=0" kernel parameter at boot time. For anyone who is looking to do the same, just follow the steps after >>> Solution – Part II (Permanent "nomodeset" option) <<< from https://www.dell.com/support/kbdoc/en-uk/000123893/manual- nomodeset-kernel-boot-line-option-for-linux-booting and replace "nomodeset" with i915.enable_psr=0 Any other updates to this issue are appreciated here! :) Have a great week! PS: a more transparent and better written bug report can be found here -> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006994 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+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 2006994] Re: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep
Thank you for this, Benjamin Renard! I have tried this and indeed, the problem is gone. I only have the laptop, no additional displays attached, however, it works fine! Until the problem is 100% solved by someone, I will just use the "i915.enable_psr=0" kernel parameter at boot time. For anyone who is looking to do the same, just follow the steps after >>> Solution – Part II (Permanent "nomodeset" option) <<< from https://www.dell.com/support/kbdoc/en-uk/000123893/manual- nomodeset-kernel-boot-line-option-for-linux-booting and replace "nomodeset" with i915.enable_psr=0 Any other updates to this issue are appreciated here! :) Have a great week! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006994 Title: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Scenario: Fresh and clean Ubuntu 22.10 install on Latitude 7390, requiring nomodeset kernel boot option to be added in GRUB at boot time when booting from USB stick. This can be achieved by following instructions from here: https://www.dell.com/support/kbdoc/en-uk/000123893/manual- nomodeset-kernel-boot-line-option-for-linux-booting Then, nomodeset needs to be permanently added to /etc/default/grub Followed instructions from https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu If nomodeset is not added, Dell Latitude 7390 will freeze at one point or another, either before reaching the Gnome desktop, either little after. This is the case with both, installing Ubuntu 22.10 from Live USB and running Ubuntu 22.10 after install the install (and having the USB stick disconnected). The issue after having Ubuntu 22.10 installed on Dell Latitude 7390 and having nomodeset permanently added to GRUB for each boot is: If by chance the system goes into sleep, after waking up, there is a totally pitch-black screen; nothing shows up, no screen backlight either. However, caps-lock works and I am able to log in to the system via ssh and can see the system is up an running well. I can even issue a request to send the system to sleep by “sudo systemctl suspend” and then wake the the system up several times without loosing ssh access, however, the screen will remain pitch-black. Other tries to troubleshoot and see if the system can be brought back with a working display (while nomodeset kernel option is being used): 1. sudo systemctl suspend -i >>> this will result in an unusable system after waking up, again, with a pitch-black screen; moreover, the caps-lock would not work, the keyboard backlight won’t work, ssh won’t work; I need a hard reset to get the system back up. 2. start the system in single user mode by inserting “single” in GRUB at boot time; >>> the system will be unusable after waking up, same as in try 1. 3. after a normal boot into the GNOME desktop with kernel nomodeset option and investigating the dmesg for any acpi, no error could be found. Tried to read up on other possible solutions, while stumbled upon the ubuntu wiki page below: https://wiki.ubuntu.com/UnderstandingSuspend Unfortunately, to not much help so far. Other notes: N1. All the above were done by having the latest BIOS v1.30.0 N2. This laptop came with Windows 10 Pro which works fine: goes into suspend and wakes up fine, with working screen and display. N3. Dell Latitude 7390 was released on 15 Feb 2018 ( source: https://www.laptoparena.net/dell/notebook-dell-latitude-7390-n025l739013emea-black-12984 ) and the user manual states it has support for Ubuntu. Therefore, other older and major Ubuntu versions were given a try, along with a new version of Fedora: N3.1 – Ubuntu 22.04 N3.2 – Ubuntu 18.04.6 N3.3 – Ubuntu 16.04.7 N3.4 – Fedora-Workstation-Live-x86_64-37-1.7 Each of the above will freeze at one point or another if nomodeset is not used, except the Ubuntu 18.04.6 and Ubuntu 16.04.7 which will run well and install well from the USB Live stick and will also run fine after the install, until the system goes into sleep, after which, when the system is awake, the screen is black and will have nothing displayed. Any advice will be appreciated. Thank you! ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuser 2832 F wireplumber /dev/snd/seq:tuser 2829 F pipewire CRDA: N/A CasperMD5CheckResult: pass
[Kernel-packages] [Bug 1199401] Re: Modify UEFI anti-bricking code
O objetivo do gerador de CNPJ é gerar CNPJ para teste de software. https://geradordecnpj.org/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1199401 Title: Modify UEFI anti-bricking code Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux source package in Quantal: Fix Released Status in linux source package in Raring: Fix Released Bug description: Ubuntu kernels have already been SRU'ed (bug #1040557) to mitigate the problem of UEFI machines being bricked by nvram being filled up. However, this problem is still present and a recent upstream fix has been accepted in mainline: f8b8404337de4e2466e2e1139ea68b1f8295974f Modify UEFI anti-bricking code This fix should be backported to Ubuntu kernels, starting with Precise. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-37-generic 3.5.0-37.58 ProcVersionSignature: Ubuntu 3.5.0-37.58-generic 3.5.7.16 Uname: Linux 3.5.0-37-generic x86_64 ApportVersion: 2.6.1-0ubuntu12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: miguel 2073 F pulseaudio /dev/snd/controlC0: miguel 2073 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Jul 9 16:00:44 2013 HibernationDevice: RESUME=UUID=a6251583-fdd9-4246-8677-7a470ac9e219 InstallationDate: Installed on 2013-03-20 (110 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120808) MachineType: TOSHIBA Satellite A210 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-37-generic root=UUID=fcec33e6-2066-4bf1-879c-0389d0b4947d ro RelatedPackageVersions: linux-restricted-modules-3.5.0-37-generic N/A linux-backports-modules-3.5.0-37-generic N/A linux-firmware1.95.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.00 dmi.board.name: IALAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV2.00:bd06/10/2008:svnTOSHIBA:pnSatelliteA210:pvrPSAELE-04R01GPT:rvnTOSHIBA:rnIALAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A210 dmi.product.version: PSAELE-04R01GPT dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1199401/+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 2008646] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008646 Title: Incomplete turbo boost on all cores in Ubuntu 22.04 and 22.10 Status in linux package in Ubuntu: Confirmed Bug description: I have an HP laptop with Core i5-8300h and it almost doesn't use all- core turbo after couple minutes after boot. When I run a single threaded task, it maintains frequencies of 3.5-4 GHz, but as I run anything on all cores the clock drops to rates near the base frequency of 2.3 GHz (runs at 1.7-2.5Ghz). The first couple minutes after boot all cores run on full multi-core boost frequency of 3.9 GHz if loaded. It can't be a thermal issue as the temperature drops to about 55°C and the fans go almost silent (much more quiet than under single-core load). The issue was present on 18.04 and original 20.04, disappeared with some update in 20.04 branch (the laptop would maintain 3.9 GHz turbo on all cores) and now returned in 22.04 and 22.10 (I've tried various DE flavors). Under the Windows the full multi-core turbo sustains for indefinite time during non SIMD workloads. Switching governors makes no difference. I've tried disabling intel_pstate, turning thermald on or off, throttled and auto-cpufreq custom daemons and nothing helped. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic 5.19.0.31.28 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Sun Feb 26 19:42:19 2023 InstallationDate: Installed on 2023-02-25 (0 days ago) InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Release amd64 (20221018.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 003: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 002: ID 1d57:fa21 Xenta 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=72585e83-b773-4fed-b0fc-bc0b92c5c7e3 ro quiet splash noresume vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.release: 15.18 dmi.bios.vendor: AMI dmi.bios.version: F.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 84F8 dmi.board.vendor: HP dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 8.10 dmi.modalias: dmi:bvnAMI:bvrF.18:bd06/20/2018:br15.18:efr8.10:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn84F8:rvr08.10:cvnHP:ct10:cvrChassisVersion:sku4HC20EA#ACB: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Notebook dmi.product.sku: 4HC20EA#ACB dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008646/+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 2008646] [NEW] Incomplete turbo boost on all cores in Ubuntu 22.04 and 22.10
Public bug reported: I have an HP laptop with Core i5-8300h and it almost doesn't use all- core turbo after couple minutes after boot. When I run a single threaded task, it maintains frequencies of 3.5-4 GHz, but as I run anything on all cores the clock drops to rates near the base frequency of 2.3 GHz (runs at 1.7-2.5Ghz). The first couple minutes after boot all cores run on full multi-core boost frequency of 3.9 GHz if loaded. It can't be a thermal issue as the temperature drops to about 55°C and the fans go almost silent (much more quiet than under single-core load). The issue was present on 18.04 and original 20.04, disappeared with some update in 20.04 branch (the laptop would maintain 3.9 GHz turbo on all cores) and now returned in 22.04 and 22.10 (I've tried various DE flavors). Under the Windows the full multi-core turbo sustains for indefinite time during non SIMD workloads. Switching governors makes no difference. I've tried disabling intel_pstate, turning thermald on or off, throttled and auto-cpufreq custom daemons and nothing helped. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic 5.19.0.31.28 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Sun Feb 26 19:42:19 2023 InstallationDate: Installed on 2023-02-25 (0 days ago) InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Release amd64 (20221018.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 003: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 002: ID 1d57:fa21 Xenta 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=72585e83-b773-4fed-b0fc-bc0b92c5c7e3 ro quiet splash noresume vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.release: 15.18 dmi.bios.vendor: AMI dmi.bios.version: F.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 84F8 dmi.board.vendor: HP dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 8.10 dmi.modalias: dmi:bvnAMI:bvrF.18:bd06/20/2018:br15.18:efr8.10:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn84F8:rvr08.10:cvnHP:ct10:cvrChassisVersion:sku4HC20EA#ACB: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Notebook dmi.product.sku: 4HC20EA#ACB dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008646 Title: Incomplete turbo boost on all cores in Ubuntu 22.04 and 22.10 Status in linux package in Ubuntu: New Bug description: I have an HP laptop with Core i5-8300h and it almost doesn't use all- core turbo after couple minutes after boot. When I run a single threaded task, it maintains frequencies of 3.5-4 GHz, but as I run anything on all cores the clock drops to rates near the base frequency of 2.3 GHz (runs at 1.7-2.5Ghz). The first couple minutes after boot all cores run on full multi-core boost frequency of 3.9 GHz if loaded. It can't be a thermal issue as the temperature drops to about 55°C and the fans go almost silent (much more quiet than under single-core load). The issue was present on 18.04 and original 20.04, disappeared with some update in 20.04 branch (the laptop would maintain 3.9 GHz turbo on all cores) and now returned in 22.04 and 22.10 (I've tried various DE flavors). Under the Windows the full multi-core turbo sustains for indefinite time during non SIMD workloads. Switching governors makes no difference. I've tried disabling intel_pstate, turning thermald on or off, throttled and auto-cpufreq custom daemons and nothing helped. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic 5.19.0.31.28 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Sun Feb 26 19:42:19 2023 InstallationDate: Installed on 2023-02-25 (0 days ago)
[Kernel-packages] [Bug 2008643] Re: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10
all was good for today. today i update system and wifi not work =( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/2008643 Title: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: sudo apt-get install bcmwl-kernel-source Building for 5.19.0-32-generic Building for architecture x86_64 Building initial module for 5.19.0-32-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.19.0-32-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. cat /var/crash/bcmwl-kernel-source.0.crash ProblemType: Package DKMSBuildLog: DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.19.0-32-generic (x86_64) Ср 22 фев 2023 08:42:01 CET make: вход в каталог «/usr/src/linux-headers-5.19.0-32-generic» warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0 You are using: gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0 CFG80211 API is prefered for this kernel version Using CFG80211 API CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:81: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.h:73: warning: "isprint" redefined 73 | #define isprint(c) bcm_isprint(c) | In file included from ./include/linux/string_helpers.h:6, from ./include/linux/seq_file.h:7, from ./include/linux/seq_file_net.h:5, from ./include/net/net_namespace.h:183, from ./include/linux/netdevice.h:38, from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:69, from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:27: ./include/linux/ctype.h:30: note: this is the location of the previous definition 30 | #define isprint(c) ((__ismask(c)&(_P|_U|_L|_D|_SP)) != 0) | In file included from ./include/linux/string.h:253, from ./include/linux/bitmap.h:11, from ./include/linux/cpumask.h:12, from ./arch/x86/include/asm/cpumask.h:5, from ./arch/x86/include/asm/msr.h:11, from ./arch/x86/include/asm/processor.h:22, from ./arch/x86/include/asm/timex.h:5, from ./include/linux/timex.h:67, from ./include/linux/time32.h:13, from ./include/linux/time.h:60, from ./include/linux/stat.h:19, from ./include/linux/module.h:13, from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:40, from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:27: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_attach’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:645:43: warning: passing argument 1 of ‘__builtin_memcpy’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] 645 | bcopy(>pub->cur_etheraddr, dev->dev_addr, ETHER_ADDR_LEN); ./include/linux/fortify-string.h:379:27: note: in definition of macro ‘__fortify_memcpy_chk’ 379 | __underlying_##op(p, q, __fortify_size); \ | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linux_osl.h:156:41: note: in expansion of macro ‘memcpy’ 156 | #define bcopy(src, dst, len)memcpy((dst), (src), (len)) | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:645:9: note: in expansion of macro ‘bcopy’ 645 | bcopy(>pub->cur_etheraddr, dev->dev_addr, ETHER_ADDR_LEN); | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:645:43: note: expected ‘void *’ but argument is of type ‘const unsigned char *’ 645 | bcopy(>pub->cur_etheraddr, dev->dev_addr, ETHER_ADDR_LEN); ./include/linux/fortify-string.h:379:27: note: in definition of macro ‘__fortify_memcpy_chk’ 379 | __underlying_##op(p, q, __fortify_size);
[Kernel-packages] [Bug 2008643] [NEW] installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10
Public bug reported: sudo apt-get install bcmwl-kernel-source Building for 5.19.0-32-generic Building for architecture x86_64 Building initial module for 5.19.0-32-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.19.0-32-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. cat /var/crash/bcmwl-kernel-source.0.crash ProblemType: Package DKMSBuildLog: DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.19.0-32-generic (x86_64) Ср 22 фев 2023 08:42:01 CET make: вход в каталог «/usr/src/linux-headers-5.19.0-32-generic» warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0 You are using: gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0 CFG80211 API is prefered for this kernel version Using CFG80211 API CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:81: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.h:73: warning: "isprint" redefined 73 | #define isprint(c) bcm_isprint(c) | In file included from ./include/linux/string_helpers.h:6, from ./include/linux/seq_file.h:7, from ./include/linux/seq_file_net.h:5, from ./include/net/net_namespace.h:183, from ./include/linux/netdevice.h:38, from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:69, from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:27: ./include/linux/ctype.h:30: note: this is the location of the previous definition 30 | #define isprint(c) ((__ismask(c)&(_P|_U|_L|_D|_SP)) != 0) | In file included from ./include/linux/string.h:253, from ./include/linux/bitmap.h:11, from ./include/linux/cpumask.h:12, from ./arch/x86/include/asm/cpumask.h:5, from ./arch/x86/include/asm/msr.h:11, from ./arch/x86/include/asm/processor.h:22, from ./arch/x86/include/asm/timex.h:5, from ./include/linux/timex.h:67, from ./include/linux/time32.h:13, from ./include/linux/time.h:60, from ./include/linux/stat.h:19, from ./include/linux/module.h:13, from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:40, from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:27: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_attach’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:645:43: warning: passing argument 1 of ‘__builtin_memcpy’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] 645 | bcopy(>pub->cur_etheraddr, dev->dev_addr, ETHER_ADDR_LEN); ./include/linux/fortify-string.h:379:27: note: in definition of macro ‘__fortify_memcpy_chk’ 379 | __underlying_##op(p, q, __fortify_size); \ | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linux_osl.h:156:41: note: in expansion of macro ‘memcpy’ 156 | #define bcopy(src, dst, len)memcpy((dst), (src), (len)) | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:645:9: note: in expansion of macro ‘bcopy’ 645 | bcopy(>pub->cur_etheraddr, dev->dev_addr, ETHER_ADDR_LEN); | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:645:43: note: expected ‘void *’ but argument is of type ‘const unsigned char *’ 645 | bcopy(>pub->cur_etheraddr, dev->dev_addr, ETHER_ADDR_LEN); ./include/linux/fortify-string.h:379:27: note: in definition of macro ‘__fortify_memcpy_chk’ 379 | __underlying_##op(p, q, __fortify_size); \ | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linux_osl.h:156:41: note: in expansion of macro ‘memcpy’ 156 | #define bcopy(src, dst, len)memcpy((dst), (src), (len)) | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:645:9: note: in expansion of macro ‘bcopy’ 645 | bcopy(>pub->cur_etheraddr, dev->dev_addr, ETHER_ADDR_LEN); | ^
[Kernel-packages] [Bug 2008633] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008633 Title: kernel: xhci_hcd :01:00.0: PM: failed to suspend async: error -16 Status in linux package in Ubuntu: Confirmed Bug description: Deep suspend fails and fallback to s2idle. Journal messages "kernel: PM: Some devices failed to suspend, or early wake event detected" & "kernel: xhci_hcd :01:00.0: PM: failed to suspend async: error -16". MINIS FORUM Mini PC B550, CPU AMD Ryzen 7 5700G 8 cores, CPU 32 GB DDR4 / 512 GB SSD ASIN: B0B5D6ZN38 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 3475 F pulseaudio /dev/snd/pcmC1D0p: user 3475 F...m pulseaudio /dev/snd/controlC0: user 3475 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Feb 26 14:58:10 2023 HibernationDevice: #RESUME=UUID=d2641363-678f-410d-928e-a78740431a60 InstallationDate: Installed on 2015-03-04 (2916 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: BESSTAR TECH LIMITED B550 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=7e84e51f-bb03-46f5-927b-3564d65843f4 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-60-generic N/A linux-backports-modules-5.15.0-60-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-02-25 (0 days ago) dmi.bios.date: 03/31/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.17 dmi.board.asset.tag: Default string dmi.board.name: B550 dmi.board.vendor: BESSTAR TECH LIMITED dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.17:bd03/31/2022:br5.17:svnBESSTARTECHLIMITED:pnB550:pvrDefaultstring:rvnBESSTARTECHLIMITED:rnB550:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B550 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: BESSTAR TECH LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008633/+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 2008633] [NEW] kernel: xhci_hcd 0000:01:00.0: PM: failed to suspend async: error -16
Public bug reported: Deep suspend fails and fallback to s2idle. Journal messages "kernel: PM: Some devices failed to suspend, or early wake event detected" & "kernel: xhci_hcd :01:00.0: PM: failed to suspend async: error -16". MINIS FORUM Mini PC B550, CPU AMD Ryzen 7 5700G 8 cores, CPU 32 GB DDR4 / 512 GB SSD ASIN: B0B5D6ZN38 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 3475 F pulseaudio /dev/snd/pcmC1D0p: user 3475 F...m pulseaudio /dev/snd/controlC0: user 3475 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Feb 26 14:58:10 2023 HibernationDevice: #RESUME=UUID=d2641363-678f-410d-928e-a78740431a60 InstallationDate: Installed on 2015-03-04 (2916 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: BESSTAR TECH LIMITED B550 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=7e84e51f-bb03-46f5-927b-3564d65843f4 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-60-generic N/A linux-backports-modules-5.15.0-60-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-02-25 (0 days ago) dmi.bios.date: 03/31/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.17 dmi.board.asset.tag: Default string dmi.board.name: B550 dmi.board.vendor: BESSTAR TECH LIMITED dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.17:bd03/31/2022:br5.17:svnBESSTARTECHLIMITED:pnB550:pvrDefaultstring:rvnBESSTARTECHLIMITED:rnB550:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B550 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: BESSTAR TECH LIMITED ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008633 Title: kernel: xhci_hcd :01:00.0: PM: failed to suspend async: error -16 Status in linux package in Ubuntu: New Bug description: Deep suspend fails and fallback to s2idle. Journal messages "kernel: PM: Some devices failed to suspend, or early wake event detected" & "kernel: xhci_hcd :01:00.0: PM: failed to suspend async: error -16". MINIS FORUM Mini PC B550, CPU AMD Ryzen 7 5700G 8 cores, CPU 32 GB DDR4 / 512 GB SSD ASIN: B0B5D6ZN38 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 3475 F pulseaudio /dev/snd/pcmC1D0p: user 3475 F...m pulseaudio /dev/snd/controlC0: user 3475 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Feb 26 14:58:10 2023 HibernationDevice: #RESUME=UUID=d2641363-678f-410d-928e-a78740431a60 InstallationDate: Installed on 2015-03-04 (2916 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: BESSTAR TECH LIMITED B550 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=7e84e51f-bb03-46f5-927b-3564d65843f4 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-60-generic N/A linux-backports-modules-5.15.0-60-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-02-25 (0 days ago) dmi.bios.date: 03/31/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.17 dmi.board.asset.tag: Default string dmi.board.name: B550 dmi.board.vendor: BESSTAR TECH LIMITED dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string
[Kernel-packages] [Bug 2008610] Status changed to Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2008610
Title:
AMDGPU init broken (sw_init of IP block failed -19) between
5.19.0.29 and 5.19.0.31
Status in linux package in Ubuntu:
Confirmed
Bug description:
After upgrading the linux kernel 5.19.0.{29=>31}, my external graphics
card stopped being used on startup, and my system fell back to
internal graphics. When using the previous kernel - a patch-level
update only - this works fine.
Both the error on 5.19.0.31 and the continued proper function on
5.19.0.29 have persisted across multiple automatic and manual runs of
update-initramfs, and across a downgrade and then upgrade of linux-
firmware to/from the non-kinetic-updates version.
Full error trace from syslog and preceding lines about AMDGPU
initialization progress are attached.
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-generic 5.19.0.31.28
ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
Uname: Linux 5.19.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 26 11:56:55 2023
InstallationDate: Installed on 2021-05-18 (649 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20T4CTO1WW
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic
root=/dev/mapper/vgubuntu-root ro quiet splash amdgpu.si_support=1
radeon.si_support=0 amdgpu.cik_support=1 radeon.cik_support=0
nvidia-drm.modeset=1 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.19.0-31-generic N/A
linux-backports-modules-5.19.0-31-generic N/A
linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
SourcePackage: linux
UpgradeStatus: Upgraded to kinetic on 2022-10-20 (128 days ago)
dmi.bios.date: 12/28/2021
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: N2XET34W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20T4CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias:
dmi:bvnLENOVO:bvrN2XET34W(1.24):bd12/28/2021:br1.24:efr1.14:svnLENOVO:pn20T4CTO1WW:pvrThinkPadP15sGen1:rvnLENOVO:rn20T4CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T4_BU_Think_FM_ThinkPadP15sGen1:
dmi.product.family: ThinkPad P15s Gen 1
dmi.product.name: 20T4CTO1WW
dmi.product.sku: LENOVO_MT_20T4_BU_Think_FM_ThinkPad P15s Gen 1
dmi.product.version: ThinkPad P15s Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008610/+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 2008610] [NEW] AMDGPU init broken (sw_init of IP block failed -19) between 5.19.0.29 and 5.19.0.31
Public bug reported:
After upgrading the linux kernel 5.19.0.{29=>31}, my external graphics
card stopped being used on startup, and my system fell back to internal
graphics. When using the previous kernel - a patch-level update only -
this works fine.
Both the error on 5.19.0.31 and the continued proper function on
5.19.0.29 have persisted across multiple automatic and manual runs of
update-initramfs, and across a downgrade and then upgrade of linux-
firmware to/from the non-kinetic-updates version.
Full error trace from syslog and preceding lines about AMDGPU
initialization progress are attached.
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-generic 5.19.0.31.28
ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
Uname: Linux 5.19.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 26 11:56:55 2023
InstallationDate: Installed on 2021-05-18 (649 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20T4CTO1WW
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic
root=/dev/mapper/vgubuntu-root ro quiet splash amdgpu.si_support=1
radeon.si_support=0 amdgpu.cik_support=1 radeon.cik_support=0
nvidia-drm.modeset=1 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.19.0-31-generic N/A
linux-backports-modules-5.19.0-31-generic N/A
linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
SourcePackage: linux
UpgradeStatus: Upgraded to kinetic on 2022-10-20 (128 days ago)
dmi.bios.date: 12/28/2021
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: N2XET34W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20T4CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias:
dmi:bvnLENOVO:bvrN2XET34W(1.24):bd12/28/2021:br1.24:efr1.14:svnLENOVO:pn20T4CTO1WW:pvrThinkPadP15sGen1:rvnLENOVO:rn20T4CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T4_BU_Think_FM_ThinkPadP15sGen1:
dmi.product.family: ThinkPad P15s Gen 1
dmi.product.name: 20T4CTO1WW
dmi.product.sku: LENOVO_MT_20T4_BU_Think_FM_ThinkPad P15s Gen 1
dmi.product.version: ThinkPad P15s Gen 1
dmi.sys.vendor: LENOVO
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug kinetic wayland-session
** Attachment added: "Syslog errors portion that do not appear on -29"
https://bugs.launchpad.net/bugs/2008610/+attachment/5650054/+files/amdgpu-syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2008610
Title:
AMDGPU init broken (sw_init of IP block failed -19) between
5.19.0.29 and 5.19.0.31
Status in linux package in Ubuntu:
New
Bug description:
After upgrading the linux kernel 5.19.0.{29=>31}, my external graphics
card stopped being used on startup, and my system fell back to
internal graphics. When using the previous kernel - a patch-level
update only - this works fine.
Both the error on 5.19.0.31 and the continued proper function on
5.19.0.29 have persisted across multiple automatic and manual runs of
update-initramfs, and across a downgrade and then upgrade of linux-
firmware to/from the non-kinetic-updates version.
Full error trace from syslog and preceding lines about AMDGPU
initialization progress are attached.
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-generic 5.19.0.31.28
ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
Uname: Linux 5.19.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 26 11:56:55 2023
InstallationDate: Installed on 2021-05-18 (649 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20T4CTO1WW
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic
root=/dev/mapper/vgubuntu-root ro quiet splash amdgpu.si_support=1
radeon.si_support=0 amdgpu.cik_support=1 radeon.cik_support=0
nvidia-drm.modeset=1 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.19.0-31-generic N/A
linux-backports-modules-5.19.0-31-generic N/A
linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
SourcePackage: linux
[Kernel-packages] [Bug 1945914] Re: nvidia-kernel-source-470 470.74-0ubuntu0.20.04.1: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** 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-470 in Ubuntu. https://bugs.launchpad.net/bugs/1945914 Title: nvidia-kernel-source-470 470.74-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: installed recommended packages and got multiple bugs ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-470 470.74-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-37-generic Date: Sun Oct 3 13:18:19 2021 Dependencies: InstallationDate: Installed on 2021-10-03 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageVersion: 470.74-0ubuntu0.20.04.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: nvidia-graphics-drivers-470 Title: nvidia-kernel-source-470 470.74-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1945914/+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
