[Kernel-packages] [Bug 2000805] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2000805 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000805 Title: rtl8156B loaded with wrong driver and not working Status in linux package in Ubuntu: Incomplete Bug description: I have a 2.5G USB Ethernet dongle that use the Realtek 8156B chipset. The default driver being loaded are cdc_mbim and cdc_ncm, but this driver (cdc_ncm) is an incorrect driver that does not work with the chip. Instead, I have to manually load the r8152 driver to make it work; I cannot blacklist cdc_ncm as I am also using it with other devices. Current Platform: Ubuntu 22.04.1, kernel 5.15.0-56-lowlatency Reproducible: always Expects: plugging in the USB dongle will have correct driver loaded, and just work Steps to fix: --- rmmod cdc_mbim rmmod cdc_ncm rmmod cdc_ether modprobe r8152 echo 0bda 8156 > /sys/bus/usb/drivers/r8152/new_id --- reference links: https://forum.manjaro.org/t/no-carrier-network-link-problem-with-usb-2-5-gbit-lan-adapter-realtek-rtl8156b-on-x86-64/97195 https://lore.kernel.org/netdev/20211227182124.5cbc0...@kicinski-fedora-pc1c0hjn.hsd1.ca.comcast.net/#t To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000805/+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 2000805] [NEW] rtl8156B loaded with wrong driver and not working
Public bug reported: I have a 2.5G USB Ethernet dongle that use the Realtek 8156B chipset. The default driver being loaded are cdc_mbim and cdc_ncm, but this driver (cdc_ncm) is an incorrect driver that does not work with the chip. Instead, I have to manually load the r8152 driver to make it work; I cannot blacklist cdc_ncm as I am also using it with other devices. Current Platform: Ubuntu 22.04.1, kernel 5.15.0-56-lowlatency Reproducible: always Expects: plugging in the USB dongle will have correct driver loaded, and just work Steps to fix: --- rmmod cdc_mbim rmmod cdc_ncm rmmod cdc_ether modprobe r8152 echo 0bda 8156 > /sys/bus/usb/drivers/r8152/new_id --- reference links: https://forum.manjaro.org/t/no-carrier-network-link-problem-with-usb-2-5-gbit-lan-adapter-realtek-rtl8156b-on-x86-64/97195 https://lore.kernel.org/netdev/20211227182124.5cbc0...@kicinski-fedora-pc1c0hjn.hsd1.ca.comcast.net/#t ** 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/2000805 Title: rtl8156B loaded with wrong driver and not working Status in linux package in Ubuntu: New Bug description: I have a 2.5G USB Ethernet dongle that use the Realtek 8156B chipset. The default driver being loaded are cdc_mbim and cdc_ncm, but this driver (cdc_ncm) is an incorrect driver that does not work with the chip. Instead, I have to manually load the r8152 driver to make it work; I cannot blacklist cdc_ncm as I am also using it with other devices. Current Platform: Ubuntu 22.04.1, kernel 5.15.0-56-lowlatency Reproducible: always Expects: plugging in the USB dongle will have correct driver loaded, and just work Steps to fix: --- rmmod cdc_mbim rmmod cdc_ncm rmmod cdc_ether modprobe r8152 echo 0bda 8156 > /sys/bus/usb/drivers/r8152/new_id --- reference links: https://forum.manjaro.org/t/no-carrier-network-link-problem-with-usb-2-5-gbit-lan-adapter-realtek-rtl8156b-on-x86-64/97195 https://lore.kernel.org/netdev/20211227182124.5cbc0...@kicinski-fedora-pc1c0hjn.hsd1.ca.comcast.net/#t To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000805/+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 1994126] Re: NULL pointer dereference in power_supply_get_property
I have the same issue for my Thinkpad P53 and I don't have a dock. It definitely related to the usb-c. case 1: If I connect my external monitor to usb-c port, it may panic on boot ( I say "may" because sometime it can last till I successfully login and run for a minute or so and then it hangs and I have to hard reboot by pressing power button for a few seconds) case 2: After I switch my external monitor to HDMI, the issue never happen case 3: If I connect my iphone to the usb-c port before reboot, it can also panic case 4: I disconnected iphone then power up and it can successfully boot. Connect iphone to the usb-c after boot and it has no issue. -- 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/1994126 Title: NULL pointer dereference in power_supply_get_property Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: Ubuntu 22.10 final release boot via usb thumb drive on thinkpad T480 (containing nvidia gpu) reproducible kernel panic during boot backtrace via OCR from picture of kernel panic: Started Periodic ext4 Online Hetadata Check for All Filesystems. Started Discard unused blocks once a week. Started Refresh fuupd metadate regularly. Started Daily rotation of log files. Started Daily man-db regeneration. Started Message of the Day. Started Daily Cleanup of Temporary Directories. Started Ubuntu Advantage Timer for running repeated jobs. Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation Socket. 1 Listening on CUPS Scheduler. 1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation for snappy deeson... Listening on UUID deemon activation socket. 1 Listening on Socket activation for snappy daemon. Reached target Socket Units. 1 Reached target Basic System. 20.300662) BUG: Kernel NULL pointer dereference, address: 20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 WPF: error code (0x0010) - not-present page 20.302458) PGD O P40 0 20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579) CPU: 4 PID: 1 Comm: systemd Tainted: P 0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 20L5000BGE/20L5000BGE, BIOS N24ET7ON (1.45) 07/22/2022 20.304190) 20.304774) RIP: 0010:0N0 20.305376) Code: Unable to access opcode bytes at RIP Oxffd6. 20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202 20.3066231 RAX: RBX: 95538288 RCX: 8c43c1d89800 20.307282) RDX: b17180087cdo RSI: 0004 RDI: 8c43c1d89800 20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09: 0 20.308627) R10: R11: R12: 00 20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15: 9553a288 20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000 20.310762) CS: 0010 DS: ES: CRO: 80050033 20.311491) CR2: fffds CRS: 00011eida002 CR4: 003706e0 20.312241) Call Trace: 20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+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 1900391] Re: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Same error when selecting any nvidia driver(screenshot in attach). The XOrg driver works without errorwhen booting Ubuntu, but is very slow. PRETTY_NAME="Ubuntu 22.04.1 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.1 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy Linux goodwin 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Motheboard: X99 LGA2011 ZX-99EV3 GCard: GTX 1660 6gb RAM: DDR4 16gb CPU: Intel Xeon E5 2678 V3 LGA2011-3 SR20Z, 12 x 2.50GHZ ** Attachment added: "image.psd.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900391/+attachment/5638680/+files/image.psd.jpg -- 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/1900391 Title: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled Status in linux package in Ubuntu: Confirmed Bug description: [4.589406] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled [4.589410] EDAC sbridge: Couldn't find mci handler [4.589411] EDAC sbridge: Failed to register device with error -19. but x79 doesn't have ecc ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-23-generic 5.8.0-23.24 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2032 F pulseaudio /dev/snd/controlC0: navycat2032 F pulseaudio /dev/snd/controlC1: navycat2032 F pulseaudio CasperMD5CheckResult: skip Date: Mon Oct 19 10:19:05 2020 InstallationDate: Installed on 2020-10-07 (11 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-23-generic N/A linux-backports-modules-5.8.0-23-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900391/+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 2000802] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2000802 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000802 Title: network Status in linux package in Ubuntu: Incomplete Bug description: network-manager not working in mint vera with kernel 5.15.0-56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000802/+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 2000802] [NEW] network
Public bug reported: network-manager not working in mint vera with kernel 5.15.0-56 ** 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/2000802 Title: network Status in linux package in Ubuntu: New Bug description: network-manager not working in mint vera with kernel 5.15.0-56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000802/+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 2000800] [NEW] Bluetooth is not being activated, I have updated with sudo apt-get update and installed the program and restarted and it does not turn on
Public bug reported: Bluetooth is not being activated, I have updated with sudo apt-get update and installed the program and restarted and it does not turn on ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 22:34:07 2022 InstallationDate: Installed on 2022-12-30 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: bnep btusb bluetooth MachineType: LENOVO 82K2 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=UUID=94a2de4f-8565-4a45-8c72-872549f49fdb ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: H3CN32WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Gaming 3 15ACH6 dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrH3CN32WW(V2.02):bd02/23/2022:br1.32:efr1.32:svnLENOVO:pn82K2:pvrIdeaPadGaming315ACH6:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPadGaming315ACH6:skuLENOVO_MT_82K2_BU_idea_FM_IdeaPadGaming315ACH6: dmi.product.family: IdeaPad Gaming 3 15ACH6 dmi.product.name: 82K2 dmi.product.sku: LENOVO_MT_82K2_BU_idea_FM_IdeaPad Gaming 3 15ACH6 dmi.product.version: IdeaPad Gaming 3 15ACH6 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:7 acl:0 sco:0 events:1 errors:0 TX bytes:61 acl:0 sco:0 commands:1 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2000800 Title: Bluetooth is not being activated, I have updated with sudo apt-get update and installed the program and restarted and it does not turn on Status in bluez package in Ubuntu: New Bug description: Bluetooth is not being activated, I have updated with sudo apt-get update and installed the program and restarted and it does not turn on ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 22:34:07 2022 InstallationDate: Installed on 2022-12-30 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: bnep btusb bluetooth MachineType: LENOVO 82K2 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=UUID=94a2de4f-8565-4a45-8c72-872549f49fdb ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: H3CN32WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Gaming 3 15ACH6 dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrH3CN32WW(V2.02):bd02/23/2022:br1.32:efr1.32:svnLENOVO:pn82K2:pvrIdeaPadGaming315ACH6:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPadGaming315ACH6:skuLENOVO_MT_82K2_BU_idea_FM_IdeaPadGaming315ACH6: dmi.product.family: IdeaPad Gaming 3 15ACH6 dmi.product.name: 82K2 dmi.product.sku: LENOVO_MT_82K2_BU_idea_FM_IdeaPad Gaming 3 15ACH6 dmi.product.version: IdeaPad Gaming 3 15ACH6 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:7 acl:0 sco:0 events:1 errors:0 TX bytes:61 acl:0 sco:0 commands:1 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000800/+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 2000491] Re: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-recoverable after screen lock and screen completely fades to black or after system goes into slee
The Dell 7390 has a built in diagnostic tool that I ran with no errors found. Moreover, if this would be a hardware issue, it would be possible to just freeze the 18.04.6 system in a different way too!? I can leave it on and hope it stays on, running, however, after a while it goes into sleep mode, from which is not possible to wake up? I have googled a bit and found a similar scenario from another user as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2000491 Title: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non- recoverable after screen lock and screen completely fades to black or after system goes into sleep Status in linux-hwe-5.4 package in Ubuntu: Invalid Bug description: This is a fresh install of Ubuntu 18.04.6 on Dell Latitude 7390. The system is non-recoverable after it goes into sleep. Or after the screen is locked by the user and after it fades to complete black. System becomes unresponsive, no mouse or keypress will get the system back on to work. If the systemctl suspend is issued, the system will not wake up again. Hard reset is needed. If Ubuntu 18.04.6 is booted from live USB, the same is happening. Sometimes, when the system is rendered unresponsive as a result of any of the above, the power led is sending the message of "processor failure" (2 x amber blinks followed by 1 x white blink). Any help is greatly appreciated! I will keep the system as is, without applying any updates for now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 27 01:13:12 2022 InstallationDate: Installed on 2022-12-26 (0 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2000491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000491] Re: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-recoverable after screen lock and screen completely fades to black or after system goes into slee
I had Windows 10 Pro on this Dell Latitude 7390 which worked fine. I then booted 18.04.6 from live USB and had Ubuntu running good and well, have done an OS backup of Windows 10 and then went ahead and installed Ubuntu 18.04.6 on it, wiping everything off. Ubuntu 18.04.6 runs well on this laptop now UNTIL IT GOES INTO SUSPEND / HIBERNATE. After which won't wake up as expected. Instead, I have to do a hard reset and boot the system again. My hardware knowledge isn't that great, however, I believe this it not a hardware fault? Win 10 would have issues too? And Ubuntu would have issues too, prior to going into suspend / hibernate? Moreover, the "processor fault" could result in some command it gets when trying to the system into suspend? Moreover, why would Ubuntu 18.04.6 boot from a live USB stick and 22.04 or 22.10 wouldn't or if it does, will freeze shortly after showing the graphical desktop? I can restore Windows 10 and keep it as such, I just like Linux, esp. Ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2000491 Title: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non- recoverable after screen lock and screen completely fades to black or after system goes into sleep Status in linux-hwe-5.4 package in Ubuntu: Invalid Bug description: This is a fresh install of Ubuntu 18.04.6 on Dell Latitude 7390. The system is non-recoverable after it goes into sleep. Or after the screen is locked by the user and after it fades to complete black. System becomes unresponsive, no mouse or keypress will get the system back on to work. If the systemctl suspend is issued, the system will not wake up again. Hard reset is needed. If Ubuntu 18.04.6 is booted from live USB, the same is happening. Sometimes, when the system is rendered unresponsive as a result of any of the above, the power led is sending the message of "processor failure" (2 x amber blinks followed by 1 x white blink). Any help is greatly appreciated! I will keep the system as is, without applying any updates for now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 27 01:13:12 2022 InstallationDate: Installed on 2022-12-26 (0 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2000491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000798] Re: cannot connect to K380 bluetooth keyboard
Forgot to mention: I use this utility to invert Fn key behaviour: https://github.com/jergusg/k380-function-keys-conf ...and it's set up to start on boot using a variant of the procedure described here: https://github.com/embuc/k480_conf My /etc/udev/rules.d/80-k380.rules looks as follows: ACTION=="add", KERNEL=="hidraw[0-9]*", RUN+="/usr/local/bin/fn_on.sh /dev/%k" Tried temporarily removing the udev rule (without a reboot, though), but nothing changed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2000798 Title: cannot connect to K380 bluetooth keyboard Status in bluez package in Ubuntu: New Bug description: Had trouble connecting my K380 keyboard with the laptop (previously used it without issues), unpaired and now I can no longer pair it. Other bluetooth devices work with this particular laptop (mouse, earbuds), the keyboard works flawlessly with a different laptop (running the same Ubuntu 20.04 OS) and an Android phone. Used bluetoothctl to peek under the hood and got nowhere after turning scan on on the controller and activating the keyboard: [NEW] Device [...mac address of the keyboard...] Keyboard K380 [CHG] Device [...mac address of the keyboard...] Connected: no [DEL] Device [...mac address of the keyboard...] Keyboard K380 After this action, I get: # connect [...mac address of the keyboard...] Device [...mac address of the keyboard...] not available When I activate the keyboard (by pressing any key on it while it's turned on), in the bluetooth settings GUI tool I see the keyboard appear for a fraction of a second in the list of unpaired devices and then it disappears. Help? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 19:41:41 2022 InstallationDate: Installed on 2022-11-03 (57 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems LAPKC71E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCTGL357.0037.2021.0712.0948 dmi.board.name: LAPKC71E dmi.board.vendor: Intel Corporation dmi.board.version: M1-402 dmi.chassis.type: 10 dmi.chassis.vendor: Intel(R) Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnIntelCorp.:bvrKCTGL357.0037.2021.0712.0948:bd07/12/2021:br5.19:efr1.5:svnIntel(R)ClientSystems:pnLAPKC71E:pvrM38559-402:rvnIntelCorporation:rnLAPKC71E:rvrM1-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuBKC71EBFB6000: dmi.product.family: KC dmi.product.name: LAPKC71E dmi.product.sku: BKC71EBFB6000 dmi.product.version: M38559-402 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 20:1E:88:3C:4C:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:221779 acl:5063 sco:0 events:6018 errors:0 TX bytes:785416 acl:104 sco:0 commands:4168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000798/+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 2000798] [NEW] cannot connect to K380 bluetooth keyboard
Public bug reported: Had trouble connecting my K380 keyboard with the laptop (previously used it without issues), unpaired and now I can no longer pair it. Other bluetooth devices work with this particular laptop (mouse, earbuds), the keyboard works flawlessly with a different laptop (running the same Ubuntu 20.04 OS) and an Android phone. Used bluetoothctl to peek under the hood and got nowhere after turning scan on on the controller and activating the keyboard: [NEW] Device [...mac address of the keyboard...] Keyboard K380 [CHG] Device [...mac address of the keyboard...] Connected: no [DEL] Device [...mac address of the keyboard...] Keyboard K380 After this action, I get: # connect [...mac address of the keyboard...] Device [...mac address of the keyboard...] not available When I activate the keyboard (by pressing any key on it while it's turned on), in the bluetooth settings GUI tool I see the keyboard appear for a fraction of a second in the list of unpaired devices and then it disappears. Help? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 19:41:41 2022 InstallationDate: Installed on 2022-11-03 (57 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems LAPKC71E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCTGL357.0037.2021.0712.0948 dmi.board.name: LAPKC71E dmi.board.vendor: Intel Corporation dmi.board.version: M1-402 dmi.chassis.type: 10 dmi.chassis.vendor: Intel(R) Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnIntelCorp.:bvrKCTGL357.0037.2021.0712.0948:bd07/12/2021:br5.19:efr1.5:svnIntel(R)ClientSystems:pnLAPKC71E:pvrM38559-402:rvnIntelCorporation:rnLAPKC71E:rvrM1-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuBKC71EBFB6000: dmi.product.family: KC dmi.product.name: LAPKC71E dmi.product.sku: BKC71EBFB6000 dmi.product.version: M38559-402 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0: Type: Primary Bus: USB BD Address: 20:1E:88:3C:4C:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:221779 acl:5063 sco:0 events:6018 errors:0 TX bytes:785416 acl:104 sco:0 commands:4168 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2000798 Title: cannot connect to K380 bluetooth keyboard Status in bluez package in Ubuntu: New Bug description: Had trouble connecting my K380 keyboard with the laptop (previously used it without issues), unpaired and now I can no longer pair it. Other bluetooth devices work with this particular laptop (mouse, earbuds), the keyboard works flawlessly with a different laptop (running the same Ubuntu 20.04 OS) and an Android phone. Used bluetoothctl to peek under the hood and got nowhere after turning scan on on the controller and activating the keyboard: [NEW] Device [...mac address of the keyboard...] Keyboard K380 [CHG] Device [...mac address of the keyboard...] Connected: no [DEL] Device [...mac address of the keyboard...] Keyboard K380 After this action, I get: # connect [...mac address of the keyboard...] Device [...mac address of the keyboard...] not available When I activate the keyboard (by pressing any key on it while it's turned on), in the bluetooth settings GUI tool I see the keyboard appear for a fraction of a second in the list of unpaired devices and then it disappears. Help? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 19:41:41 2022 InstallationDate: Installed on 2022-11-03 (57 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems LAPKC71E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage:
[Kernel-packages] [Bug 1993539] Re: Nvidia GeForce GTX 560 M not recognized as an OpenCL platform with 5.15.0-50 kernel
Thx Micheal NALLINO, your workaround solved my issue. I'm running: Linux Mint 21.1 Cinnamon Kernel: 5.15.0.16-generic NVIDIA GeForce GTX 550 Ti (GF116) and opencl is now recognized. I had the same issue on my Asus U36S laptop and is now solved too. Laptop: Linux Mint 21.1 Cinnamon Kernel: 5.15.0.16-generic NVIDIA GeForce GT 520M Thx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1993539 Title: Nvidia GeForce GTX 560 M not recognized as an OpenCL platform with 5.15.0-50 kernel Status in linux-hwe-5.15 package in Ubuntu: New Bug description: Hi, Before to update to Linux Mint 21, based on Ubuntu 22.04 LTS, I have tried 5.15.0-50 kernel with HWE. This was intended as a test of my hardware compatibility with the hardware stack of Ubuntu 22.04, before a possible update. At a first glance, all seemed OK; nut I noticed that LibreOffice was unable to use OpenCL. A simple "clinfo" command confirmed this: $ clinfo Number of platforms 0 I went back from 5.15.0-50 kernel to 5.4.0-128 one. Now, "clinfo" output is: $ clinfo Number of platforms 1 Platform Name NVIDIA CUDA Platform Vendor NVIDIA Corporation Platform VersionOpenCL 1.2 CUDA 9.1.84 Platform ProfileFULL_PROFILE Platform Extensions cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_nv_create_buffer Platform Extensions function suffix NV Platform Name NVIDIA CUDA Number of devices 1 Device Name GeForce GTX 560M Device Vendor NVIDIA Corporation Device Vendor ID0x10de Device Version OpenCL 1.1 CUDA Driver Version 390.154 Device OpenCL C Version OpenCL C 1.1 Device Type GPU Device Topology (NV)PCI-E, 01:00.0 Device Profile FULL_PROFILE Device AvailableYes Compiler Available Yes Max compute units 4 Max clock frequency 1550MHz Compute Capability (NV) 2.1 Max work item dimensions3 Max work item sizes 1024x1024x64 Max work group size 1024 Preferred work group size multiple 32 Warp size (NV) 32 Preferred / native vector sizes char 1 / 1 short1 / 1 int 1 / 1 long 1 / 1 half 0 / 0(n/a) float1 / 1 double 1 / 1 (cl_khr_fp64) Half-precision Floating-point support (n/a) Single-precision Floating-point support (core) Denormals Yes Infinity and NANs Yes Round to nearest Yes Round to zero Yes Round to infinity Yes IEEE754-2008 fused multiply-add Yes Support is emulated in software No Correctly-rounded divide and sqrt operations No Double-precision Floating-point support (cl_khr_fp64) Denormals Yes Infinity and NANs Yes Round to nearest Yes Round to zero Yes Round to infinity Yes IEEE754-2008 fused multiply-add Yes Support is emulated in software No Address bits64, Little-Endian
[Kernel-packages] [Bug 2000792] [NEW] Source not comile because of missing Makefile
Public bug reported: linux-raspi source code which downloaded from repository by '$ sudo apt source linux-image-5.15.0-1021-raspi' with kernel option CONFIG_STRICT_DEVMEM=n not compile by 'sudo make' The error message: scripts/Makefile.build:44: arch/arm64/boot/dts/overlays/Makefile: No such file or directory make[2]: *** No rule to make target 'arch/arm64/boot/dts/overlays/Makefile'. Stop. make[1]: *** [scripts/Makefile.build:560: arch/arm64/boot/dts/overlays] Error 2 make: *** [Makefile:1442: dtbs] Error 2 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- 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/2000792 Title: Source not comile because of missing Makefile Status in linux-raspi package in Ubuntu: New Bug description: linux-raspi source code which downloaded from repository by '$ sudo apt source linux-image-5.15.0-1021-raspi' with kernel option CONFIG_STRICT_DEVMEM=n not compile by 'sudo make' The error message: scripts/Makefile.build:44: arch/arm64/boot/dts/overlays/Makefile: No such file or directory make[2]: *** No rule to make target 'arch/arm64/boot/dts/overlays/Makefile'. Stop. make[1]: *** [scripts/Makefile.build:560: arch/arm64/boot/dts/overlays] Error 2 make: *** [Makefile:1442: dtbs] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2000792/+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 2000786] [NEW] Source not compile with default gcc-11 - comipe fails on lz4_decompress.c
Public bug reported: linux-raspi source code which downloaded from repository by '$ sudo apt source linux-image-5.15.0-1021-raspi' with kernel option CONFIG_STRICT_DEVMEM=n not compile by 'sudo make' if gcc = gcc-11 (gcc 11.3.0) which is the default on Debian 22.04 LTS. The make/gcc fail on lz4_decompress.c Details see at: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108232 With gcc-12 the compile go through lz4_decompress.c ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- 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/2000786 Title: Source not compile with default gcc-11 - comipe fails on lz4_decompress.c Status in linux-raspi package in Ubuntu: New Bug description: linux-raspi source code which downloaded from repository by '$ sudo apt source linux-image-5.15.0-1021-raspi' with kernel option CONFIG_STRICT_DEVMEM=n not compile by 'sudo make' if gcc = gcc-11 (gcc 11.3.0) which is the default on Debian 22.04 LTS. The make/gcc fail on lz4_decompress.c Details see at: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108232 With gcc-12 the compile go through lz4_decompress.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2000786/+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 2000785] Re: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2000785 Title: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 Status in linux-intel-iotg package in Ubuntu: New Bug description: Does not let me upgrade with sudo apt upgrade says there is an error even though I have not changed anything in the system files. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-intel-iotg-tools-common 5.15.0-1018.23 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: linux-intel-iotg-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Dec 30 13:50:37 2022 DpkgTerminalLog: Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb ... Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1018.23) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 DuplicateSignature: package:linux-intel-iotg-tools-common:5.15.0-1018.23 Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1018.23) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 InstallationDate: Installed on 2022-10-06 (84 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-intel-iotg Title: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2000785/+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 2000785] [NEW] package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-commo
Public bug reported: Does not let me upgrade with sudo apt upgrade says there is an error even though I have not changed anything in the system files. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-intel-iotg-tools-common 5.15.0-1018.23 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: linux-intel-iotg-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Dec 30 13:50:37 2022 DpkgTerminalLog: Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb ... Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1018.23) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 DuplicateSignature: package:linux-intel-iotg-tools-common:5.15.0-1018.23 Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1018.23) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 InstallationDate: Installed on 2022-10-06 (84 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-intel-iotg Title: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2000785 Title: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 Status in linux-intel-iotg package in Ubuntu: New Bug description: Does not let me upgrade with sudo apt upgrade says there is an error even though I have not changed anything in the system files. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-intel-iotg-tools-common 5.15.0-1018.23 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: linux-intel-iotg-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Dec 30 13:50:37 2022 DpkgTerminalLog: Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb ... Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1018.23) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 DuplicateSignature: package:linux-intel-iotg-tools-common:5.15.0-1018.23 Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1018.23) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 InstallationDate: Installed on 2022-10-06 (84 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-intel-iotg Title: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2000785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 2000778] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2000778 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Kinetic) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000778 Title: pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Incomplete Bug description: Issue found with Kinetic 5.19.0-27.28 and 5.19.0-28.29 in this cycle (20221114) on these SUTs * P9 baltar * ARM64 kuzzle * ARM64 howzit-kernel This should not be considered as a regression as the net test cannot be built in 5.19.0-24.25 Test log: ubuntu@baltar:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] TEST: ipv6: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [ OK ] TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [ OK ] 'socat' command not found; skipping tests TEST: UDPv4 with DSCP and ECN: PMTU exceptions [SKIP] TEST: IPv4 over vxlan4: PMTU exceptions [ OK ] TEST: IPv4 over vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over vxlan4: PMTU exceptions [ OK ] TEST: IPv6 over vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv4 over vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4 over geneve4: PMTU exceptions[ OK ] TEST: IPv4 over geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over geneve4: PMTU exceptions[ OK ] TEST: IPv6 over geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4 over geneve6: PMTU exceptions[ OK ] TEST: IPv4 over geneve6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over geneve6: PMTU exceptions[ OK ] TEST: IPv6 over geneve6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged vxlan4: PMTU exceptions [ OK ] TEST: IPv4, bridged vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged vxlan4: PMTU exceptions [ OK ] TEST: IPv6, bridged vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged vxlan6: PMTU exceptions [ OK ] TEST: IPv4, bridged vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged vxlan6: PMTU exceptions [ OK ] TEST: IPv6, bridged vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged geneve4: PMTU exceptions[ OK ] TEST: IPv4, bridged geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged geneve4: PMTU exceptions[ OK ] TEST: IPv6, bridged geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged geneve6: PMTU exceptions[ OK ] TEST: IPv4, bridged geneve6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged geneve6: PMTU exceptions[ OK ] TEST: IPv6, bridged geneve6: PMTU exceptions - nexthop objects [ OK ] ovs_bridge not supported TEST: IPv4, OVS vxlan4: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv6, OVS vxlan4: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv4, OVS vxlan6: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv6, OVS vxlan6: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv4, OVS geneve4: PMTU
[Kernel-packages] [Bug 2000778] [NEW] pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19
Public bug reported: Issue found with Kinetic 5.19.0-27.28 and 5.19.0-28.29 in this cycle (20221114) on these SUTs * P9 baltar * ARM64 kuzzle * ARM64 howzit-kernel This should not be considered as a regression as the net test cannot be built in 5.19.0-24.25 Test log: ubuntu@baltar:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] TEST: ipv6: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [ OK ] TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [ OK ] 'socat' command not found; skipping tests TEST: UDPv4 with DSCP and ECN: PMTU exceptions [SKIP] TEST: IPv4 over vxlan4: PMTU exceptions [ OK ] TEST: IPv4 over vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over vxlan4: PMTU exceptions [ OK ] TEST: IPv6 over vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv4 over vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4 over geneve4: PMTU exceptions[ OK ] TEST: IPv4 over geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over geneve4: PMTU exceptions[ OK ] TEST: IPv6 over geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4 over geneve6: PMTU exceptions[ OK ] TEST: IPv4 over geneve6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over geneve6: PMTU exceptions[ OK ] TEST: IPv6 over geneve6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged vxlan4: PMTU exceptions [ OK ] TEST: IPv4, bridged vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged vxlan4: PMTU exceptions [ OK ] TEST: IPv6, bridged vxlan4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged vxlan6: PMTU exceptions [ OK ] TEST: IPv4, bridged vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged vxlan6: PMTU exceptions [ OK ] TEST: IPv6, bridged vxlan6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged geneve4: PMTU exceptions[ OK ] TEST: IPv4, bridged geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged geneve4: PMTU exceptions[ OK ] TEST: IPv6, bridged geneve4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4, bridged geneve6: PMTU exceptions[ OK ] TEST: IPv4, bridged geneve6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6, bridged geneve6: PMTU exceptions[ OK ] TEST: IPv6, bridged geneve6: PMTU exceptions - nexthop objects [ OK ] ovs_bridge not supported TEST: IPv4, OVS vxlan4: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv6, OVS vxlan4: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv4, OVS vxlan6: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv6, OVS vxlan6: PMTU exceptions [SKIP] ovs_bridge not supported TEST: IPv4, OVS geneve4: PMTU exceptions[SKIP] ovs_bridge not supported TEST: IPv6, OVS geneve4: PMTU exceptions[SKIP] ovs_bridge not supported TEST: IPv4, OVS geneve6: PMTU exceptions[SKIP] ovs_bridge not supported TEST: IPv6, OVS geneve6: PMTU exceptions[SKIP] TEST: IPv4 over fou4: PMTU exceptions [ OK ] TEST: IPv4 over fou4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over fou4: PMTU exceptions [ OK ] TEST: IPv6 over fou4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4 over fou6: PMTU exceptions [ OK ] TEST: IPv4 over fou6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over fou6: PMTU exceptions [ OK ] TEST: IPv6 over fou6: PMTU exceptions - nexthop objects [ OK ] TEST: IPv4 over gue4: PMTU exceptions [ OK ] TEST: IPv4 over gue4: PMTU exceptions - nexthop objects [ OK ] TEST: IPv6 over gue4: PMTU exceptions [ OK ]
[Kernel-packages] [Bug 1933969] Re: test_pmtu_vti4_link_add_mtu() test from net/pmtu.sh in ubuntu_kernel_selftests cannot finish properly on 5.11 and 5.8
** Changed in: ubuntu-kernel-tests Status: New => 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/1933969 Title: test_pmtu_vti4_link_add_mtu() test from net/pmtu.sh in ubuntu_kernel_selftests cannot finish properly on 5.11 and 5.8 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: Issue found with Groovy 5.8.0-60.67 on different amd64 / arm64 / s390x instances Test case: * tools/testing/selftests/net/pmtu.sh The pmtu.sh test will hang, and gets killed: # TEST: IPv6 over IPv6: PMTU exceptions - nexthop objects[ OK ] # TEST: vti6: PMTU exceptions[ OK ] Timer expired (1800 sec.), nuking pid 13090 If you take a closer look on this node, you will see it's complaining about unregister_netdevice and modprobe command hung: unregister_netdevice: waiting for ip6_vti0 to become free. Usage count = 1 unregister_netdevice: waiting for ip6_vti0 to become free. Usage count = 1 INFO: task modprobe:40237 blocked for more than 122 seconds. Tainted: P O 5.8.0-60-generic #67-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. modprobeD0 40237 1265 0x Call Trace: [<36dc7860>] __schedule+0x300/0x840 [<36dc7e02>] schedule+0x62/0x100 [<362c3bce>] rwsem_down_write_slowpath+0x23e/0x6c0 [<36b3716c>] register_pernet_device+0x2c/0xa0 [<03ff80a16034>] vti_init+0x34/0x1000 [ip_vti] [<361a88b0>] do_one_initcall+0x40/0x200 [<3632b34e>] do_init_module+0x6e/0x530 [<3632e06a>] __do_sys_finit_module+0xaa/0xf0 [<36dcefbc>] system_call+0xe0/0x2b8 unregister_netdevice: waiting for ip6_vti0 to become free. Usage count = 1 Running process shows: root 40236 0.0 0.0 3748 1040 ?D10:39 0:00 ip link add vti4_a type vti local 192.168.1.1 remote 192.168.1.2 key 10 root 40237 0.0 0.0 6092 1560 ?D10:39 0:00 /sbin/modprobe -q -- rtnl-link-vti This command "ip link add vti4_a type vti local" belongs to the test_pmtu_vti4_link_add_mtu() test in pmtu.sh This will prevent the whole ubuntu_kernel_selftests to finish On Jenkins, the test will hang and killed by the timeout: 10:08:18 INFO | == Summary === 10:08:18 INFO | No failed cases reported 10:08:18 INFO | GOODubuntu_kernel_selftests.ftrace ubuntu_kernel_selftests.ftrace timestamp=1624439298localtime=Jun 23 10:08:18 completed successfully 10:08:18 INFO | END GOODubuntu_kernel_selftests.ftrace ubuntu_kernel_selftests.ftrace timestamp=1624439298localtime=Jun 23 10:08:18 10:08:18 DEBUG| Persistent state client._record_indent now set to 1 10:08:18 DEBUG| Persistent state client.unexpected_reboot deleted 10:08:18 INFO | END GOOD timestamp=1624439298 localtime=Jun 23 10:08:18 10:08:18 DEBUG| Persistent state client._record_indent now set to 0 10:08:18 INFO | Report successfully generated at /home/ubuntu/autotest/client/results/default/job_report.html Build timed out (after 240 minutes). Marking the build as aborted. Build was aborted Recording test results ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? Since we don't have any change to the pmtu.sh in this cycle. This looks like a potential regression to me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1933969/+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 1999094] Re: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28
This failure still can be found on 5.19.0-1015.16, I guess it's because this was not respin yet? -- 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/1999094 Title: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Fix Committed Bug description: This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all instances. Running tests... vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vdso] bug not patched vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Looking at the contents of the triggered backtrace, on 5.19.0-26 the contents look like this: vma05 1 TPASS: [vsyscall] reported correctly vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso... [New LWP 418325] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `vma05_vdso'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)): #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=11, threadid=) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=, signo=signo@entry=11) at ./nptl/pthread_kill.c:89 #3 0x7f3093a3bc46 in __GI_raise (sig=sig@entry=11) at ../sysdeps/posix/raise.c:26 #4 0x55f54287a072 in main () at vma05_vdso.c:5 vma05 1 TPASS: [vdso] backtrace complete -- while on 5.19.0-27.28 it looks like this: vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso... [New LWP 1501] Core was generated by `vma05_vdso'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f9b3c09226b in ?? () Thread 1 (LWP 1501): #0 0x7f9b3c09226b in ?? () Backtrace stopped: Cannot access memory at address 0x7ffc216242b0 vma05 1 TFAIL: [vdso] bug not patched vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Suggesting that this bug has somehow been reintroduced. Will look into this further. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1999094/+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 2000667] Re: cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from ubuntu_kernel_selftests hang with non-amd64
This is affecting cmsg_ipv6.sh test as well, for amd64 this will fail with bug 2000709 ** Summary changed: - cmsg_so_mark.sh / cmsg_time.sh in net from ubuntu_kernel_selftests hang with non-amd64 + cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from ubuntu_kernel_selftests hang with non-amd64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000667 Title: cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from ubuntu_kernel_selftests hang with non-amd64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: New Status in linux source package in Lunar: Incomplete Bug description: Issue found with 5.19.0-1010.11, 5.19.0-1011.12 This issue does not exist in 5.19.0-1009.10 because the net test can't be built by that time. Test output: Running 'make run_tests -C net TEST_PROGS=cmsg_so_mark.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=riscv -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: cmsg_so_mark.sh Timer expired (5400 sec.), nuking pid 82951 A manual test shows it will stuck with: $ sudo ./cmsg_so_mark.sh + NS=ns + IP4=172.16.0.1/24 + TGT4=172.16.0.2 + IP6=2001:db8:1::1/64 + TGT6=2001:db8:1::2 + MARK=1000 + trap cleanup EXIT + ip netns add ns + ip netns exec ns sysctl -w 'net.ipv4.ping_group_range=0 2147483647' + ip -netns ns link add type dummy + ip -netns ns link set dev dummy0 up + ip -netns ns addr add 172.16.0.1/24 dev dummy0 + ip -netns ns addr add 2001:db8:1::1/64 dev dummy0 + ip -netns ns rule add fwmark 1000 lookup 300 + ip -6 -netns ns rule add fwmark 1000 lookup 300 + ip -netns ns route add prohibit any table 300 + ip -6 -netns ns route add prohibit any table 300 + BAD=0 + TOTAL=0 + for ovr in setsock cmsg both + for i in 4 6 + '[' 4 == 4 ']' + TGT=172.16.0.2 + for p in u i r + '[' u == u ']' + prot=UDP + '[' u == i ']' + '[' u == r ']' + '[' setsock == setsock ']' + m=-M + '[' setsock == cmsg ']' + '[' setsock == both ']' + ip netns exec ns ./cmsg_sender -4 -p u -M 1001 172.16.0.2 1234 (test stuck here) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000667/+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 2000667] Re: cmsg_so_mark.sh / cmsg_time.sh in net from ubuntu_kernel_selftests hang with non-amd64
** Summary changed: - cmsg_so_mark.sh / cmsg_time.sh in net from ubuntu_kernel_selftests hang with K-RISCV kernel + cmsg_so_mark.sh / cmsg_time.sh in net from ubuntu_kernel_selftests hang with non-amd64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000667 Title: cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from ubuntu_kernel_selftests hang with non-amd64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: New Status in linux source package in Lunar: Incomplete Bug description: Issue found with 5.19.0-1010.11, 5.19.0-1011.12 This issue does not exist in 5.19.0-1009.10 because the net test can't be built by that time. Test output: Running 'make run_tests -C net TEST_PROGS=cmsg_so_mark.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=riscv -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: cmsg_so_mark.sh Timer expired (5400 sec.), nuking pid 82951 A manual test shows it will stuck with: $ sudo ./cmsg_so_mark.sh + NS=ns + IP4=172.16.0.1/24 + TGT4=172.16.0.2 + IP6=2001:db8:1::1/64 + TGT6=2001:db8:1::2 + MARK=1000 + trap cleanup EXIT + ip netns add ns + ip netns exec ns sysctl -w 'net.ipv4.ping_group_range=0 2147483647' + ip -netns ns link add type dummy + ip -netns ns link set dev dummy0 up + ip -netns ns addr add 172.16.0.1/24 dev dummy0 + ip -netns ns addr add 2001:db8:1::1/64 dev dummy0 + ip -netns ns rule add fwmark 1000 lookup 300 + ip -6 -netns ns rule add fwmark 1000 lookup 300 + ip -netns ns route add prohibit any table 300 + ip -6 -netns ns route add prohibit any table 300 + BAD=0 + TOTAL=0 + for ovr in setsock cmsg both + for i in 4 6 + '[' 4 == 4 ']' + TGT=172.16.0.2 + for p in u i r + '[' u == u ']' + prot=UDP + '[' u == i ']' + '[' u == r ']' + '[' setsock == setsock ']' + m=-M + '[' setsock == cmsg ']' + '[' setsock == both ']' + ip netns exec ns ./cmsg_sender -4 -p u -M 1001 172.16.0.2 1234 (test stuck here) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000667/+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 2000706] Re: Lunar update: v6.1.1 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v6.1.1 upstream stable release + from git://git.kernel.org/ -v6.1.1 upstream stable release -from git://git.kernel.org/ + x86/vdso: Conditionally export __vdso_sgx_enter_enclave() + libbpf: Fix uninitialized warning in btf_dump_dump_type_data + PCI: mt7621: Add sentinel to quirks table + mips: ralink: mt7621: define MT7621_SYSC_BASE with __iomem + mips: ralink: mt7621: soc queries and tests as functions + mips: ralink: mt7621: do not use kzalloc too early + irqchip/ls-extirq: Fix endianness detection + udf: Discard preallocation before extending file with a hole + udf: Fix preallocation discarding at indirect extent boundary + udf: Do not bother looking for prealloc extents if i_lenExtents matches i_size + udf: Fix extending file within last block + usb: gadget: uvc: Prevent buffer overflow in setup handler + USB: serial: option: add Quectel EM05-G modem + USB: serial: cp210x: add Kamstrup RF sniffer PIDs + USB: serial: f81232: fix division by zero on line-speed change + USB: serial: f81534: fix division by zero on line-speed change + xhci: Apply XHCI_RESET_TO_DEFAULT quirk to ADL-N + staging: r8188eu: fix led register settings + igb: Initialize mailbox message for VF reset + usb: typec: ucsi: Resume in separate work + usb: dwc3: pci: Update PCIe device ID for USB3 controller on CPU sub-system for Raptor Lake + cifs: fix oops during encryption + KEYS: encrypted: fix key instantiation with user-provided data + Linux 6.1.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/2000706 Title: Lunar update: v6.1.1 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Lunar: Confirmed 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: v6.1.1 upstream stable release from git://git.kernel.org/ x86/vdso: Conditionally export __vdso_sgx_enter_enclave() libbpf: Fix uninitialized warning in btf_dump_dump_type_data PCI: mt7621: Add sentinel to quirks table mips: ralink: mt7621: define MT7621_SYSC_BASE with __iomem mips: ralink: mt7621: soc queries and tests as functions mips: ralink: mt7621: do not use kzalloc too early irqchip/ls-extirq: Fix endianness detection udf: Discard preallocation before extending file with a hole udf: Fix preallocation discarding at indirect extent boundary udf: Do not bother looking for prealloc extents if i_lenExtents matches i_size udf: Fix extending file within last block usb: gadget: uvc: Prevent buffer overflow in setup handler USB: serial: option: add Quectel EM05-G modem USB: serial: cp210x: add Kamstrup RF sniffer PIDs USB: serial: f81232: fix division by zero on line-speed change USB: serial: f81534: fix division by zero on line-speed change xhci: Apply XHCI_RESET_TO_DEFAULT quirk to ADL-N staging: r8188eu: fix led register settings igb: Initialize mailbox message for VF reset usb: typec: ucsi: Resume in separate work usb: dwc3: pci: Update PCIe device ID for USB3 controller on CPU sub-system for Raptor Lake cifs: fix oops during encryption KEYS: encrypted: fix key instantiation with user-provided data Linux 6.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000706/+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 2000772] Re: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19
https://lists.ubuntu.com/archives/kernel-team/2022-December/135802.html ** Description changed: + [Impact] + When trying to build powerpc tests from ubuntu_kernel_selftests, it + will fail with: + inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: + /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] + 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); + | ^~~ + cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: + cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here + 25 | uint64_t val, expected[2], actual; + | ^~ + cc1: all warnings being treated as errors + + [Fix] + * ff446cd768 "selftests/powerpc: Avoid GCC 12 uninitialised variable warning" + This patch can be cherry-picked into Kinetic kernel. + + [Test] + Apply this patch to the kernel tree and build it with: + sudo make -C linux/tools/testing/selftests TARGETS=powerpc + + With this error fixed, test compliation can finish without any issue. + + [Where problems could occur] + Change for test case, no impact to acutal function. + + [Original Bug Report] Issue found with K-5.19.0-28-generic on P9 node baltar This should not be considered as a regression since ubuntu_kernel_selftests will be blocked by the net test crash before this powerpc tests can be started. This was found by manually running the test. Test build failed with: gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"unknown"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include -m64 -no-pie cycles_with_mmcr2_test.c ../../harness.c ../../utils.c ../event.c ../lib.c ebb.c ebb_handler.S trace.c busy_loop.S -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test In file included from /usr/include/stdio.h:906, - from cycles_with_mmcr2_test.c:6: + from cycles_with_mmcr2_test.c:6: In function ‘printf’, - inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: + inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] -86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); - | ^~~ + 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); + | ^~~ cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here -25 | uint64_t val, expected[2], actual; - |^~ + 25 | uint64_t val, expected[2], actual; + |^~ cc1: all warnings being treated as errors make[3]: *** [../../../lib.mk:173: /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test] Error 1 - Please find attachment for the complete build 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/2000772 Title: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Kinetic: In Progress Bug description: [Impact] When trying to build powerpc tests from ubuntu_kernel_selftests, it will fail with: inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); | ^~~ cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here 25 | uint64_t val, expected[2], actual; | ^~ cc1: all warnings being treated as errors [Fix] * ff446cd768 "selftests/powerpc: Avoid GCC 12 uninitialised variable warning" This patch can be cherry-picked into Kinetic kernel. [Test] Apply this patch to the kernel tree and build it with: sudo make -C linux/tools/testing/selftests TARGETS=powerpc With this error fixed, test compliation can finish without any issue. [Where problems could occur] Change for test case, no impact to acutal function. [Original Bug Report] Issue found with
[Kernel-packages] [Bug 1968310] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1968310 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Kinetic) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968310 Title: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Incomplete Bug description: Issue found on Jammy OEM 5.17.0-1003.3 It looks like all the sub-tests has passed, but the final return value is not 0. Running 'make run_tests -C net TEST_PROGS=arp_ndisc_evict_nocarrier.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: arp_ndisc_evict_nocarrier.sh # run arp_evict_nocarrier=1 test # ok # run arp_evict_nocarrier=0 test # ok # run all.arp_evict_nocarrier=0 test # ok # run ndisc_evict_nocarrier=1 test # ok # run ndisc_evict_nocarrier=0 test # ok # run all.ndisc_evict_nocarrier=0 test # ok not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255 make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968310/+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 2000772] Re: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) 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/2000772 Title: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Kinetic: In Progress Bug description: Issue found with K-5.19.0-28-generic on P9 node baltar This should not be considered as a regression since ubuntu_kernel_selftests will be blocked by the net test crash before this powerpc tests can be started. This was found by manually running the test. Test build failed with: gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"unknown"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include -m64 -no-pie cycles_with_mmcr2_test.c ../../harness.c ../../utils.c ../event.c ../lib.c ebb.c ebb_handler.S trace.c busy_loop.S -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test In file included from /usr/include/stdio.h:906, from cycles_with_mmcr2_test.c:6: In function ‘printf’, inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); | ^~~ cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here 25 | uint64_t val, expected[2], actual; |^~ cc1: all warnings being treated as errors make[3]: *** [../../../lib.mk:173: /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test] Error 1 Please find attachment for the complete build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000772/+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 2000772] Re: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19
Fix from upstream https://github.com/torvalds/linux/commit/ff446cd76854d47f451a84c26bb70934ae2ec5a7 -- 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/2000772 Title: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Kinetic: New Bug description: Issue found with K-5.19.0-28-generic on P9 node baltar This should not be considered as a regression since ubuntu_kernel_selftests will be blocked by the net test crash before this powerpc tests can be started. This was found by manually running the test. Test build failed with: gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"unknown"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include -m64 -no-pie cycles_with_mmcr2_test.c ../../harness.c ../../utils.c ../event.c ../lib.c ebb.c ebb_handler.S trace.c busy_loop.S -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test In file included from /usr/include/stdio.h:906, from cycles_with_mmcr2_test.c:6: In function ‘printf’, inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); | ^~~ cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here 25 | uint64_t val, expected[2], actual; |^~ cc1: all warnings being treated as errors make[3]: *** [../../../lib.mk:173: /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test] Error 1 Please find attachment for the complete build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000772/+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 2000772] [NEW] powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19
Public bug reported: Issue found with K-5.19.0-28-generic on P9 node baltar This should not be considered as a regression since ubuntu_kernel_selftests will be blocked by the net test crash before this powerpc tests can be started. This was found by manually running the test. Test build failed with: gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"unknown"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include -m64 -no-pie cycles_with_mmcr2_test.c ../../harness.c ../../utils.c ../event.c ../lib.c ebb.c ebb_handler.S trace.c busy_loop.S -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test In file included from /usr/include/stdio.h:906, from cycles_with_mmcr2_test.c:6: In function ‘printf’, inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); | ^~~ cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here 25 | uint64_t val, expected[2], actual; |^~ cc1: all warnings being treated as errors make[3]: *** [../../../lib.mk:173: /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test] Error 1 Please find attachment for the complete build log. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Tags: 5.19 kinetic ppc64el sru-20221114 ubuntu-kernel-selftests ** Attachment added: "powerpc-build.log" https://bugs.launchpad.net/bugs/2000772/+attachment/5638534/+files/powerpc-build.log ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) 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/2000772 Title: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Kinetic: New Bug description: Issue found with K-5.19.0-28-generic on P9 node baltar This should not be considered as a regression since ubuntu_kernel_selftests will be blocked by the net test crash before this powerpc tests can be started. This was found by manually running the test. Test build failed with: gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"unknown"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include -m64 -no-pie cycles_with_mmcr2_test.c ../../harness.c ../../utils.c ../event.c ../lib.c ebb.c ebb_handler.S trace.c busy_loop.S -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test In file included from /usr/include/stdio.h:906, from cycles_with_mmcr2_test.c:6: In function ‘printf’, inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); | ^~~ cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here 25 | uint64_t val, expected[2], actual; |^~ cc1: all warnings being treated as errors make[3]: *** [../../../lib.mk:173: /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test] Error 1 Please find attachment for the complete build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000772/+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 1968310] Re: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17
Patch submitted upstream https://lore.kernel.org/netdev/20221230091829.217007-1-po-hsu@canonical.com/T/#t ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 + arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K ** Also affects: linux (Ubuntu Kinetic) 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/1968310 Title: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Kinetic: New Bug description: Issue found on Jammy OEM 5.17.0-1003.3 It looks like all the sub-tests has passed, but the final return value is not 0. Running 'make run_tests -C net TEST_PROGS=arp_ndisc_evict_nocarrier.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: arp_ndisc_evict_nocarrier.sh # run arp_evict_nocarrier=1 test # ok # run arp_evict_nocarrier=0 test # ok # run all.arp_evict_nocarrier=0 test # ok # run ndisc_evict_nocarrier=1 test # ok # run ndisc_evict_nocarrier=0 test # ok # run all.ndisc_evict_nocarrier=0 test # ok not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255 make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968310/+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
