[Kernel-packages] [Bug 1934217] Re: Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi firmware crash under iperf stress tests: Microcode SW error detected. Restarting 0x0
** Changed in: linux-firmware (Ubuntu Hirsute) Status: In Progress => Invalid ** Changed in: linux-firmware (Ubuntu Hirsute) Importance: High => Undecided ** Changed in: linux-firmware (Ubuntu Hirsute) Assignee: You-Sheng Yang (vicamo) => (unassigned) -- 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/1934217 Title: Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi firmware crash under iperf stress tests: Microcode SW error detected. Restarting 0x0 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Hirsute: Invalid Bug description: - Connect both DUTs to the 5G wifi AP - on DUT 1 - $ iperf3 -s -B 192.168.50.188 - on DUT 2 - $ iperf3 -c 192.168.50.188 -B 192.168.50.91 -t 6000 - After about 30 mins the wifi crashed with firmware related error [105396.990450] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [105396.990539] iwlwifi :00:14.3: Start IWL Error Log Dump: [105396.990541] iwlwifi :00:14.3: Status: 0x0040, count: 6 [105396.990543] iwlwifi :00:14.3: Loaded firmware version: 55.d9698065.0 QuZ-a0-hr-b0-55.ucode [105396.990545] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [105396.990547] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 [105396.990548] iwlwifi :00:14.3: 0x | trm_hw_status1 [105396.990549] iwlwifi :00:14.3: 0x004CA3DE | branchlink2 [105396.990551] iwlwifi :00:14.3: 0x07F6 | interruptlink1 [105396.990552] iwlwifi :00:14.3: 0x07F6 | interruptlink2 [105396.990553] iwlwifi :00:14.3: 0x00016504 | data1 [105396.990554] iwlwifi :00:14.3: 0x1000 | data2 [105396.990555] iwlwifi :00:14.3: 0x | data3 [105396.990557] iwlwifi :00:14.3: 0x900148E4 | beacon time [105396.990558] iwlwifi :00:14.3: 0x0C6FF71A | tsf low [105396.990559] iwlwifi :00:14.3: 0x01B4 | tsf hi [105396.990560] iwlwifi :00:14.3: 0x | time gp1 [105396.990562] iwlwifi :00:14.3: 0x58CF3E54 | time gp2 [105396.990563] iwlwifi :00:14.3: 0x0001 | uCode revision type [105396.990564] iwlwifi :00:14.3: 0x0037 | uCode version major [105396.990565] iwlwifi :00:14.3: 0xD9698065 | uCode version minor [105396.990567] iwlwifi :00:14.3: 0x0351 | hw version [105396.990568] iwlwifi :00:14.3: 0x00C89004 | board version [105396.990569] iwlwifi :00:14.3: 0x800FFC03 | hcmd [105396.990570] iwlwifi :00:14.3: 0x0002 | isr0 [105396.990572] iwlwifi :00:14.3: 0x0040 | isr1 [105396.990573] iwlwifi :00:14.3: 0x08F2 | isr2 [105396.990574] iwlwifi :00:14.3: 0x04C338C8 | isr3 [105396.990575] iwlwifi :00:14.3: 0x | isr4 [105396.990577] iwlwifi :00:14.3: 0x05D6001C | last cmd Id [105396.990578] iwlwifi :00:14.3: 0x00016504 | wait_event [105396.990579] iwlwifi :00:14.3: 0x00C4 | l2p_control [105396.990580] iwlwifi :00:14.3: 0x | l2p_duration [105396.990582] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid [105396.990583] iwlwifi :00:14.3: 0x | l2p_addr_match [105396.990584] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel [105396.990585] iwlwifi :00:14.3: 0x | timestamp [105396.990586] iwlwifi :00:14.3: 0xC0D4 | flow_handler [105396.990628] iwlwifi :00:14.3: Start IWL Error Log Dump: [105396.990629] iwlwifi :00:14.3: Status: 0x0040, count: 7 [105396.990631] iwlwifi :00:14.3: 0x2000307C | ADVANCED_SYSASSERT [105396.990632] iwlwifi :00:14.3: 0x | umac branchlink1 [105396.990633] iwlwifi :00:14.3: 0x80465D2E | umac branchlink2 [105396.990634] iwlwifi :00:14.3: 0x80473128 | umac interruptlink1 [105396.990635] iwlwifi :00:14.3: 0x | umac interruptlink2 [105396.990637] iwlwifi :00:14.3: 0x | umac data1 [105396.990638] iwlwifi :00:14.3: 0xDEADBEEF | umac data2 [105396.990639] iwlwifi :00:14.3: 0xDEADBEEF | umac data3 [105396.990640] iwlwifi :00:14.3: 0x0037 | umac major [105396.990641] iwlwifi :00:14.3: 0xD9698065 | umac minor [105396.990642] iwlwifi :00:14.3: 0x58CF3E47 | frame pointer [105396.990644] iwlwifi :00:14.3: 0xC0885EB0 | stack pointer [105396.990645] iwlwifi :00:14.3: 0x0080010D | last host cmd [105396.990646] iwlwifi :00:14.3: 0x | isr status reg [105396.990668] iwlwifi :00:14.3: Fseq Registers: [105396.990691] iwlwifi :00:14.3: 0x6000 | FSEQ_ERROR_CODE [105396.990694] iwlwifi :00:14.3: 0x80290033 | FSEQ_TOP_INIT_VERSION [105396.990717] iwlwifi :00:14.3: 0x00090006 | FSEQ_CNVIO_INIT_VERSION [105396.990748] iwlwifi :00:14.3: 0xA482 | FSEQ_OTP_VERSION
[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H
This patch has already landed on 5.13 Unstable: https://kernel.ubuntu.com/git/ubuntu/unstable.git/commit/tools/testing/selftests/net?id=0ab109df63bd6d4947fb941a17eabbaff6e75c4d ** Description changed: [Impact] The IPv6: mtu exception plus redirect test in icmp_redirect.sh test from kselftest/net is expected to fail due to an unfixed bug in the IPv6 logic. When trying to run this test you will see this sub test fail with: TEST: IPv6: mtu exception plus redirect [FAIL] thus causing non-zero return value for this script. - [Fix] * 0a36a75c681880 selftests: icmp_redirect: support expected failures - This fix can be cherry-picked into all affected series. + This fix can be cherry-picked into all affected series. And it has + already landed on Unstable, test passed with Impish 5.13. [Test] Run the patched icmp_redirect.sh test manually in tools/testing/selftests/net, this sub-test will be marked as XFAIL, and the return value of this script will be 0: $ sudo ./icmp_redirect.sh ### Routing with nexthop objects and VRF ### TEST: IPv6: mtu exception plus redirect [XFAIL] Tests passed: 36 Tests failed: 0 Tests xfailed: 4 $ echo $? 0 [Where problems could occur] Change limited to testing tool, not affecting real kernel functionality. The only possible issue that I can think of is that as this script is no longer complaining about this failure, people might forgot there is such an issue exist in ipv6. [Original Bug Report] Issue found on Focal 5.6.0-1011.11-oem ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Routing with nexthop objects ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Routing with nexthop objects and VRF ### TEST: IPv4: redirect exception
[Kernel-packages] [Bug 1934217] Re: Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi firmware crash under iperf stress tests: Microcode SW error detected. Restarting 0x0
** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934217/+attachment/5508328/+files/CurrentDmesg.txt -- 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/1934217 Title: Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi firmware crash under iperf stress tests: Microcode SW error detected. Restarting 0x0 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Hirsute: In Progress Bug description: - Connect both DUTs to the 5G wifi AP - on DUT 1 - $ iperf3 -s -B 192.168.50.188 - on DUT 2 - $ iperf3 -c 192.168.50.188 -B 192.168.50.91 -t 6000 - After about 30 mins the wifi crashed with firmware related error [105396.990450] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [105396.990539] iwlwifi :00:14.3: Start IWL Error Log Dump: [105396.990541] iwlwifi :00:14.3: Status: 0x0040, count: 6 [105396.990543] iwlwifi :00:14.3: Loaded firmware version: 55.d9698065.0 QuZ-a0-hr-b0-55.ucode [105396.990545] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [105396.990547] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 [105396.990548] iwlwifi :00:14.3: 0x | trm_hw_status1 [105396.990549] iwlwifi :00:14.3: 0x004CA3DE | branchlink2 [105396.990551] iwlwifi :00:14.3: 0x07F6 | interruptlink1 [105396.990552] iwlwifi :00:14.3: 0x07F6 | interruptlink2 [105396.990553] iwlwifi :00:14.3: 0x00016504 | data1 [105396.990554] iwlwifi :00:14.3: 0x1000 | data2 [105396.990555] iwlwifi :00:14.3: 0x | data3 [105396.990557] iwlwifi :00:14.3: 0x900148E4 | beacon time [105396.990558] iwlwifi :00:14.3: 0x0C6FF71A | tsf low [105396.990559] iwlwifi :00:14.3: 0x01B4 | tsf hi [105396.990560] iwlwifi :00:14.3: 0x | time gp1 [105396.990562] iwlwifi :00:14.3: 0x58CF3E54 | time gp2 [105396.990563] iwlwifi :00:14.3: 0x0001 | uCode revision type [105396.990564] iwlwifi :00:14.3: 0x0037 | uCode version major [105396.990565] iwlwifi :00:14.3: 0xD9698065 | uCode version minor [105396.990567] iwlwifi :00:14.3: 0x0351 | hw version [105396.990568] iwlwifi :00:14.3: 0x00C89004 | board version [105396.990569] iwlwifi :00:14.3: 0x800FFC03 | hcmd [105396.990570] iwlwifi :00:14.3: 0x0002 | isr0 [105396.990572] iwlwifi :00:14.3: 0x0040 | isr1 [105396.990573] iwlwifi :00:14.3: 0x08F2 | isr2 [105396.990574] iwlwifi :00:14.3: 0x04C338C8 | isr3 [105396.990575] iwlwifi :00:14.3: 0x | isr4 [105396.990577] iwlwifi :00:14.3: 0x05D6001C | last cmd Id [105396.990578] iwlwifi :00:14.3: 0x00016504 | wait_event [105396.990579] iwlwifi :00:14.3: 0x00C4 | l2p_control [105396.990580] iwlwifi :00:14.3: 0x | l2p_duration [105396.990582] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid [105396.990583] iwlwifi :00:14.3: 0x | l2p_addr_match [105396.990584] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel [105396.990585] iwlwifi :00:14.3: 0x | timestamp [105396.990586] iwlwifi :00:14.3: 0xC0D4 | flow_handler [105396.990628] iwlwifi :00:14.3: Start IWL Error Log Dump: [105396.990629] iwlwifi :00:14.3: Status: 0x0040, count: 7 [105396.990631] iwlwifi :00:14.3: 0x2000307C | ADVANCED_SYSASSERT [105396.990632] iwlwifi :00:14.3: 0x | umac branchlink1 [105396.990633] iwlwifi :00:14.3: 0x80465D2E | umac branchlink2 [105396.990634] iwlwifi :00:14.3: 0x80473128 | umac interruptlink1 [105396.990635] iwlwifi :00:14.3: 0x | umac interruptlink2 [105396.990637] iwlwifi :00:14.3: 0x | umac data1 [105396.990638] iwlwifi :00:14.3: 0xDEADBEEF | umac data2 [105396.990639] iwlwifi :00:14.3: 0xDEADBEEF | umac data3 [105396.990640] iwlwifi :00:14.3: 0x0037 | umac major [105396.990641] iwlwifi :00:14.3: 0xD9698065 | umac minor [105396.990642] iwlwifi :00:14.3: 0x58CF3E47 | frame pointer [105396.990644] iwlwifi :00:14.3: 0xC0885EB0 | stack pointer [105396.990645] iwlwifi :00:14.3: 0x0080010D | last host cmd [105396.990646] iwlwifi :00:14.3: 0x | isr status reg [105396.990668] iwlwifi :00:14.3: Fseq Registers: [105396.990691] iwlwifi :00:14.3: 0x6000 | FSEQ_ERROR_CODE [105396.990694] iwlwifi :00:14.3: 0x80290033 | FSEQ_TOP_INIT_VERSION [105396.990717] iwlwifi :00:14.3: 0x00090006 | FSEQ_CNVIO_INIT_VERSION [105396.990748] iwlwifi :00:14.3: 0xA482 | FSEQ_OTP_VERSION [105396.990764] iwlwifi :00:14.3: 0x0003 | FSEQ_TOP_CONTENT_VERSION [105396.990787] iwlwifi
[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H
** Description changed: + [Impact] + The IPv6: mtu exception plus redirect test in icmp_redirect.sh test from kselftest/net is expected to fail due to an unfixed bug in the IPv6 logic. + + When trying to run this test you will see this sub test fail with: + TEST: IPv6: mtu exception plus redirect [FAIL] + + [Fix] + * 0a36a75c681880 selftests: icmp_redirect: support expected failures + + This fix can be cherry-picked into all affected series. + + [Test] + Run the patched icmp_redirect.sh test manually in tools/testing/selftests/net, this sub-test will be marked as XFAIL, and the return value of this script will be 0: + $ sudo ./icmp_redirect.sh + + ### + Routing with nexthop objects and VRF + ### + TEST: IPv6: mtu exception plus redirect [XFAIL] + + Tests passed: 36 + Tests failed: 0 + Tests xfailed: 4 + $ echo $? + 0 + + [Where problems could occur] + Change limited to testing tool, not affecting real kernel functionality. The only possible issue that I can think of is that as this script is no longer complaining about this failure, people might forgot there is such an issue exist in ipv6. + + + + [Original Bug Report] Issue found on Focal 5.6.0-1011.11-oem - ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Routing with nexthop objects ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Routing with nexthop objects and VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ]
[Kernel-packages] [Bug 1934217] [NEW] Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi firmware crash under iperf stress tests: Microcode SW error detected. Restarting 0x0
Public bug reported: - Connect both DUTs to the 5G wifi AP - on DUT 1 - $ iperf3 -s -B 192.168.50.188 - on DUT 2 - $ iperf3 -c 192.168.50.188 -B 192.168.50.91 -t 6000 - After about 30 mins the wifi crashed with firmware related error [105396.990450] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [105396.990539] iwlwifi :00:14.3: Start IWL Error Log Dump: [105396.990541] iwlwifi :00:14.3: Status: 0x0040, count: 6 [105396.990543] iwlwifi :00:14.3: Loaded firmware version: 55.d9698065.0 QuZ-a0-hr-b0-55.ucode [105396.990545] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [105396.990547] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 [105396.990548] iwlwifi :00:14.3: 0x | trm_hw_status1 [105396.990549] iwlwifi :00:14.3: 0x004CA3DE | branchlink2 [105396.990551] iwlwifi :00:14.3: 0x07F6 | interruptlink1 [105396.990552] iwlwifi :00:14.3: 0x07F6 | interruptlink2 [105396.990553] iwlwifi :00:14.3: 0x00016504 | data1 [105396.990554] iwlwifi :00:14.3: 0x1000 | data2 [105396.990555] iwlwifi :00:14.3: 0x | data3 [105396.990557] iwlwifi :00:14.3: 0x900148E4 | beacon time [105396.990558] iwlwifi :00:14.3: 0x0C6FF71A | tsf low [105396.990559] iwlwifi :00:14.3: 0x01B4 | tsf hi [105396.990560] iwlwifi :00:14.3: 0x | time gp1 [105396.990562] iwlwifi :00:14.3: 0x58CF3E54 | time gp2 [105396.990563] iwlwifi :00:14.3: 0x0001 | uCode revision type [105396.990564] iwlwifi :00:14.3: 0x0037 | uCode version major [105396.990565] iwlwifi :00:14.3: 0xD9698065 | uCode version minor [105396.990567] iwlwifi :00:14.3: 0x0351 | hw version [105396.990568] iwlwifi :00:14.3: 0x00C89004 | board version [105396.990569] iwlwifi :00:14.3: 0x800FFC03 | hcmd [105396.990570] iwlwifi :00:14.3: 0x0002 | isr0 [105396.990572] iwlwifi :00:14.3: 0x0040 | isr1 [105396.990573] iwlwifi :00:14.3: 0x08F2 | isr2 [105396.990574] iwlwifi :00:14.3: 0x04C338C8 | isr3 [105396.990575] iwlwifi :00:14.3: 0x | isr4 [105396.990577] iwlwifi :00:14.3: 0x05D6001C | last cmd Id [105396.990578] iwlwifi :00:14.3: 0x00016504 | wait_event [105396.990579] iwlwifi :00:14.3: 0x00C4 | l2p_control [105396.990580] iwlwifi :00:14.3: 0x | l2p_duration [105396.990582] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid [105396.990583] iwlwifi :00:14.3: 0x | l2p_addr_match [105396.990584] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel [105396.990585] iwlwifi :00:14.3: 0x | timestamp [105396.990586] iwlwifi :00:14.3: 0xC0D4 | flow_handler [105396.990628] iwlwifi :00:14.3: Start IWL Error Log Dump: [105396.990629] iwlwifi :00:14.3: Status: 0x0040, count: 7 [105396.990631] iwlwifi :00:14.3: 0x2000307C | ADVANCED_SYSASSERT [105396.990632] iwlwifi :00:14.3: 0x | umac branchlink1 [105396.990633] iwlwifi :00:14.3: 0x80465D2E | umac branchlink2 [105396.990634] iwlwifi :00:14.3: 0x80473128 | umac interruptlink1 [105396.990635] iwlwifi :00:14.3: 0x | umac interruptlink2 [105396.990637] iwlwifi :00:14.3: 0x | umac data1 [105396.990638] iwlwifi :00:14.3: 0xDEADBEEF | umac data2 [105396.990639] iwlwifi :00:14.3: 0xDEADBEEF | umac data3 [105396.990640] iwlwifi :00:14.3: 0x0037 | umac major [105396.990641] iwlwifi :00:14.3: 0xD9698065 | umac minor [105396.990642] iwlwifi :00:14.3: 0x58CF3E47 | frame pointer [105396.990644] iwlwifi :00:14.3: 0xC0885EB0 | stack pointer [105396.990645] iwlwifi :00:14.3: 0x0080010D | last host cmd [105396.990646] iwlwifi :00:14.3: 0x | isr status reg [105396.990668] iwlwifi :00:14.3: Fseq Registers: [105396.990691] iwlwifi :00:14.3: 0x6000 | FSEQ_ERROR_CODE [105396.990694] iwlwifi :00:14.3: 0x80290033 | FSEQ_TOP_INIT_VERSION [105396.990717] iwlwifi :00:14.3: 0x00090006 | FSEQ_CNVIO_INIT_VERSION [105396.990748] iwlwifi :00:14.3: 0xA482 | FSEQ_OTP_VERSION [105396.990764] iwlwifi :00:14.3: 0x0003 | FSEQ_TOP_CONTENT_VERSION [105396.990787] iwlwifi :00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN [105396.990808] iwlwifi :00:14.3: 0x2302 | FSEQ_CNVI_ID [105396.990811] iwlwifi :00:14.3: 0x01300504 | FSEQ_CNVR_ID [105396.990834] iwlwifi :00:14.3: 0x2302 | CNVI_AUX_MISC_CHIP [105396.990841] iwlwifi :00:14.3: 0x01300504 | CNVR_AUX_MISC_CHIP [105396.990868] iwlwifi :00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [105396.990887] iwlwifi :00:14.3: 0x025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [105396.991043] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 5 fired. [105396.991047] ieee80211 phy0: Hardware restart was requested ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-firmware (Ubuntu Focal) Importance: High Assignee: You-Sheng Yang
[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H
Spotted on OEM 5.13.0-1005.5 ** Changed in: linux-signed-oem-5.6 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Package changed: linux-signed-oem-5.6 (Ubuntu) => linux-oem-5.6 (Ubuntu) -- 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/1880645 Title: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Bug description: Issue found on Focal 5.6.0-1011.11-oem ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Routing with nexthop objects ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect
[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H
Spotted on 5.11.0-24.25 ** Tags added: sru-20210621 ** Tags removed: impish -- 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/1880645 Title: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: New Status in linux-signed-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-signed-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-signed-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-signed-oem-5.6 source package in Hirsute: Invalid Bug description: Issue found on Focal 5.6.0-1011.11-oem ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Routing with nexthop objects ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Routing with nexthop objects and VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus
[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H
Spotted on 5.8.0-61.68 ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-oem-5.10 (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-signed-oem-5.6 (Ubuntu Hirsute) Status: New => Invalid -- 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/1880645 Title: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: New Status in linux-signed-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-signed-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-signed-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-signed-oem-5.6 source package in Hirsute: Invalid Bug description: Issue found on Focal 5.6.0-1011.11-oem ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Routing with nexthop objects ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Routing with nexthop objects and VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception
[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H
Fix from Andrea: https://github.com/torvalds/linux/commit/0a36a75c6818800c67057458376e99b5f77c2a1f#diff-3078e2caac04cecbb93443928e200d08fec2faa8b0e0bc1ed304ba1ce4e4b440 ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-signed-oem-5.6 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- 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/1880645 Title: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: New Status in linux-signed-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-signed-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-signed-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-signed-oem-5.6 source package in Hirsute: Invalid Bug description: Issue found on Focal 5.6.0-1011.11-oem ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Routing with nexthop objects ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ###
[Kernel-packages] [Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
I was also having a suspend/resume with 460.56+. Rolling back to 460.39 fixed it. Older packages can be found at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-460/+publishinghistory List of packages I have installed: libnvidia-cfg1-460:amd64 libnvidia-common-460 libnvidia-compute-460:amd64 libnvidia-compute-460:i386 libnvidia-decode-460:amd64 libnvidia-decode-460:i386 libnvidia-encode-460:amd64 libnvidia-encode-460:i386 libnvidia-extra-460:amd64 libnvidia-extra-460:i386 libnvidia-fbc1-460:amd64 libnvidia-fbc1-460:i386 libnvidia-gl-460:amd64 libnvidia-gl-460:i386 libnvidia-ifr1-460:amd64 libnvidia-ifr1-460:i386 nvidia-compute-utils-460 nvidia-dkms-460 nvidia-driver-460 nvidia-kernel-common-460 nvidia-kernel-source-460 nvidia-prime nvidia-prime-applet nvidia-settings nvidia-utils-460 xserver-xorg-video-nvidia-460 -- 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]
[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
Hi Steve, is the firmware from #9 fixed the issue? So far, we don't sure if the firmware crashing the root cause of your issue, so KC separated it to LP: #1933755. And firmware from #9 helps LP: #1933755 (see LP: #1933755 comment #2) -- 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/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0] Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. 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 20.2.6-0ubuntu0.20.04.1 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/oem-priority/+bug/1932548/+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 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
Please don't boot into recovery mode while investigating this bug. Recovery mode is not relevant to the bug. That said, Ubuntu 20.10 reaches end of life this month so upgrading to 21.04 should probably be the next step. That will also give you kernel version 5.11 which might hopefully work better... https://ubuntu.com/download/desktop https://wiki.ubuntu.com/Releases -- 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/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+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 1786013] Autopkgtest regression report (linux-meta-azure/5.11.0.1011.11)
All autopkgtests for the newly accepted linux-meta-azure (5.11.0.1011.11) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
Thank you for reporting this bug to Ubuntu. Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Invalid Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/nvidia-graphics-drivers-340/+bug/1864781/+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 1786013] Autopkgtest regression report (linux-meta-oracle/4.15.0.1076.86)
All autopkgtests for the newly accepted linux-meta-oracle (4.15.0.1076.86) for bionic have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.27-3ubuntu1.4 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) lxd/3.0.3-0ubuntu1~18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-oracle [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
Hello Steve, Can you attach your kernel log? upload output of "$ journalctl -k". Thanks, -- 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/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0] Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. 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 20.2.6-0ubuntu0.20.04.1 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/oem-priority/+bug/1932548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
Hi Acelan: I did but... it did not work. :( Best Regards, Steve On Mon, Jun 28, 2021 at 4:50 AM AceLan Kao <1932...@bugs.launchpad.net> wrote: > 5.10 kernel supports API_MAX is 59 and on the system it uses 55, > I'm wondering if newer firmware fixes this issue. > > Please copy the firmware "iwlwifi-QuZ-a0-hr-b0-59.ucode" to > /lib/firmware and power cycle. Then check if this issue persists. > > ** Attachment added: "iwlwifi-QuZ-a0-jf-b0-59.ucode" > > https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1932548/+attachment/5507574/+files/iwlwifi-QuZ-a0-jf-b0-59.ucode > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1932548 > > Title: > [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on > wireless [8086:a0f0] > > Status in OEM Priority Project: > Confirmed > Status in linux-oem-5.10 package in Ubuntu: > New > > Bug description: > Whenever I am using a wireless connection, the image freezes roughly > every two minutes. Sometimes, email cannot be retrieved / computer > complains the connection was momentarily lost. > > - If I am on a wire, this problem does NOT occur. > - This problems occurs on wireless independent of the platform used > (behavior seen in both Google Hangout and Zoom) > - This problem does NOT occur on Windows. I did a meeting where both my > Linux and Windows machines were connected to the same meeting and using the > same wifi router, and while the performance on Windows was flawless, > unfortunately it was not so on the Ubuntu box. So I don't think my wifi > router or network is to blame. > - As far as I can recall, the problem used not to be there 2 weeks ago. > So it may have been introduced by a recent update. > - As communicated before, I am on a certified machine from Dell, > recently purchased with Ubuntu already on board from factory (I assume the > logs there were sent to you would contain the information). > - I tried to generate a log on the wireless, but the process did not let > me do this very easily. I am more than happy to send you additional > information - but please let me know which package you want me to spy upon > exactly, as I am not sure what would be helpful in this matter. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 > Uname: Linux 5.10.0-1029-oem x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Jun 18 09:47:58 2021 > DistUpgraded: Fresh install > DistributionChannelDescriptor: ># This is the distribution channel descriptor for the OEM CDs ># For more information see > http://wiki.ubuntu.com/DistributionChannelDescriptor >canonical-oem-somerville-focal-amd64-20200502-85 > DistroCodename: focal > DistroVariant: ubuntu > EcryptfsInUse: Yes > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA > controller]) > Subsystem: Dell Device [1028:0991] > InstallationDate: Installed on 2021-04-24 (54 days ago) > InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary > 20200502-05:58 > MachineType: Dell Inc. XPS 13 9310 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem > root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 03/25/2021 > dmi.bios.release: 2.1 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 2.1.1 > dmi.board.name: 08607K > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: XPS > dmi.product.name: XPS 13 9310 > dmi.product.sku: 0991 > dmi.sys.vendor: Dell Inc. > 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 20.2.6-0ubuntu0.20.04.1 > 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/oem-priority/+bug/1932548/+subscriptions > -- You received this bug notification
[Kernel-packages] [Bug 1919049] Re: Can not enable laptop screen
I'm able to reproduce it on fresh Ubuntu 21.04 installation. -- 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/1919049 Title: Can not enable laptop screen Status in linux package in Ubuntu: Confirmed Bug description: I’m using a laptop with NVIDIA GPU and only external screen. The laptop screen is disabled. When I try to enable the laptop screen with xrandr, I get: $ xrandr --output eDP-1-1 --auto --left-of DP-2 xrandr: Configure crtc 4 failed Reproduction steps: * Connect an external display to a laptop * Disable laptop display * Close the laptop lid * Reboot (keep the lid closed) * Enable laptop display with `xrandr` command Expected behavior: Laptop display is enabled Actual behavior: Laptop display is not enabled Additional information: If the laptop lid is opened during reboot, laptop display is detected correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: woody 1298 F pulseaudio /dev/snd/controlC0: woody 1298 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: KDE neon 20.04 InstallationDate: Installed on 2020-12-28 (75 days ago) InstallationMedia: neon user "Focal" - Build amd64 LIVE Binary 20201224-09:57 MachineType: TUXEDO TUXEDO NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic root=/dev/mapper/vgsystem-lvsystem ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/16/2019 dmi.bios.release: 7.13 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.13RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.9 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.13RTR2:bd10/16/2019:br7.13:efr7.9:svnTUXEDO:pnTUXEDO:pvrNotApplicable:rvnTUXEDO:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919049/+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 1884281] Re: UC20 images do not use predictable interface names on RPi4
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1884281 Title: UC20 images do not use predictable interface names on RPi4 Status in snapd: Triaged Status in linux-raspi package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: Image tested: http://cdimage.ubuntu.com/ubuntu-core/20/dangerous- beta/pending/ubuntu-core-20-arm64+raspi.img.xz Boot the image and check the naming of the ethernet interfaces. On most devices (amd64, rpi3 etc) systemd predicatable interface naming is applied e.g. enxb827eb7d1eee. However on specifically RPi4 devices traditional naming is used e.g. eth0, eth1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1884281/+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 1861645] Re: PC fails to shutdown.
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1861645 Title: PC fails to shutdown. Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: I have a pc with Motherboard Gigabyte H370M D3H, Processor Intel Core I3 8100 3.6Ghz 6MbL3, RAM Corsair 16Mb 2400 Hz. I can reboot pc without any problem, but pc is stuck on ubuntu logo when I shutdown. while shutdown keyboard and mouse are turned off but pc remains on. I have to turn the mains power off to shutdown the pc. I think this is a major bug in Ubuntu 19.10. I searched for a solution on the internet but could not find any that works. Kindly help to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prakash1438 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-31 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 003: ID 1a2c:0e24 China Resource Semico Co., Ltd USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H370M-D3H Package: systemd 242-7ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=a883551d-0fff-4cdb-bc6d-d442860a0ec0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 RfKill: Tags: eoan Uname: Linux 5.3.0-29-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: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: H370M D3H-CF 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.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: H370M-D3H 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/1861645/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/nvidia-graphics-drivers-340/+bug/1864781/+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 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Triaged => Invalid -- 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/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+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 1902748] Re: ubuntu-seed / ubuntu-boot partition detection could be improved
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1902748 Title: ubuntu-seed / ubuntu-boot partition detection could be improved Status in snapd: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: ubuntu-seed / ubuntu-boot partition detection could be improved Currently in the initrd, snapd-bootstrap searches for ubuntu-boot / ubuntu-seed partition by label or by UEFI variable that was set by sd- boot. sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH, HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to boot. https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h This is nice, but not unique enough. It would be nice if we were able to modify sd-boot stub to export something more specific that ideally maps to a sysfs path. For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH, USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH, UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such. That way initrd would be able to resolve better which block device to key off. Given that EFI device handle is passed to the kernel, doesn't kernel also know where it came from? or not? To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1902748/+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 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
** Changed in: systemd (Ubuntu) Status: Confirmed => 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Released Status in linux source package in Disco: Won't Fix Status in systemd source package in Disco: Fix Released Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Won't Fix Status in systemd package in Debian: Fix Released Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Triaged => Invalid -- 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/1825499 Title: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6] Status in systemd: Fix Released Status in libinput package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in libinput package in Fedora: Won't Fix Bug description: After installing Kubuntu 19.04, I found that vertical sensitivity is much higher than horizontal sensitivity. Installing xserver-xorg-input-synaptics improved the situation a bit and enabled KDE touchpad setting that were disabled. It's very annoying. Laptop: HP Pavilion g6. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Fri Apr 19 12:00:02 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/systemd/+bug/1825499/+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 1818253] Re: 18.10 when lid closed and opened again no keyboard
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1818253 Title: 18.10 when lid closed and opened again no keyboard Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Using Dell Inspiron 7000 w/Intel corei7. With 18.04 power settings had options for what to do when lid was closed. Now available with Gnome-tweak in 18.10. However does not work correctly. Did Google search happening to others as well especially with detach keyboards which is not my case. With 18.10 and tweak setting to suspend when lid closed, the system does suspend, however when lid is closed it appears that the on board keyboard gets totally dropped when lid is opened back up. Have to use touch screen to switch user, then touch screen again at login to get a screen keyboard, sometimes I get the on board keyboard back, usually have to reboot to get on on board keyboard back. If I power off or restart keyboard works fine. Definite regression this has worked for several older versions of Ubuntu, at least on this system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818253/+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 1822118] Re: Kernel Panic while rebooting cloud instance
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Very occasionally systemd panics on reboots of an azure instance. A workaround to this issue is described in comment #20 Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50. After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console. [ OK ] Reached target Reboot. /shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.498980] [ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu [ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 89.508026] Call Trace: [ 89.508026] dump_stack+0x63/0x8a [ 89.508026] panic+0xe7/0x247 [ 89.508026] do_exit.cold.23+0x26/0x75 [ 89.508026] do_group_exit+0x43/0xb0 [ 89.508026] __x64_sys_exit_group+0x18/0x20 [ 89.508026] do_syscall_64+0x5a/0x110 [ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 89.508026] RIP: 0033:0x7f7bf0154d86 [ 89.508026] Code: Bad RIP value. [ 89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 00e7 [ 89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 7f7bf0154d86 [ 89.508026] RDX: 007f RSI: 003c RDI: 007f [ 89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: [ 89.508026] R10: 7ffd6be6974c R11: 0206 R12: 0018 [ 89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: [ 89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation range: 0x8000-0xbfff) [ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.508026] ]--- this only occurred once in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+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 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes
marking invalid for systemd as this doesn't seem like a systemd bug ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: systemd (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1783881 Title: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: Won't Fix Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: Invalid Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+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 1789634] Re: computer does not reemerge from hibernate
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- 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/1789634 Title: computer does not reemerge from hibernate Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: I put the computer in hibernate I came back and pressed start button to reawake machine. No response. Black screen. Had to force hard reboot to get machine back to functional status. lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 posting this to systemd as that is power management package (as I understand) apt-cache policy systemd systemd: Installed: 237-3ubuntu10.3 Candidate: 237-3ubuntu10.3 Version table: *** 237-3ubuntu10.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 29 14:31:57 2018 InstallationDate: Installed on 2018-08-24 (4 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Studio 1737 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=2b8227a7-271c-4d4c-8a2b-faa238133be0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0P792H dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd04/14/2011:svnDellInc.:pnStudio1737:pvrA09:rvnDellInc.:rn0P792H:rvrA09:cvnDellInc.:ct8:cvrA09: dmi.product.name: Studio 1737 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789634/+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 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image Status in Ubuntu on IBM z Systems: Fix Released Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Invalid Bug description: Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC image on a z/VM guest leads to a kernel panic: /lib/debian-installer/start-udev: line 15: can't create /sys/module/scsi_mod/par ameters/scan: Permission denied ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ exitcode=0x00 000100 ¬0.845071| ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic #157-Ubun tu ¬0.845077|7d107c20 7d107cb0 0002 000 0 7d107d50 7d107cc8 7d107cc8 00114732 008b 009a304c 009f11d0 000b 7d107d10 7d107cb0 040001cdf800 00114732 7d107cb0 7d107d10 ¬0.845089| Call Trace: ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) ¬0.845095| ¬<001146e2>| show_stack+0x72/0xf8 ¬0.845099| ¬<00555752>| dump_stack+0x82/0xb8 ¬0.845101| ¬<00286390>| panic+0x108/0x250 ¬0.845104| ¬<00166228>| do_exit+0xac0/0xba0 ¬0.845106| ¬<001663c8>| do_group_exit+0x50/0xe0 ¬0.845108| ¬<00166488>| __wake_up_parent+0x0/0x28 ¬0.845111| ¬<007eadda>| system_call+0xee/0x28c ¬0.845113| ¬<03ff8953983a>| 0x3ff8953983a 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0010F8CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+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 1789492] Re: suspending system causes full shutdown
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1789492 Title: suspending system causes full shutdown Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Whenever I close the lid of my laptop or hit the power button, my PC is unable to suspend correctly. The system shutdowns with no indication that it ever enters the suspension state (no blinking power LED) and when I turn it on again it boots to the BIOS and goes to the GRUB and login like nothing happened. By the way, pm-suspend does works, systemctl suspend (which I think is the default) does not. If I can help with any information let me know, any help will be appreciated. Thanks! CPU: AMD A10 GPU: AMD Radeon R8 365DX OS: Ubuntu 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: luciano2313 F pulseaudio /dev/snd/controlC0: luciano2313 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion Notebook Package: systemd 237-3ubuntu10.3 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=2d26ce19-7ed2-4c63-be34-b63c3dc23812 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf [EXTENDED] /usr/lib/systemd/user/dbus.service → /usr/lib/systemd/user/dbus.service.d/flatpak.conf 3 overridden configuration files found. Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.45 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 80B6 dmi.board.vendor: HP dmi.board.version: 81.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.45:bd04/28/2017:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion Notebook dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789492/+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 1790320] Re: system does not recover from hibernation
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1790320 Title: system does not recover from hibernation Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy systemd systemd: Installed: 237-3ubuntu10.3 Candidate: 237-3ubuntu10.3 Version table: *** 237-3ubuntu10.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) What you expected to happen I walked away from the laptop. The laptop went into sleep mode or equivalent. 4)what should happen is when i move the mouse or type a key or quickly press the power button, the machine should come out of sleep mode. It does not. I have to hard reboot the machine :( ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Sep 1 19:39:46 2018 InstallationDate: Installed on 2018-08-24 (8 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Studio 1737 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=2b8227a7-271c-4d4c-8a2b-faa238133be0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0P792H dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd04/14/2011:svnDellInc.:pnStudio1737:pvrA09:rvnDellInc.:rn0P792H:rvrA09:cvnDellInc.:ct8:cvrA09: dmi.product.name: Studio 1737 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790320/+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 1794169] Re: AWS ubuntu became unreachable after ssh login
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1794169 Title: AWS ubuntu became unreachable after ssh login Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins. systemd -user became zombie and block main systemd daemon (PID 1). I've created bug https://github.com/systemd/systemd/issues/10123 but it was closed with "there's a problem with your kernel". https://github.com/systemd/systemd/issues/10123#issuecomment-423984751 Symptoms are very similar to https://github.com/systemd/systemd/issues/8598 apetren+ 26679 0.0 0.0 0 0 ?Z02:56 0:00 \_ [(sd-pam)] apetren+ 26855 0.0 0.0 76636 7816 ?Ds 02:57 0:00 /lib/systemd/systemd --user apetren+ 26856 0.0 0.0 0 0 ?Z02:57 0:00 \_ [(sd-pam)] apetren+ 26954 0.0 0.0 0 0 ?Zs 02:57 0:00 \_ [kill] apetren+ 27053 0.0 0.0 76636 7496 ?Ss 02:58 0:00 /lib/systemd/systemd --user apetren+ 27054 0.0 0.0 193972 2768 ?S02:58 0:00 \_ (sd-pam) This situation is repeatable on 7 instances 1-2 times per week. how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2. update kernel and packages to latest version 3. from another instance run while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep defunc |grep -v grep" ; done By this command in couple of days I have 2->4->6->8... zombies and in a hour system is frozen... sudo reboot is not working, because systemd with PID 1 is unreachable. kill -9 1 -- not working as well. # uname -r: Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" # systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid AWS instance m5.xlarge Please let me know if you need any information. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 Ec2AMI: ami-91caece9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: m5.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 m5.xlarge Package: systemd 237-3ubuntu10.3 PackageArchitecture: amd64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-aws N/A linux-backports-modules-4.15.0-1021-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic ec2-images Uname: Linux 4.15.0-1021-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-02cfe7fcd8a997085 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: m5.xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794169/+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 1782709] Re: Updating systemd kills network on bionic
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E162AUS-1.20]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: IBM System x -[794582G]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+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 1770940] Re: Kexec reboot doesn't work on 18.04 non-EFI system
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1770940 Title: Kexec reboot doesn't work on 18.04 non-EFI system Status in kexec-tools package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Unclear whether to report it against kexec-tools or systemd. After upgrading to Ubuntu 18.04, the „systemctl kexec” command gives the following error message: Cannot find the ESP partition mount point. What's interesting is that strace shows that systemctl tries to find the EFI partition before it emits the error message, like it was expecting an EFI system. My laptop is not capable of EFI, and it wasn't a problem for previous Ubuntu releases – the „systemctl kexec” command worked fine before. Here is my systemd version: root@thinkpad:~# systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid And my kexec-tools version is 1:2.0.16-1ubuntu1. I attached an strace output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: kexec-tools 1:2.0.16-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 13 12:48:25 2018 InstallationDate: Installed on 2014-06-10 (1432 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: kexec-tools UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1770940/+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 1774740] Re: Cannot hibernate : systemd-sleep[22332]: Failed to write 'disk' to /sys/power/state: Cannot allocate memory
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1774740 Title: Cannot hibernate : systemd-sleep[22332]: Failed to write 'disk' to /sys/power/state: Cannot allocate memory Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Roughly every other time, hibernating (via systemctl hibernate) fails : it begins then I get back to lightdm prompt. journalctl shows the lines systemd[1]: Starting Hibernate... systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/10_unattended-upgrades-hibernate as 22334. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/hdparm as 22335. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/10_grub-common as 22336. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/wpasupplicant as 22337. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/tuxonice as 22338. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/back_to_ram as 22339. systemd-sleep[22333]: /lib/systemd/system-sleep/10_unattended-upgrades-hibernate succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/back_to_ram succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/hdparm succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/tuxonice succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/10_grub-common succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/wpasupplicant succeeded. systemd-sleep[22332]: system-sleep succeeded. systemd-sleep[22332]: Suspending system... kernel: PM: hibernation entry kernel: PM: Syncing filesystems ... kernel: PM: done. kernel: Freezing user space processes ... (elapsed 0.001 seconds) done. kernel: OOM killer disabled. kernel: PM: Marking nosave pages: [mem 0x-0x0fff] kernel: PM: Marking nosave pages: [mem 0x00058000-0x00058fff] kernel: PM: Marking nosave pages: [mem 0x0009e000-0x000f] kernel: PM: Marking nosave pages: [mem 0xabbf4000-0xabbf5fff] kernel: PM: Marking nosave pages: [mem 0xbb835000-0xbc5fefff] kernel: PM: Marking nosave pages: [mem 0xbc60-0x] kernel: PM: Basic memory bitmaps created kernel: PM: Preallocating image memory... kernel: acpi LNXPOWER:16: Turning OFF kernel: acpi LNXPOWER:15: Turning OFF kernel: acpi LNXPOWER:14: Turning OFF kernel: acpi LNXPOWER:13: Turning OFF kernel: acpi LNXPOWER:12: Turning OFF kernel: acpi LNXPOWER:11: Turning OFF kernel: acpi LNXPOWER:10: Turning OFF kernel: acpi LNXPOWER:0f: Turning OFF kernel: acpi LNXPOWER:0e: Turning OFF kernel: acpi LNXPOWER:0d: Turning OFF kernel: acpi LNXPOWER:0c: Turning OFF kernel: acpi LNXPOWER:0b: Turning OFF kernel: acpi LNXPOWER:0a: Turning OFF kernel: acpi LNXPOWER:09: Turning OFF kernel: acpi LNXPOWER:08: Turning OFF kernel: acpi LNXPOWER:07: Turning OFF kernel: acpi LNXPOWER:06: Turning OFF kernel: acpi LNXPOWER:05: Turning OFF kernel: acpi LNXPOWER:04: Turning OFF kernel: acpi LNXPOWER:03: Turning OFF kernel: PM: Basic memory bitmaps freed kernel: OOM killer enabled. kernel: Restarting tasks ... done. kernel: video LNXVIDEO:00: Restoring backlight state kernel: PM: hibernation exit whoopsie[1377]: [00:31:31] Cannot reach: https://daisy.ubuntu.com whoopsie[1377]: [00:31:31] Cannot reach: https://daisy.ubuntu.com systemd-sleep[22332]: Failed to write 'disk' to /sys/power/state: Cannot allocate memory acpid[1079]: client 1225[0:0] has disconnected systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE acpid[1079]: client connected from 1225[0:0] systemd[1]: Failed to start Hibernate. acpid[1079]: 1 client rule loaded systemd[1]: Dependency failed for Hibernate. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21.2 ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jun 2 00:34:35 2018 InstallationDate: Installed on 2016-09-07 (632 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision Tower 3620 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=6ebb7e70-29f5-4ddf-a1a1-8cc58113961a ro nomodeset SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.8.1 dmi.board.name: 09WH54 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver
I installed the provided kernel package and thus far performed: 1. reboot tests 2. insmod/rmmod tests 3. fio testing: no performance regressions -- 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/1933518 Title: Update SmartPQI driver Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA 06b41e0d1800 scsi: smartpqi: Update event handler 7a84a821f194 scsi: smartpqi: Add support for wwid ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds 99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks 5be746d7d74b scsi: smartpqi: Add host level stream detection enable c7ffedb3a774 scsi: smartpqi: Add stream detection 583891c9e509 scsi: smartpqi: Align code with oob driver 598bef8d7942 scsi: smartpqi: Add support for long firmware version f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and feature bits 7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes 6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes 1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code 281a817f232e scsi: smartpqi: Refactor aio submission code 2708a25643ab scsi: smartpqi: Add support for new product ids b622a601a13a scsi: smartpqi: Correct request leakage during reset operations c6d3ee209b9e scsi: smartpqi: Use host-wide tag space The patches they provided only apply the hunk that applies to the SmartPQI driver. This commit was a much wider commit that removes references to MODULE_SUPPORTED_DEVICE in many drivers across the kernel. 6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE [Testing] TBD [Regression Risk] Patchset changes only smartpqi driver so regression is limited to systems equipped with this SCSI device. On such SmartPQI-equipped systems the patchset can cause data corruption, data loss or unavailability of SCSI storage and boot failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933518/+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 1923162] Re: riscv64 images fail to boot in qemu
** Changed in: u-boot-menu (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: New Status in u-boot-menu source package in Focal: Fix Committed Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: Fix Committed Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+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 1934166] Re: [Asus Zenbook 14] Cannot adjust brightness
Workaround: method 1 in https://www.debugpoint.com/2016/10/2-ways-fix- laptop-brightness-problem-ubuntu-linux/ -- 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/1934166 Title: [Asus Zenbook 14] Cannot adjust brightness Status in linux package in Ubuntu: New Bug description: Cannot control the brightness on my Asus Zenbook 14 UX433: - Fn+F4/F5 are not recognized and don't change the brightness (other Fn keys -- volume, keyboard brightness -- work) - No screen brightness slider in the system menu or Power menu in Settings - Screen blanks but does not turn off according to power settings or during suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934166/+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 1740536] Re: Macbook Air Will not Sleep Ubuntu 16.04
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1740536 Title: Macbook Air Will not Sleep Ubuntu 16.04 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Macbook Air with Ubuntu 16.04 installed will not sleep/susped when lid is closed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740536/+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 1740666] Re: systemd-timesyncd doesn't sync time after resume from hibernate
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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/1740666 Title: systemd-timesyncd doesn't sync time after resume from hibernate Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: When resuming, the clock remains at the time when the hibernate happened, even if timedatectl claims that it is being synced: $ timedatectl status Local time: Вс 2017-12-31 13:46:16 +05 Universal time: Вс 2017-12-31 08:46:16 UTC RTC time: Вс 2017-12-31 08:46:16 Time zone: Asia/Yekaterinburg (+05, +0500) Network time on: yes NTP synchronized: yes RTC in local TZ: no I've tried waiting a bit, but this persisted for some minutes, so I forced an update with systemctl restart systemd-timesyncd.service And afterwards the time was (apparently) correctly synced. Please, let me know what further informations are needed to debug the issue, and I would be happy to do some other test. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 31 13:41:51 2017 InstallationDate: Installed on 2017-06-05 (208 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740666/+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 1723644] Re: NetworkManager/wicd hang, might be driver issue
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Fix Committed => Won't Fix -- 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/1723644 Title: NetworkManager/wicd hang, might be driver issue Status in linux package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Bug description: Recently I had issues with NetworkManager. When I try to restart or close NetworkManager, the process hangs. First it sends a SIGTERM to the NetworkManager process, and after a while it sends SIGKILL, yet nothing happens. After the attempt to restart/close NetworkManager, the OS behaves badly: - journalctl doesn't work, doesn't output anything, SIGTERMing/SIGABRTing/ SIGKILLing it causes the kill command to hang (no matter how many times I try it), it also hangs the terminal - 'sudo dmesg' hangs (killing it with SIGKILL/SIGTERM/SIGABRT hangs the kill command, can't close the terminal) - the OS won't reboot/suspend/shutdown (it does only after holding the restart button) Suspending/rebooting normally/shutdowning normally the laptop hangs the OS (because of NetworkManager). What I've tried: - reinstalling NetworkManager (uninstalling it using --purge, installing it clean) - deleting ~/.config - deleting ~/.cache - installing a version from NetworkManager from Debian (version: 1.8.4.2), reinstalling NetworkManager from Ubuntu back affects ubuntu affects ubuntu/network-manager affects ubuntu/systemd --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1259 F pulseaudio DistroRelease: Ubuntu 17.10 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-15 (1 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) IpRoute: default via 192.168.100.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.100.0/24 dev wlp3s0 proto kernel scope link src 192.168.100.6 metric 600 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57f3 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0489:e0a3 Foxconn / Hon Hai Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G Package: systemd PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=1df26300-dc4d-42b3-bf5f-0c77c8df7667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/21/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.29 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.29 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.29:bd07/21/2017:svnAcer:pnAspireE5-575G:pvrV1.29:rvnAcer:rnIronman_SK:rvrV1.29:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.version: V1.29 dmi.sys.vendor: Acer nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected/org/freedesktop/NetworkManager/Devices/3 Bojescu 2278c0fb-6947-469e-a8fc-7bbbafb10cf2 /org/freedesktop/NetworkManager/ActiveConnection/1 enp4s0f1 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about
[Kernel-packages] [Bug 1728573] Re: request to pull in an upstream bug fix for systemd
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- 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/1728573 Title: request to pull in an upstream bug fix for systemd Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: There's a bug in systemd's virtualization detection algorithm that prevents the XenServer Tools from working: systemd-virt-detect reports "vm-other" instead of Xen on AMD hosts, and if it doesn't report "xen", then xe-daemon will refuse to start. Thus, installing Ubuntu as a guest on XenServer on an AMD host will be less than ideal. This has been patched upstream: https://github.com/systemd/systemd/commit/530c1c3028c484c503725bbac769b9051af83da7 If this fix could be pulled into Xenial / Ubuntu 16.04 LTS, it would be greatly appreciated. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728573/+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 1919049] Re: Can not enable laptop screen
I'll check that -- 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/1919049 Title: Can not enable laptop screen Status in linux package in Ubuntu: Confirmed Bug description: I’m using a laptop with NVIDIA GPU and only external screen. The laptop screen is disabled. When I try to enable the laptop screen with xrandr, I get: $ xrandr --output eDP-1-1 --auto --left-of DP-2 xrandr: Configure crtc 4 failed Reproduction steps: * Connect an external display to a laptop * Disable laptop display * Close the laptop lid * Reboot (keep the lid closed) * Enable laptop display with `xrandr` command Expected behavior: Laptop display is enabled Actual behavior: Laptop display is not enabled Additional information: If the laptop lid is opened during reboot, laptop display is detected correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: woody 1298 F pulseaudio /dev/snd/controlC0: woody 1298 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: KDE neon 20.04 InstallationDate: Installed on 2020-12-28 (75 days ago) InstallationMedia: neon user "Focal" - Build amd64 LIVE Binary 20201224-09:57 MachineType: TUXEDO TUXEDO NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic root=/dev/mapper/vgsystem-lvsystem ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/16/2019 dmi.bios.release: 7.13 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.13RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.9 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.13RTR2:bd10/16/2019:br7.13:efr7.9:svnTUXEDO:pnTUXEDO:pvrNotApplicable:rvnTUXEDO:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919049/+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 1693895] Re: ubuntu budgie suspend to ram fails on Macbook Pro Ret
** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- 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/1693895 Title: ubuntu budgie suspend to ram fails on Macbook Pro Ret Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Bug description: A default installation of Ubuntu Budgie fails to suspend to RAM. Workaround: sudo apt-get install pm-utils => Suspend works ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri May 26 20:13:16 2017 InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693895/+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 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- 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/1701222 Title: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Won't Fix Status in linux source package in Xenial: Incomplete Status in linux source package in Zesty: Incomplete Status in linux source package in Artful: Won't Fix Bug description: Issue description: Hyper-V daemons fail to start after disable/re- enable VM integration services. Platform: host independent Affected daemons - KVP, FCOPY and VSS. Distribution name and release: Ubuntu 16.04, Ubuntu 17.04 Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 4.10.0-19-generic (for Ubuntu 17.04) Repro rate: 100% Steps to reproduce: 1.Start VM with Guest Services enabled (FCopy daemon starts automatically) 2.Go to File > Settings > Integration Services, uncheck Guest Services and apply (FCopy daemon will stop at this point) 3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running). This is the issue. systemd monitors for the service and if we have the hook for the Guest Service, it tries to start the daemon again. systemd attempt to start any of the LIS daemons will fail, but manually executing the daemon binary, it will start the daemon. Additional Info: - the steps above can be repro'd with KVP / Data Exchange integration service as well. - Manually starting hv_fcopy_daemon works fine. - other distros (RHEL) does not have this behavior, the LIS daemons are started automatically by systemd once we re-enable the integration service. On the upstream kernel and the upstream hv daemons, these messages are recorded in syslog, once we re-enable the Guest service: HV_FCOPY: pread failed: Bad file descriptor systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: hv-fcopy-daemon.service: Unit entered failed state. systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701222/+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 1934191] [NEW] i40e 2.15.9 driver does not show rx_packets when xdp/ebpf is attached
Public bug reported: Intel driver for i40e, i40e-2.15.9.tar.gz does not display rx_packets from ethtool when any xdp/ebpf module is attached to the interface. This problem is seen even in version 2.10 of the i40e driver. The one that is packaged with the upstream kernel seems to be fine. ** 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/1934191 Title: i40e 2.15.9 driver does not show rx_packets when xdp/ebpf is attached Status in linux package in Ubuntu: New Bug description: Intel driver for i40e, i40e-2.15.9.tar.gz does not display rx_packets from ethtool when any xdp/ebpf module is attached to the interface. This problem is seen even in version 2.10 of the i40e driver. The one that is packaged with the upstream kernel seems to be fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934191/+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 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- 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/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Bug description: Hi, the symptom is this error message in my system's logs: juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument According to /proc/bus/input/devices the corresponding input device is: I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=13 B: KEY=1000b0400 0 e 0 B: MSC=10 This laptop is a Dell Latitude E6520. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Wed Jun 29 17:43:01 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597415/+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 1605433] Re: [Dell Alienware 17 R3] FN+F11 Enable/Disable touchpad not working
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- 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/1605433 Title: [Dell Alienware 17 R3] FN+F11 Enable/Disable touchpad not working Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: The touchpad does not work as expected. It can't be enabled or disabled through FN+F11 combination. The light (in the pad) always turns on, regardless of its non functionality. The problem seems related to bug #1523738, and some say solution #24 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523738/comments/24) works, but it didn't for me. WORKAROUND: Executing the following via a terminal allows one to disable and enable the touchpad: xinput set-prop 13 "Device Enabled" 1 xinput set-prop 13 "Device Enabled" 0 But it only works if it is enabled from the beginning from the systems configuration GUI. If it is disabled, it doesn't do the expected behavior. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Jul 21 21:07:42 2016 InstallationDate: Installed on 2016-07-03 (18 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2016-07-16T11:29:07.694480 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 4247 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (24 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 Tags: xenial Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605433/+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 1559643] Re: kswapd0 high cpu
** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- 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/1559643 Title: kswapd0 high cpu Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Bug description: kswapd0 high cpu load. System doesn't have swap partition / swap file. Using AWS t2.nano ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-34-generic 4.2.0-34.39 ProcVersionSignature: User Name 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 07:35 seq crw-rw 1 root audio 116, 33 Mar 20 07:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sun Mar 20 07:57:52 2016 Ec2AMI: ami-b7443fc0 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: t2.nano Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb 1 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic root=UUID=b079c5f1-8fc8-4bb0-aa26-31610f9c5615 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.2.0-34-generic N/A linux-backports-modules-4.2.0-34-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-11-13 (127 days ago) dmi.bios.date: 12/07/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd12/07/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559643/+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 1578141] Re: Predictable interface names partially broken with igb driver
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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/1578141 Title: Predictable interface names partially broken with igb driver Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Note: I'm not sure whether this is really a kernel bug or something within systemd/udev, please advise how to further debug. On a system with two GE ports, instead of getting named eno1 and eno2, I am getting eno1 and renameN. Where N starts at 3 and increases by 2 on every iteration of doing "rmmod igb;modprobe igb". The corresponding lines in dmesg look like this: [2.748429] igb :07:00.0: added PHC on eth0 [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8e [2.748505] igb :07:00.0: eth0: PBA No: 106100-000 [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [2.802555] igb :07:00.1: added PHC on eth1 [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8f [2.802631] igb :07:00.1: eth1: PBA No: 106100-000 [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [2.803618] igb :07:00.0 eno1: renamed from eth0 [2.833208] igb :07:00.1 rename3: renamed from eth1 What is even worse: Sometimes the naming changes and the second interface ends up as eno1 while the first interface is named renameN with an even N. The bad thing about this version is that when it happens while the installer is running, the installer will setup "rename2" as the primary network interface, which works fine for the installation itself, but after installation is finished and the first boot of the installed system happens, that interface will be gone, leaving the system without network connectivity. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 4 09:48 seq crw-rw 1 root audio 116, 33 May 4 09:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed May 4 10:00:39 2016 HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9DRT-HF+ PciMultimedia: ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/compute--node37--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DRT-HF+ dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0c:bd05/21/2014:svnSupermicro:pnX9DRT-HF+:pvr0123456789:rvnSupermicro:rnX9DRT-HF+:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: X9DRT-HF+ dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1513526] Re: Rapid resume & suspend could damage laptop
** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- 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/1513526 Title: Rapid resume & suspend could damage laptop Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Won't Fix Bug description: I suspended my laptop when battery 15%, put it in bag, suspended at 15:58, at night (22:00) I found my laptop very hot and it seems rapidly resume & suspend. WORKAROUND: Add in /etc/systemd/logind.conf : HandleLidSwitch=poweroff ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-extra-3.19.0-31-generic 3.19.0-31.36 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: khad 2193 F pulseaudio /dev/snd/pcmC1D0p: khad 2193 F...m pulseaudio /dev/snd/controlC1: khad 2193 F pulseaudio CurrentDesktop: GNOME Date: Thu Nov 5 22:51:05 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=baaa6fcc-61cf-4070-8f6a-57c140bca2bc MachineType: LENOVO 20DCA02WIA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic.efi.signed root=/dev/mapper/Onyx-Ubuntu15.04 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-31-generic N/A linux-backports-modules-3.19.0-31-generic N/A linux-firmware 1.143.4 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET46WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DCA02WIA dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJ5ET46WW(1.17):bd07/15/2015:svnLENOVO:pn20DCA02WIA:pvrThinkPadE450:rvnLENOVO:rn20DCA02WIA:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DCA02WIA dmi.product.version: ThinkPad E450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513526/+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 1492850] Re: Dell pro venue 11 - No wireless connections after sleep
** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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/1492850 Title: Dell pro venue 11 - No wireless connections after sleep Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: I try for a long time to set-up the wifi for my dell pro venue 11 v7130 (wifi chipset Intel Corporation Wireless 7260). The wifi connection is perfect until the computer is suspend. After a suspend, even activating the wifi from network manager is impossible. After suspend even an exit doesn't reconnect to the wifi connection. It seems that the wifi chipset is off and it's impossible to wake up. Recently 15.04 has been update to 4.2 RC8. Nothing new ! A file unload_modules has been created. /etc/pm/config.d with SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi" without any effect. sudo service network-manager restart doesn't work too ! Before suspend @utopie:~$ sudo lshw -C network *-network description: Interface réseau sans fil produit: Wireless 7260 fabriquant: Intel Corporation identifiant matériel: 0 information bus: pci@:01:00.0 nom logique: wlan0 version: 83 numéro de série: 5c:51:4f:d9:2e:75 bits: 64 bits horloge: 33MHz fonctionnalités: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.2.0-040200rc8-generic firmware=25.30.13.0 ip=192.168.0.50 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn ressources: irq:49 mémoire:f7d0-f7d01fff *-network DÉSACTIVÉ description: Ethernet interface identifiant matériel: 1 nom logique: wwan0 numéro de série: 1e:51:e0:b8:e1:da fonctionnalités: ethernet physical configuration: broadcast=yes driver=cdc_mbim driverversion=22-Aug-2005 firmware=CDC MBIM link=no multicast=yes After suspend (no more wifi chipset !). @utopie:~$ sudo lshw -C network *-network DÉSACTIVÉ description: Ethernet interface identifiant matériel: 1 nom logique: wwan0 numéro de série: 1e:51:e0:b8:e1:da fonctionnalités: ethernet physical configuration: broadcast=yes driver=cdc_mbim driverversion=22-Aug-2005 firmware=CDC MBIM link=no multicast=yes --- ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: baly 1169 F pulseaudio /dev/snd/controlC1: baly 1169 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=729324f1-42a5-45f8-9585-f6e0169f2d64 InstallationDate: Installed on 2015-04-23 (144 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Venue 11 Pro 7130 vPro Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-29-generic.efi.signed root=UUID=35cde4a5-bbc3-442b-b239-d3f917925a94 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-29.31-generic 3.19.8-ckt6 RelatedPackageVersions: linux-restricted-modules-3.19.0-29-generic N/A linux-backports-modules-3.19.0-29-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' Uname: Linux 3.19.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0T69G0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd02/18/2014:svnDellInc.:pnVenue11Pro7130vPro:pvr01:rvnDellInc.:rn0T69G0:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Venue 11 Pro 7130 vPro dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492850/+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 1450396] Re: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-lan setting
** Changed in: systemd (Ubuntu) Status: Triaged => Invalid -- 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/1450396 Title: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on- lan setting Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Bug description: === Update: This bug was reported from BIOS version F13 of my board, in the meantime I upgraded to the most recent version F14, but this had no impact on the bug. === Hello, using Suspend-to-RAM on my system has stopped working reliably on Vivid when booting with Systemd. When I try to suspend my PC the following happens: - PC turns off - PC unwantedly wakes up (turns on) by itself again. This time span until it turns on again can reach from a second (almost immediately) until two or three minutes. - In a few cases (<25%), the PC stays suspended properly. A way to workaround this problem is to boot my PC with Upstart instead of Systemd, then this problem never happens (and has never happened in any of the previous Ubuntu versions since 2008). Thus it seems to be a bug somehow related to Systemd. Other steps I have tried to solve the problem (without any success): - Checking BIOS settings, all options are set that way that the PC should never wake up by any event other than pressing the power button. - Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device could cause wake up events. This lists my USB controller, but deactivating it (with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the problem. Also suspend while running Upstart works fine despite the USB controller listed as "enabled". In the system logs I could see no hint what causes the undesired wake- ups. Allthough there is one factor which seems to have a certain influence: If I close programs like Pidgin, Skype or Firefox that cause continuous network traffic, the chance is higher that my PC will stay suspened (while runinng Systemd). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 30 11:24:46 2015 InstallationDate: Installed on 2015-04-16 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1450396/+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 1934187] [NEW] lxd exec fails
Public bug reported:
[Impact]
lxd will not work, as lxc exec is not able to set the apparmor confinement and
bails out executing inside the container.
[Fix]
Revert upstream commit bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check
/proc/$pid/attr/ writes against file opener").
[Test case]
lxd basic usage test suite was run.
On a 4.15 kernel, the whole lxd autopkgtest was run.
[Potential regression]
Unprivileged use of PID attributes may be permitted when they shouldn't.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
--
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/1934187
Title:
lxd exec fails
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
In Progress
Bug description:
[Impact]
lxd will not work, as lxc exec is not able to set the apparmor confinement
and bails out executing inside the container.
[Fix]
Revert upstream commit bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check
/proc/$pid/attr/ writes against file opener").
[Test case]
lxd basic usage test suite was run.
On a 4.15 kernel, the whole lxd autopkgtest was run.
[Potential regression]
Unprivileged use of PID attributes may be permitted when they shouldn't.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934187/+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 1934175] Re: Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb)
** Description changed:
- TBD
+ [Impact]
+ * We had a recent report of a kernel crash due to a NULL pointer dereference
in a Bionic 4.15 derivative kernel, as per the following log collected:
+
+ [...]
+ [537105.767348] SLUB: Unable to allocate memory on node -1,
gfp=0x14000c0(GFP_KERNEL)
+ [...]
+ [537105.767368] BUG: unable to handle kernel NULL pointer dereference at
0008
+ [537105.11] IP: kernfs_kill_sb+0x31/0x70
+ [537105.783582] PGD 0 P4D 0
+ [537105.787844] Oops: 0002 [#1] SMP PTI
+ [...]
+ RIP: 0010:kernfs_kill_sb+0x31/0x70
+ RSP: 0018:b90aec1afd00 EFLAGS: 00010286
+ RAX: RBX: 9fdbd567d900 RCX: a0143885ae01
+ RDX: RSI: a0143885ae00 RDI: a2937c40
+ RBP: b90aec1afd10 R08: a0150b581510 R09: 0001814d
+ R10: b90aec1afcd8 R11: 0100 R12: a01436e43000
+ R13: a01436e43000 R14: R15: 9fdbd567d900
+ FS: 7fe41a615b80() GS:a01afea4() knlGS:
+ CS: 0010 DS: ES: CR0: 80050033
+ CR2: 0008 CR3: 007dfe3cc003 CR4: 003606e0
+ DR0: DR1: DR2:
+ DR3: DR6: fffe0ff0 DR7: 0400
+ Call Trace:
+ sysfs_kill_sb+0x1f/0x40
+ deactivate_locked_super+0x48/0x80
+ kernfs_mount_ns+0x1eb/0x230
+ sysfs_mount+0x66/0xc0
+ mount_fs+0x37/0x160
+ ? alloc_vfsmnt+0x1b3/0x230
+ vfs_kern_mount.part.24+0x5d/0x110
+ do_mount+0x5ed/0xce0
+ [...]
+
+ * The following detailed call stack plus the disassembly help to
+ understand the cause of the issue:
+
+ mount_fs()
+ --sysfs_mount()
+ kernfs_mount_ns()
+ --deactivate_locked_super()
+ sysfs_kill_sb()
+ --kernfs_kill_sb()
+
+ The below disassembly of kernfs_kill_sb() clarifies exactly the issue:
+
+ 812f46e0 :
+ [ ... prologue ...]
+ 48 8b 9f 08 04 00 00mov0x408(%rdi),%rbx # %rbx = kernfs_super_info
*info = sb->s_fs_info
+ 49 89 fcmov%rdi,%r12 # %r12 = super_block *sb
+ 48 c7 c7 40 7c 53 82mov$0x82537c40,%rdi # %rdi =
_mutex (global)
+ 812f46f9: R_X86_64_32S kernfs_mutex
+ e8 ee da 67 00 callq 819721f0 #
mutex_lock(_mutex);
+ [...]
+ 48 8b 53 18 mov0x18(%rbx),%rdx # %rdx = info->node
+ 48 8b 43 20 mov0x20(%rbx),%rax # based on splat, RAX == 0x0
[info->head.prev]
+ 48 89 42 08 mov%rax,0x8(%rdx) # <- OOPS [tried to assign
next->prev = prev, see __list_del()]
+ 48 89 10mov%rdx,(%rax)
+ 48 b8 00 01 00 00 00movabs $0xdead0100,%rax # node->next =
LIST_POISON1
+ [...]
+
+ * The fix for this issue comes from upstream commit 82382acec0c9
+ ("kernfs: deal with kernfs_fill_super() failures"); this commit is a
+ very trivial fix that adds an INIT_LIST_HEAD(>node) in
+ kernfs_mount_ns(), making the list prev/next pointers valid since the
+ beginning. Unfortunately this commit wasn't CCed to stable email when
+ sent, so it wasn't automatically picked up by Ubuntu kernel; now it was
+ properly submitted to stable list [0].
+
+ * Along with this fix, we found another commit (7b745a4e4051) which is a
+ small/simple fix to correlated code, that also should have been sent to
+ 4.14.y stable branch, but for some reason wasn't. Since both commits
+ were accepted in linux-stable, we are hereby proposing the backport for
+ Ubuntu kernel 4.15.
+
+ [0]
+ https://lore.kernel.org/stable/20210622210622.9925-1-gpicc...@canonical.com/
+
+
+ [Test Case]
+ * We don't have a real test case, although low-memory condition or an
artificial kprobe reproducer could easily trigger the issue.
+
+ * We booted a qemu virtual machine with a kernel containing both patches
+ with no issues.
+
+
+ [Where problems could occur]
+ * The likelihood of issues are low, specially due to the fact both patches
are very simple and they are on upstream kernel for more than 3 years (and were
quickly accepted in 4.14.y stable branch last week).
+
+ * With that sad, the second patch could potentially introduce issues
+ with super_block references - I honestly cannot conceive any issues
+ potentially caused by patch 1.
--
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/1934175
Title:
Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb)
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
[Impact]
* We had a recent report of a kernel crash due to a NULL pointer dereference
in a Bionic 4.15 derivative kernel, as per the following log collected:
[...]
[537105.767348] SLUB: Unable to allocate memory on node -1,
gfp=0x14000c0(GFP_KERNEL)
[...]
[537105.767368] BUG: unable to handle kernel NULL pointer dereference at
0008
[537105.11]
[Kernel-packages] [Bug 1934179] Re: Focal update: v5.4.128 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** 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.128 upstream stable release + from git://git.kernel.org/ -v5.4.128 upstream stable release -from git://git.kernel.org/ + dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM + dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM + dmaengine: stedma40: add missing iounmap() on error in d40_probe() + afs: Fix an IS_ERR() vs NULL check + mm/memory-failure: make sure wait for page writeback in memory_failure + kvm: LAPIC: Restore guard to prevent illegal APIC register access + batman-adv: Avoid WARN_ON timing related checks + net: ipv4: fix memory leak in netlbl_cipsov4_add_std + vrf: fix maximum MTU + net: rds: fix memory leak in rds_recvmsg + net: lantiq: disable interrupt before sheduling NAPI + udp: fix race between close() and udp_abort() + rtnetlink: Fix regression in bridge VLAN configuration + net/sched: act_ct: handle DNAT tuple collision + net/mlx5e: Remove dependency in IPsec initialization flows + net/mlx5e: Fix page reclaim for dead peer hairpin + net/mlx5: Consider RoCE cap before init RDMA resources + net/mlx5e: allow TSO on VXLAN over VLAN topologies + net/mlx5e: Block offload of outer header csum for UDP tunnels + netfilter: synproxy: Fix out of bounds when parsing TCP options + sch_cake: Fix out of bounds when parsing TCP options and header + alx: Fix an error handling path in 'alx_probe()' + net: stmmac: dwmac1000: Fix extended MAC address registers definition + net: make get_net_ns return error if NET_NS is disabled + qlcnic: Fix an error handling path in 'qlcnic_probe()' + netxen_nic: Fix an error handling path in 'netxen_nic_probe()' + net: qrtr: fix OOB Read in qrtr_endpoint_post + ptp: improve max_adj check against unreasonable values + net: cdc_ncm: switch to eth%d interface naming + lantiq: net: fix duplicated skb in rx descriptor ring + net: usb: fix possible use-after-free in smsc75xx_bind + net: fec_ptp: fix issue caused by refactor the fec_devtype + net: ipv4: fix memory leak in ip_mc_add1_src + net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock + be2net: Fix an error handling path in 'be_probe()' + net: hamradio: fix memory leak in mkiss_close + net: cdc_eem: fix tx fixup skb leak + cxgb4: fix wrong shift. + bnxt_en: Rediscover PHY capabilities after firmware reset + bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path + icmp: don't send out ICMP messages with a source address of 0.0.0.0 + net: ethernet: fix potential use-after-free in ec_bhf_remove + regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting + ASoC: rt5659: Fix the lost powers for the HDA header + spi: stm32-qspi: Always wait BUSY bit to be cleared in stm32_qspi_wait_cmd() + pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled + radeon: use memcpy_to/fromio for UVD fw upload + hwmon: (scpi-hwmon) shows the negative temperature properly + can: bcm: fix infoleak in struct bcm_msg_head + can: bcm/raw/isotp: use per module netdevice notifier + can: j1939: fix Use-after-Free, hold skb ref while in use + can: mcba_usb: fix memory leak in mcba_usb + usb: core: hub: Disable autosuspend for Cypress CY7C65632 + tracing: Do not stop recording cmdlines when tracing is off + tracing: Do not stop recording comms if the trace file is being read + tracing: Do no increment trace_clock_global() by one + PCI: Mark TI C667X to avoid bus reset + PCI: Mark some NVIDIA GPUs to avoid bus reset + PCI: aardvark: Don't rely on jiffies while holding spinlock + PCI: aardvark: Fix kernel panic during PIO transfer + PCI: Add ACS quirk for Broadcom BCM57414 NIC + PCI: Work around Huawei Intelligent NIC VF FLR erratum + KVM: x86: Immediately reset the MMU context when the SMM flag is cleared + ARCv2: save ABI
[Kernel-packages] [Bug 1931442] Re: Fujitsu U7311 I219-LM wired onboard slow RX speeds
Hi, no suspend does not help. Tested with your 5.13.0-3004 kernel and 5.11.0-22-generic. Dmesg attached. ** Attachment added: "dmesg after suspend" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+attachment/5508175/+files/dmesg_suspend -- 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/1931442 Title: Fujitsu U7311 I219-LM wired onboard slow RX speeds Status in linux package in Ubuntu: Confirmed Bug description: Hello, i am having problem with very low RX speeds on my Fujitsu U7130 laptop's wired network with Intel I219-LM chip. When i start downloading any larger content, the speed is very low (ranging from 150kbps-6Mbps) or even the transfer completely stops. RX_errors are rising as well as rx_crc_errors when checking with "ethtool -S enp0s31f6". Link speed is auto-negotiated to 1000Mbps and lowering the speed manually is not having any effects on this issue. Wired TX speeds seems to be unaffected. Wireless speeds on the AX201 are as expected too. I did try to solve this problem upgrading from Ubuntu 20.04 to 21.04 and using various kernels (5.8, 5.10, 5.11, 5.12.9). I also tried to compile e1000e driver from sourceforge version 3.8.7 (https://sourceforge.net/projects/e1000/) with no joy. Bug #1927925 seems to be related as the behavior is the same, but in this case booting with kernel parameter "intel_idle.max_cstate=1" will not resolve the issue. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 uname -a Linux IO 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy linux-image-5.11.0-18-generic linux-image-5.11.0-18-generic: Installed: 5.11.0-18.19 Candidate: 5.11.0-18.19 Version table: *** 5.11.0-18.19 500 500 http://cz.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lk7r 2095 F pulseaudio /dev/snd/controlC0: lk7r 2095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-05-23 (17 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7311 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=b9466f2a-0840-40f4-8131-9b64200e5618 ro intel_idle.max_cstate=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-06-08 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 2.14 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.14 dmi.board.name: FJNB2E7 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7311 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.14:bd04/20/2021:br2.14:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7311:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7311: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7311 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+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 1931442] Re: Fujitsu U7311 I219-LM wired onboard slow RX speeds
Instead of hibernate, does suspend help? -- 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/1931442 Title: Fujitsu U7311 I219-LM wired onboard slow RX speeds Status in linux package in Ubuntu: Confirmed Bug description: Hello, i am having problem with very low RX speeds on my Fujitsu U7130 laptop's wired network with Intel I219-LM chip. When i start downloading any larger content, the speed is very low (ranging from 150kbps-6Mbps) or even the transfer completely stops. RX_errors are rising as well as rx_crc_errors when checking with "ethtool -S enp0s31f6". Link speed is auto-negotiated to 1000Mbps and lowering the speed manually is not having any effects on this issue. Wired TX speeds seems to be unaffected. Wireless speeds on the AX201 are as expected too. I did try to solve this problem upgrading from Ubuntu 20.04 to 21.04 and using various kernels (5.8, 5.10, 5.11, 5.12.9). I also tried to compile e1000e driver from sourceforge version 3.8.7 (https://sourceforge.net/projects/e1000/) with no joy. Bug #1927925 seems to be related as the behavior is the same, but in this case booting with kernel parameter "intel_idle.max_cstate=1" will not resolve the issue. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 uname -a Linux IO 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy linux-image-5.11.0-18-generic linux-image-5.11.0-18-generic: Installed: 5.11.0-18.19 Candidate: 5.11.0-18.19 Version table: *** 5.11.0-18.19 500 500 http://cz.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lk7r 2095 F pulseaudio /dev/snd/controlC0: lk7r 2095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-05-23 (17 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7311 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=b9466f2a-0840-40f4-8131-9b64200e5618 ro intel_idle.max_cstate=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-06-08 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 2.14 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.14 dmi.board.name: FJNB2E7 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7311 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.14:bd04/20/2021:br2.14:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7311:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7311: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7311 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+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 1934179] [NEW] Focal update: v5.4.128 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.128 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) 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/1934179 Title: Focal update: v5.4.128 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Bug description: 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.128 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934179/+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 1912908] Re: USB keyboard not working
I had this issue with ubuntu 20.04 and hoped it would get fixed in ubunutu 21.04 but it did not so the Kernel 5.11 also does not work and I have to keep using the old Kernel 5.4. I have never reported anything here before today, do you need more info? My laptop is an msi ps42 and a Logitech external usb keyboard -- 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/1912908 Title: USB keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 20.04.1 on a Intel NUC9. My USB keyboard is working fine with kernel 5.4.0-64 but doesn't work at all with the 5.8.0-40 kernel. I tested other external keyboards but none worked. My mouse is working fine though. ProblemType: Bug DistroRelease: Ubuntu 20.04.1 LTS (Focal Fossa) Affected Package: - linux-image-5.8.0-36-generic - linux-image-5.8.0-38-generic - linux-image-5.8.0-40-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-29 (178 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC9VXQNX NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=22f56864-ed38-49fa-9f90-e8c2a05726aa ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.187.8 RfKill: Tags: focal Uname: Linux 5.8.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QNCFLX70.0034.2019.1125.1424 dmi.board.name: NUC9VXQNB dmi.board.vendor: Intel Corporation dmi.board.version: K47179-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQNCFLX70.0034.2019.1125.1424:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9VXQNX:pvrK47173-402:rvnIntelCorporation:rnNUC9VXQNB:rvrK47179-402:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: QN dmi.product.name: NUC9VXQNX dmi.product.sku: BKNUC9VXQNX dmi.product.version: K47173-402 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912908/+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 1934175] [NEW] Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb)
Public bug reported: TBD ** Affects: linux (Ubuntu) Importance: High Assignee: Guilherme G. Piccoli (gpiccoli) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: High Assignee: Guilherme G. Piccoli (gpiccoli) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) -- 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/1934175 Title: Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb) Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934175/+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 1933766] Re: [nvidia] System freeze
** Description changed: When the laptop is left unattended until the session is locked and screen is off, after a while the whole system freeze/crash and the only way is to hard reset. Please check the attached dmesg.out.2 file for more details. + + This issue happens only when the integrated graphics is the primary GPU and nvidia is used as "on demand". + But if nvidia is the primary GPU, then there no problem at all. + ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-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..58.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 465.27 Thu Apr 22 23:21:03 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sun Jun 27 19:46:12 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 465.27, 5.11.0-22-generic, x86_64: installed virtualbox, 6.1.18, 5.11.0-18-generic, x86_64: installed virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Iris Xe Graphics [1043:1e6f] Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] InstallationDate: Installed on 2021-06-04 (22 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG 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:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.305:bd04/08/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 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.11-1ubuntu1 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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-465 in Ubuntu. https://bugs.launchpad.net/bugs/1933766 Title: [nvidia] System freeze Status in nvidia-graphics-drivers-465 package in Ubuntu: New Bug description: When the laptop is left unattended until the session is locked and screen is off, after a while the whole system freeze/crash and the only way is to hard reset. Please check the attached dmesg.out.2 file for more details. This issue happens only when the integrated graphics is the primary GPU and nvidia is used as "on demand". But if nvidia is the primary GPU, then there no problem at all. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
[Kernel-packages] [Bug 1934112] Re: Intel 100G nic get call trace for sosreport on focal ga-kenel
** 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/1934112 Title: Intel 100G nic get call trace for sosreport on focal ga-kenel Status in linux package in Ubuntu: New Bug description: On Asus Server, when it run "sosreport -a" to the network step, the console would print below call trace and the 100G Nic port became unreachable. call trace on ga-kernel ( v5.4): https://paste.ubuntu.com/p/TC5Jn6hYGF/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934112/+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 1786013] Autopkgtest regression report (linux-meta-gkeop-5.4/5.4.0.1019.20~18.04.20)
All autopkgtests for the newly accepted linux-meta-gkeop-5.4 (5.4.0.1019.20~18.04.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) lxd/3.0.3-0ubuntu1~18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) zfs-linux/0.7.5-1ubuntu16.11 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gkeop-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1934166] Re: [Asus Zenbook 14] Cannot adjust brightness
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934166/+attachment/5508162/+files/lspci-vnvn.log -- 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/1934166 Title: [Asus Zenbook 14] Cannot adjust brightness Status in linux package in Ubuntu: New Bug description: Cannot control the brightness on my Asus Zenbook 14 UX433: - Fn+F4/F5 are not recognized and don't change the brightness (other Fn keys -- volume, keyboard brightness -- work) - No screen brightness slider in the system menu or Power menu in Settings - Screen blanks but does not turn off according to power settings or during suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934166/+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 1934112] [NEW] Intel 100G nic get call trace for sosreport on focal ga-kenel
You have been subscribed to a public bug: On Asus Server, when it run "sosreport -a" to the network step, the console would print below call trace and the 100G Nic port became unreachable. call trace on ga-kernel ( v5.4): https://paste.ubuntu.com/p/TC5Jn6hYGF/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Intel 100G nic get call trace for sosreport on focal ga-kenel https://bugs.launchpad.net/bugs/1934112 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 1934166] [NEW] [Asus Zenbook 14] Cannot adjust brightness
Public bug reported: Cannot control the brightness on my Asus Zenbook 14 UX433: - Fn+F4/F5 are not recognized and don't change the brightness (other Fn keys -- volume, keyboard brightness -- work) - No screen brightness slider in the system menu or Power menu in Settings - Screen blanks but does not turn off according to power settings or during suspend ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1934166/+attachment/5508161/+files/version.log -- 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/1934166 Title: [Asus Zenbook 14] Cannot adjust brightness Status in linux package in Ubuntu: New Bug description: Cannot control the brightness on my Asus Zenbook 14 UX433: - Fn+F4/F5 are not recognized and don't change the brightness (other Fn keys -- volume, keyboard brightness -- work) - No screen brightness slider in the system menu or Power menu in Settings - Screen blanks but does not turn off according to power settings or during suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934166/+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 1928535] Re: No disk space, mainline 5.10.37 and 5.11.20, 5.11.21 failed to build
This looks to be fixed in 5.10.47. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1928535 Title: No disk space, mainline 5.10.37 and 5.11.20, 5.11.21 failed to build Status in linux package in Ubuntu: Fix Released Bug description: It looks like the build machine ran out of disk space while building 5.11.20 amd64 and 5.10.36 armhf. From: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.20/amd64/log ld: final link failed: No space left on device make[2]: *** [/home/kernel/COD/linux/Makefile:1183: vmlinux] Error 1 make[2]: Leaving directory '/home/kernel/COD/linux/debian/build/build-generic' make[1]: *** [Makefile:185: __sub-make] Error 2 make[1]: Leaving directory '/home/kernel/COD/linux' make: *** [debian/rules.d/2-binary-arch.mk:50: /home/kernel/COD/linux/debian/stamps/stamp-build-generic] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 No packages have been built for 5.10.37, 5.11.20, or 5.11.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928535/+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 1911830] Re: alsa/sdw: support soundwire audio for TGL-H machines
** Changed in: hwe-next Status: New => Fix Released ** Changed in: hwe-next Status: Fix Released => Triaged -- 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/1911830 Title: alsa/sdw: support soundwire audio for TGL-H machines Status in HWE Next: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-firmware source package in Groovy: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Bug description: [Impact] In the OEM project, we have a new TGL-H soundwire machine, with the current oem-5.10 kernel, the audio can't work. [Fix] Backport 6 patches from Intel thesofproject kernel. [Test] Put the testing sof-tgl-h.ri in the /lib/firmware/intel/sof, boot the patched kernel, we could see speakers and microphone from gnome-setting, and they all work well. [Where problems could occur] The patches changed soundwire machine driver, it is possible to make the audio on old soundwire machines not work anymore. But we tested the patches on TGL-U and cml soundwire machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1911830/+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 1872311] Re: Brightness hotkeys not working on Lenovo S740
Elias Julkunen. Did you find any solution? Currently i am facing the same problem. My hardware is Lenovo Ideapad-5-15ITL05. If you found the solution can you please share it with me? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872311 Title: Brightness hotkeys not working on Lenovo S740 Status in linux package in Ubuntu: Confirmed 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 1786013] Autopkgtest regression report (linux-meta/5.11.0.23.24)
All autopkgtests for the newly accepted linux-meta (5.11.0.23.24) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: casper/1.461 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1933748] Re: Gnome wifi menu items jumping up and down make clicking risky
Jumping does not occur most of the time that I boot or awaken it, so I'll accept your prioritization, since my idea for a patch may be more complicated to implement than I suppose. So, I won't download a new Ubuntu now. The apport-collect command is too risky to run (see https://bugs.launchpad.net/ubuntu/+source/update- manager/+bug/1933747/comments/2) and it does not provide relevant terminal output I could copy and paste into here. If there's something you'd like to know about my platform or something like that, let me know and I can try to check and report back. -- 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/1933748 Title: Gnome wifi menu items jumping up and down make clicking risky Status in gnome-shell package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Steps to reproduce: 0. I don't know the relevant circumstances about Wi-Fi networks being available and about the adapter's reception (I use a 2.4GHz USB adapter). This occurs mainly when I first try to get on a network, probably right after waking the machine from sleep and trying to get on a network. 1. In the Gnome desktop environment's top panel, at the far right, open the menu. If Wi-Fi is off, turn it on. If it says Wi-Fi Not Connected, see if that line is appearing and disappearing several times. 2. Try to select a command below that line, not a command that is exposed only by selecting Wi-Fi Not Connected but one below that, such as Settings. Because the network line is disappearing and reappearing in unpredictably rapid cycles, you may not want to click on a command below it (and risk clicking the wrong command) but merely position your cursor as if you intend to click it. Actual result: You can't be sure what you're going to click. Expected result: If a menu command must appear and disappear in unpredictable fashion, have it do so without everything below it in the menu jumping up and down. This can be managed by having the disappearing menu item be replaced by an unselectable blank menu item. Then, anything below would not jump. If the menu while it has a blank menu item is closed by any method, the blank menu item should be deleted. Thus, when the menu is opened later by any method, in the same login session or not, the blank menu item would not be included. Additional info: Ubuntu 20.04.2 LTS, kept evergreen, with Gnome desktop environment 3.36.8 (still). The package was guessed from the list of process IDs. The string: gnome-shell 3.36.9-0ubuntu0-20-04.2 I'm told that Gnome bugs have to be reported to a distro bug tracker first for proper component assignment, so I'm reporting here now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1933748/+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 1928694] Re: [Cezanne/Renoire]: Replace some fixes from linux-oem-5.10 with those landing upstream
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Invalid -- 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/1928694 Title: [Cezanne/Renoire]: Replace some fixes from linux-oem-5.10 with those landing upstream Status in amd: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Invalid Bug description: The following patches are accepted into upstream for 5.14 and should displace the existing patches carried in OEM tree. * "ACPI: processor idle: Fix up C-state latency if not ordered" replaces the hack to hardcode latency values for HP's RN systems. * "ACPI: PM: s2idle: Add missing LPS0 functions for AMD" has been accepted To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928694/+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 1911830] Re: alsa/sdw: support soundwire audio for TGL-H machines
** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Invalid -- 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/1911830 Title: alsa/sdw: support soundwire audio for TGL-H machines Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-firmware source package in Groovy: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Bug description: [Impact] In the OEM project, we have a new TGL-H soundwire machine, with the current oem-5.10 kernel, the audio can't work. [Fix] Backport 6 patches from Intel thesofproject kernel. [Test] Put the testing sof-tgl-h.ri in the /lib/firmware/intel/sof, boot the patched kernel, we could see speakers and microphone from gnome-setting, and they all work well. [Where problems could occur] The patches changed soundwire machine driver, it is possible to make the audio on old soundwire machines not work anymore. But we tested the patches on TGL-U and cml soundwire machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1911830/+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 1925452] Re: [Ubuntu 21.04] net/mlx5: Fix HW spec violation configuring uplink
I just checked the situation for this on hirsute. The patch is already included in hirsute (master): da7897c5355f net/mlx5: Fix HW spec violation configuring uplink It was added as part of: LP#1926368 "Hirsute update: v5.11.14 upstream stable release" Hence updating the hirsute entry to Fix Released and with that the entire bug. ** Changed in: linux (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => 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/1925452 Title: [Ubuntu 21.04] net/mlx5: Fix HW spec violation configuring uplink Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification: == [Impact] * In addition to 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" (handled in LP#1921104) another fix 1a73704c82ed "Fix HW spec violation configuring uplink" (handled in this bug, LP#1925452) is needed to fix issues that were introduced with commit 7d0314b11cdd "net/mlx5e: Modify uplink state on interface up/down". * Commit 1a73704c82ed "Fix HW spec violation configuring uplink" fixes a regression for mlx5 adapters required to operate in switchdev mode. * This fix makes sure that the uplink port is modified to follow only if the uplink_follow capability if it's set as required by the hw specification. * Failure cause traffic to the uplink representer net device to cease after switching to switchdev mode. [Fix] * upstream fix (upstream with v5.12-rc7) 1a73704c82ed4ee95532ac04645d02075bd1ce3d 1a73704c82ed "Fix HW spec violation configuring uplink" * can be cleanly cherry picked from hirsute master-next. * a backport for groovy: https://launchpadlibrarian.net/534888680/groovy-0001-net-mlx5-Fix-HW-spec-violation-configuring-uplink.patch * a backport for focal: https://launchpadlibrarian.net/534847308/focal-0001-net-mlx5-Fix-HW-spec-violation-configuring-uplink.patch [Test Case] * Two servers, installed with Ubuntu Server 20.04 or 20.10 are needed. * Each server needs to have a Mellanox ConnectX4/5 adapter, attached to the same switch * Adapters must be running adapter firmware level 16.29.1006 or earlier. * enable SRIOV and switchdev mode on one adapter: echo 0 > /sys/bus/pci/devices/0100\:00\:00.0/sriov_drivers_autoprobe echo 0 > /sys/bus/pci/devices/0100\:00\:00.1/sriov_drivers_autoprobe echo 64 > /sys/bus/pci/devices/0100\:00\:00.0/sriov_numvfs echo 64 > /sys/bus/pci/devices/0100\:00\:00.1/sriov_numvfs devlink dev eswitch set pci/0100:00:00.0 mode switchdev devlink dev eswitch set pci/0100:00:00.1 mode switchdev * Assign an IP address to the physical function device of the adapters on both systems * IP communication will fail * With the fix, IP communication can be established. [Regression Potential] * There is always at least some potential for regression. In this case the new code can go wrong (or might become worse than before) in case the new if statement is wrong. * It checks for the condition of "MLX5_CAP_GEN(mdev, uplink_follow)" and in case MLX5_CAP_GEN is calculated erroneous or mdev is other than expected, the mlx5_modify_vport_admin_state call might go wrong, too. * But since only the If clause was added, the changes are pretty minimal and therefore well traceable. [Other] * Since the patch/commit is upstream with 5.12-rc7, it will be in Impish. __ With the 5.4.0-48 update for Ubuntu 20.04, the commit "net/mlx5e: Modify uplink state on interface up/down" was integrated which contains a regression for mlx5 adapters with older adapter firmware. This is the second bugfix to repair the regression, required to operate the adapter in switchdev mode. The first part was integrated via Bug 192185 - LP1921104. This is the upstream fix required to be backported to Ubuntu 20.04: https://github.com/torvalds/linux/commit/1a73704c82ed4ee95532ac04645d02075bd1ce3d ---Additional Hardware Info--- Mellanox ConnectX network adapter ---uname output--- 5.4.0-73-generic ---Steps to Reproduce--- enable switchdev mode try to ping external host Backports need to be provide for 21.04, 20.10 and 20.04 (if not cleanly applyable)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925452/+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 1901406] Re: Lenovo T490 extremely show with Ubuntu 20.20 running kernel 5.8
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1901406 Title: Lenovo T490 extremely show with Ubuntu 20.20 running kernel 5.8 Status in linux package in Ubuntu: Fix Released Bug description: After upgrading from 20.04 to 20.20 on my laptop, the machine became extremely slow. After a days work I noticed that it never got any faster, and the machine was a lot colder than usual. Running cat /proc/cpuinfo and sudo cpupower frequency-info I noticed that the CPU was locked to 400Mhz. After some googling I found reports of people having trouble with CPU frequency governors on kernel 5.8. I tried to add intel_pstate=active to grub, but that didn't help. My short term workaround is to choose the old 5.4 kernel from 20.04. With this kernel everything is snappy again! Currently it's running at 3.2 Ghz with little load. CPU info from /proc/cpuinfo (with kernel 5.4): processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 142 model name: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz stepping : 12 microcode : 0xd6 cpu MHz : 4551.153 cache size: 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid: 0 initial apicid: 0 fpu : yes fpu_exception : yes cpuid level : 22 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities bugs : spectre_v1 spectre_v2 spec_store_bypass swapgs taa itlb_multihit srbds bogomips : 4199.88 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hennikul 2402 F pulseaudio /dev/snd/pcmC0D0p: hennikul 2402 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-02 (418 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20N2CTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=UUID=a36f1344-fd6c-40ef-a397-57f5a57594df ro intel_pstate=active quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy wayland-session Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-23 (2 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2020 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET83W (1.61 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N2CTO1WW 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.16 dmi.modalias: dmi:bvnLENOVO:bvrN2IET83W(1.61):bd01/19/2020:br1.61:efr1.16:svnLENOVO:pn20N2CTO1WW:pvrThinkPadT490:rvnLENOVO:rn20N2CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N2CTO1WW dmi.product.sku: LENOVO_MT_20N2_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901406/+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 1902577] Re: TGL system automatically resumes from s2idle when connecting to a docking station with a monitor
Proper fix in LP:1931072 ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1902577 Title: TGL system automatically resumes from s2idle when connecting to a docking station with a monitor Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: [Impact] TGL systems wake up automatically from s2idle when connecting to a docking station with a monitor. The wake-up events are generated when BIOS sets ALL_MONITOR_OFF for power-saving on TGL systems. [Fix] A BIOS workaround is used to skip ALL_MONITOR_OFF with an _OSI string "Linux-Dell-USB4-Wakeup". [Test] Verified on Dell's TigerLake platforms [Regression Potential] Low. This only works on platforms supporting "Linux-Dell-USB4-Wakeup". No other platforms will be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902577/+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 1930527] Re: [SRU][OEM-5.10/H] UBUNTU: SAUCE: Fix backlight control on Samsung 16727 panel
** Changed in: linux (Ubuntu) Status: New => Invalid -- 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/1930527 Title: [SRU][OEM-5.10/H] UBUNTU: SAUCE: Fix backlight control on Samsung 16727 panel Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: New Bug description: SRU justification: [Impact] Backlight can't be controlled on 5.11- version of kernel. [Fix] The panel needs DPCD to get control of backlight. After 5.12 kernel introduced new Intel HDR backlight control, and it works well on this panel. Add quirk ID to enable DPCD on 5.11- kernel. [Test] Vendor Verified on hardware, with this quirk backlight can be changed on 5.10 and 5.11 kernel. [Where problems could occur] The panel backlight may not be changed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930527/+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 1903612] Re: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel
Thank you for fixing the bug. This bug has been closed, but I will try it this weekend. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in kmod package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Confirmed Status in kmod source package in Bionic: Confirmed Status in linux-hwe source package in Bionic: Confirmed Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1903612/+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 1929166] Re: TGL-H system NV GPU fallen off the bus after resuming from s2idle with the external display connected via docking station
Proper fix in LP:1931072 ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1929166 Title: TGL-H system NV GPU fallen off the bus after resuming from s2idle with the external display connected via docking station Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] The NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if the docking station with external display connected is unplugged when the system is still in s2idle. The system will be hold by the infinite loop in ACPI method IPCS and then the PCIe root port of NVIDIA gpu fails the power transition from D3cold to D0. Then display managed by the NVDIA GPU shows nothing until system reboot. Note that it only happens when NVIDIA GPU in either Performance mode or On-Demand mode. [Fix] A BIOS workaround is used to skip the ACPI method PGSC which invokes IPCS to do source clock control of the PCIe root port with an _OSI string "Linux-Dell-USB4-NVWakeup". Should be removed until we get a generic fix for it. [Test Case] 1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the NVIDIA GPU is running in either On-Demand mode or Performance mode. 2. Connect the docking station with the external display connected. 3. Suspend the system. 4. Remove the docking station when the system is suspended. 5. Press power button to wake up the system and wait > 1 minutes to make sure if the display comes back. [Regression Potential] Low. This only works on platforms supporting "Linux-Dell-USB4-NVWakeup". No other platforms will be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929166/+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 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
ls /etc/gdm3/ config-error-dialog.sh Init PreSession Xsession custom.conf PostLoginPrime greeter.dconf-defaults PostSession PrimeOff -- 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/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+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 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
$ cat /etc/gdm3/custom.conf # GDM configuration storage # # See /usr/share/gdm/gdm.schemas for a list of available options. [daemon] AutomaticLoginEnable=False AutomaticLogin=ter # Uncomment the line below to force the login screen to use Xorg #WaylandEnable=false # Enabling automatic login # Enabling timed login # TimedLoginEnable = true # TimedLogin = user1 # TimedLoginDelay = 10 [security] [xdmcp] [chooser] [debug] # Uncomment the line below to turn on debugging # More verbose logs # Additionally lets the X server dump core if it crashes #Enable=true -- 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/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
https://covid.b-cdn.net/linux3/posts/how-to-enable-disable-wayland-on- ubuntu-20-04-desktop/62ebf7dc4f3c9aa3255575a0abc8b53134ec755235b80aa2bd1a2cf1e4d7b9d8.png This is not available in version 5.8.0-59. -- 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/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+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 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
Next please try logging into both 'Ubuntu' and 'Ubuntu on Wayland'. You can select which using the button in the bottom right corner of the login screen. Do either of those work with 5.8.0-59? I cannot do this as I have a black screen and nothing. This is not available in recovery mode. -- 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/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+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 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
I'll add this. That after I removed nvidia. I can now log in via recovery mode. There is still a black screen for normal login. -- 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/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+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 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
Note you will need to keep the Nvidia driver UNINSTALLED in order to test 'Ubuntu on Wayland'. ** Also affects: xorg-server (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/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+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 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
> Sorry. Maybe I was wrong? I made these commands in the version that works. You didn't make any mistake. journal-2.txt and journal-3.txt are from the version that does not work. > Should I choose 460? If you need the Nvidia driver to use the machine then yes you can reinstall it. I only wanted it uninstalled in order to prove this bug is in the Intel driver. Next please try logging into both 'Ubuntu' and 'Ubuntu on Wayland'. You can select which using the button in the bottom right corner of the login screen. Do either of those work with 5.8.0-59? -- 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/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
Should I choose 460? -- 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/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+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 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
** Attachment added: "Screenshot from 2021-06-30 12-29-31.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933950/+attachment/5508127/+files/Screenshot%20from%202021-06-30%2012-29-31.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+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 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
I managed to log in via recovery mode. But I cannot change the brightness. Looks like the driver is not installed ** Attachment added: "Screenshot from 2021-06-30 12-26-37.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933950/+attachment/5508126/+files/Screenshot%20from%202021-06-30%2012-26-37.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+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 1903612] Re: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel
** Changed in: kmod (Ubuntu) Status: New => Fix Released ** Changed in: kmod (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in kmod package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Confirmed Status in kmod source package in Bionic: Confirmed Status in linux-hwe source package in Bionic: Confirmed Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
Sorry. Maybe I was wrong? I made these commands in the version that works. Can I do this in a version that doesn't work? journalctl -b0 > journal0.txt journalctl -b-1 > journal-1.txt journalctl -b-2 > journal-2.txt journalctl -b-3 > journal-3.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+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 1933950] Re: I have a black screen when I login in. I have to login through a later version
OK that's helpful information. It means this is a bug in the Intel kernel driver "i915". ** Summary changed: - I have a black screen when I login in. I have to login through a later version + [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 ** No longer affects: nvidia-graphics-drivers-460 (Ubuntu) ** Tags added: i915 regression-update -- 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/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+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 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
Next please try logging into both 'Ubuntu' and 'Ubuntu on Wayland'. You can select which using the button in the bottom right corner of the login screen. -- 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/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+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 1934110] [NEW] ubuntu-host driver lacks lseek ops
Public bug reported:
[ SRU Justification ][GROOVY][HIRSUTE][IMPISH]
== Impact ==
The ubuntu-host driver lacks procfs lseek ops and lseeking on the procfs
esm-token file will jump to a NULL address causing the following splat:
942.470568] BUG: kernel NULL pointer dereference, address:
[ 942.471157] #PF: supervisor instruction fetch in kernel mode
[ 942.471724] #PF: error_code(0x0010) - not-present page
[ 942.472297] PGD 0 P4D 0
[ 942.472867] Oops: 0010 [#1] SMP PTI
[ 942.473435] CPU: 2 PID: 5661 Comm: stress-ng Not tainted 5.13.0-9-generic #9
[ 942.474012] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0
02/06/2015
[ 942.474599] RIP: 0010:0x0
[ 942.475194] Code: Unable to access opcode bytes at RIP 0xffd6.
[ 942.475792] RSP: 0018:aacf80ff7eb8 EFLAGS: 00010246
[ 942.476383] RAX: RBX: 9eaa8a175240 RCX: 0001
[ 942.476986] RDX: RSI: RDI: 9eaa838d5800
[ 942.477600] RBP: aacf80ff7ed0 R08: 4000 R09: 0004
[ 942.478203] R10: 0002 R11: R12:
[ 942.478800] R13: R14: ffea R15: 9eaa838d5800
[ 942.479399] FS: 7f998d487f00() GS:9eaaffc8()
knlGS:
[ 942.480006] CS: 0010 DS: ES: CR0: 80050033
[ 942.480607] CR2: ffd6 CR3: 00010a774002 CR4: 00370ee0
[ 942.481219] DR0: DR1: DR2:
[ 942.481855] DR3: DR6: fffe0ff0 DR7: 0400
[ 942.482458] Call Trace:
[ 942.483052] proc_reg_llseek+0x4e/0x80
[ 942.483646] ? __fdget_pos+0x43/0x50
[ 942.484234] ksys_lseek+0x84/0xc0
[ 942.484815] __x64_sys_lseek+0x1a/0x20
[ 942.485412] do_syscall_64+0x61/0xb0
[ 942.485966] ? asm_exc_page_fault+0x8/0x30
[ 942.486476] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 942.486994] RIP: 0033:0x7f998d5c1cdb
[ 942.487512] Code: ff ff c3 0f 1f 40 00 48 8b 15 89 81 0d 00 f7 d8 64 89 02
48 c7 c0 ff ff ff ff eb ba 0f 1f 00 f3 0f 1e fa b8 08 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 59 81 0d 00 f7 d8
[ 942.488593] RSP: 002b:7ffdf61c5328 EFLAGS: 0246 ORIG_RAX:
0008
[ 942.489148] RAX: ffda RBX: RCX: 7f998d5c1cdb
[ 942.489710] RDX: RSI: RDI: 0004
[ 942.490252] RBP: 0004 R08: 01785e4740dd R09: 562dbebb9e50
[ 942.490801] R10: 7ffdf61c5300 R11: 0246 R12: 7ffdf61c63f0
[ 942.491354] R13: 7ffdf61c53f0 R14: 0003 R15: 01e9
== Fix ==
Add the default_llseek ops:
diff --git a/ubuntu/ubuntu-host/ubuntu-host.c b/ubuntu/ubuntu-host/ubuntu-host.c
index 1abd402..a4c0636 100644
--- a/ubuntu/ubuntu-host/ubuntu-host.c
+++ b/ubuntu/ubuntu-host/ubuntu-host.c
@@ -38,6 +38,8 @@ static ssize_t esm_token_write(struct file *f, const char
__user *buf,
static const struct proc_ops esm_token_fops = {
.proc_read = esm_token_read,
.proc_write = esm_token_write,
+ .proc_lseek = default_llseek,
+
};
== Test plan ==
modrobe ubuntu-host
stress-ng --procfs 0 -t 60
without the fix we hit the splat. With the fix it's OK.
== Where problems could occur ==
This one liner adds the missing proc_lseek op. It is hard to see where
it can cause a regression since it affects the driver no other way. I
doubt any code is relying on the current semantics of lseek not working.
** Affects: linux (Ubuntu)
Importance: High
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Description changed:
[ SRU Justification ][GROOVY][HIRSUTE][IMPISH]
== Impact ==
The ubuntu-host driver lacks procfs lseek ops and lseeking on the procfs
esm-token file will jump to a NULL address causing the following splat:
- 942.470568] BUG: kernel NULL pointer dereference, address:
+ 942.470568] BUG: kernel NULL pointer dereference, address:
[ 942.471157] #PF: supervisor instruction fetch in kernel mode
[ 942.471724] #PF: error_code(0x0010) - not-present page
[ 942.472297] PGD 0 P4D 0
[ 942.472867] Oops: 0010 [#1] SMP PTI
[ 942.473435] CPU: 2 PID: 5661 Comm: stress-ng Not tainted 5.13.0-9-generic
#9
[ 942.474012] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0
02/06/2015
[ 942.474599] RIP: 0010:0x0
[ 942.475194] Code: Unable to access opcode bytes at RIP 0xffd6.
[ 942.475792] RSP: 0018:aacf80ff7eb8 EFLAGS: 00010246
[ 942.476383] RAX: RBX: 9eaa8a175240 RCX:
0001
[ 942.476986] RDX: RSI:
[Kernel-packages] [Bug 1932170] Re: virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** No longer affects: linux-hwe-5.11 (Ubuntu) ** No longer affects: linux-hwe-5.11 (Ubuntu Focal) -- 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/1932170 Title: virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in virtualbox package in Ubuntu: New Status in virtualbox source package in Focal: Confirmed Bug description: This is a scripted bug report about ADT failures while running virtualbox tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/v/virtualbox/20210611_210536_dcb86@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1932170/+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 1933950] Re: I have a black screen when I login in. I have to login through a later version
yes. The screen is still black -- 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/1933950 Title: I have a black screen when I login in. I have to login through a later version Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) 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: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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/1933950/+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 1933112] Re: fallocate05 from ltp-syscalls fails on H-azure
Reproduced also on QEMU with 32 or 64 CPUs, but not with 31 CPUs (focal/hwe-5.11 and mainline v5.13). Fixed by branch 'delalloc-shrink' of https://github.com/josefbacik/linux. ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: linux (Ubuntu Impish) Status: New => 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/1933112 Title: fallocate05 from ltp-syscalls fails on H-azure Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: New Status in linux source package in Impish: In Progress Bug description: Found on hirsute/azure 5.11.0-1007.7 and 5.11.0-1006.6. might be re- appearance of lp:1783880, btrfs file system, only on Azure instance Standard_F32s_v2: tst_test.c:1379: TINFO: Testing on btrfs tst_test.c:888: TINFO: Formatting /dev/loop3 with btrfs opts='' extra opts='' tst_test.c:1311: TINFO: Timeout per run is 0h 05m 00s tst_fill_fs.c:32: TINFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:59: TINFO: write(): ENOSPC (28) fallocate05.c:81: TPASS: write() wrote 65536 bytes fallocate05.c:102: TINFO: fallocate()d 0 extra blocks on full FS fallocate05.c:114: TPASS: fallocate() on full FS fallocate05.c:130: TPASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) fallocate05.c:134: TFAIL: write(): ENOSPC (28) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1933112/+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 1901406] Re: Lenovo T490 extremely show with Ubuntu 20.20 running kernel 5.8
I did not try an OEM kernel, but stock kernel 5.11.0-22 fixes the problem for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901406 Title: Lenovo T490 extremely show with Ubuntu 20.20 running kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 20.04 to 20.20 on my laptop, the machine became extremely slow. After a days work I noticed that it never got any faster, and the machine was a lot colder than usual. Running cat /proc/cpuinfo and sudo cpupower frequency-info I noticed that the CPU was locked to 400Mhz. After some googling I found reports of people having trouble with CPU frequency governors on kernel 5.8. I tried to add intel_pstate=active to grub, but that didn't help. My short term workaround is to choose the old 5.4 kernel from 20.04. With this kernel everything is snappy again! Currently it's running at 3.2 Ghz with little load. CPU info from /proc/cpuinfo (with kernel 5.4): processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 142 model name: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz stepping : 12 microcode : 0xd6 cpu MHz : 4551.153 cache size: 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid: 0 initial apicid: 0 fpu : yes fpu_exception : yes cpuid level : 22 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities bugs : spectre_v1 spectre_v2 spec_store_bypass swapgs taa itlb_multihit srbds bogomips : 4199.88 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hennikul 2402 F pulseaudio /dev/snd/pcmC0D0p: hennikul 2402 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-02 (418 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20N2CTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=UUID=a36f1344-fd6c-40ef-a397-57f5a57594df ro intel_pstate=active quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy wayland-session Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-23 (2 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2020 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET83W (1.61 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N2CTO1WW 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.16 dmi.modalias: dmi:bvnLENOVO:bvrN2IET83W(1.61):bd01/19/2020:br1.61:efr1.16:svnLENOVO:pn20N2CTO1WW:pvrThinkPadT490:rvnLENOVO:rn20N2CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N2CTO1WW dmi.product.sku: LENOVO_MT_20N2_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901406/+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
