[Kernel-packages] [Bug 2001721] Re: [amdgpu] Ubuntu screen green flickering
Thank you for taking the time to report this bug and helping to make Ubuntu better. I noted this at https://askubuntu.com/questions/1449114/ubuntu-20-04-screen-green- flickering-lenovo-ideapad-s145-15ast I wonder if it's a problem related to the 'new' HDMI cable. I suggest booting a different OS, or different release of Ubuntu using 'live' media & seeing if the issue occurs there, ie. confirming it's related to Ubuntu, and not just the 'new HDMI cable'. Apologies if I've mis-understood your 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/2001721 Title: [amdgpu] Ubuntu screen green flickering Status in linux package in Ubuntu: New Bug description: Hi i did use ubuntu for more than a year on this laptop last a few days i used HDMI cable, today for a few hours i did use a new cable "longer one" now suddenly my laptop display went green as you can see in the attachment i did some search but can't find solution. https://askubuntu.com/questions/1231441/ubuntu-screen-flickering/1250859#1250859 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534 Ali ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 4 22:41:41 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev e2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3f1a] InstallationDate: Installed on 2021-12-20 (380 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 81N3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=52450c12-da25-47db-984c-a2036e93aff5 ro reboot=pci quiet splash acpi=force vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.release: 1.20 dmi.bios.vendor: LENOVO dmi.bios.version: AYCN20WW 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: Lenovo IdeaPad S145-15AST dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrAYCN20WW:bd11/27/2019:br1.20:efr1.20:svnLENOVO:pn81N3:pvrLenovoIdeaPadS145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15AST:skuLENOVO_MT_81N3_BU_idea_FM_IdeaPadS145-15AST: dmi.product.family: IdeaPad S145-15AST dmi.product.name: 81N3 dmi.product.sku: LENOVO_MT_81N3_BU_idea_FM_IdeaPad S145-15AST dmi.product.version: Lenovo IdeaPad S145-15AST dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001721/+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 1886714] Re: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect
The bug is still present in Ubuntu 22.10 on a Gigabyte Technology Co., Ltd. GA-990FXA-UD3, when attached to an HK Onyx Studio 6. Usually a work around is to restart the Bluetooth stack twice. My wild guess is that a (ring) buffer in the Bluetooth stack is filled, and isn't reset because the sound system can't catch up. It then goes on until it crashes. -- 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/1886714 Title: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters:
[Kernel-packages] [Bug 1995787] Re: After upgrading my system suddenly my PC got freeze and start showing EXT4-fs error
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1995787 Title: After upgrading my system suddenly my PC got freeze and start showing EXT4-fs error Status in linux package in Ubuntu: Expired Bug description: After upgrading my system suddenly my PC got freeze and start showing black screen and EXT4-fs error these are some last updated packages below and I user sudo apt upgrade cmd. 2022-11-04 09:15:24 upgrade code-insiders:amd64 1.74.0-1667455053 1.74.0-1667502703 2022-11-04 09:15:38 upgrade mutter-common:all 42.2-0ubuntu1 42.5-0ubuntu1 2022-11-04 09:15:38 upgrade gir1.2-mutter-10:amd64 42.2-0ubuntu1 42.5-0ubuntu1 2022-11-04 09:15:38 upgrade libmutter-10-0:amd64 42.2-0ubuntu1 42.5-0ubuntu1 2022-11-05 08:33:17 upgrade tzdata:all 2022e-0ubuntu0.22.04.0 2022f-0ubuntu0.22.04.0 2022-11-05 11:37:45 upgrade code-insiders:amd64 1.74.0-1667502703 1.74.0-1667540431 2022-11-05 11:37:58 upgrade nodejs:amd64 16.18.0-deb-1nodesource1 16.18.1-deb-1nodesource1 2022-11-06 12:12:28 upgrade distro-info-data:all 0.52ubuntu0.1 0.52ubuntu0.2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.14 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 12:55:01 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995787/+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 2002194] Re: minetest crashes
the attached dmesg is relevant: [24734.774011] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:84db, in minetest [8353] -- 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/2002194 Title: minetest crashes Status in linux package in Ubuntu: New Bug description: Hello, sometimes minetest hangs for tens of seconds, sometimes it just crashes (interrupted (core dumped)), but sometimes it makes the complete machine unrecoverably freeze which makes me believe it's a kernel (gpu driver?) level issue. steps to reproduce: 1, have an up-to-date ubuntu 22.04 lts installed 2. compile minetest from source: 587f6656a 3. play expected result: user having fun, machine not crashing actual result: machine crashing, hanging temporarily, game crashing Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-57-generic 5.15.0-57.63 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi3717 F pulseaudio /dev/snd/controlC1: imi3717 F pulseaudio /dev/snd/pcmC1D0p: imi3717 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jan 7 03:00:44 2023 InstallationDate: Installed on 2022-05-05 (246 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Latitude 5430 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=/dev/mapper/vg_af1-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2022 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.3 dmi.board.name: 04X33N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.3:bd10/27/2022:br1.8:svnDellInc.:pnLatitude5430:pvr:rvnDellInc.:rn04X33N:rvrA00:cvnDellInc.:ct10:cvr:sku0B04: dmi.product.family: Latitude dmi.product.name: Latitude 5430 dmi.product.sku: 0B04 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002194/+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 2002194] [NEW] minetest crashes
Public bug reported: Hello, sometimes minetest hangs for tens of seconds, sometimes it just crashes (interrupted (core dumped)), but sometimes it makes the complete machine unrecoverably freeze which makes me believe it's a kernel (gpu driver?) level issue. steps to reproduce: 1, have an up-to-date ubuntu 22.04 lts installed 2. compile minetest from source: 587f6656a 3. play expected result: user having fun, machine not crashing actual result: machine crashing, hanging temporarily, game crashing Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-57-generic 5.15.0-57.63 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi3717 F pulseaudio /dev/snd/controlC1: imi3717 F pulseaudio /dev/snd/pcmC1D0p: imi3717 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jan 7 03:00:44 2023 InstallationDate: Installed on 2022-05-05 (246 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Latitude 5430 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=/dev/mapper/vg_af1-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2022 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.3 dmi.board.name: 04X33N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.3:bd10/27/2022:br1.8:svnDellInc.:pnLatitude5430:pvr:rvnDellInc.:rn04X33N:rvrA00:cvnDellInc.:ct10:cvr:sku0B04: dmi.product.family: Latitude dmi.product.name: Latitude 5430 dmi.product.sku: 0B04 dmi.sys.vendor: Dell Inc. ** Affects: linux (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 linux in Ubuntu. https://bugs.launchpad.net/bugs/2002194 Title: minetest crashes Status in linux package in Ubuntu: New Bug description: Hello, sometimes minetest hangs for tens of seconds, sometimes it just crashes (interrupted (core dumped)), but sometimes it makes the complete machine unrecoverably freeze which makes me believe it's a kernel (gpu driver?) level issue. steps to reproduce: 1, have an up-to-date ubuntu 22.04 lts installed 2. compile minetest from source: 587f6656a 3. play expected result: user having fun, machine not crashing actual result: machine crashing, hanging temporarily, game crashing Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-57-generic 5.15.0-57.63 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi3717 F pulseaudio /dev/snd/controlC1: imi3717 F pulseaudio /dev/snd/pcmC1D0p: imi3717 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jan 7 03:00:44 2023 InstallationDate: Installed on 2022-05-05 (246 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Latitude 5430 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=/dev/mapper/vg_af1-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2022 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.3 dmi.board.name: 04X33N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.3:bd10/27/2022:br1.8:svnDellInc.:pnLatitude5430:pvr:rvnDellInc.:rn04X33N:rvrA00:cvnDellInc.:ct10:cvr:sku0B04: dmi.product.family: Latitude dmi.product.name: Latitude 5430 dmi.product.sku: 0B04
[Kernel-packages] [Bug 1983180]
Sorry, I forgot to include the exact messages! These are the messages that appear in the systemlog and on the console, interrupting the splash screen: [0.857051] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20210730/psargs-330) [0.858519] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.859946] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20210730/psargs-330) [0.861572] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.863666] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20210730/psargs-330) [0.865063] ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.866642] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20210730/psargs-330) [0.868458] ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-529) -- 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/1983180 Title: ACPI Error _CPC not found Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: just recently (I guess since the last update) I get a few ACPI error messages during start up. Those are also visible with dmesg: ... [0.713907] ACPI: AC: AC Adapter [AC] (on-line) [0.713978] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 [0.714011] ACPI: button: Sleep Button [SLPB] [0.714040] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 [0.714061] ACPI: button: Lid Switch [LID] [0.714087] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [0.714105] ACPI: button: Power Button [PWRF] [0.714187] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714199] No Local Variables are initialized for Method [_CPC] [0.714201] No Arguments are initialized for method [_CPC] [0.714203] ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714395] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714404] No Local Variables are initialized for Method [_CPC] [0.714405] No Arguments are initialized for method [_CPC] [0.714407] ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714480] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714488] No Local Variables are initialized for Method [_CPC] [0.714490] No Arguments are initialized for method [_CPC] [0.714492] ACPI Error: Aborting method \_SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714640] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714651] No Local Variables are initialized for Method [_CPC] [0.714653] No Arguments are initialized for method [_CPC] [0.714655] ACPI Error: Aborting method \_SB.PR04._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714940] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714952] No Local Variables are initialized for Method [_CPC] [0.714953] No Arguments are initialized for method [_CPC] [0.714955] ACPI Error: Aborting method \_SB.PR05._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.715106] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.715118] No Local Variables are initialized for Method [_CPC] [0.715119] No Arguments are initialized for method [_CPC] [0.715121] ACPI Error: Aborting method \_SB.PR06._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.715309] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.715321] No Local Variables are initialized for Method [_CPC] [0.715322] No Arguments are initialized for method [_CPC] [0.715324] ACPI Error: Aborting method \_SB.PR07._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.715611] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.715623] No Local Variables are initialized for Method [_CPC] [0.715624] No Arguments are initialized for method [_CPC] [0.715626] ACPI Error: Aborting method \_SB.PR08._CPC due to
[Kernel-packages] [Bug 1983180]
It is January 2023 now, and this bug is still active in kernel 5.15.86. :( I am running KDE Neon with self compiled kernel 5.15.x (because it is marked as "longterm") on a Fujitsu mainboard, equipped with an Intel Core i5. (See below.) I wouldn't mind having these messages in the systemlog, as they are harmless and the system runs without any quirk. But but they appear on the console as well, even interrupting the splash screen! (Which is a bit of a humiliation, if there's a Windows user looking over your shoulder while your machine is booting...) I know that this is a pure cosmetic complain, but it has been happening for more than a year now, and I really would like to get rid of this annoyance. I tried the usual grub command line options like "loglevel=3" "acpi_osi=! \"acpi_osi=Windows 2015\"" but neither did suppress these console messages. Hardware information: ~$ LC_ALL="C" sudo dmidecode -t 2 # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 3.0.0 present. Handle 0x0043, DMI type 2, 15 bytes Base Board Information Manufacturer: FUJITSU Product Name: D3431-A1 Version: S26361-D3431-A1 Serial Number: 51857501 Asset Tag: Features: Board is a hosting board Board is replaceable Location In Chassis: Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 ~$ LC_ALL="C" lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 39 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Vendor ID: GenuineIntel Model name:Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz CPU family: 6 Model: 94 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 Stepping:3 CPU max MHz: 3600. CPU min MHz: 800. BogoMIPS:6399.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts ac pi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_p erfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dte s64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2 apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefet ch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriorit y 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 hw p_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities ... -- 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/1983180 Title: ACPI Error _CPC not found Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: just recently (I guess since the last update) I get a few ACPI error messages during start up. Those are also visible with dmesg: ... [0.713907] ACPI: AC: AC Adapter [AC] (on-line) [0.713978] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 [0.714011] ACPI: button: Sleep Button [SLPB] [0.714040] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 [0.714061] ACPI: button: Lid Switch [LID] [0.714087] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [0.714105] ACPI: button: Power Button [PWRF] [0.714187] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714199] No Local Variables are initialized for Method [_CPC] [0.714201] No Arguments are initialized for method [_CPC] [0.714203] ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714395] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714404] No Local Variables are initialized for Method [_CPC] [0.714405] No Arguments are initialized for method [_CPC] [0.714407] ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714480] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714488] No Local Variables are initialized for Method [_CPC] [0.714490] No Arguments are initialized
[Kernel-packages] [Bug 2002191] [NEW] 5.4.0.136
Public bug reported: Can't shutdown ** 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/2002191 Title: 5.4.0.136 Status in linux package in Ubuntu: New Bug description: Can't shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002191/+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 1981783]
Sorry, I forgot to include the exact messages! These are the messages that appear in the systemlog and on the console, interrupting the splash screen: [0.857051] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20210730/psargs-330) [0.858519] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.859946] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20210730/psargs-330) [0.861572] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.863666] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20210730/psargs-330) [0.865063] ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.866642] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20210730/psargs-330) [0.868458] ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-529) -- 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/1981783 Title: there is an ACPI error message every time it booting Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: there is the following message every time it boots [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 11:15:30 2022 InstallationDate: Installed on 2022-04-21 (85 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1981783/+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 1981783]
It is January 2023 now, and this bug is still active in kernel 5.15.86. :( I am running KDE Neon with self compiled kernel 5.15.x (because it is marked as "longterm") on a Fujitsu mainboard, equipped with an Intel Core i5. (See below.) I wouldn't mind having these messages in the systemlog, as they are harmless and the system runs without any quirk. But but they appear on the console as well, even interrupting the splash screen! (Which is a bit of a humiliation, if there's a Windows user looking over your shoulder while your machine is booting...) I know that this is a pure cosmetic complain, but it has been happening for more than a year now, and I really would like to get rid of this annoyance. I tried the usual grub command line options like "loglevel=3" "acpi_osi=! \"acpi_osi=Windows 2015\"" but neither did suppress these console messages. Hardware information: ~$ LC_ALL="C" sudo dmidecode -t 2 # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 3.0.0 present. Handle 0x0043, DMI type 2, 15 bytes Base Board Information Manufacturer: FUJITSU Product Name: D3431-A1 Version: S26361-D3431-A1 Serial Number: 51857501 Asset Tag: Features: Board is a hosting board Board is replaceable Location In Chassis: Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 ~$ LC_ALL="C" lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 39 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Vendor ID: GenuineIntel Model name:Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz CPU family: 6 Model: 94 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 Stepping:3 CPU max MHz: 3600. CPU min MHz: 800. BogoMIPS:6399.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts ac pi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_p erfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dte s64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2 apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefet ch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriorit y 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 hw p_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities ... -- 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/1981783 Title: there is an ACPI error message every time it booting Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: there is the following message every time it boots [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 11:15:30 2022 InstallationDate: Installed on 2022-04-21 (85 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1981783/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
The entire upload will be uploaded to all older releases but we do have a security upload already in the unapproved queues that should go out first, but that needs approving those first, them passing the SRU verification, a resigning against the new signing key the new shim needs, and finally someone to release them. So that the security update can be released to security pocket. This won't be ready before Monday the week after next week at the earliest (7 day testing period in proposed). People that can approve are still out and only return next week, so I don't think that's entirely realistic we get the existing uploads into proposed on Monday. If we could get them in by Thursday they could go out Monday the 23rd and we may be able to then upload this fix and release it on like 31st or so. We're strictly limited by the point release - it needs to be ready for that. ** Changed in: grub2-signed (Ubuntu) Milestone: None => ubuntu-22.04.2 ** Changed in: grub2-unsigned (Ubuntu) Milestone: None => ubuntu-22.04.2 -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Fix Committed Status in grub2-unsigned package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Workaround] Some workarounds have been suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125 [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory region starvation in <1G addresses: Type StartEnd # Pages Attributes Available -00086FFF 0087 000F BS_Data00087000-00087FFF 0001 000F Available 00088000-0009EFFF 0017 000F Reserved 0009F000-0009 0001 000F Available 0010-00FF 0F00 000F LoaderCode 0100-01021FFF 0022 000F Available 01022000-238A7FFF 00022886 000F BS_Data238A8000-23927FFF 0080 000F Available 23928000-28860FFF 4F39 000F BS_Data28861000-2AB09FFF 22A9 000F LoaderCode 2AB0A000-2ACF8FFF 01EF 000F BS_Data2ACF9000-2B2FAFFF 0602 000F Available 2B2FB000-2B611FFF 0317 000F BS_Data2B612000-2B630FFF 001F 000F Available 2B631000-2B632FFF 0002 000F BS_Data2B633000-2B63CFFF 000A 000F Available 2B63D000-2B649FFF 000D 000F BS_Data2B64A000-2B64EFFF 0005 000F Available 2B64F000-2B666FFF 0018 000F BS_Data2B667000-2D8D5FFF 226F 000F LoaderCode 2D8D6000-2D8E9FFF 0014 000F BS_Data2D8EA000-2D925FFF 003C 000F LoaderCode 2D926000-2D932FFF 000D 000F
[Kernel-packages] [Bug 1998950] Re: GPU hang on Alder Lake laptop
Since there appears to be upstream patches in kernel 6.0 and Mesa 22.3.1 which fix this, perhaps it would be possible to backport those to the versions in Ubuntu 22.10? If not, would it at least be possible to upload such packages to Lunar so that there's an option which doesn't involve reinstalling the machine to go back to 22.04? Right now my machine is freezing multiple times per day and it would be really valuable to get those backports applied. I'm pretty sure this affects all Alder Lake-P GPUs on Kinetic, since the upstream bug report mentions multiple different hardware variants. -- 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/1998950 Title: GPU hang on Alder Lake laptop Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.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-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1998950/+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 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
This bug looks like its been verified, but the bot has flipped the verification tags. Setting back to done. ** Tags removed: verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-focal verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: IMPACT: Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak Suggested-by: Rafael J. Wysocki Signed-off-by: Dave Hansen Reviewed-by: Mario Limonciello Tested-by: K Prateek Nayak Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com FIX: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 TESTCASE: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+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 1996740] Re: 5.15.0-53-generic no longer boots
Based on #61 I'm marking this bug as verification complete. ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: == SRU Justification == [Impact] "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp displays" caused AMD Navi10 GFX to panic at boot. [Fix] Backport the revised version of "drm/amd/display: Add helper for blanking all dp displays". [Test] Users confirmed the issue went away with this fix. We also verified the original issue we fixed didn't reappear. [Where problems could occur] We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many cases are untested, hence the potential risk is there. == Original Bug Report == Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+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 1995408] Re: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks
Microsoft tested, marking verification done. ** Tags added: verification-done-kinetic -- 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/1995408 Title: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] Hypervisor only allocates interrupts to happen on a single physical GPU, which can lead to CPU soft locks when using PCI NVME under heavy load. Kinetic will get this patch via stable updates. [Test Case] Microsoft tested [Where things could go wrong] Hypervisor PCI driver may not load correctly. Patch did not apply cleanly and could lead to merge conflicts once the upstream patch is pulled in. [Other Info] SF: #00346549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1995408/+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 2001703] Re: Update the NVIDIA drivers 2023/01
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.78.01-0ubuntu1 --- nvidia-graphics-drivers-525 (525.78.01-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #2001703). * debian/additional_card_ids, debian/additional_runtimepm_ids: - Add the missing 2717 ID. -- Alberto Milone Wed, 04 Jan 2023 16:25:19 + ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2001703 Title: Update the NVIDIA drivers 2023/01 Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525 source package in Focal: In Progress Status in nvidia-graphics-drivers-525 source package in Jammy: In Progress Status in nvidia-graphics-drivers-525 source package in Kinetic: In Progress Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Fixed a regression that prevented the G-SYNC/G-SYNC Compatible Visual Indicator from being displayed when running Vulkan X11 applications. - Fixed a bug where usage of VK_KHR_present_id could cause applications to crash with Xid 32 errors. - Fixed excess CPU usage in hybrid graphics configurations where an external display is connected to an NVIDIA discrete GPU and configured as a PRIME Display Offload sink (also known as "Reverse Prime"). * debian/additional_card_ids, debian/additional_runtimepm_ids: - Add the missing 2717 ID. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2001703/+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 1991833] Re: VRF Kernel Module Does Not Exist
** Changed in: linux-aws (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1991833 Title: VRF Kernel Module Does Not Exist Status in linux-aws package in Ubuntu: Invalid Bug description: On a standard Ubuntu 22.04 LTS image, the vrf module exists and can be loaded. The AMI image ami-08c40ec9ead489470 in AWS us-east-1 (and all other regions that I have tested) does not have this kernel module built therefore I cannot create vrf network devices. Usually I could run `ip link add vrf-mgmt type vrf table 10` and create the VRF device, but instead get an error `Error: Unknown device type.`. Trying to load the module: # modprobe vrf modprobe: FATAL: Module vrf not found in directory /lib/modules/5.15.0-1020-aws # Boot config # grep VRF /boot/config-5.15.0-1020-aws CONFIG_NET_VRF=m ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-aws-headers-5.15.0-1020 5.15.0-1020.24 ProcVersionSignature: Ubuntu 5.15.0-1020.24-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 5 18:41:11 2022 Ec2AMI: ami-08c40ec9ead489470 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1a Ec2InstanceType: t3.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1991833/+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 2001564] Re: Kernel crash due to Bluefield pka TRNG ioctl call
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Shih-Yi Chen (shihyic) ** Changed in: linux-bluefield (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Jammy) Assignee: (unassigned) => Shih-Yi Chen (shihyic) ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2001564 Title: Kernel crash due to Bluefield pka TRNG ioctl call Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: In Progress Status in linux-bluefield source package in Jammy: In Progress Bug description: SRU Justification [Impact] Bluefield 3 on Ubuntu 22.04 and OpenSSL 3.0.2, encounters kernel crash/oops when HTTPS client uses OpenSSL with PKA engine during TLS handshake. The issue is with TRNG ioctl call. The kernel logs show the following errors. Unable to handle kernel access to user memory outside uaccess routines at virtual address ce65d328 BF3 on Ubuntu 22.04, OpenSSl 3.0.2 [Fix] * Change RNG ioctl kernel handler code to copy data from user to kernel space. [Test Case] openssl rand -engine pka 512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2001564/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Backporting to LTS is a good idea IMHO. A few additional use cases to consider - Users on the threshold who experience slight initrd image growth due to any module update - Users who thought they might be able to continue just using older images may fail to recognize grub will eventually remove those older images during regular updates. - Users that take their laptops on the road, but then plug them into their dock with larger displays to get the real work done only to have a boot failure. And yet when they take it into Best Buy it just works somehow. -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Fix Committed Status in grub2-unsigned package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Workaround] Some workarounds have been suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125 [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory region starvation in <1G addresses: Type StartEnd # Pages Attributes Available -00086FFF 0087 000F BS_Data00087000-00087FFF 0001 000F Available 00088000-0009EFFF 0017 000F Reserved 0009F000-0009 0001 000F Available 0010-00FF 0F00 000F LoaderCode 0100-01021FFF 0022 000F Available 01022000-238A7FFF 00022886 000F BS_Data238A8000-23927FFF 0080 000F Available 23928000-28860FFF 4F39 000F BS_Data28861000-2AB09FFF 22A9 000F LoaderCode 2AB0A000-2ACF8FFF 01EF 000F BS_Data2ACF9000-2B2FAFFF 0602 000F Available 2B2FB000-2B611FFF 0317 000F BS_Data2B612000-2B630FFF 001F 000F Available 2B631000-2B632FFF 0002 000F BS_Data2B633000-2B63CFFF 000A 000F Available 2B63D000-2B649FFF 000D 000F BS_Data2B64A000-2B64EFFF 0005 000F Available 2B64F000-2B666FFF 0018 000F BS_Data2B667000-2D8D5FFF 226F 000F LoaderCode 2D8D6000-2D8E9FFF 0014 000F BS_Data2D8EA000-2D925FFF 003C 000F LoaderCode 2D926000-2D932FFF 000D 000F BS_Data2D933000-2D969FFF 0037 000F BS_Code2D96A000-2D973FFF 000A 000F BS_Data2D974000-2E377FFF 0A04 000F Available 2E378000-2E37AFFF 0003 000F ... Reserved 3C08B000-4192 58A5 000F ACPI_NVS 4193-41B2 0200
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
I second backporting this to jammy at least as it is an LTS. -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Fix Committed Status in grub2-unsigned package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Workaround] Some workarounds have been suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125 [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory region starvation in <1G addresses: Type StartEnd # Pages Attributes Available -00086FFF 0087 000F BS_Data00087000-00087FFF 0001 000F Available 00088000-0009EFFF 0017 000F Reserved 0009F000-0009 0001 000F Available 0010-00FF 0F00 000F LoaderCode 0100-01021FFF 0022 000F Available 01022000-238A7FFF 00022886 000F BS_Data238A8000-23927FFF 0080 000F Available 23928000-28860FFF 4F39 000F BS_Data28861000-2AB09FFF 22A9 000F LoaderCode 2AB0A000-2ACF8FFF 01EF 000F BS_Data2ACF9000-2B2FAFFF 0602 000F Available 2B2FB000-2B611FFF 0317 000F BS_Data2B612000-2B630FFF 001F 000F Available 2B631000-2B632FFF 0002 000F BS_Data2B633000-2B63CFFF 000A 000F Available 2B63D000-2B649FFF 000D 000F BS_Data2B64A000-2B64EFFF 0005 000F Available 2B64F000-2B666FFF 0018 000F BS_Data2B667000-2D8D5FFF 226F 000F LoaderCode 2D8D6000-2D8E9FFF 0014 000F BS_Data2D8EA000-2D925FFF 003C 000F LoaderCode 2D926000-2D932FFF 000D 000F BS_Data2D933000-2D969FFF 0037 000F BS_Code2D96A000-2D973FFF 000A 000F BS_Data2D974000-2E377FFF 0A04 000F Available 2E378000-2E37AFFF 0003 000F ... Reserved 3C08B000-4192 58A5 000F ACPI_NVS 4193-41B2 0200 000F ACPI_Recl 41B3-41BFEFFF 00CF 000F BS_Data41BFF000-41BF 0001 000F Available 0001-0002AB7F 001AB800 000F Reserved 000A-000F 0060 Reserved 41C0-43FF 2400 Reserved 4400-47FF 4000 000F
[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
Hi According to : https://bugzilla.kernel.org/show_bug.cgi?id=215993#c27 https://github.com/thesofproject/linux/issues/3814 please someone could talk with ASUS to make Bios update ASAP it could be resolve the problem I see now new update (310) anyone installed it ? https://www.asus.com/laptops/for-home/zenbook/zenbook-14-oled-ux3402/helpdesk_bios/?model2Name=zenbook-14-oled-ux3402 ** Bug watch added: Linux Kernel Bug Tracker #215993 https://bugzilla.kernel.org/show_bug.cgi?id=215993 ** Bug watch added: github.com/thesofproject/linux/issues #3814 https://github.com/thesofproject/linux/issues/3814 -- 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/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all Status in linux package in Ubuntu: Confirmed Bug description: Sound/speakers don't work at all on Asus Zenbook 14 OLED and other similar models with Realtek ALC294. No solution works. Audio is not muted, tried adding snd-hda arguments - no dice. This has been reported numerous times, when will a fix finally be rolled out?! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1730 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 12 13:57:05 2022 InstallationDate: Installed on 2022-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+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/5.19.0.1014.11)
All autopkgtests for the newly accepted linux-meta-oracle (5.19.0.1014.11) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: systemd/251.4-1ubuntu7 (amd64, arm64) 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/kinetic/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: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix 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: Won't Fix 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: Won't Fix 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 1919321] Re: Fix system sleep on TGL systems with Intel ME
This fix should be dropped for 6.1. -- 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/1919321 Title: Fix system sleep on TGL systems with Intel ME Status in HWE Next: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: [Impact] On TGL systems, PCI devices stops working after system resume. One notable case is that USB controller stops working after s2idle. [Fix] Serialize e1000e PM ops and makes e1000e is the last to suspend the first to resume. [Test] Issue is not reproducible on 3000 cycles suspend tests. [Where problems could occur] Suspend and resume will be a bit slower. Other than that there's no real behavior change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1919321/+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 2002105] [NEW] 5.15.0-57 update breaks arrow (mouse) movement in some games (steam through proton)
Public bug reported: Since this update 5.15.0-57 the cursor movement in some of the games I play is broken. For example in Supreme Commander 2 the arrow vanishes for a split second and reappears in the next split second, while moving the mouse. The problem is not there when I revert to 5.15.0-56. I can't give any other information to help. I didn't noticed this behavior in desktop apps at the moment. My system info: https://docs.google.com/document/d/1yYK4Rx4Mu- XeaO9YiiDxI79BS17ge_5pYAdPank6K84/edit?usp=sharing ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - 5.15.0-57 update breaks arrow (mouse) movement in some games (steam throug proton) + 5.15.0-57 update breaks arrow (mouse) movement in some games (steam through proton) -- 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/2002105 Title: 5.15.0-57 update breaks arrow (mouse) movement in some games (steam through proton) Status in linux package in Ubuntu: New Bug description: Since this update 5.15.0-57 the cursor movement in some of the games I play is broken. For example in Supreme Commander 2 the arrow vanishes for a split second and reappears in the next split second, while moving the mouse. The problem is not there when I revert to 5.15.0-56. I can't give any other information to help. I didn't noticed this behavior in desktop apps at the moment. My system info: https://docs.google.com/document/d/1yYK4Rx4Mu- XeaO9YiiDxI79BS17ge_5pYAdPank6K84/edit?usp=sharing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002105/+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-gcp/5.19.0.1014.11)
All autopkgtests for the newly accepted linux-meta-gcp (5.19.0.1014.11) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: systemd/251.4-1ubuntu7 (arm64, 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/kinetic/update_excuses.html#linux-meta-gcp [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: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix 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: Won't Fix 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: Won't Fix 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 2000917] Re: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound
*** This bug is a duplicate of bug 1783689 *** https://bugs.launchpad.net/bugs/1783689 Ah my apologies, I didn't realise I had already reported this a few months back when updating to jammy here https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965750 -- 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/2000917 Title: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Every now and then, after boot, I get no sounds at all coming from the speakers. Everything seems normal - the control center reports the output as active, and if I play anything with sound I can see the VU meter going back and forth. I've attached a screenshot showing as much. The internal microphone does not pick up any sounds either when this happens. If I connect my Bose NC700 bluetooth headset, I get sound out of it just fine, and the mike on it also works. Sometimes the internal sound will start working after a few times of switching back and forth internal audio / bluetooth headset. Restarting the systemd pipewire and pipewire-pulse user services doesn't help. Nor does killing & respawning wireplumber. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire-pulse 0.3.58-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: sway Date: Tue Jan 3 11:25:23 2023 InstallationDate: Installed on 2023-01-03 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: pipewire UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2000917/+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 2000917] Re: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound
*** This bug is a duplicate of bug 1783689 *** https://bugs.launchpad.net/bugs/1783689 That does sound like it could be an issue for sure. -- 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/2000917 Title: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Every now and then, after boot, I get no sounds at all coming from the speakers. Everything seems normal - the control center reports the output as active, and if I play anything with sound I can see the VU meter going back and forth. I've attached a screenshot showing as much. The internal microphone does not pick up any sounds either when this happens. If I connect my Bose NC700 bluetooth headset, I get sound out of it just fine, and the mike on it also works. Sometimes the internal sound will start working after a few times of switching back and forth internal audio / bluetooth headset. Restarting the systemd pipewire and pipewire-pulse user services doesn't help. Nor does killing & respawning wireplumber. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire-pulse 0.3.58-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: sway Date: Tue Jan 3 11:25:23 2023 InstallationDate: Installed on 2023-01-03 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: pipewire UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2000917/+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 1968155] Re: Multiple errors with DVD drive: ata1: SError: { PHYRdyChg CommWake 10B8B DevExch }
Solved for my devices by backport of libata patch in kernel 5.15.0-57.
Thanks everybody for all the help.
** 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/1968155
Title:
Multiple errors with DVD drive: ata1: SError: { PHYRdyChg CommWake
10B8B DevExch }
Status in linux package in Ubuntu:
Fix Released
Bug description:
Going from kernel version 5.4.0-99 to 5.4.0-100 my optical drive (Pioneer
BD-RW BDR-207M) became unusable. I include a selection of the errors, the
dmesg errors immediately after boot without trying to use the drive yet, the
system specs from system report, and the output of the inxi -Fdxxx commandin
the file attachment.txt.
Up to and including kernel 5.4.0-99 everything worked OK. Kernel 5.13.0-30
also works, from kernel 5.13.0-35 the same problem occurs. Might it be a
problem with atalib?
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jaap 1928 F pulseaudio
/dev/snd/controlC1: jaap 1928 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 20.3
InstallationDate: Installed on 2022-02-01 (64 days ago)
InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-100-generic
root=UUID=9d60bcb5-650d-484d-ae74-728526cd6db1 ro ipv6.disable=1
elevator=deadline quiet splash nomodeset
ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
RelatedPackageVersions:
linux-restricted-modules-5.4.0-100-generic N/A
linux-backports-modules-5.4.0-100-generic N/A
linux-firmware 1.187.29
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: yes
Tags: una
Uname: Linux 5.4.0-100-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
systemd-timesync vboxusers
_MarkForUpload: True
dmi.bios.date: 12/01/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.80
dmi.board.name: X570 Taichi
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP3.80:bd12/01/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jaap 1928 F pulseaudio
/dev/snd/controlC1: jaap 1928 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 20.3
InstallationDate: Installed on 2022-02-01 (64 days ago)
InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-100-generic
root=UUID=9d60bcb5-650d-484d-ae74-728526cd6db1 ro ipv6.disable=1
elevator=deadline quiet splash nomodeset
ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
RelatedPackageVersions:
linux-restricted-modules-5.4.0-100-generic N/A
linux-backports-modules-5.4.0-100-generic N/A
linux-firmware 1.187.29
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: yes
Tags: una
Uname: Linux 5.4.0-100-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
systemd-timesync vboxusers
_MarkForUpload: True
dmi.bios.date: 12/01/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.80
dmi.board.name: X570 Taichi
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
[Kernel-packages] [Bug 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out
I see it seems depends on how the adapter is connected. Previously it was plugged into monitor's USB hub and I had the issues. Now I've plugged it directly into laptop's port, it works fine so far. I guess it may be caused by other devices (maybe usb headset I have?.. it may explain why it happens during video calls) on the same bus interfering with the network adapter. -- 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/1953554 Title: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Bug description: Hi, I am facing this problem in Focal with the USB 3.0 Ethernet Gigabit adapter "ASIX Electronics Corp. AX88179 Gigabit Ethernet" (waneth is the name I assigned to this ethernet connected to the cable modem/router): [ cut here ] [94104.121581] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out [94104.121606] WARNING: CPU: 2 PID: 217952 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 [94104.121615] Modules linked in: binfmt_misc xt_recent nfnetlink nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_sof_pci_intel_apl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof soundwire_bus snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl_msr snd_soc_sst_ipc intel_rapl_common 8814au(OE) mei_hdcp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_pmc_bxt snd_soc_core intel_telemetry_pltdrv intel_punit_ipc snd_compress intel_telemetry_core snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek coretemp snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine kvm_intel snd_hda_intel kvm snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl intel_cstate snd_hda_core snd_hwdep snd_pcm snd_timer ax88179_178a cfg80211 efi_pstore mei_me usbnet ee1004 snd mii soundcore mei mac_hid bridge ip6t_REJECT nf_reject_ipv6 stp llc x t_hl [94104.121696] ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_limit xt_addrtype xt_tcpudp xt_MASQUERADE iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables sch_fq_codel iptable_filter bpfilter msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core aesni_intel crypto_simd i2c_i801 xhci_pci i2c_smbus cryptd r8169 realtek xhci_pci_renesas drm sdhci_pci ahci cqhci sdhci libahci video [94104.121771] CPU: 2 PID: 217952 Comm: PLUGIN[cgroups] Tainted: G OE 5.13.0-22-generic #22~20.04.1-Ubuntu [94104.121775] Hardware name: GIGABYTE MZGLKDP-00/MZGLKDP-00, BIOS F1 12/21/2017 [94104.121777] RIP: 0010:dev_watchdog+0x24f/0x260 [94104.121782] Code: c7 36 fd ff eb ab 4c 89 ff c6 05 60 f1 6e 01 01 e8 86 11 fa ff 44 89 e9 4c 89 fe 48 c7 c7 20 9c ca 89 48 89 c2 e8 38 17 17 00 <0f> 0b eb 8c 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 [94104.121785] RSP: 0018:b515c0138e88 EFLAGS: 00010282 [94104.121788] RAX: RBX: 91214fc45e00 RCX: 0027 [94104.121790] RDX: 0027 RSI: dfff RDI: 9124b05189c8 [94104.121792] RBP: b515c0138eb8 R08: 9124b05189c0 R09: b515c0138c60 [94104.121794] R10: 0001 R11: 0001 R12: 0001 [94104.121795] R13: R14: 912154a7d480 R15: 912154a7d000 [94104.121797] FS: 7f74619e5700() GS:9124b050() knlGS: [94104.121800] CS: 0010 DS: ES: CR0: 80050033 [94104.121802] CR2: 5635dd41b584 CR3: 00020592a000 CR4: 00350ee0 [94104.121805] Call Trace: [94104.121807] [94104.121812] ? pfifo_fast_enqueue+0x150/0x150 [94104.121816] call_timer_fn+0x2c/0x100 [94104.121821] run_timer_softirq+0x3d7/0x480 [94104.121824] ? perf_trace_softirq+0x9d/0xd0 [94104.121829] __do_softirq+0xdd/0x29b [94104.121835] irq_exit_rcu+0xa4/0xb0 [94104.121837] sysvec_apic_timer_interrupt+0x7c/0x90 [94104.121841] [94104.121843] asm_sysvec_apic_timer_interrupt+0x12/0x20 [94104.121846] RIP: 0010:errseq_sample+0x2/0x10 [94104.121850] Code: ff 48 d3 e2 48 f7 d2 48 21 d0 0f 01 ca 48 85 c0 0f 94 c0 0f b6 c0 c3 b8 01 00 00 00 c3 b8 f2 ff ff ff c3 cc cc cc cc cc 8b 07 00 00 00 00 f6 c4 10 0f 44 c2 c3 66 90 8b 17 31 c0 39 16 74 1b [94104.121853] RSP: 0018:b515c29cfb68 EFLAGS: 0286 [94104.121855] RAX: RBX: 91214298e500 RCX: 0002 [94104.121857] RDX: 0001 RSI:
[Kernel-packages] [Bug 1994126] Re: NULL pointer dereference in power_supply_get_property
@kaihengfeng nice, is there some live or installer .iso to try it out? -- 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 2002089] Re: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2002089 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Triaged Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+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 1968604] Re: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug
Same here, in Linux mint 21.3, @bert.ram.aerts thanks for workaround! -- 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/1968604 Title: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug Status in linux-firmware package in Ubuntu: Confirmed Bug description: I have usb bluetooth 5.0 dongle which uses Realtek RTL8761B chip. 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio USB adapter very often stops working, can't connect or find other bluetooth devices. The adapter can't work even after reboots. The following entries appear in the log: апр 11 13:47:14 desktop kernel: Bluetooth: hci0: command 0x2005 tx timeout апр 11 13:47:16 desktop kernel: Bluetooth: hci0: command 0x2041 tx timeout апр 11 13:47:18 desktop kernel: Bluetooth: hci0: command 0x2042 tx timeout Firmware loaded correctly, but something is not working. апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814 1) I use: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) linux-firmware: 20220329.git681281e4-0ubuntu1 3) What you expected to happen? I expect a well working bluetooth adapter. 4) What happened instead? My bluetooth adapter may work, may not. The adapter may stop finding and connecting to other devices. I've found the same bug https://bugzilla.kernel.org/show_bug.cgi?id=214111#c1 I've downloaded Windows's archive http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2021/05/ca0e770c-6a5d-4de0-b37a-f4b91cccd8c3_7778831d2b9d721cf94d5a8d8c0676ff1b96c874.cab I've unpacked file rtl8761b_mp_chip_bt40_fw_asic_rom_patch_new.dll and replaced /usr/lib/firmware/rtl_bt/rtl8761bu_fw.bin and deleted rtl8761bu_config.bin After I changed firmware my usb dongle work fine. Could you change firmware rtl8761bu_fw.bin rtl8761bu_config.bin to other correct version? Could you move Realtek's rtl_bt firmware or RTL8761B's firmware into separate packages. I will remove the RTL8761B firmware package and put them manually. bluetoothctl --version bluetoothctl: 5.64 hci0: Type: Primary Bus: USB BD Address: 00:E0:4C:FC:E2:03 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:5751 acl:49 sco:0 events:489 errors:0 TX bytes:219114 acl:398 sco:0 commands:83 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'desktop' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x97b LMP Version: 5.1 (0xa) Subversion: 0xec43 Manufacturer: Realtek Semiconductor Corporation (93) rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Realtek's worker updated these bad firmware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=45dc5f0b8e2f2d43312d22511cb26658b9ee2c80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1968604/+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 2002089] Re: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1
Proposed fixes: https://patchwork.kernel.org/project/netdevbpf/patch/20230105154215.198828-1-m.chetan.ku...@linux.intel.com/ [patchwork.kernel.org] : [v2,net-next,1/5] net: wwan: t7xx: Add AP CLDMA https://patchwork.kernel.org/project/netdevbpf/patch/20230105154229.198843-1-m.chetan.ku...@linux.intel.com/ [patchwork.kernel.org] : [v2,net-next,2/5] net: wwan: t7xx: Infrastructure for early port configuration https://patchwork.kernel.org/project/netdevbpf/patch/20230105154245.198858-1-m.chetan.ku...@linux.intel.com/ [patchwork.kernel.org] : [v2,net-next,3/5] net: wwan: t7xx: PCIe reset rescan https://patchwork.kernel.org/project/netdevbpf/patch/20230105154300.198873-1-m.chetan.ku...@linux.intel.com/ [patchwork.kernel.org] : [v2,net-next,4/5] net: wwan: t7xx: Enable devlink based fw flashing and coredump collection The first patch duplicates what we had for bug 1990700, so the outdated one has to be reverted first. There is also an 5th patch for documentation. Will include that as well for integrity. ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux (Ubuntu Kinetic) Status: New => Triaged ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux (Ubuntu Lunar) Status: New => Triaged ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Triaged ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Triaged ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-6.1 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Triaged Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+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 2002088] Re: Ubuntu Desktop freezes
Ubuntu version is 22.10. -- 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/2002088 Title: Ubuntu Desktop freezes Status in linux package in Ubuntu: New Bug description: While using desktop the machine suddenly freezes and computer has to be shut down from power button and restarted. However, I could log in from another machine by using ssh and saw that dmesg is showing lots of these messages: [ 6834.800344] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread slack:cs0 pid 5441) [ 6834.800351] amdgpu :08:00.0: amdgpu: in page starting at address 0x800106bf from IH client 0x12 (VMC) [ 6834.800355] amdgpu :08:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00240051 [ 6834.800356] amdgpu :08:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) [ 6834.800358] amdgpu :08:00.0: amdgpu: MORE_FAULTS: 0x1 [ 6834.800359] amdgpu :08:00.0: amdgpu: WALKER_ERROR: 0x0 [ 6834.800359] amdgpu :08:00.0: amdgpu: PERMISSION_FAULTS: 0x5 [ 6834.800360] amdgpu :08:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 6834.800361] amdgpu :08:00.0: amdgpu: RW: 0x1 [ 6834.800362] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread slack:cs0 pid 5441) [ 6834.800364] amdgpu :08:00.0: amdgpu: in page starting at address 0x800106bf1000 from IH client 0x12 (VMC) [ 6834.800373] amdgpu :08:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00240051 [ 6834.800374] amdgpu :08:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) [ 6834.800375] amdgpu :08:00.0: amdgpu: MORE_FAULTS: 0x1 [ 6834.800376] amdgpu :08:00.0: amdgpu: WALKER_ERROR: 0x0 [ 6834.800376] amdgpu :08:00.0: amdgpu: PERMISSION_FAULTS: 0x5 [ 6834.800377] amdgpu :08:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 6834.800378] amdgpu :08:00.0: amdgpu: RW: 0x1 [ 6834.800379] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread slack:cs0 pid 5441) [ 6834.800380] amdgpu :08:00.0: amdgpu: in page starting at address 0x800106bf2000 from IH client 0x12 (VMC) [ 6834.800382] amdgpu :08:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x [ 6834.800383] amdgpu :08:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) [ 6834.800384] amdgpu :08:00.0: amdgpu: MORE_FAULTS: 0x0 [ 6834.800385] amdgpu :08:00.0: amdgpu: WALKER_ERROR: 0x0 [ 6834.800386] amdgpu :08:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [ 6834.800386] amdgpu :08:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 6834.800387] amdgpu :08:00.0: amdgpu: RW: 0x0 [ 6834.800388] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread slack:cs0 pid 5441) [ 6834.800389] amdgpu :08:00.0: amdgpu: in page starting at address 0x800106bf3000 from IH client 0x12 (VMC) [ 6834.800391] amdgpu :08:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x [ 6834.800392] amdgpu :08:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) [ 6834.800393] amdgpu :08:00.0: amdgpu: MORE_FAULTS: 0x0 [ 6834.800394] amdgpu :08:00.0: amdgpu: WALKER_ERROR: 0x0 [ 6834.800394] amdgpu :08:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [ 6834.800395] amdgpu :08:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 6834.800396] amdgpu :08:00.0: amdgpu: RW: 0x0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002088/+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 2002088] Re: Ubuntu Desktop freezes
** Attachment added: "Full dmesg output." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002088/+attachment/5639537/+files/dmesg.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/2002088 Title: Ubuntu Desktop freezes Status in linux package in Ubuntu: New Bug description: While using desktop the machine suddenly freezes and computer has to be shut down from power button and restarted. However, I could log in from another machine by using ssh and saw that dmesg is showing lots of these messages: [ 6834.800344] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread slack:cs0 pid 5441) [ 6834.800351] amdgpu :08:00.0: amdgpu: in page starting at address 0x800106bf from IH client 0x12 (VMC) [ 6834.800355] amdgpu :08:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00240051 [ 6834.800356] amdgpu :08:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) [ 6834.800358] amdgpu :08:00.0: amdgpu: MORE_FAULTS: 0x1 [ 6834.800359] amdgpu :08:00.0: amdgpu: WALKER_ERROR: 0x0 [ 6834.800359] amdgpu :08:00.0: amdgpu: PERMISSION_FAULTS: 0x5 [ 6834.800360] amdgpu :08:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 6834.800361] amdgpu :08:00.0: amdgpu: RW: 0x1 [ 6834.800362] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread slack:cs0 pid 5441) [ 6834.800364] amdgpu :08:00.0: amdgpu: in page starting at address 0x800106bf1000 from IH client 0x12 (VMC) [ 6834.800373] amdgpu :08:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00240051 [ 6834.800374] amdgpu :08:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) [ 6834.800375] amdgpu :08:00.0: amdgpu: MORE_FAULTS: 0x1 [ 6834.800376] amdgpu :08:00.0: amdgpu: WALKER_ERROR: 0x0 [ 6834.800376] amdgpu :08:00.0: amdgpu: PERMISSION_FAULTS: 0x5 [ 6834.800377] amdgpu :08:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 6834.800378] amdgpu :08:00.0: amdgpu: RW: 0x1 [ 6834.800379] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread slack:cs0 pid 5441) [ 6834.800380] amdgpu :08:00.0: amdgpu: in page starting at address 0x800106bf2000 from IH client 0x12 (VMC) [ 6834.800382] amdgpu :08:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x [ 6834.800383] amdgpu :08:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) [ 6834.800384] amdgpu :08:00.0: amdgpu: MORE_FAULTS: 0x0 [ 6834.800385] amdgpu :08:00.0: amdgpu: WALKER_ERROR: 0x0 [ 6834.800386] amdgpu :08:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [ 6834.800386] amdgpu :08:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 6834.800387] amdgpu :08:00.0: amdgpu: RW: 0x0 [ 6834.800388] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread slack:cs0 pid 5441) [ 6834.800389] amdgpu :08:00.0: amdgpu: in page starting at address 0x800106bf3000 from IH client 0x12 (VMC) [ 6834.800391] amdgpu :08:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x [ 6834.800392] amdgpu :08:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) [ 6834.800393] amdgpu :08:00.0: amdgpu: MORE_FAULTS: 0x0 [ 6834.800394] amdgpu :08:00.0: amdgpu: WALKER_ERROR: 0x0 [ 6834.800394] amdgpu :08:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [ 6834.800395] amdgpu :08:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 6834.800396] amdgpu :08:00.0: amdgpu: RW: 0x0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002088/+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 2002088] [NEW] Ubuntu Desktop freezes
Public bug reported: While using desktop the machine suddenly freezes and computer has to be shut down from power button and restarted. However, I could log in from another machine by using ssh and saw that dmesg is showing lots of these messages: [ 6834.800344] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread slack:cs0 pid 5441) [ 6834.800351] amdgpu :08:00.0: amdgpu: in page starting at address 0x800106bf from IH client 0x12 (VMC) [ 6834.800355] amdgpu :08:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00240051 [ 6834.800356] amdgpu :08:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) [ 6834.800358] amdgpu :08:00.0: amdgpu: MORE_FAULTS: 0x1 [ 6834.800359] amdgpu :08:00.0: amdgpu: WALKER_ERROR: 0x0 [ 6834.800359] amdgpu :08:00.0: amdgpu: PERMISSION_FAULTS: 0x5 [ 6834.800360] amdgpu :08:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 6834.800361] amdgpu :08:00.0: amdgpu: RW: 0x1 [ 6834.800362] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread slack:cs0 pid 5441) [ 6834.800364] amdgpu :08:00.0: amdgpu: in page starting at address 0x800106bf1000 from IH client 0x12 (VMC) [ 6834.800373] amdgpu :08:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00240051 [ 6834.800374] amdgpu :08:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) [ 6834.800375] amdgpu :08:00.0: amdgpu: MORE_FAULTS: 0x1 [ 6834.800376] amdgpu :08:00.0: amdgpu: WALKER_ERROR: 0x0 [ 6834.800376] amdgpu :08:00.0: amdgpu: PERMISSION_FAULTS: 0x5 [ 6834.800377] amdgpu :08:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 6834.800378] amdgpu :08:00.0: amdgpu: RW: 0x1 [ 6834.800379] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread slack:cs0 pid 5441) [ 6834.800380] amdgpu :08:00.0: amdgpu: in page starting at address 0x800106bf2000 from IH client 0x12 (VMC) [ 6834.800382] amdgpu :08:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x [ 6834.800383] amdgpu :08:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) [ 6834.800384] amdgpu :08:00.0: amdgpu: MORE_FAULTS: 0x0 [ 6834.800385] amdgpu :08:00.0: amdgpu: WALKER_ERROR: 0x0 [ 6834.800386] amdgpu :08:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [ 6834.800386] amdgpu :08:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 6834.800387] amdgpu :08:00.0: amdgpu: RW: 0x0 [ 6834.800388] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread slack:cs0 pid 5441) [ 6834.800389] amdgpu :08:00.0: amdgpu: in page starting at address 0x800106bf3000 from IH client 0x12 (VMC) [ 6834.800391] amdgpu :08:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x [ 6834.800392] amdgpu :08:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) [ 6834.800393] amdgpu :08:00.0: amdgpu: MORE_FAULTS: 0x0 [ 6834.800394] amdgpu :08:00.0: amdgpu: WALKER_ERROR: 0x0 [ 6834.800394] amdgpu :08:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [ 6834.800395] amdgpu :08:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 6834.800396] amdgpu :08:00.0: amdgpu: RW: 0x0 ** 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/2002088 Title: Ubuntu Desktop freezes Status in linux package in Ubuntu: New Bug description: While using desktop the machine suddenly freezes and computer has to be shut down from power button and restarted. However, I could log in from another machine by using ssh and saw that dmesg is showing lots of these messages: [ 6834.800344] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread slack:cs0 pid 5441) [ 6834.800351] amdgpu :08:00.0: amdgpu: in page starting at address 0x800106bf from IH client 0x12 (VMC) [ 6834.800355] amdgpu :08:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00240051 [ 6834.800356] amdgpu :08:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) [ 6834.800358] amdgpu :08:00.0: amdgpu: MORE_FAULTS: 0x1 [ 6834.800359] amdgpu :08:00.0: amdgpu: WALKER_ERROR: 0x0 [ 6834.800359] amdgpu :08:00.0: amdgpu: PERMISSION_FAULTS: 0x5 [ 6834.800360] amdgpu :08:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 6834.800361] amdgpu :08:00.0: amdgpu: RW: 0x1 [ 6834.800362] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread slack:cs0 pid 5441) [ 6834.800364] amdgpu :08:00.0: amdgpu: in page
[Kernel-packages] [Bug 2002089] [NEW] Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1
Public bug reported: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: You-Sheng Yang (vicamo) Status: Triaged ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: High Assignee: You-Sheng Yang (vicamo) Status: Triaged ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: High Assignee: You-Sheng Yang (vicamo) Status: Triaged ** Affects: linux (Ubuntu Kinetic) Importance: High Assignee: You-Sheng Yang (vicamo) Status: Triaged ** Affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Lunar) Importance: High Assignee: You-Sheng Yang (vicamo) Status: Triaged ** Affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1992733 somerville ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Tags added: oem-priority originate-from-1992733 somerville ** Also affects: linux-oem-6.1 (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/2002089 Title: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Triaged Status in linux source package in Kinetic: Triaged Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002) [ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002089/+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 2002090] [NEW] Kernel crash with preinstalled Kinetic image
Public bug reported: When trying to boot the Kinetic preinstalled image ubuntu-22.10-preinstalled-server-riscv64+licheerv.img.xz (https://cdimage.ubuntu.com/releases/22.10/release/ubuntu-22.10-preinstalled- server-riscv64+licheerv.img.xz) with a 0fe6:9700 "ICS Advent DM9601 Fast Ethernet Adapter" plugged in the following crash occurs: [ 163.933818] Unable to handle kernel paging request at virtual address fffdf54d0289 [ 163.941784] Oops [#1] [ 163.944072] Modules linked in: binfmt_misc cfg80211 snd_soc_hdmi_codec dw_hdmi_i2s_audio dw_hdmi_cec sr9700 dm9601 usbnet pwrseq_simple sunxi_cir rc_core sun8i_drm_hdmi dw_hdmi sun8i_mixer sunxi phy_generic sunxi_cedrus(C) snd_soc_simple_card v4l2_mem2mem sun20i_codec snd_soc_dmic videobuf2_dma_contig snd_soc_simple_card_utils videobuf2_memops videobuf2_v4l2 sun4i_drm videobuf2_common sun4i_frontend sun4i_tcon sun8i_tcon_top display_connector drm_cma_helper snd_soc_core videodev snd_compress ac97_bus snd_pcm_dmaengine drm_kms_helper snd_pcm leds_sun50i_r329 led_class_multicolor mc snd_timer fb_sys_fops snd syscopyarea sysfillrect sysimgblt leds_gpio backlight soundcore nls_iso8859_1 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 efivarfs raid10 raid456 libcrc32c async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid1 raid0 multipath linear [ 164.030015] CPU: 0 PID: 668 Comm: (d-logind) Tainted: G C 5.17.0-1003-allwinner #3-Ubuntu [ 164.039517] Hardware name: Sipeed Lichee RV Dock (DT) [ 164.044578] epc : __update_blocked_fair.isra.0+0xb6/0x3ca [ 164.050012] ra : __update_blocked_fair.isra.0+0xa6/0x3ca [ 164.055437] epc : 80060b1e ra : 80060b0e sp : ffd8056d7650 [ 164.062678] gp : 81e93b80 tp : ffd804023e80 t0 : 000e [ 164.069918] t1 : t2 : 0407 s0 : ffd8056d76d0 [ 164.077156] s1 : ffd806012800 a0 : a1 : d4be6efdf54d01a9 [ 164.084395] a2 : 0007 a3 : 81ea6540 a4 : ffd80461e780 [ 164.091634] a5 : ffd80493db98 a6 : a7 : [ 164.098873] s2 : ffd806012940 s3 : 1000 s4 : ffd81ecc2780 [ 164.106114] s5 : s6 : b67e s7 : ffd8056d76d7 [ 164.113354] s8 : 80e7d600 s9 : 00262b36e925 s10: 0100 [ 164.120595] s11: ffd804432400 t3 : 001c t4 : 016cddfa32cc [ 164.127835] t5 : 0407 t6 : 0407ab360ba9 [ 164.133162] status: 00020100 badaddr: fffdf54d0289 cause: 000d [ 164.141097] [] update_blocked_averages+0x124/0x1d2 [ 164.147475] [] newidle_balance+0x120/0x3b6 [ 164.153160] [] pick_next_task_fair+0x4e/0x318 [ 164.159102] [] __schedule+0x144/0x630 [ 164.164354] [] schedule+0x50/0xc2 [ 164.169253] [] io_schedule+0x4c/0x66 [ 164.174413] [] folio_wait_bit_common+0x218/0x396 [ 164.180630] [] filemap_update_page+0x2cc/0x2da [ 164.186660] [] filemap_get_pages+0x1f2/0x314 [ 164.192516] [] filemap_read+0xaa/0x276 [ 164.197851] [] generic_file_read_iter+0xf2/0x14e [ 164.204054] [] ext4_file_read_iter+0x60/0x160 [ 164.210007] [] __kernel_read+0xfc/0x23c [ 164.215433] [] kernel_read+0x58/0x8e [ 164.220594] [] search_binary_handler+0x64/0x240 [ 164.226710] [] exec_binprm+0x54/0x14a [ 164.231956] [] bprm_execve.part.0+0x178/0x1d2 [ 164.237899] [] bprm_execve+0x56/0x80 [ 164.243059] [] do_execveat_common+0x16e/0x1ee [ 164.248999] [] sys_execve+0x3c/0x48 [ 164.254072] [] ret_from_syscall+0x0/0x2 ** Affects: linux-allwinner (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner in Ubuntu. https://bugs.launchpad.net/bugs/2002090 Title: Kernel crash with preinstalled Kinetic image Status in linux-allwinner package in Ubuntu: New Bug description: When trying to boot the Kinetic preinstalled image ubuntu-22.10-preinstalled-server-riscv64+licheerv.img.xz (https://cdimage.ubuntu.com/releases/22.10/release/ubuntu-22.10-preinstalled- server-riscv64+licheerv.img.xz) with a 0fe6:9700 "ICS Advent DM9601 Fast Ethernet Adapter" plugged in the following crash occurs: [ 163.933818] Unable to handle kernel paging request at virtual address fffdf54d0289 [ 163.941784] Oops [#1] [ 163.944072] Modules linked in: binfmt_misc cfg80211 snd_soc_hdmi_codec dw_hdmi_i2s_audio dw_hdmi_cec sr9700 dm9601 usbnet pwrseq_simple sunxi_cir rc_core sun8i_drm_hdmi dw_hdmi sun8i_mixer sunxi phy_generic sunxi_cedrus(C) snd_soc_simple_card v4l2_mem2mem sun20i_codec snd_soc_dmic videobuf2_dma_contig snd_soc_simple_card_utils videobuf2_memops videobuf2_v4l2 sun4i_drm videobuf2_common sun4i_frontend sun4i_tcon sun8i_tcon_top display_connector drm_cma_helper snd_soc_core
[Kernel-packages] [Bug 1987269] Re: [5.18.0 mainline] mlx5 deadlock
** Changed in: linux (Ubuntu) Status: Expired => 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/1987269 Title: [5.18.0 mainline] mlx5 deadlock Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy $ uname -a Linux pc1-rb3-n3 5.18.0-051800-generic #202205222030 SMP PREEMPT_DYNAMIC Sun May 22 20:33:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.735461] INFO: task ovn-controller:30439 blocked for more than 120 seconds. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.742835] Not tainted 5.18.0-051800-generic #202205222030 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.749051] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757010] task:ovn-controller state:D stack:0 pid:30439 ppid: 1 flags:0x0002 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757019] Call Trace: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757024] Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757031] __schedule+0x246/0x5c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757045] schedule+0x55/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757050] schedule_preempt_disabled+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757057] __mutex_lock.constprop.0+0x2f3/0x4c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757064] __mutex_lock_slowpath+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757069] mutex_lock+0x35/0x40 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757073] rtnetlink_rcv_msg+0x114/0x3f0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757082] ? rtnl_calcit.isra.0+0x140/0x140 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757087] netlink_rcv_skb+0x56/0x100 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757095] rtnetlink_rcv+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757099] netlink_unicast+0x236/0x350 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757104] netlink_sendmsg+0x25e/0x4d0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757109] sock_sendmsg+0x66/0x70 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757117] sys_sendmsg+0x24f/0x290 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757123] ? import_iovec+0x1b/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757130] ? sendmsg_copy_msghdr+0x7c/0xa0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757137] ___sys_sendmsg+0x81/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757143] ? ___sys_recvmsg+0x99/0x110 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757148] ? netdev_name_node_lookup_rcu+0x6b/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757155] ? fput+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757161] ? __sys_sendmsg+0x98/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757166] ? __fget_light+0xa7/0x130 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757174] __sys_sendmsg+0x62/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757180] __x64_sys_sendmsg+0x1d/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757186] do_syscall_64+0x5c/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757191] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757194] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757200] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757203] ? exit_to_user_mode_prepare+0x37/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757210] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757214] ? __x64_sys_write+0x19/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757220] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757224] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757227] entry_SYSCALL_64_after_hwframe+0x44/0xae Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757232] RIP: 0033:0x7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757239] RSP: 002b:7ffd50fa8ec0 EFLAGS: 0293 ORIG_RAX: 002e Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757246] RAX: ffda RBX: 0001 RCX: 7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757252] RDX: RSI: 7ffd50fa8f50 RDI: 0020 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757255] RBP: 7ffd50fa9c40 R08: R09: 55e1a6a66f60 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757260] R10: 0001 R11: 0293 R12: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757264] R13: 55e1a53bc510 R14: 00074f30 R15: 7ffd50fa8f50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757271] Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757646]
[Kernel-packages] [Bug 1976228] Re: [Ubuntu 22.04 LTS]The host OS becomes read-only after the 'rescan-scsi-bus.sh -r' command is executed
Hello jeff, This seems unrelated with external storage devices, I did the test on host with local disk only, “rescan-scsi-bus.sh -r” remove local disks wrongly. After excuting “rescan-scsi-bus.sh -r” ,whole / mount status change to ro: /dev/mapper/ubuntu--vg-ubuntu--lv on / type ext4 (ro,relatime) I hope this information will help you locate the issue,and find a solution to the script. Br, Zihao Yang ** Attachment added: "rescan_log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976228/+attachment/5639515/+files/rescan_log.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/1976228 Title: [Ubuntu 22.04 LTS]The host OS becomes read-only after the 'rescan- scsi-bus.sh -r' command is executed Status in linux package in Ubuntu: Confirmed Bug description: OS:Ubuntu 22.04 LTS kernel:5.15.0-33-generic host model:Dell PowerEdge R630 issue description: After I mapped luns from array to my host, I ran 'rescan-scsi-bus.sh -r' to scan for luns, my host crashed and became read-only.After the KVM forcibly restarts the host, the host is restored to normal. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 30 08:33 seq crw-rw 1 root audio 116, 33 May 30 08:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 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: CRDA: N/A DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-26 (4 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/14/2021 dmi.bios.release: 2.13 dmi.bios.version: 2.13.0 dmi.board.name: 02C2CP dmi.board.version: A01 dmi.chassis.type: 23 dmi.modalias: dmi:bvn:bvr2.13.0:bd05/14/2021:br2.13:svn:pn:pvr:rvn:rn02C2CP:rvrA01:cvn:ct23:cvr:skuSKU=NotProvided;ModelName=: dmi.product.sku: SKU=NotProvided;ModelName= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976228/+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
** 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 Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => 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/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: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Kinetic: In Progress Status in linux source package in Lunar: In Progress 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 2002079] [NEW] Lunar update: v6.1.2 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: v6.1.2 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002079 Title: Lunar update: v6.1.2 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.2 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002079/+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
