[Kernel-packages] [Bug 1946001] Re: impish:linux 5.13 panic during systemd autotest
This bug is awaiting verification that the linux-raspi/5.13.0-1010.11 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- 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/1946001 Title: impish:linux 5.13 panic during systemd autotest Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Impish: Fix Released Bug description: Found this when running the systemd autopkgtest on linux-aws 5.13.0-1004.5 (apparently it seems to affect nested kvm only): systemd-testsuite login: [ 70.235559] int3: [#1] SMP NOPTI [ 70.237824] CPU: 0 PID: 326 Comm: systemd-journal Not tainted 5.13.0-1004-aws #5-Ubuntu [ 70.237852] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 [ 70.237864] RIP: 0010:kmem_cache_alloc+0x57/0x240 [ 70.237875] Code: 08 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 c7 45 c8 00 00 00 00 e8 d6 bb ff ff 49 89 c4 48 85 c0 0f 84 cd 00 00 00 cc <0a> 7 [ 70.237994] RSP: 0018:aabd001cfd78 EFLAGS: 0286 [ 70.239655] RAX: 97e8411da400 RBX: 1000 RCX: 0400 [ 70.239670] RDX: 0001 RSI: 0cc0 RDI: 97e8411da400 [ 70.239679] RBP: aabd001cfdb8 R08: R09: 9802 [ 70.239688] R10: R11: R12: 97e8411da400 [ 70.239696] R13: 97e8411da400 R14: 0cc0 R15: b2737cf0 [ 70.239705] FS: 7fc6fc243380() GS:97e85c00() knlGS: [ 70.239713] CS: 0010 DS: ES: CR0: 80050033 [ 70.239720] CR2: 7fc6f9249000 CR3: 03c5c000 CR4: 06f0 [ 70.239727] Call Trace: [ 70.239733] getname_flags.part.0+0x30/0x1b0 [ 70.239741] getname+0x35/0x50 [ 70.239746] do_sys_openat2+0x64/0x150 [ 70.239753] __x64_sys_openat+0x55/0x90 [ 70.239759] do_syscall_64+0x61/0xb0 [ 70.239766] ? do_syscall_64+0x6e/0xb0 [ 70.239772] ? do_sync_core+0x26/0x30 [ 70.239779] ? flush_smp_call_function_queue+0x119/0x190 [ 70.239786] ? exit_to_user_mode_prepare+0x37/0xb0 [ 70.239793] ? irqentry_exit_to_user_mode+0x9/0x20 [ 70.239800] ? irqentry_exit+0x19/0x30 [ 70.239807] ? sysvec_call_function+0x4e/0x90 [ 70.239813] ? asm_sysvec_call_function+0xa/0x20 [ 70.239819] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 70.239826] RIP: 0033:0x7fc6fca946e4 [ 70.239834] Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 16 d2 f7 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 4 [ 70.239845] RSP: 002b:7ffc9699f1a0 EFLAGS: 0293 ORIG_RAX: 0101 [ 70.240063] RAX: ffda RBX: RCX: 7fc6fca946e4 [ 70.240075] RDX: 00080802 RSI: 556e8d5885d0 RDI: ff9c [ 70.240085] RBP: 556e8d5885d0 R08: R09: [ 70.240095] R10: R11: 0293 R12: 00080802 [ 70.240104] R13: R14: 556e8d59dd90 R15: fffa [ 70.240113] Modules linked in: btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raidy [ 70.281001] ---[ end trace 044cf87b8c867a36 ]--- [ 70.281099] RIP: 0010:kmem_cache_alloc+0x57/0x240 [ 70.281107] Code: 08 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 c7 45 c8 00 00 00 00 e8 d6 bb ff ff 49 89 c4 48 85 c0 0f 84 cd 00 00 00 cc <0a> 7 [ 70.281115] RSP: 0018:aabd001cfd78 EFLAGS: 0286 [ 70.281132] RAX: 97e8411da400 RBX: 1000 RCX: 0400 [ 70.281138] RDX: 0001 RSI: 0cc0 RDI: 97e8411da400 [ 70.281143] RBP: aabd001cfdb8 R08: R09: 9802 [ 70.281148] R10: R11: R12: 97e8411da400 [ 70.281154] R13: 97e8411da400 R14: 0cc0 R15: b2737cf0 [ 70.281159] FS: 7fc6fc243380() GS:97e85c00() knlGS: [ 70.281173] CS: 0010 DS: ES: CR0: 80050033 [ 70.281178] CR2: 7fc6f9249000 CR3: 03c5c000 CR4: 06f0 [ 70.281183] Kernel panic - not syncing: Fatal exception in
[Kernel-packages] [Bug 1932157] Re: [21.10 FEAT] KVM: Use interpretation of specification exceptions
This bug is awaiting verification that the linux-raspi/5.13.0-1010.11 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- 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/1932157 Title: [21.10 FEAT] KVM: Use interpretation of specification exceptions Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This allows KVM to let SIE interpret specification exceptions instead of doing this itself, leading to performance improvements. This feature will be made available with kernel >=5.15 A backport will be provided once available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932157/+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 1947027] Re: hirsute/linux-azure: Backport CIFS patches
https://lists.ubuntu.com/archives/kernel-team/2021-October/125315.html -- 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/1947027 Title: hirsute/linux-azure: Backport CIFS patches Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Hirsute: In Progress Bug description: [SRU Justification] [Impact] Microsoft has asked to backport cifs patches up through v5.15-rc3 from git://git.samba.org/sfrench/cifs-2.6.git 5.11-backport [Test Case] Connect to a SAMBA server [Where things might go wrong] Connections may fail, or have poor performance. [Other Info] SF: #00316229 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1947027/+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 1947174] Re: Add final-checks to check certificates
verification-done-hirsute: dget https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+sourcefiles/linux/5.11.0-40.44/linux_5.11.0-40.44.dsc dpkg-source -x linux_5.11.0-40.44.dsc grep CONFIG_SYSTEM_TRUSTED_KEYS linux-5.11.0/debian/scripts/misc/final-checks if ! grep -q '^CONFIG_SYSTEM_TRUSTED_KEYS="debian/canonical-certs.pem"$' $debian/config/config.common.ubuntu; then failure "'CONFIG_SYSTEM_TRUSTED_KEYS="debian/canonical-certs.pem"' is required" ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947174 Title: Add final-checks to check certificates Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] * As part of landing builtin revocation certificates work https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029 it has been identified that many kernels do not correct enforce newly enfoced keys in the derivative flavours. I.e. due to annotations not importing parent annotations, due to not having do_enforce_all, or using older formats of annotations files. * As part fips validation work final-checks got added to check and assert that correct things are turned on. * It has been agreed that having a final-check for builtin system trusted & revocation certificates would be a good thing. If packaging declares that certain certificates should be built-in trusted or revoked, the kernel must be configured pointing at the packaging generated .pem bundle in the config. [Test Plan] * Kernel should build * If trusted or revocation are configured in packaging but the config option is misconfigured (i.e. typo or not set), the kernel build and cranky close should fail [Where problems could occur] * This is a packaging change only, thus may result in valid kernels ftbfs but should be easy to rectify. [Other Info] * Also see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029 and kernels that derived from a primary kernel that had that fixed, and the subsequently failed boot testing due to not enabling those options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947174/+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 1945632] Re: Re-enable DEBUG_INFO_BTF where it was disabled
verification-done-focal: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+files/linux-buildinfo-5.11.0-40-generic_5.11.0-40.44~20.04.2_amd64.deb dpkg -x linux-buildinfo-5.11.0-40-generic_5.11.0-40.44~20.04.2_amd64.deb . grep DEBUG_INFO_BTF usr/lib/linux/5.11.0-40-generic/config CONFIG_DEBUG_INFO_BTF=y CONFIG_DEBUG_INFO_BTF_MODULES=y ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945632 Title: Re-enable DEBUG_INFO_BTF where it was disabled Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-hwe-5.11 source package in Focal: Fix Committed Status in linux-hwe-5.13 source package in Focal: Fix Committed Bug description: [Impact] * pahole used to segfault on 32-bit platforms, which has now been fixed * pahole used to be too old in focal, which is now being SRUed * renable DEBUG_INFO_BTF in all the kernels/arches that had it disabled, as otherwise one cannot compile/use advanced BTF features on newer kernels. [Test Plan] * Check the built kernel's config that it has CONFIG_DEBUG_INFO_BTF=y * Check build log that it contains ``` BTF .btf.vmlinux.bin.o ``` [Where problems could occur] * In the future, kernel may require even newer version of pahole from dwarves, making the builds fail to build again, as building BTF debug information will now be required. Until either BTF is disabled again or pahole is upgraded again. [Other Info] * Latest pahole is available from focal-proposed, hirsute-proposed, impish release, builders-extra PPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945632/+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 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915
I confirm on focal. WORKAROUND, install linux-firmware package from Impish (1.201) instead of one from focal (1.187) The many kernel errors about PCI devices dissapear during the boot time. Not sure about the real impact on the system itself. sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.11.0-27-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. -- 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/1939986 Title: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915 Status in initramfs-tools package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Confirmed Bug description: Dear all, I can see that the linux-firmware is missing firmware files, in Ubuntu 20.04.1 LTS, for initramfs, when it loads i915. Package: linux-firmware 1.187.15 It contains the following files, for the module i915: i915/tgl_dmc_ver2_04.bin 2019-09-13 installed i915/tgl_dmc_ver2_06.bin 2020-03-04 installed i915/tgl_dmc_ver2_08.bin 2020-08-13 installed i915/tgl_guc_35.2.0.bin 2019-11-06 installed i915/tgl_huc_7.0.12.bin 2020-03-04 installed i915/tgl_huc_7.0.3.bin2019-11-06 installed Package: linux-firmware MUST at least contain the following files, for the module i915: i915/tgl_huc_7.5.0.bin2020-08-13 i915: Add HuC firwmare v7.5.0 for TGL as the module asks for it, during 'update-initramfs', to avoid: W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 But it COULD also contain : i915/tgl_dmc_ver2_12.bin 2021-07-28 i915: Add v2.12 DMC for TGL i915/tgl_guc_49.0.1.bin 2020-11-24 i915: Add GuC firmware v49.0.1 for all platforms i915/tgl_guc_62.0.0.bin 2021-06-29 firmware/i915/guc: Add GuC v62.0.0 for all platforms i915/tgl_huc_7.9.3.bin2021-06-29 firmware/i915/guc: Add HuC v7.9.3 for TGL & DG1 Source: $ modprobe --show-depends --ignore-install i915 ... insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko $ modinfo -F firmware /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko ... i915/tgl_dmc_ver2_08.bin i915/tgl_guc_35.2.0.bin i915/tgl_huc_7.5.0.bin Actual result: $ sudo update-initramfs -u W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 Expected result: No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915 Info : INTEL Repository of firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.15 ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46 Uname: Linux 5.10.0-1038-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1699 F pulseaudio /dev/snd/pcmC0D0p: chris
[Kernel-packages] [Bug 1917114] Re: printers epson and canon and HP all printers support linux ubuntu LTS
Please explain precisely the bug ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1917114 Title: printers epson and canon and HP all printers support linux ubuntu LTS Status in linux package in Ubuntu: Incomplete Bug description: printers epson and canon and HP all printers support linux ubuntu LTS all printers scanners epson and canon and HP make working linux ubuntu 20.04 LTS and all LTS operatio desktops --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: snowden1430 F pulseaudio /dev/snd/controlC0: snowden1430 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7817 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: snowden1430 F pulseaudio /dev/snd/controlC0: snowden1430 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7817 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tessetessu 1414 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed
[Kernel-packages] [Bug 1947818] Re: The fans are constantly whirring on ThinkPad P14S Gen 2
Please advise - GPU usage is minimal and fan still running high. -- 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/1947818 Title: The fans are constantly whirring on ThinkPad P14S Gen 2 Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: The fans are constantly whirring despite next to no CPU usage, it's quite loud, on versions 20.04, 21.04 and 21.10 it has the same issues. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1947818/+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 1932157] Re: [21.10 FEAT] KVM: Use interpretation of specification exceptions
I'm updating the tags to verification-done-impish, since this ticket was marked as affecting impish on s390x only (not raspi). And it was already Fix Released for Impish (s390x) according to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932157/comments/8 ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- 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/1932157 Title: [21.10 FEAT] KVM: Use interpretation of specification exceptions Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This allows KVM to let SIE interpret specification exceptions instead of doing this itself, leading to performance improvements. This feature will be made available with kernel >=5.15 A backport will be provided once available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932157/+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 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
@vicamo
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/?id=6f8c8bf4c7c9be1c42088689fd4370e06b46608a
"ath10k: fix module load regression with iram-recovery feature"
new patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks QCA9984
Firmware load capability
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Triaged
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support")
in v5.11 fails firmware loading without IRAM recovery feature. However,
the latest firmware from
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
doesn't support IRAM, it follows new official ath10k firmwares may no
longer be loadable for kernel newer than v5.11.
[Fix]
A fix is proposed to
http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that
turns the lack/failure of IRAM recovery support a warning instead.
[Test Case]
With this fix, kernel gives errors about the IRAM supportness, but
proceeds to remaining procedures as before.
ath10k_pci :04:00.0: No hardware memory
ath10k_pci :04:00.0: failed to copy target iram contents: -12
ath10k_pci :07:00.0: No hardware memory
ath10k_pci :07:00.0: failed to copy target iram contents: -12
[Where problems could occur]
So the IRAM recovery feature may or may not be supported in the
officially released firmware, and people meet problems when using
non-IRAM supported firmware may still have a fallback to use older, but
IRAM recovery supported ones.
== original bug report ==
Hello, I use Ubuntu 20.04.2 LTS.
The kernel was recently updated to 5.11
5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Since then the ath10k_core driver for my QCA9984 card is broken and
only loads ~3 firmware versions from the 3.9.0.2 branch
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
The firmware versions 70 / 86 / 91 are functional (but these firmware
versions are already 2 years old)
Responsible for this is the defective patch "ath10k: add target IRAM
recovery feature support"
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8
If I understand the patch correctly then the driver tries to load
firmware with the feature "iram recovery" into the memory of the host
(for recvovery purposes).
If this fails, the firmware is discarded and the network controller
remains unusable.
Of course, this is not a desirable behavior for optional firmware
features.
dmesg:
[3.074952] ath: loading out-of-tree module taints kernel.
[3.090522] ath: module verification failed: signature and/or required key
missing - tainting kernel
[3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[7.047910] ath10k_pci :03:00.0: failed to copy target iram contents:
-12
[7.103260] ath10k_pci :03:00.0: could not init core (-12)
[7.103267] ath10k_pci :03:00.0: could not probe fw (-12)
[7.108570] ath10k_pci :04:00.0: failed to copy target iram contents:
-12
[7.163247]
[Kernel-packages] [Bug 1945576] Re: Intel I225-IT ethernet controller: igc: probe of 0000:02:00.0 failed with error -1
This bug is awaiting verification that the linux-oem-5.10/5.10.0-1051.53 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945576 Title: Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with error -1 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-intel package in Ubuntu: Invalid Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-intel source package in Focal: Won't Fix Status in linux-intel-5.13 source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-intel source package in Hirsute: Invalid Status in linux-intel-5.13 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-intel source package in Impish: Invalid Status in linux-intel-5.13 source package in Impish: Invalid Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Environment] Device : Aaeon Up xtreme i11 Platform: Intel TigerLake-UP3 I225-IT NVM version: 1.79 I225-IT Stepping: B3 Ubuntu version: 20.04.3 LTS with kernel 5.11.0-27-generic [Description] It can work under Windows10. But uner Ubuntu, we can't find the interface by ifconfig command and the system dmesg will has the error of igc driver module : igc: probe of :02:00.0 failed with error -1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945576/+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 1947174] Re: Add final-checks to check certificates
verification-done-impish: dget https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+sourcefiles/linux/5.13.0-21.21/linux_5.13.0-21.21.dsc dpkg-source -x linux_5.13.0-21.21.dsc grep CONFIG_SYSTEM_TRUSTED_KEYS linux-5.13.0/debian/scripts/misc/final-checks if ! grep -q '^CONFIG_SYSTEM_TRUSTED_KEYS="debian/canonical-certs.pem"$' $debian/config/config.common.ubuntu; then failure "'CONFIG_SYSTEM_TRUSTED_KEYS="debian/canonical-certs.pem"' is required" ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- 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/1947174 Title: Add final-checks to check certificates Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] * As part of landing builtin revocation certificates work https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029 it has been identified that many kernels do not correct enforce newly enfoced keys in the derivative flavours. I.e. due to annotations not importing parent annotations, due to not having do_enforce_all, or using older formats of annotations files. * As part fips validation work final-checks got added to check and assert that correct things are turned on. * It has been agreed that having a final-check for builtin system trusted & revocation certificates would be a good thing. If packaging declares that certain certificates should be built-in trusted or revoked, the kernel must be configured pointing at the packaging generated .pem bundle in the config. [Test Plan] * Kernel should build * If trusted or revocation are configured in packaging but the config option is misconfigured (i.e. typo or not set), the kernel build and cranky close should fail [Where problems could occur] * This is a packaging change only, thus may result in valid kernels ftbfs but should be easy to rectify. [Other Info] * Also see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029 and kernels that derived from a primary kernel that had that fixed, and the subsequently failed boot testing due to not enabling those options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947174/+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 1945632] Re: Re-enable DEBUG_INFO_BTF where it was disabled
verification-done-impish: wget https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+files/linux-buildinfo-5.13.0-21-generic_5.13.0-21.21_amd64.deb dpkg -x linux-buildinfo-5.13.0-21-generic_5.13.0-21.21_amd64.deb . grep DEBUG_INFO_BTF usr/lib/linux/5.13.0-21-generic/config CONFIG_DEBUG_INFO_BTF=y CONFIG_DEBUG_INFO_BTF_MODULES=y ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945632 Title: Re-enable DEBUG_INFO_BTF where it was disabled Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-hwe-5.11 source package in Focal: Fix Committed Status in linux-hwe-5.13 source package in Focal: Fix Committed Bug description: [Impact] * pahole used to segfault on 32-bit platforms, which has now been fixed * pahole used to be too old in focal, which is now being SRUed * renable DEBUG_INFO_BTF in all the kernels/arches that had it disabled, as otherwise one cannot compile/use advanced BTF features on newer kernels. [Test Plan] * Check the built kernel's config that it has CONFIG_DEBUG_INFO_BTF=y * Check build log that it contains ``` BTF .btf.vmlinux.bin.o ``` [Where problems could occur] * In the future, kernel may require even newer version of pahole from dwarves, making the builds fail to build again, as building BTF debug information will now be required. Until either BTF is disabled again or pahole is upgraded again. [Other Info] * Latest pahole is available from focal-proposed, hirsute-proposed, impish release, builders-extra PPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945632/+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 1947174] Re: Add final-checks to check certificates
verification-done-focal: dget https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+sourcefiles/linux/5.4.0-90.101/linux_5.4.0-90.101.dsc dpkg-source -x linux_5.4.0-90.101.dsc grep CONFIG_SYSTEM_TRUSTED_KEYS linux-5.4.0/debian/scripts/misc/final-checks if ! grep -q '^CONFIG_SYSTEM_TRUSTED_KEYS="debian/canonical-certs.pem"$' $debian/config/config.common.ubuntu; then failure "'CONFIG_SYSTEM_TRUSTED_KEYS="debian/canonical-certs.pem"' is required" ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947174 Title: Add final-checks to check certificates Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] * As part of landing builtin revocation certificates work https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029 it has been identified that many kernels do not correct enforce newly enfoced keys in the derivative flavours. I.e. due to annotations not importing parent annotations, due to not having do_enforce_all, or using older formats of annotations files. * As part fips validation work final-checks got added to check and assert that correct things are turned on. * It has been agreed that having a final-check for builtin system trusted & revocation certificates would be a good thing. If packaging declares that certain certificates should be built-in trusted or revoked, the kernel must be configured pointing at the packaging generated .pem bundle in the config. [Test Plan] * Kernel should build * If trusted or revocation are configured in packaging but the config option is misconfigured (i.e. typo or not set), the kernel build and cranky close should fail [Where problems could occur] * This is a packaging change only, thus may result in valid kernels ftbfs but should be easy to rectify. [Other Info] * Also see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029 and kernels that derived from a primary kernel that had that fixed, and the subsequently failed boot testing due to not enabling those options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947174/+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 1947174] Re: Add final-checks to check certificates
verification-done-bionic: dget https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+sourcefiles/linux/4.15.0-162.170/linux_4.15.0-162.170.dsc dpkg-source -x linux_4.15.0-162.170.dsc grep CONFIG_SYSTEM_TRUSTED_KEYS linux-4.15.0/debian/scripts/misc/final-checks if ! grep -q '^CONFIG_SYSTEM_TRUSTED_KEYS="debian/canonical-certs.pem"$' $debian/config/config.common.ubuntu; then failure "'CONFIG_SYSTEM_TRUSTED_KEYS="debian/canonical-certs.pem"' is required" ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1947174 Title: Add final-checks to check certificates Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] * As part of landing builtin revocation certificates work https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029 it has been identified that many kernels do not correct enforce newly enfoced keys in the derivative flavours. I.e. due to annotations not importing parent annotations, due to not having do_enforce_all, or using older formats of annotations files. * As part fips validation work final-checks got added to check and assert that correct things are turned on. * It has been agreed that having a final-check for builtin system trusted & revocation certificates would be a good thing. If packaging declares that certain certificates should be built-in trusted or revoked, the kernel must be configured pointing at the packaging generated .pem bundle in the config. [Test Plan] * Kernel should build * If trusted or revocation are configured in packaging but the config option is misconfigured (i.e. typo or not set), the kernel build and cranky close should fail [Where problems could occur] * This is a packaging change only, thus may result in valid kernels ftbfs but should be easy to rectify. [Other Info] * Also see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029 and kernels that derived from a primary kernel that had that fixed, and the subsequently failed boot testing due to not enabling those options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947174/+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 1945180] Re: vrf: fix refcnt leak with vxlan slaves
Hi Kelsey, sorry, I missed the notification, I'll take care of it right
away.
--
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/1945180
Title:
vrf: fix refcnt leak with vxlan slaves
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
There are cases, where deleting a VRF device can hang waiting for the refcnt
to drop to 0, with the message:
unregister_netdevice: waiting for vrf1 to become free. Usage count = 1
This is fixed upstream with commit b87b04f5019e ("ipv4: Fix device
used for dst_alloc with local routes"), included in linux v5.13. The
original patch, which has introduced the bug, is included in linux
v4.10.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b87b04f5019e
[Test Case]
The upstream patch includes a test case, which describe how to
reproduce the bug.
[Regression Potential]
The patch affects ipv4 routing. It is straightforward, it links new
dst to a vrf device instead of the loopback if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945180/+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 1788578] Re: Some test in ubuntu_bpf test_verifier failed on i386 Bionic kernel
** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Description changed: + [Impact] + Narrow loads for bpf_perf_event_data is not possible on 32-bit arches. + + [Test case] + Run the bpf test_verifier. + + [Potential regression] + Loading sample_period of bpf_perf_event_data may fail. + + == + + This issue was only spotted on i386 Bionic kernel. - #146/p unpriv: spill/fill of different pointers ldx FAIL - Unexpected error message! - 0: (bf) r6 = r10 - 1: (07) r6 += -8 - 2: (15) if r1 == 0x0 goto pc+3 - R1=ctx(id=0,off=0,imm=0) R6=fp-8 R10=fp0 - 3: (bf) r2 = r10 - 4: (07) r2 += -76 - 5: (7b) *(u64 *)(r6 +0) = r2 - 6: (55) if r1 != 0x0 goto pc+1 - R1=ctx(id=0,off=0,imm=0) R2=fp-76 R6=fp-8 R10=fp0 fp-8=fp - 7: (7b) *(u64 *)(r6 +0) = r1 - 8: (79) r1 = *(u64 *)(r6 +0) - 9: (79) r1 = *(u64 *)(r1 +68) - #352/p check bpf_perf_event_data->sample_period byte load permitted FAIL - Failed to load prog 'Permission denied'! - 0: (b7) r0 = 0 - 1: (71) r0 = *(u8 *)(r1 +68) - invalid bpf_context access off=68 size=1 - #353/p check bpf_perf_event_data->sample_period half load permitted FAIL - Failed to load prog 'Permission denied'! - 0: (b7) r0 = 0 - 1: (69) r0 = *(u16 *)(r1 +68) - invalid bpf_context access off=68 size=2 - #354/p check bpf_perf_event_data->sample_period word load permitted FAIL - Failed to load prog 'Permission denied'! - 0: (b7) r0 = 0 - 1: (61) r0 = *(u32 *)(r1 +68) - invalid bpf_context access off=68 size=4 - #355/p check bpf_perf_event_data->sample_period dword load permitted FAIL - Failed to load prog 'Permission denied'! - 0: (b7) r0 = 0 - 1: (79) r0 = *(u64 *)(r1 +68) - invalid bpf_context access off=68 size=8 + #146/p unpriv: spill/fill of different pointers ldx FAIL + Unexpected error message! + 0: (bf) r6 = r10 + 1: (07) r6 += -8 + 2: (15) if r1 == 0x0 goto pc+3 + R1=ctx(id=0,off=0,imm=0) R6=fp-8 R10=fp0 + 3: (bf) r2 = r10 + 4: (07) r2 += -76 + 5: (7b) *(u64 *)(r6 +0) = r2 + 6: (55) if r1 != 0x0 goto pc+1 + R1=ctx(id=0,off=0,imm=0) R2=fp-76 R6=fp-8 R10=fp0 fp-8=fp + 7: (7b) *(u64 *)(r6 +0) = r1 + 8: (79) r1 = *(u64 *)(r6 +0) + 9: (79) r1 = *(u64 *)(r1 +68) + #352/p check bpf_perf_event_data->sample_period byte load permitted FAIL + Failed to load prog 'Permission denied'! + 0: (b7) r0 = 0 + 1: (71) r0 = *(u8 *)(r1 +68) + invalid bpf_context access off=68 size=1 + #353/p check bpf_perf_event_data->sample_period half load permitted FAIL + Failed to load prog 'Permission denied'! + 0: (b7) r0 = 0 + 1: (69) r0 = *(u16 *)(r1 +68) + invalid bpf_context access off=68 size=2 + #354/p check bpf_perf_event_data->sample_period word load permitted FAIL + Failed to load prog 'Permission denied'! + 0: (b7) r0 = 0 + 1: (61) r0 = *(u32 *)(r1 +68) + invalid bpf_context access off=68 size=4 + #355/p check bpf_perf_event_data->sample_period dword load permitted FAIL + Failed to load prog 'Permission denied'! + 0: (b7) r0 = 0 + 1: (79) r0 = *(u64 *)(r1 +68) + invalid bpf_context access off=68 size=8 Summary: 708 PASSED, 5 FAILED ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: User Name 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic i686 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Aug 23 08:23 seq - crw-rw 1 root audio 116, 33 Aug 23 08:23 timer + total 0 + crw-rw 1 root audio 116, 1 Aug 23 08:23 seq + crw-rw 1 root audio 116, 33 Aug 23 08:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: - + Date: Thu Aug 23 08:41:26 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: - Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub - Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub - Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub + Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: - + ProcFB: 0 mgadrmfb
[Kernel-packages] [Bug 1931072] Re: USB Type-C hotplug event not handled properly in TGL-H system during s2idle
Hi Chris, may you please verify the Impish kernel in -proposed resolves this bug? You can find further instructions for this in comment #8. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1931072 Title: USB Type-C hotplug event not handled properly in TGL-H system during s2idle Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] The system will be hold by the infinite loop in ACPI method IPCS after exiting s2idle in TGL-H systems if the docking station with external display connected is unplugged when the system is still in s2idle. It's because the system is unaware of the unplug event and it seems keep something asserted which will never be released while the system trying to exit s2idle. [Fix] Disconnect TypeC PHYs during system suspend and shutdown, even with the corresponding TypeC sink still plugged to its connector. The HPD event is no longer triggered when the system is in s2idle so the resume process will not be hindered. [Test Case] 1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the NVIDIA GPU is running in either On-Demand mode or Performance mode. 2. Connect the docking station with the external display connected. 3. Suspend the system. 4. Remove the docking station when the system is suspended. 5. Press power button to wake up the system and wait > 1 minutes to make sure if the display comes back. [Where problems could occur] Low. This will only make a difference in the TypeC DP alternate mode, and the display driver will detect the display connector after resume. == Original Bug Description == [Summary] As mentioned in #1929166, the NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if the USB Type-C docking/dongle with external display connected is unplugged when the system is still in s2idle. The system will be hold by the infinite loop in ACPI method IPCS and then the PCIe root port of NVIDIA gpu fails the power transition from D3cold to D0. It's because the display connector hotplug event not handled properly in graphics drivers and the system will freeze for > 30 seconds to wait for ACPI method IPCS to exit. [ 154.446781] [ 154.446783] [ 154.446783] Initialized Local Variables for Method [IPCS]: [ 154.446784] Local0: 9863e365 Integer 09C5 [ 154.446790] [ 154.446791] Initialized Arguments for Method [IPCS]: (7 arguments defined for method invocation) [ 154.446792] Arg0: 25568fbd Integer 00AC [ 154.446795] Arg1: 9ef30e76 Integer [ 154.446798] Arg2: fdf820f0 Integer 0010 [ 154.446801] Arg3: 9fc2a088 Integer 0001 [ 154.446804] Arg4: 3a3418f7 Integer 0001 [ 154.446807] Arg5: 20c4b87c Integer [ 154.446810] Arg6: 8b965a8a Integer [ 154.446813] [ 154.446815] ACPI Error: Aborting method \IPCS due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446824] ACPI Error: Aborting method \MCUI due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446829] ACPI Error: Aborting method \SPCX due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446835] ACPI Error: Aborting method \_SB.PC00.PGSC due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446841] ACPI Error: Aborting method \_SB.PC00.PGON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446846] ACPI Error: Aborting method \_SB.PC00.PEG1.NPON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446852] ACPI Error: Aborting method \_SB.PC00.PEG1.PG01._ON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446860] acpi device:02: Failed to change power state to D0 [ 154.690760] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) [Reproduce Steps] 1. Connect either Dell WD19SC/DC/TB docking station(USB Type-C) to the system. 2. Connect to external display to HDMI/DisplayPort of the
[Kernel-packages] [Bug 1945180] Re: vrf: fix refcnt leak with vxlan slaves
Hi Nicolas or Samuel, may you please verify the Bionic kernel in
-proposed resolves this bug? You can find more instructions in comment
#4. Thank you!
--
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/1945180
Title:
vrf: fix refcnt leak with vxlan slaves
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
There are cases, where deleting a VRF device can hang waiting for the refcnt
to drop to 0, with the message:
unregister_netdevice: waiting for vrf1 to become free. Usage count = 1
This is fixed upstream with commit b87b04f5019e ("ipv4: Fix device
used for dst_alloc with local routes"), included in linux v5.13. The
original patch, which has introduced the bug, is included in linux
v4.10.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b87b04f5019e
[Test Case]
The upstream patch includes a test case, which describe how to
reproduce the bug.
[Regression Potential]
The patch affects ipv4 routing. It is straightforward, it links new
dst to a vrf device instead of the loopback if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945180/+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 1946266] Re: Add psample tunnel support and also two fixes for psample issues.
Hi Bodong, may you please verify the Focal kernel in -proposed resolves this bug? You can find more instructions in comment #1. Thank you! -- 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/1946266 Title: Add psample tunnel support and also two fixes for psample issues. Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) Fix psample compilation issue and add tunnel support * brief explanation of fixes Enhance psample * How to test Add tc rule with tunnel and sample actions and run traffic. Verify sample traffic on the sample interface. * What it could break. psample could be broke as new function is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1946266/+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 1944390] Re: Fix ignoring ct state match of OVS offload to TC/HW
Hi Bodong, may you please verify the focal/bluefield kernel in -proposed resolves this bug? You can find more instructions in comment #1. Thank you! -- 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/1944390 Title: Fix ignoring ct state match of OVS offload to TC/HW Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug When using OVS with tc to offload connection tracking flows, if user matches on ct_state other then trk and est, such as ct_state +rpl, it will be silently ignored by TC/HW and might result in wrong actions being executed. * How to test Create OVS bridge with 2 devices $dev1, $dev2 (can be any devices) Enable HW offload and configure connection tracking OpenFlow rules which match on ct_state +rpl and do different actions based on that match. e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est-rpl, actions=$dev1" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est+rpl, actions=$dev2" With commits, ovs dump-flows (or tc show on devs) will have ct_state +rpl match, and without they don't have, meaning the match is ignored. * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1944390/+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 1946393] Re: Fix byte count on fragmented packets in tc ct action
Hi Bodong, may you please verify the Focal/bluefield kernel in -proposed resolves this bug? You can find more instructions in comment #1. Thank you! -- 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/1946393 Title: Fix byte count on fragmented packets in tc ct action Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug First fragmented packets (frag offset = 0) byte len is zeroed when stolen by ip_defrag(). And since act_ct update the stats only afterwards (at end of execute), bytes aren't correctly accounted for such packets. * How to test Create OVS bridge with 2 devices $dev1, $dev2 (can be any devices) Enable HW offload and configure connection tracking OpenFlow rules as below e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run fragmented icmp ping traffic (e.g ping -s 2000) dump ovs rules (ovs-appctl dpctl/dump-flows), observe byte count on frag=first rule: ct_state(-trk),recirc_id(0),in_port(2),eth_type(0x0800),ipv4(proto=1,frag=first), packets:10, bytes:13960, used:1.370s, actions:ct(zone=1),recirc(0x1) bytes would be zero if bug occurs. * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1946393/+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 1943464] Re: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference
Hi Niklas, thanks for the backports. I applied them on a focal kernel and triggered some build here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1943464/ Regarding the test case, well, I think we at least need to think about a regression test case or so - since a test plan will be needed as part of the SRU Justification. But anyway, I work on the SRU submission (and the justification) next week... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943464 Title: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Incomplete Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: After reassign RoCE ConnectX-5 Card Pchid to another LPAR dmesg show under Ubuntu the following Error message Ubuntu 20.04.01 with updates oot@t35lp02:~# uname -a Linux t35lp02.lnxne.boe 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 17:41:33 UTC 2021 s390x s390x s390x GNU/Linux root@t35lp02:~# DMESG Output 761.778422] mlx5_core 0018:00:00.1: poll_health:715:(pid 0): Fatal error 1 detected [ 761.778432] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[0] 0x [ 761.778435] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[1] 0x [ 761.778437] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[2] 0x [ 761.778439] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[3] 0x [ 761.778442] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[4] 0x [ 761.778444] mlx5_core 0018:00:00.1: print_health_info:384:(pid 0): assert_exit_ptr 0x [ 761.778447] mlx5_core 0018:00:00.1: print_health_info:386:(pid 0): assert_callra 0x [ 761.778451] mlx5_core 0018:00:00.1: print_health_info:389:(pid 0): fw_ver 65535.65535.65535 [ 761.778454] mlx5_core 0018:00:00.1: print_health_info:390:(pid 0): hw_id 0x [ 761.778456] mlx5_core 0018:00:00.1: print_health_info:391:(pid 0): irisc_index 255 [ 761.778460] mlx5_core 0018:00:00.1: print_health_info:392:(pid 0): synd 0xff: unrecognized error [ 761.778462] mlx5_core 0018:00:00.1: print_health_info:394:(pid 0): ext_synd 0x [ 761.778465] mlx5_core 0018:00:00.1: print_health_info:396:(pid 0): raw fw_ver 0x [ 761.778467] mlx5_core 0018:00:00.1: mlx5_trigger_health_work:696:(pid 0): new health works are not permitted at this stage [ 763.179016] mlx5_core 0018:00:00.1: E-Switch: cleanup [ 768.348431] mlx5_core 0018:00:00.1: mlx5_reclaim_startup_pages:562:(pid 123): FW did not return all pages. giving up... [ 768.348433] [ cut here ] [ 768.348434] FW pages counter is 43318 after reclaiming all pages [ 768.348562] WARNING: CPU: 0 PID: 123 at drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c:567 mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core] [ 768.348563] Modules linked in: s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_service_time mlx5_ib ib_uverbs ib_core pkey qeth_l2 zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 mlx5_core sha256_s390 sha1_s390 sha_common tls mlxfw ptp pps_core zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 768.348586] CPU: 0 PID: 123 Comm: kmcheck Tainted: GW 5.4.0-80-generic #90-Ubuntu [ 768.348586] Hardware name: IBM 8561 T01 703 (LPAR) [ 768.348587] Krnl PSW : 0704c0018000 03ff808d33ac (mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core]) [ 768.348607]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 768.348608] Krnl GPRS: 0004 0006 0034 0007 [ 768.348608]0007 fcb4fa00 007b 03e00458fafc [ 768.348609]b7d406f0 4d849c00 b7d00120 0001b6c0 [ 768.348610]f4cb1100 03e00458fe70 03ff808d33a8 03e00458fa50 [ 768.348615] Krnl Code: 03ff808d339c: c0241043larl %r2,03ff80955422 03ff808d33a2: c0e570c7brasl %r14,03ff808c1530 #03ff808d33a8: a7f40001brc 15,03ff808d33aa >03ff808d33ac: e330a5f04012lt
[Kernel-packages] [Bug 1944586] Re: kernel bug found when disconnecting one fiber channel interface on Cisco Chassis with fnic DRV_VERSION "1.6.0.47"
Hi Eric, may you please verify the focal kernel in -proposed resolves this bug? You can find more instructions for this in comment #4. Thank you! -- 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/1944586 Title: kernel bug found when disconnecting one fiber channel interface on Cisco Chassis with fnic DRV_VERSION "1.6.0.47" Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: [Impact] It has been brought to my attention the following: " We have been experiencing node lockups and degradation when testing fiber channel fail over for multi-path PURESTORAGE drives. Testing usually consists of either failing over the fabric or the local I/O module for the Cisco chassis which houses a number of individual blades. After rebooting a local Chassis I/O module we see commands like multipath -ll hanging. Resetting the blades individual fiber channel interface results in the following messages. " 6051160.241383] rport-9:0-1: blocked FC remote port time out: removing target and saving binding [6051160.252901] BUG: kernel NULL pointer dereference, address: 0040 [6051160.262267] #PF: supervisor read access in kernel mode [6051160.269314] #PF: error_code(0x) - not-present page [6051160.276016] PGD 0 P4D 0 [6051160.279807] Oops: [#1] SMP NOPTI [6051160.284642] CPU: 10 PID: 49346 Comm: kworker/10:2 Tainted: P O 5.4.0-77-generic #86-Ubuntu [6051160.295967] Hardware name: Cisco Systems Inc UCSB-B200-M5/UCSB-B200-M5, BIOS B200M5.4.1.1d.0.0609200543 06/09/2020 [6051160.308199] Workqueue: fc_dl_9 fc_timeout_deleted_rport [scsi_transport_fc] [6051160.316640] RIP: 0010:fnic_terminate_rport_io+0x10f/0x510 [fnic] [6051160.324050] Code: 48 89 c3 48 85 c0 0f 84 7b 02 00 00 48 05 20 01 00 00 48 89 45 b0 0f 84 6b 02 00 00 48 8b 83 58 01 00 00 48 8b 80 b8 01 00 00 <48> 8b 78 40 e8 68 e6 06 00 85 c0 0f 84 4c 02 00 00 48 8b 83 58 01 [6051160.346553] RSP: 0018:bc224f297d90 EFLAGS: 00010082 [6051160.353115] RAX: RBX: 90abdd4c4b00 RCX: 90d8ab2c2bb0 [6051160.361983] RDX: 90d8b5467400 RSI: RDI: 90d8ab3b4b40 [6051160.370812] RBP: bc224f297df8 R08: 90d8c08978c8 R09: 90d8b8850800 [6051160.379518] R10: 90d8a59d64c0 R11: 0001 R12: 90d8ab2c31f8 [6051160.388242] R13: R14: 0246 R15: 90d8ab2c27b8 [6051160.396953] FS: () GS:90d8c088() knlGS: [6051160.406838] CS: 0010 DS: ES: CR0: 80050033 [6051160.414168] CR2: 0040 CR3: 000fc1c0a004 CR4: 007626e0 [6051160.423146] DR0: DR1: DR2: [6051160.431884] DR3: DR6: fffe0ff0 DR7: 0400 [6051160.440615] PKRU: 5554 [6051160.444337] Call Trace: [6051160.447841] fc_terminate_rport_io+0x56/0x70 [scsi_transport_fc] [6051160.455263] fc_timeout_deleted_rport.cold+0x1bc/0x2c7 [scsi_transport_fc] [6051160.463623] process_one_work+0x1eb/0x3b0 [6051160.468784] worker_thread+0x4d/0x400 [6051160.473660] kthread+0x104/0x140 [6051160.478102] ? process_one_work+0x3b0/0x3b0 [6051160.483439] ? kthread_park+0x90/0x90 [6051160.488213] ret_from_fork+0x1f/0x40 [6051160.492901] Modules linked in: dm_service_time zfs(PO) zunicode(PO) zlua(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_nat vhost_vsock vmw_vsock_virtio_transport_common vsock unix_diag nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vhost_net vhost tap 8021q garp mrp bluetooth ecdh_generic ecc tcp_diag inet_diag sctp nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nls_iso8859_1 dm_queue_length dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common isst_if_common skx_edac nfit x86_pkg_temp_thermal intel_powerclamp ipmi_ssif coretemp kvm_intel kvm rapl input_leds joydev intel_cstate mei_me ioatdma mei dca ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [6051160.492928] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear fnic mgag200 drm_vram_helper i2c_algo_bit ttm drm_kms_helper crct10dif_pclmul syscopyarea hid_generic crc32_pclmul libfcoe sysfillrect ghash_clmulni_intel sysimgblt aesni_intel fb_sys_fops crypto_simd libfc usbhid cryptd scsi_transport_fc hid drm glue_helper enic ahci lpc_ich libahci wmi [6051160.632623] CR2: 0040 [6051160.637043] ---[ end trace
[Kernel-packages] [Bug 1949223] [NEW] touchpad doesn't work at all
Public bug reported: Ideapad S145 15IL ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordi 1348 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 20:13:07 2021 InstallationDate: Installed on 2021-10-19 (9 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 002: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 0bda:c02f Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=8cde5310-21f1-4c24-98ac-6e014d06c83b ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 05/31/2021 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN53WW 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-15IIL dmi.ec.firmware.release: 1.53 dmi.modalias: dmi:bvnLENOVO:bvrDKCN53WW:bd05/31/2021:br1.53:efr1.53:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:skuLENOVO_MT_81W8_BU_idea_FM_IdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish 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/1949223 Title: touchpad doesn't work at all Status in linux package in Ubuntu: New Bug description: Ideapad S145 15IL ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordi 1348 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 20:13:07 2021 InstallationDate: Installed on 2021-10-19 (9 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 002: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 0bda:c02f Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=8cde5310-21f1-4c24-98ac-6e014d06c83b ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 05/31/2021 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN53WW 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-15IIL dmi.ec.firmware.release: 1.53 dmi.modalias: dmi:bvnLENOVO:bvrDKCN53WW:bd05/31/2021:br1.53:efr1.53:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:skuLENOVO_MT_81W8_BU_idea_FM_IdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL:
[Kernel-packages] [Bug 1949223] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949223 Title: touchpad doesn't work at all Status in linux package in Ubuntu: Confirmed Bug description: Ideapad S145 15IL ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordi 1348 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 20:13:07 2021 InstallationDate: Installed on 2021-10-19 (9 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 002: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 0bda:c02f Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=8cde5310-21f1-4c24-98ac-6e014d06c83b ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 05/31/2021 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN53WW 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-15IIL dmi.ec.firmware.release: 1.53 dmi.modalias: dmi:bvnLENOVO:bvrDKCN53WW:bd05/31/2021:br1.53:efr1.53:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:skuLENOVO_MT_81W8_BU_idea_FM_IdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949223/+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 1949232] [NEW] Touchpad doesn't work in ubuntu.
Public bug reported: The touchpad works fine in windows 10. I tried to install drivers, but with no luck. It is not totally being recognized by the system. Ubuntu 20.04.3 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 21:43:23 2021 InstallationDate: Installed on 2021-10-29 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1949232 Title: Touchpad doesn't work in ubuntu. Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: The touchpad works fine in windows 10. I tried to install drivers, but with no luck. It is not totally being recognized by the system. Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 21:43:23 2021 InstallationDate: Installed on 2021-10-29 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1949232/+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 1945180] Re: vrf: fix refcnt leak with vxlan slaves
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1945180
Title:
vrf: fix refcnt leak with vxlan slaves
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
There are cases, where deleting a VRF device can hang waiting for the refcnt
to drop to 0, with the message:
unregister_netdevice: waiting for vrf1 to become free. Usage count = 1
This is fixed upstream with commit b87b04f5019e ("ipv4: Fix device
used for dst_alloc with local routes"), included in linux v5.13. The
original patch, which has introduced the bug, is included in linux
v4.10.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b87b04f5019e
[Test Case]
The upstream patch includes a test case, which describe how to
reproduce the bug.
[Regression Potential]
The patch affects ipv4 routing. It is straightforward, it links new
dst to a vrf device instead of the loopback if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945180/+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 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
Hey, Andre. As we talked, this is applied to 5.4 kernels as well, 5.4.0-90 should have it. Can you test that it fixes the problem? Thanks. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945707 Title: BCM57800 SRIOV bug causes interfaces to disappear Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] bnx2x driver won't add all devices ports/interfaces. [Test case] Boot system with bnx2x device and verify all ports/interfaces have been added. [Potential regression] bnx2x devices won't be properly probed. Devices won't be added or SR-IOV won't be correctly supported. --- Original Description --- Works with focal kernel 5.4.0-80 Broken with focal kernel 5.4.0-88 On a Dell R720 with the BCM57800 based 1/10 Gigabit Integrated Network cards Kernel 5.11.22-3 causes half of the network interfaces to disappear specifically the 1gb ports. Commands like "ip link show" and "dmesg" no longer show eno3 and eno4 nor any other interface name for these ports. I've read the note in the release notes and this does not appear to be a case of the interface changing names, the 3rd and 4th interface don't show up at all. The card is based on the BCM57800 chipset and has two SFP+ and two gigabit ports on the same card. Commands like "ip link show" no longer show ports 3 and 4. "lspci" still shows four items. dmesg only shows the first two interfaces. This problem seems to be known upstream, and seems to be a regression. More information at https://bugzilla.proxmox.com/show_bug.cgi?id=3558 This is being seen at a customer during an openstack install. It would be appreciated if a workaround could be provided or the fix could be prioritized. Using standard Focal 20.04 LTS kernel (it installs ok with the working kernel then upgrades to the non-working one -- this is done through maas and is difficult to control). Tested other kernels like hwe-* and all seem to be affected too. Client does not want to disable SRIOV on whole card and also cannot disable only ports 3/4 (the bios will not allow it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+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 1788578] Re: Some test in ubuntu_bpf test_verifier failed on i386 Bionic kernel
** Description changed: [Impact] Narrow loads for bpf_perf_event_data is not possible on 32-bit arches. [Test case] Run the bpf test_verifier. [Potential regression] - Loading sample_period of bpf_perf_event_data may fail. + Loading sample_period of bpf_perf_event_data may fail. Unaligned access may lead to processor exceptions on some architectures. == - This issue was only spotted on i386 Bionic kernel. #146/p unpriv: spill/fill of different pointers ldx FAIL Unexpected error message! 0: (bf) r6 = r10 1: (07) r6 += -8 2: (15) if r1 == 0x0 goto pc+3 R1=ctx(id=0,off=0,imm=0) R6=fp-8 R10=fp0 3: (bf) r2 = r10 4: (07) r2 += -76 5: (7b) *(u64 *)(r6 +0) = r2 6: (55) if r1 != 0x0 goto pc+1 R1=ctx(id=0,off=0,imm=0) R2=fp-76 R6=fp-8 R10=fp0 fp-8=fp 7: (7b) *(u64 *)(r6 +0) = r1 8: (79) r1 = *(u64 *)(r6 +0) 9: (79) r1 = *(u64 *)(r1 +68) #352/p check bpf_perf_event_data->sample_period byte load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (71) r0 = *(u8 *)(r1 +68) invalid bpf_context access off=68 size=1 #353/p check bpf_perf_event_data->sample_period half load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (69) r0 = *(u16 *)(r1 +68) invalid bpf_context access off=68 size=2 #354/p check bpf_perf_event_data->sample_period word load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (61) r0 = *(u32 *)(r1 +68) invalid bpf_context access off=68 size=4 #355/p check bpf_perf_event_data->sample_period dword load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (79) r0 = *(u64 *)(r1 +68) invalid bpf_context access off=68 size=8 Summary: 708 PASSED, 5 FAILED ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: User Name 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 23 08:23 seq crw-rw 1 root audio 116, 33 Aug 23 08:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Thu Aug 23 08:41:26 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. -- 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/1788578 Title: Some test in ubuntu_bpf test_verifier failed on i386 Bionic kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: In Progress Bug description: [Impact] Narrow loads for bpf_perf_event_data is not possible on 32-bit arches. [Test case] Run the bpf test_verifier. [Potential regression] Loading sample_period of bpf_perf_event_data may fail. Unaligned access may lead to processor exceptions on some architectures. == This issue was only spotted on i386 Bionic kernel. #146/p unpriv: spill/fill of different pointers ldx FAIL Unexpected error message! 0: (bf) r6 = r10 1: (07) r6 += -8 2: (15) if r1 == 0x0 goto pc+3 R1=ctx(id=0,off=0,imm=0) R6=fp-8
[Kernel-packages] [Bug 1944613] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (unknown type name ‘__u64’)
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1944613 Title: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (unknown type name ‘__u64’) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.4 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe-5.4 source package in Bionic: In Progress Status in linux source package in Focal: Fix Committed Status in linux-hwe-5.4 source package in Focal: Invalid Bug description: [Impact] BugLink: https://bugs.launchpad.net/bugs/1944613 There are build issues in selftests/memfd/fuse_test.c where __u64 is not defined. This is issue is probably due to the fact that in 5.4 there is a type include in one of the includes in the file, however this include probably was not there for 4.15. Regardless we fix this by including the type file directly. [Fix] * selftests/memfd: fix __u64 not defined build issue Add #include to define the type [Test Plan] Recompile tests to make sure they build and tests pass. [Where problems could occur] Should be no problems since we are adding an include file that userspace files always have access to. -- Failed to build on B/linux-hwe-5.4 5.4.0-85.95~18.04.1. This was observed in previous cycles. I am working on a fix for it right now. 13203 fuse_test.c:63:8: error: unknown type name ‘__u64’ 13204static __u64 mfd_assert_get_seals(int fd) 13205 ^ 13206 fuse_test.c:76:42: error: unknown type name ‘__u64’; did you mean ‘__f64’? 13207static void mfd_assert_has_seals(int fd, __u64 seals) 13208 ^ 13209 __f64 13210 fuse_test.c:88:42: error: unknown type name ‘__u64’; did you mean ‘__f64’? 13211static void mfd_assert_add_seals(int fd, __u64 seals) 13212 ^ 13213 __f64 13214 fuse_test.c:102:39: error: unknown type name ‘__u64’; did you mean ‘__f64’? 13215static int mfd_busy_add_seals(int fd, __u64 seals) 13216 ^ 13217 __f64 13218 fuse_test.c: In function ‘sealing_thread_fn’: 13219 fuse_test.c:185:6: warning: implicit declaration of function ‘mfd_busy_add_seals’; did you mean ‘mfd_assert_get_seals’? [-Wimplicit-function-declaration] 13220 r = mfd_busy_add_seals(global_mfd, F_SEAL_WRITE); 13221 ^~ 13222 mfd_assert_get_seals 13223 fuse_test.c:193:3: warning: implicit declaration of function ‘mfd_assert_add_seals’; did you mean ‘mfd_assert_get_seals’? [-Wimplicit-function-declaration] 13224 mfd_assert_add_seals(global_mfd, F_SEAL_WRITE); 13225 ^~~~ 13226 mfd_assert_get_seals 13227 fuse_test.c: In function ‘main’: 13228 fuse_test.c:302:2: warning: implicit declaration of function ‘mfd_assert_has_seals’; did you mean ‘mfd_assert_get_seals’? [-Wimplicit-function-declaration] 13229 mfd_assert_has_seals(mfd, F_SEAL_WRITE); 13230 ^~~~ 13231 mfd_assert_get_seals 13232 make[1]: *** [/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/fuse_test] Error 1 13233 make: *** [all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1944613/+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 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
Sure! I cannot redeploy right now because I'm using the cloud to chase another bug, bug will do asap and report back. Thank you! -- 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/1945707 Title: BCM57800 SRIOV bug causes interfaces to disappear Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] bnx2x driver won't add all devices ports/interfaces. [Test case] Boot system with bnx2x device and verify all ports/interfaces have been added. [Potential regression] bnx2x devices won't be properly probed. Devices won't be added or SR-IOV won't be correctly supported. --- Original Description --- Works with focal kernel 5.4.0-80 Broken with focal kernel 5.4.0-88 On a Dell R720 with the BCM57800 based 1/10 Gigabit Integrated Network cards Kernel 5.11.22-3 causes half of the network interfaces to disappear specifically the 1gb ports. Commands like "ip link show" and "dmesg" no longer show eno3 and eno4 nor any other interface name for these ports. I've read the note in the release notes and this does not appear to be a case of the interface changing names, the 3rd and 4th interface don't show up at all. The card is based on the BCM57800 chipset and has two SFP+ and two gigabit ports on the same card. Commands like "ip link show" no longer show ports 3 and 4. "lspci" still shows four items. dmesg only shows the first two interfaces. This problem seems to be known upstream, and seems to be a regression. More information at https://bugzilla.proxmox.com/show_bug.cgi?id=3558 This is being seen at a customer during an openstack install. It would be appreciated if a workaround could be provided or the fix could be prioritized. Using standard Focal 20.04 LTS kernel (it installs ok with the working kernel then upgrades to the non-working one -- this is done through maas and is difficult to control). Tested other kernels like hwe-* and all seem to be affected too. Client does not want to disable SRIOV on whole card and also cannot disable only ports 3/4 (the bios will not allow it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+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 1934414] Re: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 i386 (Segmentation fault)
Backporting everything necessary would be up to many potential regressions. That would include support for BPF calls and the change to make unknown opcode handling more robust. The former would be commit cc8b0b92a1699bc32f7fec71daa2bfc90de43a4d "bpf: introduce function calls (function boundaries)", which would open a big can of worms we don't want to do. The latter is commit 5e581dad4fec0e6d062740dc35b8dc248b39d224 "bpf: make unknown opcode handling more robust". Though it might add more robustness, it changes the table in the interpreter, so I decided not to backport it now, and fixup the error messages in test_verifier, instead. By the way, commit 21ccaf21497b72f42133182716a42dbf573d314b "bpf: add further test cases around div/mod and others" should have been 3, at least 2, different commits. As it only changes tests, I am find simply doing a partial backport of it. I have it ready and tested, will send a patchset to the list. Cascardo. ** Description changed: - This is a scripted bug report about ADT failures while running linux - tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the - dep8 tests of the tested source or the kernel has yet to be determined. + [Impact] + selftests net will fail on i386, requiring engineers time to investigate, or leading to new BPF failures to be ignored. + + [Fix] + The fix is only to tests. + + [Test case] + Run test_bpf.sh from tools/testing/selftests/net/. + + [Potential regression] + Tests could fail on other architectures. + + + + + + This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz - 03:37:02 DEBUG| [stdout] selftests: test_bpf.sh 03:37:02 DEBUG| [stdout] 03:37:03 ERROR| [stderr] Segmentation fault 03:37:03 DEBUG| [stdout] test_bpf: [FAIL] 03:37:03 DEBUG| [stdout] not ok 1..8 selftests: test_bpf.sh [FAIL] 03:37:03 DEBUG| [stdout] selftests: netdevice.sh 03:37:03 DEBUG| [stdout] -- 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/1934414 Title: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 i386 (Segmentation fault) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [Impact] selftests net will fail on i386, requiring engineers time to investigate, or leading to new BPF failures to be ignored. [Fix] The fix is only to tests. [Test case] Run test_bpf.sh from tools/testing/selftests/net/. [Potential regression] Tests could fail on other architectures. This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz 03:37:02 DEBUG| [stdout] selftests: test_bpf.sh 03:37:02 DEBUG| [stdout] 03:37:03 ERROR| [stderr] Segmentation fault 03:37:03 DEBUG| [stdout] test_bpf: [FAIL] 03:37:03 DEBUG| [stdout] not ok 1..8 selftests: test_bpf.sh [FAIL] 03:37:03 DEBUG| [stdout] selftests: netdevice.sh 03:37:03 DEBUG| [stdout] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934414/+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 1927272] Re: Some kernel selftests fail on linux-kvm
** Tags added: 5.13 impish sru-20211018 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1927272 Title: Some kernel selftests fail on linux-kvm Status in ubuntu-kernel-tests: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Bug description: This is a catch-all Launchpad report to list the kernel selftests failures in linux-kvm kernel. The comments will be used to reference and discuss about the failures, pointing to individual issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927272/+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 1945348] Re: Yellow Carp S0i3 stability fix
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945348 Title: Yellow Carp S0i3 stability fix Status in amd: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Fix Committed Bug description: [Impact] Below errors are reported with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8. [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 amdgpu :04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 amdgpu :04:00.0: PM: failed to resume async: error -110 [Fix] The patch fixes this by forcing exit gfxoff for sdma resume. The patch is in 5.15-rc4 (https://github.com/torvalds/linux/commit/26db706a6d77b9e184feb11725e97e53b7a89519) [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD platforms with s0ix supports. The changes repeat what is (should be) done in firmware. = original descriptions = A problem is identified with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8 sometimes there will be failures. It will manifest as: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 amdgpu :04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 amdgpu :04:00.0: PM: failed to resume async: error -110 The fix for this will be going into 5.15-rcX and also to 5.14.y. Just want to give a pointer to Canonical team that if this comes up where to expect the fix for OEM kernel. The patch going into 5.15-rcX and 5.14.y is: https://lists.freedesktop.org/archives/amd-gfx/2021-September/069451.html To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1945348/+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 1949245] [NEW] AMD ACP 6.x DMIC Supports
Public bug reported: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Assignee: Alex Hung (alexhung) Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: amd Assignee: (unassigned) => Alex Hung (alexhung) ** Information type changed from Proprietary to Public ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** No longer affects: amd ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1949245 Title: AMD ACP 6.x DMIC Supports Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1949245/+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 1949245] [NEW] AMD ACP 6.x DMIC Supports
You have been subscribed to a public bug: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. ** Affects: amd Importance: Undecided Assignee: Alex Hung (alexhung) Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New -- AMD ACP 6.x DMIC Supports https://bugs.launchpad.net/bugs/1949245 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945348] Re: Yellow Carp S0i3 stability fix
** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu) Status: Fix Committed => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945348 Title: Yellow Carp S0i3 stability fix Status in amd: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Below errors are reported with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8. [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 amdgpu :04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 amdgpu :04:00.0: PM: failed to resume async: error -110 [Fix] The patch fixes this by forcing exit gfxoff for sdma resume. The patch is in 5.15-rc4 (https://github.com/torvalds/linux/commit/26db706a6d77b9e184feb11725e97e53b7a89519) [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD platforms with s0ix supports. The changes repeat what is (should be) done in firmware. = original descriptions = A problem is identified with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8 sometimes there will be failures. It will manifest as: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 amdgpu :04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 amdgpu :04:00.0: PM: failed to resume async: error -110 The fix for this will be going into 5.15-rcX and also to 5.14.y. Just want to give a pointer to Canonical team that if this comes up where to expect the fix for OEM kernel. The patch going into 5.15-rcX and 5.14.y is: https://lists.freedesktop.org/archives/amd-gfx/2021-September/069451.html To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1945348/+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 1949249] [NEW] zfs send --dedup with HWE kernel modules produces unreceivable stream
Public bug reported: If you do zfs send -D with 0.8.x userland and 2.0.x kernel, it will actually try to produce a deduplicated send stream (whereas 2.0.x userland stubs out that flag and prints a "this did nothing, stop trying to use it" note). On the system that generated it (20.04 amd64, running 5.11.0-38-generic with zfs-0.8.3-1ubuntu12.13 zfs-kmod-2.0.2-1ubuntu5.1): $ dd if=/dev/urandom of=/badidea/1 bs=1M count=16 $ sudo dd if=/dev/urandom of=/badidea/1 bs=1M count=16 $ sudo cp /badidea/1 /badidea/2 $ sudo zfs snap badidea@snap1 $ sudo zfs send -RLeD badidea@snap1 > dedupstream $ sudo zfs recv badidea/badbadidea < dedupstream internal error: Unknown error 1037 Aborted On my Debian 10 testbed running zfs-2.1.99-422_gb0f3f393d (and same for kmod): cannot receive: stream has unsupported feature, feature flags = 7 This functionality was dropped in commit 196bee4cfd576fb15baa6a64ad6501c594f45497. Since it does all its voodoo in userland, it can indeed still generate a dedup'd stream. Might it make sense to at least print a warning if using zfs send --dedup with 2.0.x, as well as maybe copying the warning that 2.0.x spits out on attempting to receive such a stream, so people don't conclude that being unable to receive a send stream they generated means their system is broken? ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1949249 Title: zfs send --dedup with HWE kernel modules produces unreceivable stream Status in zfs-linux package in Ubuntu: New Bug description: If you do zfs send -D with 0.8.x userland and 2.0.x kernel, it will actually try to produce a deduplicated send stream (whereas 2.0.x userland stubs out that flag and prints a "this did nothing, stop trying to use it" note). On the system that generated it (20.04 amd64, running 5.11.0-38-generic with zfs-0.8.3-1ubuntu12.13 zfs-kmod-2.0.2-1ubuntu5.1): $ dd if=/dev/urandom of=/badidea/1 bs=1M count=16 $ sudo dd if=/dev/urandom of=/badidea/1 bs=1M count=16 $ sudo cp /badidea/1 /badidea/2 $ sudo zfs snap badidea@snap1 $ sudo zfs send -RLeD badidea@snap1 > dedupstream $ sudo zfs recv badidea/badbadidea < dedupstream internal error: Unknown error 1037 Aborted On my Debian 10 testbed running zfs-2.1.99-422_gb0f3f393d (and same for kmod): cannot receive: stream has unsupported feature, feature flags = 7 This functionality was dropped in commit 196bee4cfd576fb15baa6a64ad6501c594f45497. Since it does all its voodoo in userland, it can indeed still generate a dedup'd stream. Might it make sense to at least print a warning if using zfs send --dedup with 2.0.x, as well as maybe copying the warning that 2.0.x spits out on attempting to receive such a stream, so people don't conclude that being unable to receive a send stream they generated means their system is broken? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1949249/+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 1941999] Re: ubuntu 20.04 kernel 5.4.0-80 modprobe -r amdgpu 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/1941999 Title: ubuntu 20.04 kernel 5.4.0-80 modprobe -r amdgpu error Status in linux package in Ubuntu: Expired Bug description: Since kernel 5.4.0-80 of ubuntu20.04, unloading of kernel module of amdgpu became an error and could not be done. modprobe -s -r amdgpu It can be unloaded up to kernel 5.4.0-77 without any problem. Can be unloaded with kernel 5.8.0-63 without any problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941999/+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 1949247] Re: kernel: BUG: unable to handle page fault for address
I just stumbled on what may be a similar problem, here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908912 -- 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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: Confirmed Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64
[Kernel-packages] [Bug 1908912] Re: "BUG: unable to handle page fault for address" 5.4.0-58-generic #64~18.04.1-Ubuntu
I'm on 20.04.3, kernel 5.4.0-89, with a similar problem: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949247 -- 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/1908912 Title: "BUG: unable to handle page fault for address" 5.4.0-58-generic #64~18.04.1-Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: mezimm00@m5:~$ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 mezimm00@m5:~$ apt-cache policy linux-image-5.4.0-58-generic linux-image-5.4.0-58-generic: Installed: 5.4.0-58.64~18.04.1 Candidate: 5.4.0-58.64~18.04.1 Version table: *** 5.4.0-58.64~18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status Dec 20 08:59:56 m5 kernel: [144210.719252] BUG: unable to handle page fault for address: 0007fb39be0e Dec 20 08:59:56 m5 kernel: [144210.719320] #PF: supervisor read access in kernel mode Dec 20 08:59:56 m5 kernel: [144210.719358] #PF: error_code(0x) - not-present page Dec 20 08:59:56 m5 kernel: [144210.719395] PGD 0 P4D 0 Dec 20 08:59:56 m5 kernel: [144210.719420] Oops: [#1] SMP PTI Dec 20 08:59:56 m5 kernel: [144210.719449] CPU: 139 PID: 3081629 Comm: lsof Not tainted 5.4.0-58-generic #64~18.04.1-Ubuntu Dec 20 08:59:56 m5 kernel: [144210.719505] Hardware name: Dell Inc. PowerEdge R930/0T55KM, BIOS 2.8.1 01/02/2020 Dec 20 08:59:56 m5 kernel: [144210.719563] RIP: 0010:lock_get_status+0x221/0x380 Dec 20 08:59:56 m5 kernel: [144210.719600] Code: fd 7b de 91 4c 89 e7 e8 fd 30 fb ff 4d 85 ed 0f 84 de 00 00 00 49 8b 45 28 4d 8b 4d 40 44 89 f2 48 c7 c6 91 52 d7 91 4c 89 e7 <44> 8b 40 10 44 89 c1 41 81 e0 ff ff 0f 00 c1 e9 14 e8 c9 30 fb ff Dec 20 08:59:56 m5 kernel: [144210.719717] RSP: 0018:b731373efd98 EFLAGS: 00010286 Dec 20 08:59:56 m5 kernel: [144210.719755] RAX: 0007fb39bdfe RBX: 939c33a080d8 RCX: 0001 Dec 20 08:59:56 m5 kernel: [144210.719803] RDX: 0003b0a9 RSI: 91d75291 RDI: 938e2d796800 Dec 20 08:59:56 m5 kernel: [144210.719851] RBP: b731373efdc8 R08: 1000 R09: 93565c5a23b8 Dec 20 08:59:56 m5 kernel: [144210.719899] R10: b731373efe50 R11: 9394905b51d5 R12: 938e2d796800 Dec 20 08:59:56 m5 kernel: [144210.719948] R13: 934002945d90 R14: 0003b0a9 R15: 9390ce8a38a0 Dec 20 08:59:56 m5 kernel: [144210.719997] FS: 7ff9bcbb4040() GS:939c3fa8() knlGS: Dec 20 08:59:56 m5 kernel: [144210.720050] CS: 0010 DS: ES: CR0: 80050033 Dec 20 08:59:56 m5 kernel: [144210.720090] CR2: 0007fb39be0e CR3: 00e75d31a002 CR4: 001606e0 Dec 20 08:59:56 m5 kernel: [144210.720138] DR0: DR1: DR2: Dec 20 08:59:56 m5 kernel: [144210.720186] DR3: DR6: fffe0ff0 DR7: 0400 Dec 20 08:59:56 m5 kernel: [144210.720233] Call Trace: Dec 20 08:59:56 m5 kernel: [144210.720262] locks_show+0x83/0xc0 Dec 20 08:59:56 m5 kernel: [144210.720297] seq_read+0x2a4/0x420 Dec 20 08:59:56 m5 kernel: [144210.720330] proc_reg_read+0x3e/0x60 Dec 20 08:59:56 m5 kernel: [144210.720361] __vfs_read+0x1b/0x40 Dec 20 08:59:56 m5 kernel: [144210.721947] vfs_read+0x8e/0x130 Dec 20 08:59:56 m5 kernel: [144210.723479] ksys_read+0xa7/0xe0 Dec 20 08:59:56 m5 kernel: [144210.725009] __x64_sys_read+0x1a/0x20 Dec 20 08:59:56 m5 kernel: [144210.726545] do_syscall_64+0x57/0x190 Dec 20 08:59:56 m5 kernel: [144210.728064] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Dec 20 08:59:56 m5 kernel: [144210.729580] RIP: 0033:0x7ff9bc48e151 Dec 20 08:59:56 m5 kernel: [144210.731081] Code: fe ff ff 48 8d 3d 3f 9b 0a 00 48 83 ec 08 e8 66 4a 02 00 66 0f 1f 44 00 00 48 8d 05 91 08 2e 00 8b 00 85 c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 89 d4 53 Dec 20 08:59:56 m5 kernel: [144210.734225] RSP: 002b:7ffc9e915348 EFLAGS: 0246 ORIG_RAX: Dec 20 08:59:56 m5 kernel: [144210.735809] RAX: ffda RBX: 55f16fee7260 RCX: 7ff9bc48e151 Dec 20 08:59:56 m5 kernel: [144210.737396] RDX: 1000 RSI: 55f16fee8d80 RDI: 0003 Dec 20 08:59:56 m5 kernel: [144210.738947] RBP: 0d68 R08: 0001 R09: 55f16fee7340 Dec 20 08:59:56 m5 kernel: [144210.740456] R10: 7ff9bcbb4040 R11: 0246 R12: 7ff9bc765760 Dec 20 08:59:56 m5 kernel: [144210.741923] R13: 7ff9bc7662a0 R14: 55f16fee7260 R15: 0fff Dec 20 08:59:56 m5 kernel: [144210.743353] Modules linked in: ip6table_filter ip6_tables tcp_diag udp_diag inet_diag xt_REDIRECT ip_vs_rr xt_ipvs ip_vs
[Kernel-packages] [Bug 1949247] Re: kernel: BUG: unable to handle page fault for address
** Description changed: + Ubuntu 20.04.3, kernel 5.4.0-89. + - -- Support: http://www.ubuntu.com/support - -- + -- -- A start job for unit motd-news.service has finished successfully. - -- + -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: lightdm5230 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: lightdm5230 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on
[Kernel-packages] [Bug 1949247] Re: kernel: BUG: unable to handle page fault for address (5.4.0-89)
** Summary changed: - kernel: BUG: unable to handle page fault for address + kernel: BUG: unable to handle page fault for address (5.4.0-89) -- 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/1949247 Title: kernel: BUG: unable to handle page fault for address (5.4.0-89) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.3, kernel 5.4.0-89. - -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4:
[Kernel-packages] [Bug 1949247] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537101/+files/CRDA.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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture:
[Kernel-packages] [Bug 1949247] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537106/+files/Lsusb-v.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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21
[Kernel-packages] [Bug 1949247] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537103/+files/IwConfig.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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21
[Kernel-packages] [Bug 1949247] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537109/+files/ProcInterrupts.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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion:
[Kernel-packages] [Bug 1949247] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537105/+files/Lspci-vt.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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21
[Kernel-packages] [Bug 1949247] [NEW] kernel: BUG: unable to handle page fault for address
Public bug reported: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5230 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-06-02 (1245 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 003: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux
[Kernel-packages] [Bug 1949247] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537102/+files/CurrentDmesg.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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21
[Kernel-packages] [Bug 1949247] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537107/+files/ProcCpuinfo.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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21
[Kernel-packages] [Bug 1949247] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537112/+files/WifiSyslog.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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21
[Kernel-packages] [Bug 1949247] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537111/+files/UdevDb.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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21
[Kernel-packages] [Bug 1949247] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537108/+files/ProcCpuinfoMinimal.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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion:
[Kernel-packages] [Bug 1949247] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537110/+files/ProcModules.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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21
[Kernel-packages] [Bug 1949247] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537104/+files/Lspci.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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21
[Kernel-packages] [Bug 1949247] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537100/+files/AlsaInfo.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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21
[Kernel-packages] [Bug 1949247] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1949247/+attachment/5537113/+files/acpidump.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/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: New Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21
[Kernel-packages] [Bug 1949247] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949247 Title: kernel: BUG: unable to handle page fault for address Status in linux package in Ubuntu: Confirmed Bug description: -- Support: http://www.ubuntu.com/support -- -- A start job for unit motd-news.service has finished successfully. -- -- The job identifier is 11021. Oct 28 15:17:02 ASRock kernel: BUG: unable to handle page fault for address: aae9bb40 Oct 28 15:17:02 ASRock kernel: #PF: supervisor write access in kernel mode Oct 28 15:17:02 ASRock kernel: #PF: error_code(0x0002) - not-present page Oct 28 15:17:02 ASRock kernel: PGD 5100e067 P4D 5100e067 PUD 5100f063 PMD 118c2f063 PTE 800faed64062 Oct 28 15:17:02 ASRock kernel: Oops: 0002 [#1] SMP PTI Oct 28 15:17:02 ASRock kernel: CPU: 3 PID: 75151 Comm: kworker/3:1 Not tainted 5.4.0-89-generic #100-Ubuntu Oct 28 15:17:02 ASRock kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-HVS, BIOS P2.30 07/11/2012 Oct 28 15:17:02 ASRock kernel: Workqueue: cgroup_destroy css_killed_work_fn Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 Oct 28 15:17:02 ASRock kernel: Call Trace: Oct 28 15:17:02 ASRock kernel: _raw_spin_lock_irq+0x26/0x2a Oct 28 15:17:02 ASRock kernel: memcg_drain_all_list_lrus+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: memcg_offline_kmem.part.0+0x9c/0xc0 Oct 28 15:17:02 ASRock kernel: mem_cgroup_css_offline+0xbc/0xf0 Oct 28 15:17:02 ASRock kernel: css_killed_work_fn+0x57/0xe0 Oct 28 15:17:02 ASRock kernel: process_one_work+0x1eb/0x3b0 Oct 28 15:17:02 ASRock kernel: worker_thread+0x4d/0x400 Oct 28 15:17:02 ASRock kernel: kthread+0x104/0x140 Oct 28 15:17:02 ASRock kernel: ? process_one_work+0x3b0/0x3b0 Oct 28 15:17:02 ASRock kernel: ? kthread_park+0x90/0x90 Oct 28 15:17:02 ASRock kernel: ret_from_fork+0x35/0x40 Oct 28 15:17:02 ASRock kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 > Oct 28 15:17:02 ASRock kernel: sysimgblt cryptd psmouse i2c_i801 pata_acpi fb_sys_fops drm lpc_ich raid_class r8169 scsi_transport_sas realtek video Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 Oct 28 15:17:02 ASRock kernel: ---[ end trace 202eca3b53bcb6e9 ]--- Oct 28 15:17:02 ASRock kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x145/0x1d0 Oct 28 15:17:02 ASRock kernel: Code: 02 89 c6 c1 e6 10 0f 84 93 00 00 00 c1 ee 12 83 e0 03 83 ee 01 48 c1 e0 05 48 63 f6 48 05 00 bb 02 00 48 03 04 f5 80 99 a4 aa <48> 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 85 c0 > Oct 28 15:17:02 ASRock kernel: RSP: 0018:bbfc007f7d88 EFLAGS: 00010082 Oct 28 15:17:02 ASRock kernel: RAX: aae9bb40 RBX: 9a24da391ce8 RCX: 0010 Oct 28 15:17:02 ASRock kernel: RDX: 9a24db5abb00 RSI: 0f04 RDI: 9a24ccce4480 Oct 28 15:17:02 ASRock kernel: RBP: bbfc007f7d88 R08: 0010 R09: 8080808080808080 Oct 28 15:17:02 ASRock kernel: R10: 9a24822734f4 R11: 0018 R12: 9a24ca204000 Oct 28 15:17:02 ASRock kernel: R13: 9a24ccce4480 R14: 9a24cc7b17a0 R15: Oct 28 15:17:02 ASRock kernel: FS: () GS:9a24db58() knlGS: Oct 28 15:17:02 ASRock kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 15:17:02 ASRock kernel: CR2: aae9bb40 CR3: 5c6b8001 CR4: 000606e0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse:
[Kernel-packages] [Bug 1897764] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed on X-gcp-4.15 / F-5.4 zVM
** Tags added: hinted impish sru-20211018 -- 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/1897764 Title: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed on X-gcp-4.15 / F-5.4 zVM Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux source package in Focal: Invalid Status in linux source package in Groovy: Invalid Bug description: Issue found on Focal 5.4.0-49.53 zVM kernel04 Test failed with: # selftests: memory-hotplug: mem-on-off-test.sh # Test scope: 2% hotplug memory # online all hot-pluggable memory in offline state: # SKIPPED - no hot-pluggable memory in offline state # offline 2% hot-pluggable memory in online state # trying to offline 1 out of 16 memory block(s): # online->offline memory0 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 0: unexpected fail # online->offline memory1 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 1: unexpected fail # online->offline memory10 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 10: unexpected fail # online->offline memory11 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 11: unexpected fail # online->offline memory12 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 12: unexpected fail # online->offline memory13 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 13: unexpected fail # online->offline memory14 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 14: unexpected fail # online->offline memory15 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 15: unexpected fail # online->offline memory2 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 2: unexpected fail # online->offline memory3 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 3: unexpected fail # online->offline memory4 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 4: unexpected fail # online->offline memory5 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 5: unexpected fail # online->offline memory6 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 6: unexpected fail # online->offline memory7 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 7: unexpected fail # online->offline memory8 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 8: unexpected fail # online->offline memory9 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 9: unexpected fail # FAILED - unable to offline some memory blocks, device busy? # online all hot-pluggable memory in offline state: # SKIPPED - no hot-pluggable memory in offline state # Test with memory notifier error injection not ok 1 selftests: memory-hotplug: mem-on-off-test.sh # exit=1 This issue can be found on 5.4.0-46.50, 5.4.0-45.49 zVM as well. Passed with 5.4.0-44.48 Passed with 5.4.0-43.47 Failed with 5.4.0-42.46 Looks like it's not very stable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1897764/+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 1949106] [NEW] HP hotkeys does not work.
You have been subscribed to a public bug: HP hotkeys does not work at all on HP 15-da1071ne laptop. Brightness keys returns the same scancode, airplane mode returns nothing at all, closing the lid toggles airplane mode. Using evtest: Available devices: /dev/input/event0: Lid Switch /dev/input/event1: Power Button /dev/input/event2: Power Button /dev/input/event3: AT Translated Set 2 keyboard /dev/input/event4: SynPS/2 Synaptics TouchPad /dev/input/event5: Video Bus /dev/input/event6: Video Bus /dev/input/event7: HP Wireless hotkeys /dev/input/event8: HP TrueVision HD Camera: HP Tru /dev/input/event9: HDA Intel PCH Mic /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: HDA Intel PCH HDMI/DP,pcm=9 /dev/input/event15: HDA Intel PCH HDMI/DP,pcm=10 /dev/input/event16: HP WMI hotkeys Testing event 16 (HP WMI hotkeys): No output for the mentioned keys. Testing event 3 (AT Translated Set 2 keyboard): #Brightness up/down yield the following (both the same): Event: time 1630657967.702964, type 4 (EV_MSC), code 4 (MSC_SCAN), value ab Event: time 1630657967.702964, -- SYN_REPORT #Closing the lid then reopening it yields the following: Event: time 1630658208.483290, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9c Event: time 1630658208.483290, type 1 (EV_KEY), code 96 (KEY_KPENTER), value 0 Event: time 1630658208.483290, -- SYN_REPORT Event: time 1630658211.288732, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8 Event: time 1630658211.288732, -- SYN_REPORT Event: time 1630658211.298740, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8 Event: time 1630658211.298740, -- SYN_REPORT Event: time 1630658212.041279, type 4 (EV_MSC), code 4 (MSC_SCAN), value d7 Event: time 1630658212.041279, type 1 (EV_KEY), code 238 (KEY_WLAN), value 1 Event: time 1630658212.041279, -- SYN_REPORT Event: time 1630658212.051527, type 4 (EV_MSC), code 4 (MSC_SCAN), value d7 Event: time 1630658212.051527, type 1 (EV_KEY), code 238 (KEY_WLAN), value 0 Event: time 1630658212.051527, -- SYN_REPORT Event: time 1630658212.058783, type 4 (EV_MSC), code 4 (MSC_SCAN), value e3 Event: time 1630658212.058783, type 1 (EV_KEY), code 143 (KEY_WAKEUP), value 1 Event: time 1630658212.058783, -- SYN_REPORT Event: time 1630658212.069128, type 4 (EV_MSC), code 4 (MSC_SCAN), value e3 Event: time 1630658212.069128, type 1 (EV_KEY), code 143 (KEY_WAKEUP), value 0 Event: time 1630658212.069128, -- SYN_REPORT Check the dmesg attached. If anything else is needed I will provide it. This bug has been occurring since at least kernel 5.4 on various Ubuntu based distros, and still happens on kernel 5.13 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment kernel-bug keyboard -- HP hotkeys does not work. https://bugs.launchpad.net/bugs/1949106 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949106] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1949106 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: impish -- 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/1949106 Title: HP hotkeys does not work. Status in linux package in Ubuntu: Incomplete Bug description: HP hotkeys does not work at all on HP 15-da1071ne laptop. Brightness keys returns the same scancode, airplane mode returns nothing at all, closing the lid toggles airplane mode. Using evtest: Available devices: /dev/input/event0:Lid Switch /dev/input/event1:Power Button /dev/input/event2:Power Button /dev/input/event3:AT Translated Set 2 keyboard /dev/input/event4:SynPS/2 Synaptics TouchPad /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:HP Wireless hotkeys /dev/input/event8:HP TrueVision HD Camera: HP Tru /dev/input/event9:HDA Intel PCH Mic /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: HDA Intel PCH HDMI/DP,pcm=9 /dev/input/event15: HDA Intel PCH HDMI/DP,pcm=10 /dev/input/event16: HP WMI hotkeys Testing event 16 (HP WMI hotkeys): No output for the mentioned keys. Testing event 3 (AT Translated Set 2 keyboard): #Brightness up/down yield the following (both the same): Event: time 1630657967.702964, type 4 (EV_MSC), code 4 (MSC_SCAN), value ab Event: time 1630657967.702964, -- SYN_REPORT #Closing the lid then reopening it yields the following: Event: time 1630658208.483290, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9c Event: time 1630658208.483290, type 1 (EV_KEY), code 96 (KEY_KPENTER), value 0 Event: time 1630658208.483290, -- SYN_REPORT Event: time 1630658211.288732, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8 Event: time 1630658211.288732, -- SYN_REPORT Event: time 1630658211.298740, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8 Event: time 1630658211.298740, -- SYN_REPORT Event: time 1630658212.041279, type 4 (EV_MSC), code 4 (MSC_SCAN), value d7 Event: time 1630658212.041279, type 1 (EV_KEY), code 238 (KEY_WLAN), value 1 Event: time 1630658212.041279, -- SYN_REPORT Event: time 1630658212.051527, type 4 (EV_MSC), code 4 (MSC_SCAN), value d7 Event: time 1630658212.051527, type 1 (EV_KEY), code 238 (KEY_WLAN), value 0 Event: time 1630658212.051527, -- SYN_REPORT Event: time 1630658212.058783, type 4 (EV_MSC), code 4 (MSC_SCAN), value e3 Event: time 1630658212.058783, type 1 (EV_KEY), code 143 (KEY_WAKEUP), value 1 Event: time 1630658212.058783, -- SYN_REPORT Event: time 1630658212.069128, type 4 (EV_MSC), code 4 (MSC_SCAN), value e3 Event: time 1630658212.069128, type 1 (EV_KEY), code 143 (KEY_WAKEUP), value 0 Event: time 1630658212.069128, -- SYN_REPORT Check the dmesg attached. If anything else is needed I will provide it. This bug has been occurring since at least kernel 5.4 on various Ubuntu based distros, and still happens on kernel 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949106/+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 1949106] Re: HP hotkeys does not work.
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949106 Title: HP hotkeys does not work. Status in linux package in Ubuntu: Incomplete Bug description: HP hotkeys does not work at all on HP 15-da1071ne laptop. Brightness keys returns the same scancode, airplane mode returns nothing at all, closing the lid toggles airplane mode. Using evtest: Available devices: /dev/input/event0:Lid Switch /dev/input/event1:Power Button /dev/input/event2:Power Button /dev/input/event3:AT Translated Set 2 keyboard /dev/input/event4:SynPS/2 Synaptics TouchPad /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:HP Wireless hotkeys /dev/input/event8:HP TrueVision HD Camera: HP Tru /dev/input/event9:HDA Intel PCH Mic /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: HDA Intel PCH HDMI/DP,pcm=9 /dev/input/event15: HDA Intel PCH HDMI/DP,pcm=10 /dev/input/event16: HP WMI hotkeys Testing event 16 (HP WMI hotkeys): No output for the mentioned keys. Testing event 3 (AT Translated Set 2 keyboard): #Brightness up/down yield the following (both the same): Event: time 1630657967.702964, type 4 (EV_MSC), code 4 (MSC_SCAN), value ab Event: time 1630657967.702964, -- SYN_REPORT #Closing the lid then reopening it yields the following: Event: time 1630658208.483290, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9c Event: time 1630658208.483290, type 1 (EV_KEY), code 96 (KEY_KPENTER), value 0 Event: time 1630658208.483290, -- SYN_REPORT Event: time 1630658211.288732, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8 Event: time 1630658211.288732, -- SYN_REPORT Event: time 1630658211.298740, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8 Event: time 1630658211.298740, -- SYN_REPORT Event: time 1630658212.041279, type 4 (EV_MSC), code 4 (MSC_SCAN), value d7 Event: time 1630658212.041279, type 1 (EV_KEY), code 238 (KEY_WLAN), value 1 Event: time 1630658212.041279, -- SYN_REPORT Event: time 1630658212.051527, type 4 (EV_MSC), code 4 (MSC_SCAN), value d7 Event: time 1630658212.051527, type 1 (EV_KEY), code 238 (KEY_WLAN), value 0 Event: time 1630658212.051527, -- SYN_REPORT Event: time 1630658212.058783, type 4 (EV_MSC), code 4 (MSC_SCAN), value e3 Event: time 1630658212.058783, type 1 (EV_KEY), code 143 (KEY_WAKEUP), value 1 Event: time 1630658212.058783, -- SYN_REPORT Event: time 1630658212.069128, type 4 (EV_MSC), code 4 (MSC_SCAN), value e3 Event: time 1630658212.069128, type 1 (EV_KEY), code 143 (KEY_WAKEUP), value 0 Event: time 1630658212.069128, -- SYN_REPORT Check the dmesg attached. If anything else is needed I will provide it. This bug has been occurring since at least kernel 5.4 on various Ubuntu based distros, and still happens on kernel 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949106/+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 1830585] Re: cpuset_memory_spread from controllers test suite in LTP failed (hog the memory on the unexpected node)
Found on: 2021.10.18/impish/linux-oracle/5.13.0-1009.11 ** Tags added: impish oracle -- 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/1830585 Title: cpuset_memory_spread from controllers test suite in LTP failed (hog the memory on the unexpected node) Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Status in linux source package in Focal: New Status in linux-azure source package in Focal: New Status in linux source package in Hirsute: New Status in linux-azure source package in Hirsute: New Bug description: Test failed with: cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected node(FilePages_For_Nodes(KB): _0: 2276 _1: 102428, Expect Nodes: 1). <<>> tag=cpuset_memory_spread stime=1558937747 cmdline=" cpuset_memory_spread_testset.sh" contacts="" analysis=exit <<>> 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 0.0993112 s, 1.1 GB/s cpuset_memory_spread 1 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 3 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 5 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected node(FilePages_For_Nodes(KB): _0: 2276 _1: 102428, Expect Nodes: 1). cpuset_memory_spread 9 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 11 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 13 TPASS: Cpuset memory spread page test succeeded. <<>> initiation_status="ok" duration=10 termination_type=exited termination_id=1 corefile=no cutime=364 cstime=383 <<>> ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 27 05:39 seq crw-rw 1 root audio 116, 33 May 27 05:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon May 27 06:16:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830585/+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 1949181] [NEW] package nvidia-driver-460-server 460.91.03-0ubuntu0.20.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: RROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-kernel-source-460-server.0.crash' Error! Bad return status for module build on kernel: 5.11.0-38-generic (x86_64) Consult /var/lib/dkms/nvidia-srv/460.91.03/build/make.log for more information. dpkg: erreur de traitement du paquet nvidia-dkms-460-server (--configure) : installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 dpkg: des problèmes de dépendances empêchent la configuration de nvidia-driver-460-server : nvidia-driver-460-server dépend de nvidia-dkms-460-server (<= 460.91.03-1) ; cependant : Le paquet nvidia-dkms-460-server n'est pas encore configuré. nvidia-driver-460-server dépend de nvidia-dkms-460-server (>= 460.91.03) ; cependant : Le paquet nvidia-dkms-460-server n'est pas encore configuré. dpkg: erreur de traitement du paquet nvidia-driver-460-server (--configure) : problèmes de dépendances - laissé non configuré Aucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-driver-460-server 460.91.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: tzdata:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 29 10:24:28 2021 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2021-10-19 (10 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460-server Title: package nvidia-driver-460-server 460.91.03-0ubuntu0.20.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1949181 Title: package nvidia-driver-460-server 460.91.03-0ubuntu0.20.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in nvidia-graphics-drivers-460-server package in Ubuntu: New Bug description: RROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-kernel-source-460-server.0.crash' Error! Bad return status for module build on kernel: 5.11.0-38-generic (x86_64) Consult /var/lib/dkms/nvidia-srv/460.91.03/build/make.log for more information. dpkg: erreur de traitement du paquet nvidia-dkms-460-server (--configure) : installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 dpkg: des problèmes de dépendances empêchent la configuration de nvidia-driver-460-server : nvidia-driver-460-server dépend de nvidia-dkms-460-server (<= 460.91.03-1) ; cependant : Le paquet nvidia-dkms-460-server n'est pas encore configuré. nvidia-driver-460-server dépend de nvidia-dkms-460-server (>= 460.91.03) ; cependant : Le paquet nvidia-dkms-460-server n'est pas encore configuré. dpkg: erreur de traitement du paquet nvidia-driver-460-server (--configure) : problèmes de dépendances - laissé non configuré Aucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-driver-460-server 460.91.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: tzdata:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 29 10:24:28 2021 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2021-10-19 (10 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460-server Title: package nvidia-driver-460-server 460.91.03-0ubuntu0.20.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Kernel-packages] [Bug 1948025] Re: Update the NVIDIA drivers October 2021
** Description changed: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [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] == 470 == - * New upstream release (LP: #1948025): - - Fixed a bug that can cause a kernel crash in SLI Mosaic - configurations. - - Added support for the EGL_NV_robustness_video_memory_purge. + * New upstream release (LP: #1948025): + - Fixed a bug that can cause a kernel crash in SLI Mosaic + configurations. + - Added support for the EGL_NV_robustness_video_memory_purge. == 495 == - * Initial release (LP: #1948025). + * Initial release (LP: #1948025). + + == 460-server == + + * New upstream release (LP: #1948025). + + + == 450-server == + + * New upstream release (LP: #1948025). + * debian/templates/dkms_nvidia.conf.in: + - Drop buildfix_kernel_5.14.patch. + + + == 418-server == + + * New upstream release (LP: #1948025). + * debian/templates/dkms_nvidia.conf.in: + - Drop buildfix_kernel_5.14.patch. ** Also affects: fabric-manager-460 (Ubuntu) Importance: Undecided Status: New ** Also affects: fabric-manager-450 (Ubuntu) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-460 (Ubuntu) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-450 (Ubuntu) Importance: Undecided Status: New ** Changed in: fabric-manager-450 (Ubuntu) Importance: Undecided => High ** Changed in: fabric-manager-450 (Ubuntu) Status: New => Triaged ** Changed in: fabric-manager-450 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: fabric-manager-460 (Ubuntu) Importance: Undecided => High ** Changed in: fabric-manager-460 (Ubuntu) Status: New => Triaged ** Changed in: fabric-manager-460 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: libnvidia-nscq-450 (Ubuntu) Importance: Undecided => High ** Changed in: libnvidia-nscq-450 (Ubuntu) Status: New => Triaged ** Changed in: libnvidia-nscq-450 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: libnvidia-nscq-460 (Ubuntu) Importance: Undecided => High ** Changed in: libnvidia-nscq-460 (Ubuntu) Status: New => Triaged ** Changed in: libnvidia-nscq-460 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Focal) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Triaged Status in fabric-manager-460 package in Ubuntu: Triaged Status in libnvidia-nscq-450 package in Ubuntu: Triaged Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source
[Kernel-packages] [Bug 1943464] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2021-10-29 06:01 EDT---
Ok, so for focal master-next we didn't yet have the earlier commits
2a671f77ee49 ("s390/pci: fix use after free of zpci_dev")
0b13525c20fe ("s390/pci: fix leak of PCI device structure")
so I had to backport those in addition to
a46044a92add s390/pci: fix zpci_zdev_put() on reserve
That said I tested first with the current focal kernel and similar to what I
mentioned on the stable list for v5.10.x[0] the original scenario that caused
the crash does not cause a crash there. I think this is due to the common code
not
keeping a reference to function 0 around after it is removed. I guess this is
also why this was never seen during the initial multi-function support
development. However even if I don't know how to trigger the problem on focal
it is still there. Should some code keep a reference to the PCI device after
removal we would run
into the same crash trying to access it. We also do still leak the PCI device
structure on removal without these patches.
[0]
https://lore.kernel.org/stable/31dcc776244843aa76deebd49f4ba3fbe4819990.ca...@linux.ibm.com/
--
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/1943464
Title:
Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL
dereference
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Incomplete
Status in linux source package in Hirsute:
In Progress
Status in linux source package in Impish:
Fix Released
Bug description:
After reassign RoCE ConnectX-5 Card Pchid to another LPAR dmesg show
under Ubuntu the following Error message
Ubuntu 20.04.01 with updates
oot@t35lp02:~# uname -a
Linux t35lp02.lnxne.boe 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 17:41:33
UTC 2021 s390x s390x s390x GNU/Linux
root@t35lp02:~#
DMESG Output
761.778422] mlx5_core 0018:00:00.1: poll_health:715:(pid 0): Fatal error 1
detected
[ 761.778432] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0):
assert_var[0] 0x
[ 761.778435] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0):
assert_var[1] 0x
[ 761.778437] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0):
assert_var[2] 0x
[ 761.778439] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0):
assert_var[3] 0x
[ 761.778442] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0):
assert_var[4] 0x
[ 761.778444] mlx5_core 0018:00:00.1: print_health_info:384:(pid 0):
assert_exit_ptr 0x
[ 761.778447] mlx5_core 0018:00:00.1: print_health_info:386:(pid 0):
assert_callra 0x
[ 761.778451] mlx5_core 0018:00:00.1: print_health_info:389:(pid 0): fw_ver
65535.65535.65535
[ 761.778454] mlx5_core 0018:00:00.1: print_health_info:390:(pid 0): hw_id
0x
[ 761.778456] mlx5_core 0018:00:00.1: print_health_info:391:(pid 0):
irisc_index 255
[ 761.778460] mlx5_core 0018:00:00.1: print_health_info:392:(pid 0): synd
0xff: unrecognized error
[ 761.778462] mlx5_core 0018:00:00.1: print_health_info:394:(pid 0):
ext_synd 0x
[ 761.778465] mlx5_core 0018:00:00.1: print_health_info:396:(pid 0): raw
fw_ver 0x
[ 761.778467] mlx5_core 0018:00:00.1: mlx5_trigger_health_work:696:(pid 0):
new health works are not permitted at this stage
[ 763.179016] mlx5_core 0018:00:00.1: E-Switch: cleanup
[ 768.348431] mlx5_core 0018:00:00.1: mlx5_reclaim_startup_pages:562:(pid
123): FW did not return all pages. giving up...
[ 768.348433] [ cut here ]
[ 768.348434] FW pages counter is 43318 after reclaiming all pages
[ 768.348562] WARNING: CPU: 0 PID: 123 at
drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c:567
mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core]
[ 768.348563] Modules linked in: s390_trng chsc_sch eadm_sch vfio_ccw
vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm
drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress
zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor
async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_service_time mlx5_ib
ib_uverbs ib_core pkey qeth_l2 zcrypt crc32_vx_s390 ghash_s390 prng aes_s390
des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 mlx5_core sha256_s390
sha1_s390 sha_common tls mlxfw ptp pps_core zfcp scsi_transport_fc
dasd_eckd_mod dasd_mod qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua
dm_multipath
[ 768.348586] CPU: 0 PID: 123 Comm: kmcheck Tainted: GW
5.4.0-80-generic #90-Ubuntu
[ 768.348586] Hardware name: IBM 8561 T01 703 (LPAR)
[ 768.348587] Krnl PSW : 0704c0018000 03ff808d33ac
(mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core])
[ 768.348607]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0
RI:0 EA:3
[
[Kernel-packages] [Bug 1943464] Focal: 0001-s390-pci-fix-leak-of-PCI-device-structure.patch
--- Comment (attachment only) From niklas.schne...@ibm.com 2021-10-29 06:02 EDT--- ** Attachment added: "Focal: 0001-s390-pci-fix-leak-of-PCI-device-structure.patch" https://bugs.launchpad.net/bugs/1943464/+attachment/5536976/+files/0001-s390-pci-fix-leak-of-PCI-device-structure.patch -- 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/1943464 Title: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Incomplete Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: After reassign RoCE ConnectX-5 Card Pchid to another LPAR dmesg show under Ubuntu the following Error message Ubuntu 20.04.01 with updates oot@t35lp02:~# uname -a Linux t35lp02.lnxne.boe 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 17:41:33 UTC 2021 s390x s390x s390x GNU/Linux root@t35lp02:~# DMESG Output 761.778422] mlx5_core 0018:00:00.1: poll_health:715:(pid 0): Fatal error 1 detected [ 761.778432] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[0] 0x [ 761.778435] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[1] 0x [ 761.778437] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[2] 0x [ 761.778439] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[3] 0x [ 761.778442] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[4] 0x [ 761.778444] mlx5_core 0018:00:00.1: print_health_info:384:(pid 0): assert_exit_ptr 0x [ 761.778447] mlx5_core 0018:00:00.1: print_health_info:386:(pid 0): assert_callra 0x [ 761.778451] mlx5_core 0018:00:00.1: print_health_info:389:(pid 0): fw_ver 65535.65535.65535 [ 761.778454] mlx5_core 0018:00:00.1: print_health_info:390:(pid 0): hw_id 0x [ 761.778456] mlx5_core 0018:00:00.1: print_health_info:391:(pid 0): irisc_index 255 [ 761.778460] mlx5_core 0018:00:00.1: print_health_info:392:(pid 0): synd 0xff: unrecognized error [ 761.778462] mlx5_core 0018:00:00.1: print_health_info:394:(pid 0): ext_synd 0x [ 761.778465] mlx5_core 0018:00:00.1: print_health_info:396:(pid 0): raw fw_ver 0x [ 761.778467] mlx5_core 0018:00:00.1: mlx5_trigger_health_work:696:(pid 0): new health works are not permitted at this stage [ 763.179016] mlx5_core 0018:00:00.1: E-Switch: cleanup [ 768.348431] mlx5_core 0018:00:00.1: mlx5_reclaim_startup_pages:562:(pid 123): FW did not return all pages. giving up... [ 768.348433] [ cut here ] [ 768.348434] FW pages counter is 43318 after reclaiming all pages [ 768.348562] WARNING: CPU: 0 PID: 123 at drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c:567 mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core] [ 768.348563] Modules linked in: s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_service_time mlx5_ib ib_uverbs ib_core pkey qeth_l2 zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 mlx5_core sha256_s390 sha1_s390 sha_common tls mlxfw ptp pps_core zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 768.348586] CPU: 0 PID: 123 Comm: kmcheck Tainted: GW 5.4.0-80-generic #90-Ubuntu [ 768.348586] Hardware name: IBM 8561 T01 703 (LPAR) [ 768.348587] Krnl PSW : 0704c0018000 03ff808d33ac (mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core]) [ 768.348607]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 768.348608] Krnl GPRS: 0004 0006 0034 0007 [ 768.348608]0007 fcb4fa00 007b 03e00458fafc [ 768.348609]b7d406f0 4d849c00 b7d00120 0001b6c0 [ 768.348610]f4cb1100 03e00458fe70 03ff808d33a8 03e00458fa50 [ 768.348615] Krnl Code: 03ff808d339c: c0241043larl %r2,03ff80955422 03ff808d33a2: c0e570c7brasl %r14,03ff808c1530 #03ff808d33a8: a7f40001brc 15,03ff808d33aa >03ff808d33ac: e330a5f04012lt %r3,263664(%r10) 03ff808d33b2: a784ffd7brc
[Kernel-packages] [Bug 1943464] Focal: 0002-s390-pci-fix-use-after-free-of-zpci_dev.patch
--- Comment (attachment only) From niklas.schne...@ibm.com 2021-10-29 06:03 EDT--- ** Attachment added: "Focal: 0002-s390-pci-fix-use-after-free-of-zpci_dev.patch" https://bugs.launchpad.net/bugs/1943464/+attachment/5536977/+files/0002-s390-pci-fix-use-after-free-of-zpci_dev.patch -- 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/1943464 Title: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Incomplete Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: After reassign RoCE ConnectX-5 Card Pchid to another LPAR dmesg show under Ubuntu the following Error message Ubuntu 20.04.01 with updates oot@t35lp02:~# uname -a Linux t35lp02.lnxne.boe 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 17:41:33 UTC 2021 s390x s390x s390x GNU/Linux root@t35lp02:~# DMESG Output 761.778422] mlx5_core 0018:00:00.1: poll_health:715:(pid 0): Fatal error 1 detected [ 761.778432] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[0] 0x [ 761.778435] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[1] 0x [ 761.778437] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[2] 0x [ 761.778439] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[3] 0x [ 761.778442] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[4] 0x [ 761.778444] mlx5_core 0018:00:00.1: print_health_info:384:(pid 0): assert_exit_ptr 0x [ 761.778447] mlx5_core 0018:00:00.1: print_health_info:386:(pid 0): assert_callra 0x [ 761.778451] mlx5_core 0018:00:00.1: print_health_info:389:(pid 0): fw_ver 65535.65535.65535 [ 761.778454] mlx5_core 0018:00:00.1: print_health_info:390:(pid 0): hw_id 0x [ 761.778456] mlx5_core 0018:00:00.1: print_health_info:391:(pid 0): irisc_index 255 [ 761.778460] mlx5_core 0018:00:00.1: print_health_info:392:(pid 0): synd 0xff: unrecognized error [ 761.778462] mlx5_core 0018:00:00.1: print_health_info:394:(pid 0): ext_synd 0x [ 761.778465] mlx5_core 0018:00:00.1: print_health_info:396:(pid 0): raw fw_ver 0x [ 761.778467] mlx5_core 0018:00:00.1: mlx5_trigger_health_work:696:(pid 0): new health works are not permitted at this stage [ 763.179016] mlx5_core 0018:00:00.1: E-Switch: cleanup [ 768.348431] mlx5_core 0018:00:00.1: mlx5_reclaim_startup_pages:562:(pid 123): FW did not return all pages. giving up... [ 768.348433] [ cut here ] [ 768.348434] FW pages counter is 43318 after reclaiming all pages [ 768.348562] WARNING: CPU: 0 PID: 123 at drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c:567 mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core] [ 768.348563] Modules linked in: s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_service_time mlx5_ib ib_uverbs ib_core pkey qeth_l2 zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 mlx5_core sha256_s390 sha1_s390 sha_common tls mlxfw ptp pps_core zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 768.348586] CPU: 0 PID: 123 Comm: kmcheck Tainted: GW 5.4.0-80-generic #90-Ubuntu [ 768.348586] Hardware name: IBM 8561 T01 703 (LPAR) [ 768.348587] Krnl PSW : 0704c0018000 03ff808d33ac (mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core]) [ 768.348607]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 768.348608] Krnl GPRS: 0004 0006 0034 0007 [ 768.348608]0007 fcb4fa00 007b 03e00458fafc [ 768.348609]b7d406f0 4d849c00 b7d00120 0001b6c0 [ 768.348610]f4cb1100 03e00458fe70 03ff808d33a8 03e00458fa50 [ 768.348615] Krnl Code: 03ff808d339c: c0241043larl %r2,03ff80955422 03ff808d33a2: c0e570c7brasl %r14,03ff808c1530 #03ff808d33a8: a7f40001brc 15,03ff808d33aa >03ff808d33ac: e330a5f04012lt %r3,263664(%r10) 03ff808d33b2: a784ffd7brc
[Kernel-packages] [Bug 1943464] Focal: 0003-s390-pci-fix-zpci_zdev_put-on-reserve.patch
--- Comment (attachment only) From niklas.schne...@ibm.com 2021-10-29 06:03 EDT--- ** Attachment added: "Focal: 0003-s390-pci-fix-zpci_zdev_put-on-reserve.patch" https://bugs.launchpad.net/bugs/1943464/+attachment/5536978/+files/0003-s390-pci-fix-zpci_zdev_put-on-reserve.patch -- 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/1943464 Title: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Incomplete Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: After reassign RoCE ConnectX-5 Card Pchid to another LPAR dmesg show under Ubuntu the following Error message Ubuntu 20.04.01 with updates oot@t35lp02:~# uname -a Linux t35lp02.lnxne.boe 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 17:41:33 UTC 2021 s390x s390x s390x GNU/Linux root@t35lp02:~# DMESG Output 761.778422] mlx5_core 0018:00:00.1: poll_health:715:(pid 0): Fatal error 1 detected [ 761.778432] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[0] 0x [ 761.778435] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[1] 0x [ 761.778437] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[2] 0x [ 761.778439] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[3] 0x [ 761.778442] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[4] 0x [ 761.778444] mlx5_core 0018:00:00.1: print_health_info:384:(pid 0): assert_exit_ptr 0x [ 761.778447] mlx5_core 0018:00:00.1: print_health_info:386:(pid 0): assert_callra 0x [ 761.778451] mlx5_core 0018:00:00.1: print_health_info:389:(pid 0): fw_ver 65535.65535.65535 [ 761.778454] mlx5_core 0018:00:00.1: print_health_info:390:(pid 0): hw_id 0x [ 761.778456] mlx5_core 0018:00:00.1: print_health_info:391:(pid 0): irisc_index 255 [ 761.778460] mlx5_core 0018:00:00.1: print_health_info:392:(pid 0): synd 0xff: unrecognized error [ 761.778462] mlx5_core 0018:00:00.1: print_health_info:394:(pid 0): ext_synd 0x [ 761.778465] mlx5_core 0018:00:00.1: print_health_info:396:(pid 0): raw fw_ver 0x [ 761.778467] mlx5_core 0018:00:00.1: mlx5_trigger_health_work:696:(pid 0): new health works are not permitted at this stage [ 763.179016] mlx5_core 0018:00:00.1: E-Switch: cleanup [ 768.348431] mlx5_core 0018:00:00.1: mlx5_reclaim_startup_pages:562:(pid 123): FW did not return all pages. giving up... [ 768.348433] [ cut here ] [ 768.348434] FW pages counter is 43318 after reclaiming all pages [ 768.348562] WARNING: CPU: 0 PID: 123 at drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c:567 mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core] [ 768.348563] Modules linked in: s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_service_time mlx5_ib ib_uverbs ib_core pkey qeth_l2 zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 mlx5_core sha256_s390 sha1_s390 sha_common tls mlxfw ptp pps_core zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 768.348586] CPU: 0 PID: 123 Comm: kmcheck Tainted: GW 5.4.0-80-generic #90-Ubuntu [ 768.348586] Hardware name: IBM 8561 T01 703 (LPAR) [ 768.348587] Krnl PSW : 0704c0018000 03ff808d33ac (mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core]) [ 768.348607]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 768.348608] Krnl GPRS: 0004 0006 0034 0007 [ 768.348608]0007 fcb4fa00 007b 03e00458fafc [ 768.348609]b7d406f0 4d849c00 b7d00120 0001b6c0 [ 768.348610]f4cb1100 03e00458fe70 03ff808d33a8 03e00458fa50 [ 768.348615] Krnl Code: 03ff808d339c: c0241043larl %r2,03ff80955422 03ff808d33a2: c0e570c7brasl %r14,03ff808c1530 #03ff808d33a8: a7f40001brc 15,03ff808d33aa >03ff808d33ac: e330a5f04012lt %r3,263664(%r10) 03ff808d33b2: a784ffd7brc 8,03ff808d3360
