[Kernel-packages] [Bug 2060852] [NEW] nvidia-driver-550-open fails with secure boot enabled
Public bug reported: I switched to the 550-open driver to test this out but the module fails to load with secureboot enabled. The key is rejected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nvidia-kernel-source-550-open 550.67-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 13:45:43 2024 Dependencies: InstallationDate: Installed on 2023-04-10 (366 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nvidia-graphics-drivers-550 UpgradeStatus: Upgraded to noble on 2024-04-10 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2023-12-15T17:01:26.953508 ** Affects: nvidia-graphics-drivers-550 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-550 in Ubuntu. https://bugs.launchpad.net/bugs/2060852 Title: nvidia-driver-550-open fails with secure boot enabled Status in nvidia-graphics-drivers-550 package in Ubuntu: New Bug description: I switched to the 550-open driver to test this out but the module fails to load with secureboot enabled. The key is rejected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nvidia-kernel-source-550-open 550.67-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 13:45:43 2024 Dependencies: InstallationDate: Installed on 2023-04-10 (366 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nvidia-graphics-drivers-550 UpgradeStatus: Upgraded to noble on 2024-04-10 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2023-12-15T17:01:26.953508 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2060852/+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 2046059] Re: kernel cannot find lz4hc and z3fold modules on boot
Works fine on Debian Bookworm on GCP too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046059 Title: kernel cannot find lz4hc and z3fold modules on boot Status in cloud-images: New Status in linux-signed-hwe-6.2 package in Ubuntu: New Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: I've been using zswap without any issues for a while, but fairly recently (can't be certain when) the kernel became unable to find the modules for lz4hc compression and the z3fold zpool. $ egrep 'lz4hc|z3fold' /var/log/syslog Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 'lz4hc' Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 'z3fold' Jan 25 06:35:11 vps-5d014c2f kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 Jan 25 06:35:11 vps-5d014c2f kernel: [0.020859] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 Jan 25 06:35:11 vps-5d014c2f kernel: [1.128588] zswap: compressor lz4hc not available, using default lzo Jan 25 06:35:11 vps-5d014c2f kernel: [1.130368] zswap: zpool z3fold not available, using default zbud But the modules are in the initrd (as they always have been): $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold' usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko I'm at a complete loss. If the modules are there, why can't the kernel find them? Both modules can be loaded (obviously from a different location – not the initrd) and the relevant parameters changed with startup scripts but this is a workaround not a solution. From: https://askubuntu.com/q/1234721/170177 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Sun Dec 10 11:22:41 2023 Ec2AMI: ami-0008be8e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: vps2020-starter-1-2-20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2046059/+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 1626838] Re: yakkety compiling failed on ubuntu trusty
** Changed in: linux (Ubuntu) Status: Confirmed => New ** Project changed: ubuntu-ubuntu-server => 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/1626838 Title: yakkety compiling failed on ubuntu trusty Status in trusty-backports: Won't Fix Status in Yakkety Backports: Won't Fix Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hi ubuntu kernel team, I am compiling my own ubuntu kernel on ubuntu trusty, and I git clone https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/yakkety, the build almost success, but failed at the end with missing modules, I haven't done any change for the source code : Then I start a docker container using xenial image, try the same build steps, I can successfullly build kernel deb pkgs . Do you have idea why it throw missing module error on ubuntu trusty ? Thanks . root@kbuild:~/yakkety# uname -a Linux kbuild 3.13.0-58-generic #97-Ubuntu SMP Wed Jul 8 02:56:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@kbuild:~/yakkety# apt-get build-dep linux-image-4.4.0-36-generic root@kbuild:~/yakkety# fakeroot debian/rules clean root@kbuild:~/yakkety# AUTOBUILD=1 fakeroot debian/rules binary-generic --ignore make[2]: Leaving directory `/root/yakkety/debian/build/build-generic' make[1]: Leaving directory `/root/yakkety' Debug: module-check-generic install -d /root/yakkety/debian.master/abi/4.4.0-34.53/amd64 find /root/yakkety/debian/build/build-generic/ -name \*.ko | \ sed -e 's/.*\/\([^\/]*\)\.ko/\1/' | sort > /root/yakkety/debian.master/abi/4.4.0-34.53/amd64/generic.modules II: Checking modules for generic... reading new modules...read 4590 modules. reading old modules... MISS: spl MISS: splat MISS: zavl MISS: zcommon MISS: zfs MISS: znvpair MISS: zpios MISS: zunicode read 4598 modules : new(0) missing(8) EE: Missing modules (start begging for mercy) make: *** [module-check-generic] Error 1 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 23 03:51 seq crw-rw 1 root audio 116, 33 Sep 23 03:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-58-generic root=UUID=80575ee5-f6ee-41e2-bab6-e4af1c26d1c1 ro nofb nomodeset vga=normal console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22 RelatedPackageVersions: linux-restricted-modules-3.13.0-58-generic N/A linux-backports-modules-3.13.0-58-generic N/A linux-firmware 1.127.16 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.13.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2015.1.2:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2015.1.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1626838/+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 1727861] Re: kernel BUG at /build/linux-hwe-IJy1zi/linux-hwe-4.10.0/fs/cachefiles/namei.c:164!
** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1727861 Title: kernel BUG at /build/linux-hwe-IJy1zi/linux- hwe-4.10.0/fs/cachefiles/namei.c:164! Status in Linux: Confirmed Status in linux-meta-hwe package in Ubuntu: Fix Committed Status in cachefilesd package in Debian: Fix Released Bug description: I have just installed cachefilesd and rebooted. The only change I made was the location of the cache - everything else is set to default. The cache location exists and is writable. I thought I'd test so first attempt: $ cat /mnt/server/share/file > /dev/null No problem. Second attempt: $ cat /mnt/server/share/file > /dev/null [ 471.283546] [ cut here ] [ 471.288354] kernel BUG at /build/linux-hwe-IJy1zi/linux-hwe-4.10.0/fs/cachefiles/namei.c:164! [ 471.296977] invalid opcode: [#1] SMP [ 471.301172] Modules linked in: arc4 md4 cachefiles cifs ccm fscache ip6table_filter ip6_tables iptable_filter ip_tables x_tables ppdev pvpanic input_leds parport_pc serio_raw parport autofs4 btrfs xor raid6_pq crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse virtio_net virtio_scsi [ 471.332032] CPU: 0 PID: 5 Comm: kworker/u2:0 Not tainted 4.10.0-37-generic #41~16.04.1-Ubuntu [ 471.340656] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [ 471.350158] Workqueue: fscache_object fscache_object_work_func [fscache] [ 471.356972] task: 8ddee426ad00 task.stack: bb3f401b [ 471.363083] RIP: 0010:cachefiles_walk_to_object+0x718/0x890 [cachefiles] [ 471.370055] RSP: 0018:bb3f401b3d18 EFLAGS: 00010202 [ 471.375385] RAX: 8ddee18a6201 RBX: 8ddee0b6bd28 RCX: 00019523 [ 471.382897] RDX: 00019522 RSI: 8ddee621c720 RDI: 8ddee4001280 [ 471.390234] RBP: bb3f401b3dc8 R08: 0001c720 R09: c0459068 [ 471.397468] R10: e66040862980 R11: 97c487ed R12: 8ddee11750c0 [ 471.404704] R13: 8ddee0b6bd80 R14: 8ddee0b6bd28 R15: 8ddee1175780 [ 471.411991] FS: () GS:8ddee620() knlGS: [ 471.420180] CS: 0010 DS: ES: CR0: 80050033 [ 471.426037] CR2: 025c4008 CR3: 20b6a000 CR4: 001406f0 [ 471.433359] DR0: DR1: DR2: [ 471.440678] DR3: DR6: fffe0ff0 DR7: 0400 [ 471.447921] Call Trace: [ 471.450478] ? wake_atomic_t_function+0x60/0x60 [ 471.455109] cachefiles_lookup_object+0x51/0xf0 [cachefiles] [ 471.460872] fscache_look_up_object+0xa6/0x1c0 [fscache] [ 471.466378] fscache_object_work_func+0x9d/0x200 [fscache] [ 471.472012] process_one_work+0x16b/0x4a0 [ 471.476118] worker_thread+0x4b/0x500 [ 471.479880] kthread+0x109/0x140 [ 471.483294] ? process_one_work+0x4a0/0x4a0 [ 471.487577] ? kthread_create_on_node+0x60/0x60 [ 471.492208] ret_from_fork+0x2c/0x40 [ 471.495879] Code: 78 ff ff ff 4c 89 f7 49 89 de 48 8b 00 ff 50 58 e9 b5 fc ff ff 48 c7 c7 68 b3 45 c0 e8 b5 75 75 d6 31 f6 4c 89 ef e8 bd 2c 00 00 <0f> 0b 41 bc ff ff ff ff 48 8b 90 98 00 00 00 48 8b bd 78 ff ff [ 471.514854] RIP: cachefiles_walk_to_object+0x718/0x890 [cachefiles] RSP: bb3f401b3d18 [ 471.523171] ---[ end trace d57820f35931610a ]--- I tried with the following builds but the result is the same: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.17/linux-image-4.10.17-041017-generic_4.10.17-041017.201705201051_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc6/linux-image-4.14.0-041400rc6-generic_4.14.0-041400rc6.201710230731_amd64.deb I tried setting the cache back to the default of /var/cache/fscache and it seemed to start working. I ran the test three or four times. Then it failed in the same way. I'm running Ubuntu 16.04 on Google Cloud Compute. In case it's a filesystem issue: $ sudo dumpe2fs -h /dev/sda1 dumpe2fs 1.42.13 (17-May-2015) Filesystem volume name: cloudimg-rootfs Last mounted on: / Filesystem UUID: 67e1c0a6-cdc9-4247-b2e5-dd20ef042025 Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options:user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 128 Block count: 2621179 Reserved block count: 0 Free blocks: 1076375
[Kernel-packages] [Bug 2049317] Re: UBSAN array-index-out-of-bounds error in dmesg - amd gpu drivers
I've started seeing this for the Virtualbox modules. Could just be a coincidence but thought I'd mention it. ** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049317 Title: UBSAN array-index-out-of-bounds error in dmesg - amd gpu drivers Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: lsb_release -a System info Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy uname -a Linux dario-Aspire-E5-553G 6.5.0-14-generic #14~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux At boot and in dmesg (and /var/log/syslog) this error appears, repeated multiple times, I don't remember seeing it in the past, If necessary I can provide the ful /var/log/syslog file: Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.503732] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.504707] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1502:42 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.506717] index 1 is out of range for type 'ATOM_PPLIB_CAC_Leakage_Record [1]' Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507673] CPU: 1 PID: 136 Comm: systemd-udevd Not tainted 6.5.0-14-generic #14~22.04.1-Ubuntu Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507677] Hardware name: Acer Aspire E5-553G/Wasp_BR, BIOS V1.31 03/28/2018 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507679] Call Trace: Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507681] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507684] dump_stack_lvl+0x48/0x70 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507694] dump_stack+0x10/0x20 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507696] __ubsan_handle_out_of_bounds+0xc6/0x110 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507701] init_dpm2_parameters+0x2d6/0x360 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.509001] pp_tables_initialize+0x12c/0x440 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.510250] ? amdgpu_ring_test_helper+0x83/0x90 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.511425] hwmgr_hw_init+0x7b/0x1e0 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.512733] pp_hw_init+0x16/0x50 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.513987] amdgpu_device_ip_init+0x48d/0x960 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.515143] amdgpu_device_init+0x9c8/0x1160 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.516313] amdgpu_driver_load_kms+0x1a/0x1c0 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.517507] amdgpu_pci_probe+0x182/0x450 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518678] local_pci_probe+0x47/0xb0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518684] pci_call_probe+0x55/0x190 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518688] pci_device_probe+0x84/0x120 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518692] really_probe+0x1cc/0x430 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518696] __driver_probe_device+0x8c/0x190 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518709] driver_probe_device+0x24/0xd0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518712] __driver_attach+0x10b/0x210 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518715] ? __pfx___driver_attach+0x10/0x10 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518718] bus_for_each_dev+0x8d/0xf0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518723] driver_attach+0x1e/0x30 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518727] bus_add_driver+0x127/0x240 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518731] driver_register+0x5e/0x130 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518735] ? __pfx_amdgpu_init+0x10/0x10 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.519866] __pci_register_driver+0x62/0x70 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.519871] amdgpu_init+0x69/0xff0 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521048] do_one_initcall+0x5e/0x340 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521056] do_init_module+0x68/0x260 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521062] load_module+0xb85/0xcd0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521066] ? security_kernel_post_read_file+0x75/0x90 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521070] ? security_kernel_post_read_file+0x75/0x90 Jan 14 20:24:13 dario-Aspire-E5-553G
[Kernel-packages] [Bug 2051418] Re: Error in removing linux-image-6.5.0-14-generic
** Project changed: subiquity => ubuntu ** Package changed: ubuntu => linux-meta-hwe-6.5 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051418 Title: Error in removing linux-image-6.5.0-14-generic Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: Here is the error when trying to upgrade Ubuntu: $ sudo apt-get autoremove [sudo] password for minisforum-um790pro-nicolas: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: linux-image-6.5.0-14-generic 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 14.3 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 248924 files and directories currently installed.) Removing linux-image-6.5.0-14-generic (6.5.0-14.14) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-6.5.0-14-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' /usr/sbin/grub-mkconfig: 12: /etc/default/grub: processor.max_cstate=1: not found run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127 dpkg: error processing package linux-image-6.5.0-14-generic (--remove): installed linux-image-6.5.0-14-generic package post-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: linux-image-6.5.0-14-generic Processing was halted because there were too many errors. E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-535/libnvidia-gl-535_535.113.01-0ubuntu3_amd64.deb ./casper/minimal.standard.live.squashfs CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sat Jan 27 10:39:26 2024 InstallationDate: Installed on 2023-10-29 (90 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: subiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2051418/+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 2046059] Re: kernel cannot find lz4hc and z3fold modules on boot
Noble on LXD works correctly too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046059 Title: kernel cannot find lz4hc and z3fold modules on boot Status in cloud-images: New Status in linux-signed-hwe-6.2 package in Ubuntu: New Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: I've been using zswap without any issues for a while, but fairly recently (can't be certain when) the kernel became unable to find the modules for lz4hc compression and the z3fold zpool. $ egrep 'lz4hc|z3fold' /var/log/syslog Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 'lz4hc' Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 'z3fold' Jan 25 06:35:11 vps-5d014c2f kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 Jan 25 06:35:11 vps-5d014c2f kernel: [0.020859] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 Jan 25 06:35:11 vps-5d014c2f kernel: [1.128588] zswap: compressor lz4hc not available, using default lzo Jan 25 06:35:11 vps-5d014c2f kernel: [1.130368] zswap: zpool z3fold not available, using default zbud But the modules are in the initrd (as they always have been): $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold' usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko I'm at a complete loss. If the modules are there, why can't the kernel find them? Both modules can be loaded (obviously from a different location – not the initrd) and the relevant parameters changed with startup scripts but this is a workaround not a solution. From: https://askubuntu.com/q/1234721/170177 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Sun Dec 10 11:22:41 2023 Ec2AMI: ami-0008be8e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: vps2020-starter-1-2-20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2046059/+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 2046059] Re: kernel cannot find lz4hc and z3fold modules on boot
I tried again in Qemu with 16.04, 20.04, 22.04 and 24.04 and none of them see this issue. So I tried with Jammy on LXD and the issue does present itself. So the issue appears to be with the UEC images. I also tried Mantic on LXD and it works fine. So something has been fixed between Jammy and Mantic. I can test others if it will help. I cannot test Noble as there is no image available for LXD, though I'm sure it can still be done (somehow). If the documentation is up to date --> cloud-images. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046059 Title: kernel cannot find lz4hc and z3fold modules on boot Status in cloud-images: New Status in linux-signed-hwe-6.2 package in Ubuntu: New Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: I've been using zswap without any issues for a while, but fairly recently (can't be certain when) the kernel became unable to find the modules for lz4hc compression and the z3fold zpool. $ egrep 'lz4hc|z3fold' /var/log/syslog Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 'lz4hc' Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 'z3fold' Jan 25 06:35:11 vps-5d014c2f kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 Jan 25 06:35:11 vps-5d014c2f kernel: [0.020859] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 Jan 25 06:35:11 vps-5d014c2f kernel: [1.128588] zswap: compressor lz4hc not available, using default lzo Jan 25 06:35:11 vps-5d014c2f kernel: [1.130368] zswap: zpool z3fold not available, using default zbud But the modules are in the initrd (as they always have been): $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold' usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko I'm at a complete loss. If the modules are there, why can't the kernel find them? Both modules can be loaded (obviously from a different location – not the initrd) and the relevant parameters changed with startup scripts but this is a workaround not a solution. From: https://askubuntu.com/q/1234721/170177 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Sun Dec 10 11:22:41 2023 Ec2AMI: ami-0008be8e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: vps2020-starter-1-2-20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2046059/+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 2046059] Re: kernel cannot find lz4hc and z3fold modules on boot
I tried again in Qemu with 16.04, 20.04, 22.04 and 24.04 and none of them see this issue. So I tried with Jammy on LXD and the issue does present itself. So the issue appears to be with the UEC images. I also tried Mantic on LXD and it works fine. So something has been fixed between Jammy and Mantic. I can test others if it will help. I cannot test Noble as there is no image available for LXD, though I'm sure it can still be done (somehow). If the documentation is up to date --> cloud-image. ** Also affects: cloud-images Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046059 Title: kernel cannot find lz4hc and z3fold modules on boot Status in cloud-images: New Status in linux-signed-hwe-6.2 package in Ubuntu: New Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: I've been using zswap without any issues for a while, but fairly recently (can't be certain when) the kernel became unable to find the modules for lz4hc compression and the z3fold zpool. $ egrep 'lz4hc|z3fold' /var/log/syslog Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 'lz4hc' Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 'z3fold' Jan 25 06:35:11 vps-5d014c2f kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 Jan 25 06:35:11 vps-5d014c2f kernel: [0.020859] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 Jan 25 06:35:11 vps-5d014c2f kernel: [1.128588] zswap: compressor lz4hc not available, using default lzo Jan 25 06:35:11 vps-5d014c2f kernel: [1.130368] zswap: zpool z3fold not available, using default zbud But the modules are in the initrd (as they always have been): $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold' usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko I'm at a complete loss. If the modules are there, why can't the kernel find them? Both modules can be loaded (obviously from a different location – not the initrd) and the relevant parameters changed with startup scripts but this is a workaround not a solution. From: https://askubuntu.com/q/1234721/170177 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Sun Dec 10 11:22:41 2023 Ec2AMI: ami-0008be8e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: vps2020-starter-1-2-20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2046059/+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 2046059] Re: kernel cannot find lz4hc and z3fold modules on boot
New kernel, no change. ** Description changed: I've been using zswap without any issues for a while, but fairly recently (can't be certain when) the kernel became unable to find the modules for lz4hc compression and the z3fold zpool. - $ sudo dmesg | grep -E 'z3fold|lz4hc' - [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 - [0.021736] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 - [1.099655] zswap: compressor lz4hc not available, using default lzo - [1.101349] zswap: zpool z3fold not available, using default zbud + $ egrep 'lz4hc|z3fold' /var/log/syslog + Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 'lz4hc' + Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 'z3fold' + Jan 25 06:35:11 vps-5d014c2f kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 + Jan 25 06:35:11 vps-5d014c2f kernel: [0.020859] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 + Jan 25 06:35:11 vps-5d014c2f kernel: [1.128588] zswap: compressor lz4hc not available, using default lzo + Jan 25 06:35:11 vps-5d014c2f kernel: [1.130368] zswap: zpool z3fold not available, using default zbud But the modules are in the initrd (as they always have been): $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold' usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko I'm at a complete loss. If the modules are there, why can't the kernel find them? Both modules can be loaded (obviously from a different location – not the initrd) and the relevant parameters changed with startup scripts but this is a workaround not a solution. From: https://askubuntu.com/q/1234721/170177 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Sun Dec 10 11:22:41 2023 Ec2AMI: ami-0008be8e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: vps2020-starter-1-2-20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago) ** Also affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046059 Title: kernel cannot find lz4hc and z3fold modules on boot Status in linux-signed-hwe-6.2 package in Ubuntu: New Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: I've been using zswap without any issues for a while, but fairly recently (can't be certain when) the kernel became unable to find the modules for lz4hc compression and the z3fold zpool. $ egrep 'lz4hc|z3fold' /var/log/syslog Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 'lz4hc' Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 'z3fold' Jan 25 06:35:11 vps-5d014c2f kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 Jan 25 06:35:11 vps-5d014c2f kernel: [0.020859] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1
[Kernel-packages] [Bug 2047042] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008
So I ran multiple btrfs scrubs and they all reported no error, but for some reason my system now works. I still have the incorrect extent counts but there's no lock-ups. Additional scrubs find nothing wrong. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2047042 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux-signed-hwe-6.2 package in Ubuntu: New Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Yet again my BTRFS root filesystem has failed. There is nothing wrong with my hardware - it's been tested over and over. I can boot fine (the gods know what damage is done when I do) but processes eventually succumb to disk-wait and the whole system ends up frozen. Trying to force a shutdown with sysrq+e/i doesn't help as the processes are stuck disk-wait. [ 28.460735] BTRFS error (device sdb3): incorrect extent count for 13631488; counted 0, expected 1 [ 28.476525] BTRFS error (device sdb3): incorrect extent count for 431808839680; counted 0, expected 1 [ 28.510255] BTRFS error (device sdb3): incorrect extent count for 646590758912; counted 5, expected 6 [ 28.512311] BTRFS error (device sdb3): incorrect extent count for 656254435328; counted 10, expected 11 [ 28.517812] BTRFS error (device sdb3): incorrect extent count for 684171722752; counted 1, expected 2 [ 28.518855] BTRFS error (device sdb3): incorrect extent count for 692761657344; counted 0, expected 1 [ 28.787901] BTRFS error (device sdb3): incorrect extent count for 1032064073728; counted 51, expected 52 No idea how to fix this. Running a Live DVD, mounting and scrubbing shows no errors. Unmounting sticks at disk-wait. Running "btrfs check" in a Live DVD shows errors, but I daren't ask it to --repair as everyone advises not to, so why this is exists is anyone's guess. [ 50.701078] BUG: kernel NULL pointer dereference, address: 0008 [ 50.701101] #PF: supervisor read access in kernel mode [ 50.701112] #PF: error_code(0x) - not-present page [ 50.701124] PGD 0 P4D 0 [ 50.701134] Oops: [#1] PREEMPT SMP PTI [ 50.701146] CPU: 0 PID: 372 Comm: btrfs-transacti Tainted: P OE 6.5.0-14-generic #14~22.04.1-Ubuntu [ 50.701166] Hardware name: LENOVO 0606AD5/LENOVO, BIOS A0KT60AUS 12/15/2016 [ 50.701180] RIP: 0010:assert_eb_page_uptodate+0x2b/0xd0 [btrfs] [ 50.701317] Code: 1f 44 00 00 55 48 89 e5 41 55 41 54 53 48 8b 47 10 4c 8b 6f 18 f6 c4 04 75 26 41 81 bd 90 0c 00 00 ff 0f 00 00 49 89 f4 76 2b <48> 8b 46 08 a8 01 0f 85 82 00 00 00 66 90 49 8b 04 24 a8 04 74 3f [ 50.701370] RSP: 0018:96de80c0b9d8 EFLAGS: 00010212 [ 50.701394] RAX: 0213 RBX: RCX: 1000 [ 50.701419] RDX: 4087 RSI: RDI: 8ab9d10a4870 [ 50.701443] RBP: 96de80c0b9f0 R08: R09: [ 50.701468] R10: R11: R12: [ 50.701492] R13: 8ab9c1189000 R14: 8ab9d10a4870 R15: 00d0 [ 50.701517] FS: () GS:8ac8ffa0() knlGS: [ 50.701554] CS: 0010 DS: ES: CR0: 80050033 [ 50.701577] CR2: 0008 CR3: 000118366001 CR4: 000606f0 [ 50.701602] Call Trace: [ 50.701621] [ 50.701640] ? show_regs+0x6d/0x80 [ 50.701667] ? __die+0x24/0x80 [ 50.701688] ? page_fault_oops+0x99/0x1b0 [ 50.701713] ? kernelmode_fixup_or_oops+0xb2/0x140 [ 50.701736] ? __bad_area_nosemaphore+0x1a5/0x2c0 [ 50.701758] ? bad_area_nosemaphore+0x16/0x30 [ 50.701780] ? do_user_addr_fault+0x2c4/0x6b0 [ 50.701802] ? exc_page_fault+0x83/0x1b0 [ 50.701826] ? asm_exc_page_fault+0x27/0x30 [ 50.701852] ? assert_eb_page_uptodate+0x2b/0xd0 [btrfs] [ 50.701962] ? btrfs_search_slot+0x98b/0x1030 [btrfs] [ 50.702054] extent_buffer_test_bit+0x51/0xa0 [btrfs] [ 50.702163] free_space_test_bit+0xa6/0xe0 [btrfs] [ 50.702275] modify_free_space_bitmap+0x106/0x400 [btrfs] [ 50.702386] __add_to_free_space_tree+0x88/0xe0 [btrfs] [ 50.702502] add_to_free_space_tree+0xaa/0x160 [btrfs] [ 50.702611] do_free_extent_accounting+0x52/0x230 [btrfs] [ 50.702705] __btrfs_free_extent+0x9df/0x1070 [btrfs] [ 50.702799] run_delayed_data_ref+0x8b/0x180 [btrfs] [ 50.702892] btrfs_run_delayed_refs_for_head+0x183/0x550 [btrfs] [ 50.702986] __btrfs_run_delayed_refs+0xc0/0x150 [btrfs] [ 50.703080] btrfs_run_delayed_refs+0x6d/0x1f0 [btrfs] [ 50.703172] ? start_transaction+0x252/0x630 [btrfs] [ 50.703271] btrfs_commit_transaction+0x6a/0xbb0 [btrfs] [ 50.703369] ? start_transaction+0xc8/0x630 [btrfs] [ 50.703468]
[Kernel-packages] [Bug 2047042] [NEW] BUG: kernel NULL pointer dereference, address: 0000000000000008
Public bug reported: Yet again my BTRFS root filesystem has failed. There is nothing wrong with my hardware - it's been tested over and over. I can boot fine (the gods know what damage is done when I do) but processes eventually succumb to disk-wait and the whole system ends up frozen. Trying to force a shutdown with sysrq+e/i doesn't help as the processes are stuck disk-wait. [ 28.460735] BTRFS error (device sdb3): incorrect extent count for 13631488; counted 0, expected 1 [ 28.476525] BTRFS error (device sdb3): incorrect extent count for 431808839680; counted 0, expected 1 [ 28.510255] BTRFS error (device sdb3): incorrect extent count for 646590758912; counted 5, expected 6 [ 28.512311] BTRFS error (device sdb3): incorrect extent count for 656254435328; counted 10, expected 11 [ 28.517812] BTRFS error (device sdb3): incorrect extent count for 684171722752; counted 1, expected 2 [ 28.518855] BTRFS error (device sdb3): incorrect extent count for 692761657344; counted 0, expected 1 [ 28.787901] BTRFS error (device sdb3): incorrect extent count for 1032064073728; counted 51, expected 52 No idea how to fix this. Running a Live DVD, mounting and scrubbing shows no errors. Unmounting sticks at disk-wait. Running "btrfs check" in a Live DVD shows errors, but I daren't ask it to --repair as everyone advises not to, so why this is exists is anyone's guess. [ 50.701078] BUG: kernel NULL pointer dereference, address: 0008 [ 50.701101] #PF: supervisor read access in kernel mode [ 50.701112] #PF: error_code(0x) - not-present page [ 50.701124] PGD 0 P4D 0 [ 50.701134] Oops: [#1] PREEMPT SMP PTI [ 50.701146] CPU: 0 PID: 372 Comm: btrfs-transacti Tainted: P OE 6.5.0-14-generic #14~22.04.1-Ubuntu [ 50.701166] Hardware name: LENOVO 0606AD5/LENOVO, BIOS A0KT60AUS 12/15/2016 [ 50.701180] RIP: 0010:assert_eb_page_uptodate+0x2b/0xd0 [btrfs] [ 50.701317] Code: 1f 44 00 00 55 48 89 e5 41 55 41 54 53 48 8b 47 10 4c 8b 6f 18 f6 c4 04 75 26 41 81 bd 90 0c 00 00 ff 0f 00 00 49 89 f4 76 2b <48> 8b 46 08 a8 01 0f 85 82 00 00 00 66 90 49 8b 04 24 a8 04 74 3f [ 50.701370] RSP: 0018:96de80c0b9d8 EFLAGS: 00010212 [ 50.701394] RAX: 0213 RBX: RCX: 1000 [ 50.701419] RDX: 4087 RSI: RDI: 8ab9d10a4870 [ 50.701443] RBP: 96de80c0b9f0 R08: R09: [ 50.701468] R10: R11: R12: [ 50.701492] R13: 8ab9c1189000 R14: 8ab9d10a4870 R15: 00d0 [ 50.701517] FS: () GS:8ac8ffa0() knlGS: [ 50.701554] CS: 0010 DS: ES: CR0: 80050033 [ 50.701577] CR2: 0008 CR3: 000118366001 CR4: 000606f0 [ 50.701602] Call Trace: [ 50.701621] [ 50.701640] ? show_regs+0x6d/0x80 [ 50.701667] ? __die+0x24/0x80 [ 50.701688] ? page_fault_oops+0x99/0x1b0 [ 50.701713] ? kernelmode_fixup_or_oops+0xb2/0x140 [ 50.701736] ? __bad_area_nosemaphore+0x1a5/0x2c0 [ 50.701758] ? bad_area_nosemaphore+0x16/0x30 [ 50.701780] ? do_user_addr_fault+0x2c4/0x6b0 [ 50.701802] ? exc_page_fault+0x83/0x1b0 [ 50.701826] ? asm_exc_page_fault+0x27/0x30 [ 50.701852] ? assert_eb_page_uptodate+0x2b/0xd0 [btrfs] [ 50.701962] ? btrfs_search_slot+0x98b/0x1030 [btrfs] [ 50.702054] extent_buffer_test_bit+0x51/0xa0 [btrfs] [ 50.702163] free_space_test_bit+0xa6/0xe0 [btrfs] [ 50.702275] modify_free_space_bitmap+0x106/0x400 [btrfs] [ 50.702386] __add_to_free_space_tree+0x88/0xe0 [btrfs] [ 50.702502] add_to_free_space_tree+0xaa/0x160 [btrfs] [ 50.702611] do_free_extent_accounting+0x52/0x230 [btrfs] [ 50.702705] __btrfs_free_extent+0x9df/0x1070 [btrfs] [ 50.702799] run_delayed_data_ref+0x8b/0x180 [btrfs] [ 50.702892] btrfs_run_delayed_refs_for_head+0x183/0x550 [btrfs] [ 50.702986] __btrfs_run_delayed_refs+0xc0/0x150 [btrfs] [ 50.703080] btrfs_run_delayed_refs+0x6d/0x1f0 [btrfs] [ 50.703172] ? start_transaction+0x252/0x630 [btrfs] [ 50.703271] btrfs_commit_transaction+0x6a/0xbb0 [btrfs] [ 50.703369] ? start_transaction+0xc8/0x630 [btrfs] [ 50.703468] transaction_kthread+0x14b/0x1c0 [btrfs] [ 50.703564] ? __pfx_transaction_kthread+0x10/0x10 [btrfs] [ 50.703662] kthread+0xf2/0x120 [ 50.703685] ? __pfx_kthread+0x10/0x10 [ 50.703707] ret_from_fork+0x47/0x70 [ 50.703730] ? __pfx_kthread+0x10/0x10 [ 50.703752] ret_from_fork_asm+0x1b/0x30 [ 50.703776] [ 50.703793] Modules linked in: bridge stp llc snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi ledtrig_audio intel_rapl_msr intel_rapl_common snd_hda_intel sb_edac snd_intel_dspcfg snd_intel_sdw_acpi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec snd_hda_core coretemp snd_hwdep crct10dif_pclmul crc32_pclmul polyval_clmulni snd_pcm polyval_generic ghash_clmulni_intel kvm_intel
[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so
The mainline kernel mapping has no entry for 6.2 (https://people.canonical.com/~kernel/info/kernel-version-map.html) so I took a guess and installed https://kernel.ubuntu.com/mainline/v6.2/ (AMD64). Testing this. I also tried https://kernel.ubuntu.com/mainline/v6.7-rc5/ but the header package requires a newer libc and so failed. Hence my Nvidia drivers wouldn't build. So that wasn't an option. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045951 Title: GpuWatchdog segfault in libcef.so Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash can occur in Chrome and Brave. In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen]. Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in. For me, this first appears to have occured on Dec 2. Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 7efc77192336 sp 7efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0) Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway. This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components. The only upstream reported kernel bug was closed as not enough information was supplied: https://bugzilla.kernel.org/show_bug.cgi?id=209129 This has been reported for Ubuntu a number of times but I thought it best to start fresh: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294 https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286 From around the Interwebs: https://bbs.archlinux.org/viewtopic.php?id=263124 https://askubuntu.com/q/1490916/170177 https://github.com/ValveSoftware/steam-for-linux/issues/7370 https://github.com/ValveSoftware/steam-for-linux/issues/9793 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399 https://unix.stackexchange.com/q/658684/45386 https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/ For testing I tried the following but couldn't trigger this manually: Windows+L to lock screen, switch monitor off, switch back on and log back in. Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in. xset dpms force off then wake the screen up. Any ideas how to continue would be greatly appreciated. I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though. I also note the --disable-gpu-* options for CEF which I'll also test. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Dec 8 07:09:25 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 To manage notificat
[Kernel-packages] [Bug 2042877] Re: kernel: r8169 0000:0d:00.0 enp13s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
Please provide the dmesg log. You may have better luck with the r8169 binary package. ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2042877 Title: kernel: r8169 :0d:00.0 enp13s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). Status in linux-signed-hwe-6.2 package in Ubuntu: Incomplete Bug description: I tried everything. Manually installed the latest kernel, no luck. Updated the driver, also no luck. Here is my lshw output: id: network description: Ethernet interface product: RTL8125 2.5GbE Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:0d:00.0 logical name: enp13s0 version: 05 serial: XXX size: 1Gbit/s capacity: 1Gbit/s width:64 bits clock:33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation = on broadcast = yes driver= r8169 driverversion = 6.2.0-36-generic duplex= full firmware = rtl8125b-2_0.0.2 07/13/20 ip= 192.168.0.228 latency = 0 link = yes multicast = yes port = twisted pair speed = 1Gbit/s resources: irq : 34 ioport: f000(size=256) memory: fc70-fc70 memory: fc71-fc713fff ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 6 22:37:44 2023 InstallationDate: Installed on 2023-06-01 (158 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.2 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-6.2/+bug/2042877/+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 2036287] Re: 6.2.0-32 kernel doesn't work with Asus Vivobook
** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036287 Title: 6.2.0-32 kernel doesn't work with Asus Vivobook Status in linux-signed-hwe-6.2 package in Ubuntu: Fix Released Bug description: I have both kernel 6.2.0-32 and 6.2.0-26 installed on my Asus Vivobook. Since 6.2.0-32 install boot has been impossible. I think this may be a common problem as I'm seeing issues with Ubuntu: https://ubuntuforums.org/showthread.php?t=2490616 and Linux Mint: https://forums.linuxmint.com/viewtopic.php?t=403618 https://askubuntu.com/questions/1485350/booting-ubuntu-22-with- kernel-6-2-0-32-is-impossible ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 15 20:38:11 2023 InstallationDate: Installed on 2023-01-20 (238 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 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-6.2/+bug/2036287/+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 2046071] Re: Brightness control is inoperative
Which older kernels? Also see https://wiki.ubuntu.com/Kernel/Bugs ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046071 Title: Brightness control is inoperative Status in linux-signed-hwe-6.2 package in Ubuntu: Incomplete Bug description: I can't control the brightness at, be it from the fn buttons or the GUI. The brightness is set to the max level with any way to lower it or control it. This problem doesn't exist in older kernels. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 10 17:48:35 2023 InstallationDate: Installed on 2023-12-07 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-6.2 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-6.2/+bug/2046071/+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 2039755] Re: kernel crashes in CIFS code
Have you tried the upstream kernel? Also see https://wiki.ubuntu.com/Kernel/Bugs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039755 Title: kernel crashes in CIFS code Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: I've had several crashes like this on 2 different systems mounting the same SMB server. Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here ] Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs] Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_u ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundw ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp snd_soc_core snd_ctl_ led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn snd_intel_dspcfg snd_inte l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop dell_smm_hwmon Oct 19 13:25:47 1y51573u kernel: [ 1103.030844] nls_iso8859_1 kvm snd_pcm irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios snd_seq iwlmvm btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor snd btmt k mtd libarc4 soundcore videodev bluetooth processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch processor_thermal_device iwlwifi hid_sensor_trigge r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf intel_pch_the rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid sparse_keymap Oct 19 13:25:47 1y51573u kernel: [ 1103.030992] soc_button_array acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c r8153_ecm cdc_et her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic ghash_clmulni _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid hid video wmi pinctrl_cannonlake z3fold zstd Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023 Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events delayed_mntput Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs] Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 de 48 c7 c6 Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 EFLAGS: 00010286 Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX: RBX: 9d72da1353c0 RCX: Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX: RSI: RDI: Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: R09: Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10: R11: R12: 9d72ca687800 Oct 19 13:25:47 1y51573u
[Kernel-packages] [Bug 2046141] Re: os drivers error view in laptop so i want solution
What the hell is this supposed to be? ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Invalid ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Assignee: AshimShaheer (ashimsha) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046141 Title: os drivers error view in laptop so i want solution Status in linux-signed-hwe-6.2 package in Ubuntu: Invalid Bug description: The text in the image you sent is: **Send problem report to the developers?** **Package** linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 **✓ Problem Type** Bug ** ApportVersion** 2.20.11-0ubuntu82.5 ** Architecture** amd64 **✓ CasperMD5CheckResult** pass **✓ CurrentDesktop** ubuntu:GNOME ** Date** Mon Dec 11 13:51:59 2023 > Dependencies ** DistroRelease** Ubuntu 22.04 **✓ InstallationDate** Installed on 2023-12-04 (7 days ago) ** InstallationMedia** Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) **✓ PackageArchitecture** amd64 > ProcCpuinfoMinimal > ProcEnviron **✓ ProcVersionSignature** Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 ** SourcePackage** linux-signed-hwe-6.2 **✓ Tags** jammy wayland-session **✓ Uname** Linux 6.2.0-37-generic x86_64 **✓ UpgradeStatus** No upgrade log present (probably fresh install) **Note:** The `>` symbol at the beginning of two lines indicates that the information on those lines is optional. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 13:27:04 2023 InstallationDate: Installed on 2023-12-04 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 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-6.2/+bug/2046141/+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 2045951] Re: GpuWatchdog segfault in libcef.so
I left the computer to lock itself and killed all steamwebhelper processes before attempting to log in. The system once again became unusable but no segault occurred. It's possible the segfault is a symptom rather than a cure. Nonetheless there are no logs to help debug any further. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045951 Title: GpuWatchdog segfault in libcef.so Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash can occur in Chrome and Brave. In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen]. Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in. For me, this first appears to have occured on Dec 2. Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 7efc77192336 sp 7efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0) Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway. This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components. The only upstream reported kernel bug was closed as not enough information was supplied: https://bugzilla.kernel.org/show_bug.cgi?id=209129 This has been reported for Ubuntu a number of times but I thought it best to start fresh: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294 https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286 From around the Interwebs: https://bbs.archlinux.org/viewtopic.php?id=263124 https://askubuntu.com/q/1490916/170177 https://github.com/ValveSoftware/steam-for-linux/issues/7370 https://github.com/ValveSoftware/steam-for-linux/issues/9793 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399 https://unix.stackexchange.com/q/658684/45386 https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/ For testing I tried the following but couldn't trigger this manually: Windows+L to lock screen, switch monitor off, switch back on and log back in. Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in. xset dpms force off then wake the screen up. Any ideas how to continue would be greatly appreciated. I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though. I also note the --disable-gpu-* options for CEF which I'll also test. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Dec 8 07:09:25 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045951/+sub
[Kernel-packages] [Bug 2039755] Re: kernel crashes in CIFS code
** Summary changed: - lernel crashes in CIFS code + kernel crashes in CIFS code -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039755 Title: kernel crashes in CIFS code Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: I've had several crashes like this on 2 different systems mounting the same SMB server. Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here ] Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs] Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_u ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundw ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp snd_soc_core snd_ctl_ led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn snd_intel_dspcfg snd_inte l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop dell_smm_hwmon Oct 19 13:25:47 1y51573u kernel: [ 1103.030844] nls_iso8859_1 kvm snd_pcm irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios snd_seq iwlmvm btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor snd btmt k mtd libarc4 soundcore videodev bluetooth processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch processor_thermal_device iwlwifi hid_sensor_trigge r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf intel_pch_the rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid sparse_keymap Oct 19 13:25:47 1y51573u kernel: [ 1103.030992] soc_button_array acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c r8153_ecm cdc_et her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic ghash_clmulni _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid hid video wmi pinctrl_cannonlake z3fold zstd Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023 Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events delayed_mntput Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs] Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 de 48 c7 c6 Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 EFLAGS: 00010286 Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX: RBX: 9d72da1353c0 RCX: Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX: RSI: RDI: Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: R09: Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10: R11: R12: 9d72ca687800 Oct 19 13:25:47 1y51573u kernel:
[Kernel-packages] [Bug 2046059] Re: kernel cannot find lz4hc and z3fold modules on boot
** Description changed: - I've been using zswap without any issues for a while, but on upgrading - from 18.04 to 22.04 (via 20.04) the kernel starting failing to find the + I've been using zswap without any issues for a while, but fairly + recently (can't be certain when) the kernel became unable to find the modules for lz4hc compression and the z3fold zpool. $ sudo dmesg | grep -E 'z3fold|lz4hc' [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 [0.021736] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 [1.099655] zswap: compressor lz4hc not available, using default lzo [1.101349] zswap: zpool z3fold not available, using default zbud But the modules are in the initrd (as they always have been): $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold' usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko I'm at a complete loss. If the modules are there, why can't the kernel find them? Both modules can be loaded (obviously from a different location – not the initrd) and the relevant parameters changed with startup scripts but this is a workaround not a solution. From: https://askubuntu.com/q/1234721/170177 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Sun Dec 10 11:22:41 2023 Ec2AMI: ami-0008be8e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: vps2020-starter-1-2-20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_GB.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046059 Title: kernel cannot find lz4hc and z3fold modules on boot Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: I've been using zswap without any issues for a while, but fairly recently (can't be certain when) the kernel became unable to find the modules for lz4hc compression and the z3fold zpool. $ sudo dmesg | grep -E 'z3fold|lz4hc' [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 [0.021736] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 [1.099655] zswap: compressor lz4hc not available, using default lzo [1.101349] zswap: zpool z3fold not available, using default zbud But the modules are in the initrd (as they always have been): $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold' usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko I'm at a complete loss. If the modules are there, why can't the kernel find them? Both modules can be loaded (obviously from a different location – not the initrd) and the relevant parameters changed with startup scripts but this is a workaround not a solution. From: https://askubuntu.com/q/1234721/170177 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack
[Kernel-packages] [Bug 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic
** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036271 Title: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic Status in linux-signed-hwe-6.2 package in Ubuntu: Fix Released Bug description: My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic on a Lenovo Ideapad Flex 5 14ALC05 The Ubuntu splash screen appear with the loader but the boot process is stuck there (with the loader still animating) No problem when booting with the kernel 6.2.0-26-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 15 19:22:42 2023 InstallationDate: Installed on 2021-08-26 (750 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036271/+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 2046059] [NEW] kernel cannot find lz4hc and z3fold modules on boot
Public bug reported: I've been using zswap without any issues for a while, but on upgrading from 18.04 to 22.04 (via 20.04) the kernel starting failing to find the modules for lz4hc compression and the z3fold zpool. $ sudo dmesg | grep -E 'z3fold|lz4hc' [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 [0.021736] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 [1.099655] zswap: compressor lz4hc not available, using default lzo [1.101349] zswap: zpool z3fold not available, using default zbud But the modules are in the initrd (as they always have been): $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold' usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko I'm at a complete loss. If the modules are there, why can't the kernel find them? Both modules can be loaded (obviously from a different location – not the initrd) and the relevant parameters changed with startup scripts but this is a workaround not a solution. From: https://askubuntu.com/q/1234721/170177 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Sun Dec 10 11:22:41 2023 Ec2AMI: ami-0008be8e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: vps2020-starter-1-2-20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046059 Title: kernel cannot find lz4hc and z3fold modules on boot Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: I've been using zswap without any issues for a while, but on upgrading from 18.04 to 22.04 (via 20.04) the kernel starting failing to find the modules for lz4hc compression and the z3fold zpool. $ sudo dmesg | grep -E 'z3fold|lz4hc' [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 [0.021736] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 [1.099655] zswap: compressor lz4hc not available, using default lzo [1.101349] zswap: zpool z3fold not available, using default zbud But the modules are in the initrd (as they always have been): $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold' usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko I'm at a complete loss. If the modules are there, why can't the kernel find them? Both modules can be loaded (obviously from a different location – not the initrd) and the relevant parameters changed with startup scripts but this is a workaround not a solution. From: https://askubuntu.com/q/1234721/170177 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Sun Dec 10 11:22:41 2023 Ec2AMI: ami-0008be8e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova
[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so
** Description changed: The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash can occur in Chrome and Brave. In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen]. Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in. For me, this first appears to have occured on Dec 2. Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 7efc77192336 sp 7efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0) Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway. This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components. - The only bug reported kernel bug was closed as not enough information was supplied: + The only upstream reported kernel bug was closed as not enough information was supplied: https://bugzilla.kernel.org/show_bug.cgi?id=209129 This has been reported for Ubuntu a number of times but I thought it best to start fresh: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294 https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286 From around the Interwebs: https://bbs.archlinux.org/viewtopic.php?id=263124 https://askubuntu.com/q/1490916/170177 https://github.com/ValveSoftware/steam-for-linux/issues/7370 https://github.com/ValveSoftware/steam-for-linux/issues/9793 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399 https://unix.stackexchange.com/q/658684/45386 https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/ For testing I tried the following but couldn't trigger this manually: Windows+L to lock screen, switch monitor off, switch back on and log back in. Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in. xset dpms force off then wake the screen up. Any ideas how to continue would be greatly appreciated. I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though. I also note the --disable-gpu-* options for CEF which I'll also test. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Dec 8 07:09:25 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045951 Title: GpuWatchdog segfault in libcef.so Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash can occur in Chrome and Brave. In my specific case this occurs w
[Kernel-packages] [Bug 2043136] Re: Bluetooth prpblem
** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2043136 Title: Bluetooth prpblem Status in linux-signed-hwe-6.2 package in Ubuntu: Incomplete Bug description: It is always disconnected, I tried with Shell and Blueman, but both are not good. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 22:42:12 2023 InstallationDate: Installed on 2023-08-10 (90 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.2 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-6.2/+bug/2043136/+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 2045951] Re: GpuWatchdog segfault in libcef.so
** Description changed: The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework - (CEF) [Steam, Code, Spotify, Teams...]. Indeed the same crash can occur - in Chrome and Brave. + (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash + can occur in Chrome and Brave. In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen]. Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in. For me, this first appears to have occured on Dec 2. Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 7efc77192336 sp 7efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0) Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway. This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components. The only bug reported kernel bug was closed as not enough information was supplied: https://bugzilla.kernel.org/show_bug.cgi?id=209129 This has been reported for Ubuntu a number of times but I thought it best to start fresh: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294 https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286 From around the Interwebs: https://bbs.archlinux.org/viewtopic.php?id=263124 https://askubuntu.com/questions/1490916/gpuwatchdog-segfault-error-6-in-libcef-so-likely-on-cpu-15-core-7-socket-0 https://github.com/ValveSoftware/steam-for-linux/issues/7370 https://github.com/ValveSoftware/steam-for-linux/issues/9793 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399 https://unix.stackexchange.com/questions/658684/ms-teams-makes-the-whole-gui-stall-gpuwatchdog-segfault https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/ For testing I tried the following but couldn't trigger this manually: Windows+L to lock screen, switch monitor off, switch back on and log back in. Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in. xset dpms force off then wake the screen up. Any ideas how to continue would be greatly appreciated. I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though. I also note the --disable-gpu-* options for CEF which I'll also test. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Dec 8 07:09:25 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 ** Description changed: The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash can occur in Chrome and Brave. In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know ho
[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so
To make Electron aware: https://github.com/electron/electron/issues/40732 ** Bug watch added: github.com/electron/electron/issues #40732 https://github.com/electron/electron/issues/40732 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045951 Title: GpuWatchdog segfault in libcef.so Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash can occur in Chrome and Brave. In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen]. Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in. For me, this first appears to have occured on Dec 2. Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 7efc77192336 sp 7efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0) Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway. This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components. The only bug reported kernel bug was closed as not enough information was supplied: https://bugzilla.kernel.org/show_bug.cgi?id=209129 This has been reported for Ubuntu a number of times but I thought it best to start fresh: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294 https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286 From around the Interwebs: https://bbs.archlinux.org/viewtopic.php?id=263124 https://askubuntu.com/questions/1490916/gpuwatchdog-segfault-error-6-in-libcef-so-likely-on-cpu-15-core-7-socket-0 https://github.com/ValveSoftware/steam-for-linux/issues/7370 https://github.com/ValveSoftware/steam-for-linux/issues/9793 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399 https://unix.stackexchange.com/questions/658684/ms-teams-makes-the-whole-gui-stall-gpuwatchdog-segfault https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/ For testing I tried the following but couldn't trigger this manually: Windows+L to lock screen, switch monitor off, switch back on and log back in. Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in. xset dpms force off then wake the screen up. Any ideas how to continue would be greatly appreciated. I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though. I also note the --disable-gpu-* options for CEF which I'll also test. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Dec 8 07:09:25 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-sign
[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so
** Attachment added: "apt history.log.1" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045951/+attachment/5727428/+files/history.log.1.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045951 Title: GpuWatchdog segfault in libcef.so Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams...]. Indeed the same crash can occur in Chrome and Brave. In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen]. Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in. For me, this first appears to have occured on Dec 2. Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 7efc77192336 sp 7efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0) Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway. This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components. The only bug reported kernel bug was closed as not enough information was supplied: https://bugzilla.kernel.org/show_bug.cgi?id=209129 This has been reported for Ubuntu a number of times but I thought it best to start fresh: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294 https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286 From around the Interwebs: https://bbs.archlinux.org/viewtopic.php?id=263124 https://askubuntu.com/questions/1490916/gpuwatchdog-segfault-error-6-in-libcef-so-likely-on-cpu-15-core-7-socket-0 https://github.com/ValveSoftware/steam-for-linux/issues/7370 https://github.com/ValveSoftware/steam-for-linux/issues/9793 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399 https://unix.stackexchange.com/questions/658684/ms-teams-makes-the-whole-gui-stall-gpuwatchdog-segfault https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/ For testing I tried the following but couldn't trigger this manually: Windows+L to lock screen, switch monitor off, switch back on and log back in. Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in. xset dpms force off then wake the screen up. Any ideas how to continue would be greatly appreciated. I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though. I also note the --disable-gpu-* options for CEF which I'll also test. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Dec 8 07:09:25 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/20
[Kernel-packages] [Bug 2045951] [NEW] GpuWatchdog segfault in libcef.so
Public bug reported: The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams...]. Indeed the same crash can occur in Chrome and Brave. In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen]. Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in. For me, this first appears to have occured on Dec 2. Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 7efc77192336 sp 7efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0) Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway. This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components. The only bug reported kernel bug was closed as not enough information was supplied: https://bugzilla.kernel.org/show_bug.cgi?id=209129 This has been reported for Ubuntu a number of times but I thought it best to start fresh: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294 https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286 From around the Interwebs: https://bbs.archlinux.org/viewtopic.php?id=263124 https://askubuntu.com/questions/1490916/gpuwatchdog-segfault-error-6-in-libcef-so-likely-on-cpu-15-core-7-socket-0 https://github.com/ValveSoftware/steam-for-linux/issues/7370 https://github.com/ValveSoftware/steam-for-linux/issues/9793 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399 https://unix.stackexchange.com/questions/658684/ms-teams-makes-the-whole-gui-stall-gpuwatchdog-segfault https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/ For testing I tried the following but couldn't trigger this manually: Windows+L to lock screen, switch monitor off, switch back on and log back in. Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in. xset dpms force off then wake the screen up. Any ideas how to continue would be greatly appreciated. I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though. I also note the --disable-gpu-* options for CEF which I'll also test. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Dec 8 07:09:25 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "apt history.log" https://bugs.launchpad.net/bugs/2045951/+attachment/5727424/+files/history.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045951 Title: GpuWatchdog segfault in libcef.so Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [
[Kernel-packages] [Bug 1903203] Re: System becomes un-responsive due to gpu segfault
** Package changed: syslog-ng (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/1903203 Title: System becomes un-responsive due to gpu segfault Status in linux package in Ubuntu: New Bug description: I was using: Ubuntu 20.04 (installed a month ago, updated recently) Vmware Workstation 16 (Ubuntu 20.04 VM) Nvidia GTX 1080 TI Driver Version: 450.80.02 CUDA Version: 11.0 What happened: System instantly became unresponsive. Mouse stopped moving, keyboard had no effect (tried ALT+F2). I had to press and hold the power button until the system hard reset. This is the second time I observed this type issue, but last time, the mouse would move with extreme lag. /var/log/syslog: Nov 5 11:54:37 eypc crash_20201105115437_38.dmp[0]: Uploading dump (out-of-process)#012/tmp/dumps/crash_20201105115437_38.dmp Nov 5 11:54:38 eypc crash_20201105115437_38.dmp[0]: Finished uploading minidump (out-of-process): success = yes Nov 5 11:54:38 eypc crash_20201105115437_38.dmp[0]: response: CrashID=bp-373c5190-00a9-43c1-aa4c-80c4a2201105 Nov 5 11:54:38 eypc crash_20201105115437_38.dmp[0]: file ''/tmp/dumps/crash_20201105115437_38.dmp'', upload yes: ''CrashID=bp-373c5190-00a9-43c1-aa4c-80c4a2201105'' Nov 5 11:55:02 eypc kernel: [47695.080487] GpuWatchdog[35222]: segfault at 0 ip 7f3832af62dd sp 7f38278c34d0 error 6 in libcef.so[7f382ed7+69a4000] Nov 5 11:55:02 eypc kernel: [47695.080492] Code: 00 79 09 48 8b 7d a0 e8 21 80 c1 02 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 c1 a5 37 03 01 80 bd 7f ff Since the computer restarted, the log saved in /tmp is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903203/+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 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu
Are you still having this issue? ** Tags added: amd64 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/1861294 Title: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu Status in linux package in Ubuntu: Incomplete Bug description: Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630 (Coffeelake 3x8 GT2). I had chrome, slack and vmware-player running in Gnome. While doing some git clone, screen+mouse+keyboard froze for 2 minutes after which xorg and everything else recovered. I saw this in dmesg: kernel: show_signal_msg: 2 callbacks suppressed kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000] kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller kernel: nvme nvme0: 12/0/0 default/read/poll queues While writing this bug report, the system froze again, and this time it didn't recover. After a cold reset I didn't see any other GpuWatchdog messages in journalctl. Ubuntu applied a BIOS firmware update before the first freeze, so my BIOS was updated as part of the cold reset I did. Not sure if this is relevant to reproducing the freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+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 2027846] Re: tmpfs: Deleted files keep reappearing
Stupidity on my part. Pure stupidity. /tmp/wine/wine64/wine is a symlink back into the git directory! ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2027846 Title: tmpfs: Deleted files keep reappearing Status in linux package in Ubuntu: Invalid Bug description: I am trying to do a number of compilations, including bisects, etc. As part of the process I delete all the files from a compilation so that everything is nice and clean. However, some of these files keep reappearing! In this case I am bisecting Wine. To help I added an ltrace to the Wine shell script... I am compiling to /tmp/wine. /tmp is a tmpfs mount. I added ltrace to /tmp/wine/wine64/wine, which is a shell script. The last line of that script being: exec ltrace "$WINELOADER" "$@" I have then deleted everything in this directory (multiple times). When attempting to access /tmp/wine/wine64/wine I am told that the file does not exist, as expected. I then run a compilation. On checking /tmp/wine/wine64/wine it contains the ltrace: exec ltrace "$WINELOADER" "$@" I thought it might just be bash, but I checked with Pluma and this file contains ltrace – data I have deleted multiple times and should have been overwritten. I tried multiple "sync"s and dropping the caches, but it makes no difference. Why does this data keep reappearing? Why can't I delete a file? What kind of madness is this? There are no words for just how bad this is. In particular: this is definitely a security issue. If a user deletes a file, all I have to do is recreate a file with the same name and I have access to all that user's data. I've spent hours bisecting, but it turns out I cannot trust any of the results as I have no guarantee that any of the files have actually changed. I haven't checked the upstream kernel yet, but I am aware that this is required. It could take many hours. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-76-generic 5.15.0-76.83 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ken 8889 F pulseaudio /dev/snd/controlC1: ken 8889 F pulseaudio /dev/snd/pcmC1D7p: ken8889 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat Jul 15 06:32:07 2023 MachineType: LENOVO 0606AD5 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-76-generic root=UUID=bc8de7a2-4160-4017-937e-3d4126551687 ro rootflags=subvol=@ root=/dev/sdb10 quiet splash zswap.enabled=1 zswap.compressor=lz4 zswap.max_pool_percent=50 zswap.zpool=z3fold module_blacklist=mei_me hugepagesz=1G hugepages=3 hugepagesz=2M hugepages=100 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-76-generic N/A linux-backports-modules-5.15.0-76-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.14 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-09-26 (291 days ago) dmi.bios.date: 12/15/2016 dmi.bios.release: 0.60 dmi.bios.vendor: LENOVO dmi.bios.version: A0KT60AUS dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NONE dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvrA0KT60AUS:bd12/15/2016:br0.60:svnLENOVO:pn0606AD5:pvrThinkStationS30:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct7:cvrNONE:skuLENOVO_BI_A0: dmi.product.family: To be filled by O.E.M. dmi.product.name: 0606AD5 dmi.product.sku: LENOVO_BI_A0 dmi.product.version: ThinkStation S30 dmi.sys.vendor: LENOVO modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027846/+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 2027667] Re: Certain website floods syslog
** Package changed: linux (Ubuntu) => firefox (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/2027667 Title: Certain website floods syslog Status in firefox package in Ubuntu: New Bug description: When viewing https://paris2024.sapsailing.com/gwt/RaceBoard.html?regattaName=OSG2024TEV2023+-+Men%27s+Windsurfing=iQFOiL+men+-+R4=OSG2024TEV2023+-+Men%27s+Windsurfing=83eb5c2a-d3ab-4e22-8422-1e4ab154ed34=b8220cee-9ec7-4640-b8d8-f40e079456d5=FULL_ANALYSIS syslog is flooded with hundreds of lines like these: Jul 13 11:24:47 moshe kernel: [12492.404743] audit: type=1326 audit(1689236687.177:2451): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.405092] audit: type=1326 audit(1689236687.177:2452): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.407568] audit: type=1326 audit(1689236687.181:2453): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.407827] audit: type=1326 audit(1689236687.181:2454): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.408397] audit: type=1326 audit(1689236687.181:2455): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.408622] audit: type=1326 audit(1689236687.181:2456): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.409197] audit: type=1326 audit(1689236687.181:2457): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.409429] audit: type=1326 audit(1689236687.181:2458): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.410412] audit: type=1326 audit(1689236687.185:2459): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.410696] audit: type=1326 audit(1689236687.185:2460): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:25:39 moshe kernel: [12544.337807] kauditd_printk_skb: 9 callbacks suppressed Jul 13 11:25:39 moshe kernel: [12544.337809] audit: type=1326 audit(1689236739.112:2470): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:25:39 moshe kernel: [12544.337928] audit: type=1326 audit(1689236739.112:2471): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:25:39 moshe kernel: [12544.338412] audit: type=1326 audit(1689236739.112:2472): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:25:39 moshe kernel: [12544.338602] audit: type=1326 audit(1689236739.116:2473): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox"
[Kernel-packages] [Bug 2009271] Re: Too many BDL entries regression
Happens with 5.19.0-38-generic. -- 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/2009271 Title: Too many BDL entries regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: Hello, Thanks for your hard work :) I got this error after kernel update to 5.19.0-35 as explained here : https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log and here : https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u A load of syslog "Too many BDL entries" appears. Have a nice week-end, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5004 F wireplumber /dev/snd/controlC1: laurent5004 F wireplumber /dev/snd/seq:laurent5000 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 16:47:55 2023 InstallationDate: Installed on 2020-07-01 (976 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009271/+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 1991691] Re: cannot change mount namespace
I can confirm that 5.19.0-21-generic in kinetic-proposed does indeed fix this issue for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Fix Committed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+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 1944657] [NEW] CD-ROM tray opens on boot up linux mint 20.2 version 5.0.5
Public bug reported: Upon boot up the CD-ROM tray opens and closes. This happens on 5.4.0-86 and 5.4.0-84. Went back to 5.4.0-81 and things are normal. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1944657 Title: CD-ROM tray opens on boot up linux mint 20.2 version 5.0.5 Status in linux package in Ubuntu: New Bug description: Upon boot up the CD-ROM tray opens and closes. This happens on 5.4.0-86 and 5.4.0-84. Went back to 5.4.0-81 and things are normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944657/+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 1835660] Re: initramfs unpacking failed
I've discovered that this behavior can also occur with the installer (similar to bug 1900130) when the USB stick to which the installer ISO was written is bad. (In this case, the error message is saying exactly what it should be saying.) -- 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: Fix Released Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Released Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Released Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Fix Released Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1920707] Re: AMD A4-5300: no sound
I started running a bisect but it takes hours for one step. It's not a realistic option. Adding snd_hda_intel to /etc/modules doesn't work, so a crappy workaround is to add @reboot /sbin/modprobe snd_hda_intel to root's crontab, until I can be bothered to come back to this, but I just don't have the time right now. -- 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/1920707 Title: AMD A4-5300: no sound Status in linux package in Ubuntu: Confirmed Bug description: Starting with linux-4.15.0-137-generic, there is no sound at all on a system with an AMD A4-5300. From a working kernel: Mar 22 05:00:29 richie kernel: [ 33.029621] snd_hda_intel :00:01.1: Force to non-snoop mode [...] Mar 22 05:00:29 richie kernel: [ 33.589291] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:01.1/sound/card0/input5 Mar 22 05:00:29 richie kernel: [ 33.601773] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line Mar 22 05:00:29 richie kernel: [ 33.601776] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Mar 22 05:00:29 richie kernel: [ 33.601779] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) Mar 22 05:00:29 richie kernel: [ 33.601781] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0 Mar 22 05:00:29 richie kernel: [ 33.601782] snd_hda_codec_realtek hdaudioC1D0:inputs: Mar 22 05:00:29 richie kernel: [ 33.601784] snd_hda_codec_realtek hdaudioC1D0: Front Mic=0x19 Mar 22 05:00:29 richie kernel: [ 33.601786] snd_hda_codec_realtek hdaudioC1D0: Rear Mic=0x18 Mar 22 05:00:29 richie kernel: [ 33.601787] snd_hda_codec_realtek hdaudioC1D0: Line=0x1a Mar 22 05:00:29 richie kernel: [ 33.614365] input: HD-Audio Generic Front Mic as /devices/pci:00/:00:14.2/sound/card1/input6 Mar 22 05:00:29 richie kernel: [ 33.614426] input: HD-Audio Generic Rear Mic as /devices/pci:00/:00:14.2/sound/card1/input7 Mar 22 05:00:29 richie kernel: [ 33.614481] input: HD-Audio Generic Line as /devices/pci:00/:00:14.2/sound/card1/input8 Mar 22 05:00:29 richie kernel: [ 33.614536] input: HD-Audio Generic Line Out as /devices/pci:00/:00:14.2/sound/card1/input9 Mar 22 05:00:29 richie kernel: [ 33.614597] input: HD-Audio Generic Front Headphone as /devices/pci:00/:00:14.2/sound/card1/input10 $ lsmod | grep -F snd snd81920 21 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi snd_hda_codec 126976 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hda_codec_generic73728 1 snd_hda_codec_realtek snd_hda_codec_hdmi 49152 1 snd_hda_codec_realtek 106496 1 snd_hda_core 81920 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_hda_intel 45056 5 snd_hwdep 20480 1 snd_hda_codec snd_pcm98304 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core snd_rawmidi32768 1 snd_seq_midi snd_seq65536 2 snd_seq_midi,snd_seq_midi_event snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi snd_seq_midi 16384 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_timer 32768 2 snd_seq,snd_pcm On a broken kernel, dmesg contains no information about the snd_* modules, and lsmod shows that none have loaded. In both cases lspci -v gives the same details: 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI Audio Controller Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity HDMI Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 5 Memory at feb44000 (32-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Kernel modules: snd_hda_intel `sudo modprobe snd_hda_intel` loads all the correct modules and brings sound back. For some reason the newer kernels aren't loading snd_hda_intel (or something related) when it should be. Will update after testing mainline kernels, etc. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-139-generic 4.15.0-139.143 ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18 Uname: Linux 4.15.0-139-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Mon Mar 22 04:42:26 2021 HibernationDevice: RESUME=UUID=5d6634dd-fb1b-49f6-b17a-4197a3814382
[Kernel-packages] [Bug 1920707] Re: AMD A4-5300: no sound
Tested 5.12.0-051200rc4-generic and the problem still occurs. Could this be an issue in another package? Would udev be involved? Otherwise the next step is for me to file upstream. ** Tags added: kernel-bug-exists-upstream kernel-sound-hdmi -- 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/1920707 Title: AMD A4-5300: no sound Status in linux package in Ubuntu: Confirmed Bug description: Starting with linux-4.15.0-137-generic, there is no sound at all on a system with an AMD A4-5300. From a working kernel: Mar 22 05:00:29 richie kernel: [ 33.029621] snd_hda_intel :00:01.1: Force to non-snoop mode [...] Mar 22 05:00:29 richie kernel: [ 33.589291] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:01.1/sound/card0/input5 Mar 22 05:00:29 richie kernel: [ 33.601773] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line Mar 22 05:00:29 richie kernel: [ 33.601776] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Mar 22 05:00:29 richie kernel: [ 33.601779] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) Mar 22 05:00:29 richie kernel: [ 33.601781] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0 Mar 22 05:00:29 richie kernel: [ 33.601782] snd_hda_codec_realtek hdaudioC1D0:inputs: Mar 22 05:00:29 richie kernel: [ 33.601784] snd_hda_codec_realtek hdaudioC1D0: Front Mic=0x19 Mar 22 05:00:29 richie kernel: [ 33.601786] snd_hda_codec_realtek hdaudioC1D0: Rear Mic=0x18 Mar 22 05:00:29 richie kernel: [ 33.601787] snd_hda_codec_realtek hdaudioC1D0: Line=0x1a Mar 22 05:00:29 richie kernel: [ 33.614365] input: HD-Audio Generic Front Mic as /devices/pci:00/:00:14.2/sound/card1/input6 Mar 22 05:00:29 richie kernel: [ 33.614426] input: HD-Audio Generic Rear Mic as /devices/pci:00/:00:14.2/sound/card1/input7 Mar 22 05:00:29 richie kernel: [ 33.614481] input: HD-Audio Generic Line as /devices/pci:00/:00:14.2/sound/card1/input8 Mar 22 05:00:29 richie kernel: [ 33.614536] input: HD-Audio Generic Line Out as /devices/pci:00/:00:14.2/sound/card1/input9 Mar 22 05:00:29 richie kernel: [ 33.614597] input: HD-Audio Generic Front Headphone as /devices/pci:00/:00:14.2/sound/card1/input10 $ lsmod | grep -F snd snd81920 21 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi snd_hda_codec 126976 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hda_codec_generic73728 1 snd_hda_codec_realtek snd_hda_codec_hdmi 49152 1 snd_hda_codec_realtek 106496 1 snd_hda_core 81920 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_hda_intel 45056 5 snd_hwdep 20480 1 snd_hda_codec snd_pcm98304 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core snd_rawmidi32768 1 snd_seq_midi snd_seq65536 2 snd_seq_midi,snd_seq_midi_event snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi snd_seq_midi 16384 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_timer 32768 2 snd_seq,snd_pcm On a broken kernel, dmesg contains no information about the snd_* modules, and lsmod shows that none have loaded. In both cases lspci -v gives the same details: 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI Audio Controller Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity HDMI Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 5 Memory at feb44000 (32-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Kernel modules: snd_hda_intel `sudo modprobe snd_hda_intel` loads all the correct modules and brings sound back. For some reason the newer kernels aren't loading snd_hda_intel (or something related) when it should be. Will update after testing mainline kernels, etc. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-139-generic 4.15.0-139.143 ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18 Uname: Linux 4.15.0-139-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Mon Mar 22 04:42:26 2021 HibernationDevice: RESUME=UUID=5d6634dd-fb1b-49f6-b17a-4197a3814382 InstallationDate: Installed on 2015-11-28 (1940 days ago)
[Kernel-packages] [Bug 1920707] Re: AMD Trinity HDMI Audio Controller: no sound
Tested the mainline kernel 4.15.18-041518-generic and the problem still occurs. ** Summary changed: - AMD Trinity HDMI Audio Controller: no sound + AMD A4-5300: no sound -- 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/1920707 Title: AMD A4-5300: no sound Status in linux package in Ubuntu: Confirmed Bug description: Starting with linux-4.15.0-137-generic, there is no sound at all on a system with an AMD A4-5300. From a working kernel: Mar 22 05:00:29 richie kernel: [ 33.029621] snd_hda_intel :00:01.1: Force to non-snoop mode [...] Mar 22 05:00:29 richie kernel: [ 33.589291] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:01.1/sound/card0/input5 Mar 22 05:00:29 richie kernel: [ 33.601773] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line Mar 22 05:00:29 richie kernel: [ 33.601776] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Mar 22 05:00:29 richie kernel: [ 33.601779] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) Mar 22 05:00:29 richie kernel: [ 33.601781] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0 Mar 22 05:00:29 richie kernel: [ 33.601782] snd_hda_codec_realtek hdaudioC1D0:inputs: Mar 22 05:00:29 richie kernel: [ 33.601784] snd_hda_codec_realtek hdaudioC1D0: Front Mic=0x19 Mar 22 05:00:29 richie kernel: [ 33.601786] snd_hda_codec_realtek hdaudioC1D0: Rear Mic=0x18 Mar 22 05:00:29 richie kernel: [ 33.601787] snd_hda_codec_realtek hdaudioC1D0: Line=0x1a Mar 22 05:00:29 richie kernel: [ 33.614365] input: HD-Audio Generic Front Mic as /devices/pci:00/:00:14.2/sound/card1/input6 Mar 22 05:00:29 richie kernel: [ 33.614426] input: HD-Audio Generic Rear Mic as /devices/pci:00/:00:14.2/sound/card1/input7 Mar 22 05:00:29 richie kernel: [ 33.614481] input: HD-Audio Generic Line as /devices/pci:00/:00:14.2/sound/card1/input8 Mar 22 05:00:29 richie kernel: [ 33.614536] input: HD-Audio Generic Line Out as /devices/pci:00/:00:14.2/sound/card1/input9 Mar 22 05:00:29 richie kernel: [ 33.614597] input: HD-Audio Generic Front Headphone as /devices/pci:00/:00:14.2/sound/card1/input10 $ lsmod | grep -F snd snd81920 21 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi snd_hda_codec 126976 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hda_codec_generic73728 1 snd_hda_codec_realtek snd_hda_codec_hdmi 49152 1 snd_hda_codec_realtek 106496 1 snd_hda_core 81920 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_hda_intel 45056 5 snd_hwdep 20480 1 snd_hda_codec snd_pcm98304 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core snd_rawmidi32768 1 snd_seq_midi snd_seq65536 2 snd_seq_midi,snd_seq_midi_event snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi snd_seq_midi 16384 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_timer 32768 2 snd_seq,snd_pcm On a broken kernel, dmesg contains no information about the snd_* modules, and lsmod shows that none have loaded. In both cases lspci -v gives the same details: 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI Audio Controller Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity HDMI Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 5 Memory at feb44000 (32-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Kernel modules: snd_hda_intel `sudo modprobe snd_hda_intel` loads all the correct modules and brings sound back. For some reason the newer kernels aren't loading snd_hda_intel (or something related) when it should be. Will update after testing mainline kernels, etc. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-139-generic 4.15.0-139.143 ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18 Uname: Linux 4.15.0-139-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Mon Mar 22 04:42:26 2021 HibernationDevice: RESUME=UUID=5d6634dd-fb1b-49f6-b17a-4197a3814382 InstallationDate: Installed on 2015-11-28 (1940 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
[Kernel-packages] [Bug 1920707] [NEW] AMD Trinity HDMI Audio Controller: no sound
Public bug reported: Starting with linux-4.15.0-137-generic, there is no sound at all on a system with an AMD A4-5300. >From a working kernel: Mar 22 05:00:29 richie kernel: [ 33.029621] snd_hda_intel :00:01.1: Force to non-snoop mode [...] Mar 22 05:00:29 richie kernel: [ 33.589291] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:01.1/sound/card0/input5 Mar 22 05:00:29 richie kernel: [ 33.601773] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line Mar 22 05:00:29 richie kernel: [ 33.601776] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Mar 22 05:00:29 richie kernel: [ 33.601779] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) Mar 22 05:00:29 richie kernel: [ 33.601781] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0 Mar 22 05:00:29 richie kernel: [ 33.601782] snd_hda_codec_realtek hdaudioC1D0:inputs: Mar 22 05:00:29 richie kernel: [ 33.601784] snd_hda_codec_realtek hdaudioC1D0: Front Mic=0x19 Mar 22 05:00:29 richie kernel: [ 33.601786] snd_hda_codec_realtek hdaudioC1D0: Rear Mic=0x18 Mar 22 05:00:29 richie kernel: [ 33.601787] snd_hda_codec_realtek hdaudioC1D0: Line=0x1a Mar 22 05:00:29 richie kernel: [ 33.614365] input: HD-Audio Generic Front Mic as /devices/pci:00/:00:14.2/sound/card1/input6 Mar 22 05:00:29 richie kernel: [ 33.614426] input: HD-Audio Generic Rear Mic as /devices/pci:00/:00:14.2/sound/card1/input7 Mar 22 05:00:29 richie kernel: [ 33.614481] input: HD-Audio Generic Line as /devices/pci:00/:00:14.2/sound/card1/input8 Mar 22 05:00:29 richie kernel: [ 33.614536] input: HD-Audio Generic Line Out as /devices/pci:00/:00:14.2/sound/card1/input9 Mar 22 05:00:29 richie kernel: [ 33.614597] input: HD-Audio Generic Front Headphone as /devices/pci:00/:00:14.2/sound/card1/input10 $ lsmod | grep -F snd snd81920 21 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi snd_hda_codec 126976 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hda_codec_generic73728 1 snd_hda_codec_realtek snd_hda_codec_hdmi 49152 1 snd_hda_codec_realtek 106496 1 snd_hda_core 81920 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_hda_intel 45056 5 snd_hwdep 20480 1 snd_hda_codec snd_pcm98304 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core snd_rawmidi32768 1 snd_seq_midi snd_seq65536 2 snd_seq_midi,snd_seq_midi_event snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi snd_seq_midi 16384 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_timer 32768 2 snd_seq,snd_pcm On a broken kernel, dmesg contains no information about the snd_* modules, and lsmod shows that none have loaded. In both cases lspci -v gives the same details: 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI Audio Controller Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity HDMI Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 5 Memory at feb44000 (32-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Kernel modules: snd_hda_intel `sudo modprobe snd_hda_intel` loads all the correct modules and brings sound back. For some reason the newer kernels aren't loading snd_hda_intel (or something related) when it should be. Will update after testing mainline kernels, etc. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-139-generic 4.15.0-139.143 ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18 Uname: Linux 4.15.0-139-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Mon Mar 22 04:42:26 2021 HibernationDevice: RESUME=UUID=5d6634dd-fb1b-49f6-b17a-4197a3814382 InstallationDate: Installed on 2015-11-28 (1940 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7721 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-139-generic root=UUID=6c84fef8-256e-4a5c-9033-28e0b9342a56 ro zswap.enabled=1 quiet splash zswap.compressor=lz4hc zswap.max_pool_percent=20 zswap.zpool=z3fold vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions:
[Kernel-packages] [Bug 1917245] Re: HP and Canon support ubuntu LTS linux systems
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917245 Title: HP and Canon support ubuntu LTS linux systems Status in linux package in Ubuntu: Invalid Bug description: HP and Canon and epson printers and scanners support ubuntu LTS linux systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: snowden1435 F pulseaudio /dev/snd/controlC0: snowden1435 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (13 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917245/+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 1917110] Re: deus ex mankind divide working too slow linux ubuntu 20.04 LTS
What makes you think that this is a Linux bug? Did you bother reporting this to Steam? ** 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/1917110 Title: deus ex mankind divide working too slow linux ubuntu 20.04 LTS Status in linux package in Ubuntu: Incomplete Bug description: deus ex mankind divide working too slow my linux ubuntu 20.04 LTS desktop openGL 3.0 and openGL 2.1 working too slow linux ubuntu 20.04 LTS desktop MSI MS 7817 --- 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 1400 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-20 (7 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Hewlett-Packard HP Compaq 6000 Pro MT PC 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.8.0-44-generic root=UUID=2a4fb579-9676-4e2a-8293-120b9188db54 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-44-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: 08/25/2009 dmi.bios.release: 1.9 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G2 v01.09 dmi.board.asset.tag: CZC0195QPD dmi.board.name: 3048h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC0195QPD dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G2v01.09:bd08/25/2009:br1.9:svnHewlett-Packard:pnHPCompaq6000ProMTPC:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq 6000 Pro MT PC dmi.product.sku: VN784ET#UUW dmi.sys.vendor: Hewlett-Packard --- 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 on 2021-02-20 (7 days
[Kernel-packages] [Bug 1917112] Re: deus ex human revolution director cut working too slow steam proton
What makes you think that this is a Linux bug? Did you bother reporting this to Steam? ** 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/1917112 Title: deus ex human revolution director cut working too slow steam proton Status in linux package in Ubuntu: Incomplete Bug description: deus ex human revolution director cut working too slow steam proton experimental same is deus ex the fall and deus mandkind divide all deus ex games working too slow working too slow linux kernels 5.4 and linux kernels 5.8 working too slow Computer Information: Manufacturer: Unknown Model: Unknown Form Factor: Desktop No Touch Input Detected Processor Information: CPU Vendor: GenuineIntel CPU Brand: Intel(R) Pentium(R) CPU G3420 @ 3.20GHz CPU Family: 0x6 CPU Model: 0x3c CPU Stepping: 0x3 CPU Type: 0x0 Speed: 3200 Mhz 2 logical processors 2 physical processors HyperThreading: Unsupported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Unsupported SSE41: Supported SSE42: Supported AES: Unsupported AVX: Unsupported AVX2: Unsupported AVX512F: Unsupported AVX512PF: Unsupported AVX512ER: Unsupported AVX512CD: Unsupported AVX512VNNI: Unsupported SHA: Unsupported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: Ubuntu 20.04.2 LTS (64 bit) Kernel Name: Linux Kernel Version: 5.4.0-66-generic X Server Vendor: The X.Org Foundation X Server Release: 12009000 X Window Manager: GNOME Shell Steam Runtime Version: steam-runtime_0.20201203.1 Video Card: Driver: Intel Open Source Technology Center Mesa DRI Intel(R) HD Graphics (HSW GT1) Driver Version: 3.0 Mesa 20.2.6 OpenGL Version: 3.0 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 60 Hz VendorID: 0x8086 DeviceID: 0x402 Revision Not Detected Number of Monitors: 1 Number of Logical Video Cards: 1 Primary Display Resolution: 1280 x 1024 Desktop Resolution: 1280 x 1024 Primary Display Size: 13.39" x 10.63" (17.09" diag) 34.0cm x 27.0cm (43.4cm diag) Primary VRAM Not Detected Sound card: Audio device: Intel Haswell HDMI Memory: RAM: 3798 Mb VR Hardware: VR Headset: None detected Miscellaneous: UI Language: English LANG: fi_FI.UTF-8 Total Hard Disk Space Available: 937366 Mb Largest Free Hard Disk Block: 851473 Mb The runtime information tool is preparing a report, please wait... --- 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:
[Kernel-packages] [Bug 1917264] Re: HP and Canon and Epson printers inks status
What debugging have you done to determine that this is a Linux bug, because I very much doubt it is? ** 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/1917264 Title: HP and Canon and Epson printers inks status Status in linux package in Ubuntu: Incomplete Bug description: HP and Canon and Epson printers inks status information how much is colours and black inks status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: snowden1435 F pulseaudio /dev/snd/controlC0: snowden1435 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (13 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 1381 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-20 (8 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. E402SA 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.8.0-44-generic root=UUID=32c14ba7-6abd-49ad-b9b6-25073031646a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.187.9 Tags: focal Uname: Linux 5.8.0-44-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: 12/14/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402SA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE402SA.208:bd12/14/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnE402SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: E dmi.product.name: E402SA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tessetessu 1398 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-20 (8 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" -
[Kernel-packages] [Bug 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
** Tags added: bionic focal regression-update -- 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/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: New Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+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 1909782] Re: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2, 1
This bugreport can be closed. -- 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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ] Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 03ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 06e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0x370 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400300] kthread+0x12f/0x150 Dec 20 09:08:40 ken-macbookpro21 kerne
[Kernel-packages] [Bug 1911240] [NEW] package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess retur
Public bug reported: dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 12 13:53:08 2021 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-01-12 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1911240 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 12 13:53:08 2021 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-01-12 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1911240/+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 1910900] Re: package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi
You need to provide /var/lib/dkms/nvidia/390.141/build/make.log ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1910900 Title: package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: sometimes works great ProblemType: Package DistroRelease: Ubuntu 20.10 Package: nvidia-dkms-390 390.141-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jan 10 02:36:18 2021 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910900/+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 1909782] Re: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2, 1
linux-image-5.8.0-36-generic seems fine, and all is working well again. Not sure if something was tweaked/fixed or if it is just serendipity, but all is well now. -- 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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ] Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 03ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 06e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_t
[Kernel-packages] [Bug 1909782] Re: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2, 1
linux-image-5.8.0-34-generic also crashes on boot. syslog attached. I am holding back the kernel to linux-image-5.8.0-31-generic for the time being. -- 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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ] Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 03ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 06e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0x370
[Kernel-packages] [Bug 1909782] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448439/+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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] work
[Kernel-packages] [Bug 1909782] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448441/+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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread
[Kernel-packages] [Bug 1909782] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448440/+files/ProcEnviron.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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0
[Kernel-packages] [Bug 1909782] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448445/+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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0
[Kernel-packages] [Bug 1909782] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448447/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 82000000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 82000000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:00000000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 000080050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:
[Kernel-packages] [Bug 1909782] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448442/+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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0
[Kernel-packages] [Bug 1909782] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448443/+files/PulseList.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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0
[Kernel-packages] [Bug 1909782] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448446/+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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0
[Kernel-packages] [Bug 1909782] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448444/+files/RfKill.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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0
[Kernel-packages] [Bug 1909782] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448437/+files/PaInfo.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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0
[Kernel-packages] [Bug 1909782] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448438/+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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0
[Kernel-packages] [Bug 1909782] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448436/+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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0
[Kernel-packages] [Bug 1909782] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448435/+files/Lsusb-t.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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0
[Kernel-packages] [Bug 1909782] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448430/+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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x
[Kernel-packages] [Bug 1909782] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448432/+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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0x370 Dec 20
[Kernel-packages] [Bug 1909782] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448431/+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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0
[Kernel-packages] [Bug 1909782] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448434/+files/Lsusb.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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0x370 Dec 20
[Kernel-packages] [Bug 1909782] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448429/+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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0x370 Dec 20
[Kernel-packages] [Bug 1909782] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1909782/+attachment/5448433/+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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ]---- Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 000003ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS:0000 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 000006e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0
[Kernel-packages] [Bug 1909782] Re: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2, 1
apport information ** Tags added: apport-collected ** Description changed: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ] Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 03ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 06e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0x370 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400300] kthread+0x12f/0x150 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400305] ? process_one_work+0x3b0/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400309] ? __kthread_bind_mask+0x70/0x70 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400315] ret_from_fork+0x22/0x30 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400320
[Kernel-packages] [Bug 1909782] Re: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2, 1
** 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/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: New Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ] Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 03ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 06e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0x370 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400300] kthread+0x12f/0x150 Dec 20 09:08:40 ken-
[Kernel-packages] [Bug 1890641] Re: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
I am also affected by this bug, but I'm missing at least two firmware files, not just one. I'm missing rtl8168fp-3.fw and rtl8125a-3.fw, I had to download those two files manually -- 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/1890641 Title: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 Status in linux-firmware package in Ubuntu: Confirmed Bug description: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 after running sudo apt upgrade in ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 22:38:31 2020 InstallationDate: Installed on 2019-06-16 (417 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-03-08 22:54:00.439353 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1890641/+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 1501972] Re: nvidia kernel module failed to build [/bin/sh: 1: cc: not found]
"Fix: sudo apt install -y --reinstall gcc g++ gcc-7 g++-7" How on Earth is that a fix? Does an updated package do this for you? I'm doubting it very much. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1501972 Title: nvidia kernel module failed to build [/bin/sh: 1: cc: not found] Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-352 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-352-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I really have no idea of this issue, i just booted up and ubuntu notified me that there was a problem... hopefully ubuntu is self reporting enough information. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-346 346.96-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.19.0-30.33~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 DKMSKernelVersion: 3.13.0-65-generic Date: Thu Oct 1 18:17:00 2015 InstallationDate: Installed on 2015-09-25 (6 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageVersion: 346.96-0ubuntu0.0.1 RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: nvidia-graphics-drivers-346 Title: nvidia-346 346.96-0ubuntu0.0.1: nvidia-346 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.346.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1501972/+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 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]
I've also seen this with kernel 5.3.0-40-generic (Default with 19.10 and 18.04.04 LTS). Lenovo X1 with Intel i7-10710u and AC 9560 [2.861512] iwlwifi :00:14.3: enabling device ( -> 0002) [2.886678] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 [2.886992] iwlwifi :00:14.3: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm [2.957792] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, REV=0x354 [3.993914] iwlwifi :00:14.3: Collecting data: trigger 15 fired. [3.993992] iwlwifi :00:14.3: Start IWL Error Log Dump: [3.993994] iwlwifi :00:14.3: Status: 0x, count: -1882382615 [3.993995] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0 [3.993996] iwlwifi :00:14.3: 0xDBCE3CFD | ADVANCED_SYSASSERT [3.993997] iwlwifi :00:14.3: 0xBD97B500 | trm_hw_status0 [3.993998] iwlwifi :00:14.3: 0xD7117653 | trm_hw_status1 [3.993998] iwlwifi :00:14.3: 0xF5F2EB57 | branchlink2 [3.993999] iwlwifi :00:14.3: 0x9B39FEF9 | interruptlink1 [3.994000] iwlwifi :00:14.3: 0xB2A3CEE9 | interruptlink2 [3.994000] iwlwifi :00:14.3: 0xCA222955 | data1 [3.994001] iwlwifi :00:14.3: 0xF44FBCC7 | data2 [3.994002] iwlwifi :00:14.3: 0xEE8D27D9 | data3 [3.994002] iwlwifi :00:14.3: 0xAFC8456A | beacon time [3.994003] iwlwifi :00:14.3: 0x9AB5BE48 | tsf low [3.994004] iwlwifi :00:14.3: 0xF38BEF03 | tsf hi [3.994004] iwlwifi :00:14.3: 0x39BDB17C | time gp1 [3.994005] iwlwifi :00:14.3: 0xC1A8E7FD | time gp2 [3.994005] iwlwifi :00:14.3: 0x4D1F50A7 | uCode revision type [3.994006] iwlwifi :00:14.3: 0x73AEC515 | uCode version major [3.994007] iwlwifi :00:14.3: 0x1CE1133D | uCode version minor [3.994007] iwlwifi :00:14.3: 0x7BC1ED24 | hw version [3.994008] iwlwifi :00:14.3: 0x79824309 | board version [3.994009] iwlwifi :00:14.3: 0xC1BFAA89 | hcmd [3.994009] iwlwifi :00:14.3: 0xADE45947 | isr0 [3.994010] iwlwifi :00:14.3: 0xA25E02D6 | isr1 [3.994010] iwlwifi :00:14.3: 0x833363D2 | isr2 [3.994011] iwlwifi :00:14.3: 0x1AC562DF | isr3 [3.994012] iwlwifi :00:14.3: 0xE80F3DF6 | isr4 [3.994012] iwlwifi :00:14.3: 0xE602AE3E | last cmd Id [3.994013] iwlwifi :00:14.3: 0xC2989879 | wait_event [3.994014] iwlwifi :00:14.3: 0x43276623 | l2p_control [3.994014] iwlwifi :00:14.3: 0xF885020C | l2p_duration [3.994015] iwlwifi :00:14.3: 0x80B661F2 | l2p_mhvalid [3.994015] iwlwifi :00:14.3: 0x95039050 | l2p_addr_match [3.994016] iwlwifi :00:14.3: 0x16C3FB52 | lmpm_pmg_sel [3.994017] iwlwifi :00:14.3: 0x786AD9A2 | timestamp [3.994017] iwlwifi :00:14.3: 0xFEB64616 | flow_handler [3.994051] iwlwifi :00:14.3: Start IWL Error Log Dump: [3.994052] iwlwifi :00:14.3: Status: 0x, count: 7 [3.994053] iwlwifi :00:14.3: 0x201013F1 | ADVANCED_SYSASSERT [3.994053] iwlwifi :00:14.3: 0x | umac branchlink1 [3.994054] iwlwifi :00:14.3: 0xC008CF5C | umac branchlink2 [3.994055] iwlwifi :00:14.3: 0x | umac interruptlink1 [3.994055] iwlwifi :00:14.3: 0x | umac interruptlink2 [3.994056] iwlwifi :00:14.3: 0x0003 | umac data1 [3.994056] iwlwifi :00:14.3: 0x2302 | umac data2 [3.994057] iwlwifi :00:14.3: 0x01300202 | umac data3 [3.994058] iwlwifi :00:14.3: 0x0030 | umac major [3.994058] iwlwifi :00:14.3: 0x4FA0041F | umac minor [3.994059] iwlwifi :00:14.3: 0x5D0F | frame pointer [3.994060] iwlwifi :00:14.3: 0xC0887F58 | stack pointer [3.994060] iwlwifi :00:14.3: 0x | last host cmd [3.994061] iwlwifi :00:14.3: 0x | isr status reg [3.994079] iwlwifi :00:14.3: Fseq Registers: [3.994082] iwlwifi :00:14.3: 0x0003 | FSEQ_ERROR_CODE [3.994084] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION [3.994086] iwlwifi :00:14.3: 0x2DE993BB | FSEQ_CNVIO_INIT_VERSION [3.994088] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION [3.994090] iwlwifi :00:14.3: 0x51BA0460 | FSEQ_TOP_CONTENT_VERSION [3.994093] iwlwifi :00:14.3: 0x0140B0CE | FSEQ_ALIVE_TOKEN [3.994095] iwlwifi :00:14.3: 0xF7FBE573 | FSEQ_CNVI_ID [3.994097] iwlwifi :00:14.3: 0x601005B0 | FSEQ_CNVR_ID [3.994099] iwlwifi :00:14.3: 0x2302 | CNVI_AUX_MISC_CHIP [3.994104] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP [3.994108] iwlwifi :00:14.3: 0x485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [3.994142] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [3.994171] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c6f, CPU2 Status: 0x3 [3.994172] iwlwifi :00:14.3: Failed to start RT ucode: -110 [3.994174] iwlwifi :00:14.3: Firmware
[Kernel-packages] [Bug 1854827] Re: stuck when a device connected
Thank you for the information. But I gave the device away and I can't try it. -- 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/1854827 Title: stuck when a device connected Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: - Login Ubuntu - Connect to PowerdUSB of ThinkPad USB-C Dock Expected: Window manager responds mouse moves ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ken1252 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 3 01:09:07 2019 InstallationDate: Installed on 2019-04-27 (219 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20N8CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=2bbcdfff-f6a0-4ce7-8329-00d9eac16f29 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-28 (4 days ago) dmi.bios.date: 01/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET27W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET27W(1.10):bd01/22/2019:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854827/+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 1851162] Re: nvidia-drivers-390 fail to build with kernel 5.3
All good here too with 390.116-0ubuntu0.18.04.3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1851162 Title: nvidia-drivers-390 fail to build with kernel 5.3 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe source package in Bionic: Confirmed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Bug description: nvidia-graphics-drivers-390 fails to build against linux 5.3. SRU Request: [Test Case] 1) Enable the -proposed repository, and install the new 390 NVIDIA driver (nvidia-graphics-drivers-390_390.116-0ubuntu0.18.04.2). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update only fixes build issues with Linux versions 5.3. __ With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851162/+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 1851162] Re: nvidia-drivers-390 fail to build with kernel 5.3
Updated Bionic with all the latest packages before adding -proposed. Building module: cleaning build area... unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=5.3.0-26-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/5.3.0-26-generic/build LD=/usr/bin/ld.bfd modules..(bad exit status: 2) Error! Bad return status for module build on kernel: 5.3.0-26-generic (x86_64) Consult /var/lib/dkms/nvidia/390.116/build/make.log for more information. ...done. It seems to try twice during the update: Building module: cleaning build area... unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=5.3.0-26-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/5.3.0-26-generic/build LD=/usr/bin/ld.bfd modules..(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-kernel-source-390.0.crash' Error! Bad return status for module build on kernel: 5.3.0-26-generic (x86_64) Consult /var/lib/dkms/nvidia/390.116/build/make.log for more information. ...done. Build log attached. ** Attachment added: "/var/lib/dkms/nvidia/390.116/build/make.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+attachment/5322038/+files/make.log ** Tags removed: verification-needed-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1851162 Title: nvidia-drivers-390 fail to build with kernel 5.3 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux-hwe source package in Bionic: New Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Bug description: nvidia-graphics-drivers-390 fails to build against linux 5.3. SRU Request: [Test Case] 1) Enable the -proposed repository, and install the new 390 NVIDIA driver (nvidia-graphics-drivers-390_390.116-0ubuntu0.18.04.2). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update only fixes build issues with Linux versions 5.3. __ With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851162/+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 1843385] Re: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
Probably the same as Bug #1851162 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1843385 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Just upgraded the distro to 19.10 (dev) ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 (not installed) ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Tue Sep 10 08:08:26 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2016-02-03 (1314 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.3 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-09-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1843385/+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 1853196] Re: nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed to build
*** This bug is a duplicate of bug 1851162 *** https://bugs.launchpad.net/bugs/1851162 ** This bug has been marked a duplicate of bug 1851162 nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1853196 Title: nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: i tried to install nvidia drivers from this link https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-19-10-eoan-ermine-linux . My video card is nvdia Gforce GT610. Sometimes on boot there is pixel "scratches" (on the pink screen). ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-kernel-source-390 390.129-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 DKMSKernelVersion: 5.3.0-23-generic Date: Tue Nov 19 22:29:16 2019 Dependencies: PackageVersion: 390.129-0ubuntu2 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1853196/+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 1844613] Re: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 1851162 *** https://bugs.launchpad.net/bugs/1851162 ** This bug has been marked a duplicate of bug 1851162 nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1844613 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: each time the pc starts, the error message is shown, but if i close that i can work w/o any problem ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 390.129-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Tue Sep 17 23:42:51 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-02-09 (587 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.3 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-09-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1844613/+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 1846995] Re: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
Did you build a custom kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1846995 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Doing a do-release-upgrade -d from 19.04 to 19.10. The upgrade crashed out part way through, automatically reporting this bug. update-initramfs: Generating /boot/initrd.img-5.3.0-13-generic Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.39.2-3) ... Processing triggers for libc-bin (2.30-0ubuntu2) ... Processing triggers for menu (2.1.47ubuntu3) ... Errors were encountered while processing: nvidia-dkms-390 nvidia-driver-390 Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (624.7 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 390.129-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Oct 7 01:17:46 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-04-23 (531 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-10-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1846995/+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 1857378] Re: Please drop i386 dkms package, as there are no i386 kernel
Or don't. https://discourse.ubuntu.com/t/intel-32bit-packages-on-ubuntu-from-19-10-onwards/11263/90 ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1857378 Title: Please drop i386 dkms package, as there are no i386 kernel Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: Please drop i386 dkms package, as there are no i386 kernel Systems should enable amd64 archive and install amd64 kernel & the amd64 dkms package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1857378/+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 1851162] Re: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19
The HWE package now force-upgrades to 5.3.0, rendering that entire package useless. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1851162 Title: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+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 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
Nilesh's fix worked for me thanks ... Ubuntu 16.04 Dell Inspiron 15 3000 series kernel 4.15.0-72-generic -- 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/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263): "/dev/input/event5" # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
[Kernel-packages] [Bug 1854827] Re: stuck when a device connected
$ dmesg -w > dmesg.log How can I help with this? ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854827/+attachment/5309397/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854827 Title: stuck when a device connected Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: - Login Ubuntu - Connect to PowerdUSB of ThinkPad USB-C Dock Expected: Window manager responds mouse moves ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ken1252 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 3 01:09:07 2019 InstallationDate: Installed on 2019-04-27 (219 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20N8CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=2bbcdfff-f6a0-4ce7-8329-00d9eac16f29 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-28 (4 days ago) dmi.bios.date: 01/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET27W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET27W(1.10):bd01/22/2019:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854827/+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 1854827] [NEW] stuck when a device connected
Public bug reported: Steps to reproduce: - Login Ubuntu - Connect to PowerdUSB of ThinkPad USB-C Dock Expected: Window manager responds mouse moves ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ken1252 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 3 01:09:07 2019 InstallationDate: Installed on 2019-04-27 (219 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20N8CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=2bbcdfff-f6a0-4ce7-8329-00d9eac16f29 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-28 (4 days ago) dmi.bios.date: 01/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET27W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET27W(1.10):bd01/22/2019:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan -- 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/1854827 Title: stuck when a device connected Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: - Login Ubuntu - Connect to PowerdUSB of ThinkPad USB-C Dock Expected: Window manager responds mouse moves ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ken1252 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 3 01:09:07 2019 InstallationDate: Installed on 2019-04-27 (219 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20N8CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=2bbcdfff-f6a0-4ce7-8329-00d9eac16f29 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-28 (4 days ago) dmi.bios.date: 01/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET27W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET27W(1.10):bd01/22/2019:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854827/+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 1854827] Re: stuck when a device connected
It seems that the CurrentDmesg.txt is not sufficient because the problem happened before reboot. -- 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/1854827 Title: stuck when a device connected Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: - Login Ubuntu - Connect to PowerdUSB of ThinkPad USB-C Dock Expected: Window manager responds mouse moves ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ken1252 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 3 01:09:07 2019 InstallationDate: Installed on 2019-04-27 (219 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20N8CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=2bbcdfff-f6a0-4ce7-8329-00d9eac16f29 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-28 (4 days ago) dmi.bios.date: 01/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET27W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N8CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET27W(1.10):bd01/22/2019:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E490 dmi.product.name: 20N8CTO1WW dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490 dmi.product.version: ThinkPad E490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854827/+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 1851162] Re: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19
Build log attached. ** Attachment added: "DKMS build log" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+attachment/5302550/+files/make.log ** Description changed: - With linux-image-5.0.0-23 I had no problems. Following an update 5.3.0 - was installed, the DKMS failed, and the system became unusable. + With linux-image-5.0.0-23 I had no problems. Following an update linux- + image-5.3.0-19 was installed, the DKMS build failed, and the system + became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1851162 Title: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+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 1851162] [NEW] nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19
Public bug reported: With linux-image-5.0.0-23 I had no problems. Following an update linux- image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1851162 Title: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+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 1804040] Re: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build [ERROR: Kernel configuration is invalid.]
I've marked this as affecting me but I've just realised that I'm using a different kernel. In my case 5.0.x works fine, 5.3.0 fails in (apparently) the same way: DKMS make.log for nvidia-390.116 for kernel 5.3.0-19-generic (x86_64) Sun 3 Nov 19:50:42 GMT 2019 make[1]: Entering directory '/usr/src/linux-headers-5.3.0-19-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1804040 Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build [ERROR: Kernel configuration is invalid.] Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: failed to update my system ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-dkms-390 390.77-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 DKMSKernelVersion: 4.15.0-39-generic Date: Mon Nov 19 23:00:47 2018 InstallationDate: Installed on 2018-09-16 (64 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageVersion: 390.77-0ubuntu0.18.04.1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1804040/+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 1848790] Re: USB not working under arm64 on Pi4
fixed links User on lingon on raspberry pi forum posted the following: The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the issue seen earlier that using more RAM than 3072 MB breaks the USB: [url]https://www.raspberrypi.org/forums/viewtopic.php?f=63=246766=25[/url] The issue was solved by a kernel patch: [url]https://www.raspberrypi.org/forums/viewtopic.php?f=63=246766=50#p1517839[/url] and the kernel patch was this one: [url]https://github.com/raspberrypi/linux/issues/3093#issuecomment-520269280[/url] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1848790] Re: USB not working under arm64 on Pi4
Fixed links User on lingon on raspberry pi forum posted the following: The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the issue seen earlier that using more RAM than 3072 MB breaks the USB: [url]https://www.raspberrypi.org/forums/viewtopic.php?f=63=246766=25[/url] The issue was solved by a kernel patch: [url]https://www.raspberrypi.org/forums/viewtopic.php?f=63=246766=50#p1517839[/url] and the kernel patch was this one: [url]https://github.com/raspberrypi/linux/issues/3093#issuecomment-520269280[/url] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1848790] Re: USB not working under arm64 on Pi4
fixed links User on lingon on raspberry pi forum posted the following: The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the issue seen earlier that using more RAM than 3072 MB breaks the USB: https://www.raspberrypi.org/forums/v...46766=25 The issue was solved by a kernel patch: https://www.raspberrypi.org/forums/v...rt=50#p1517839 and the kernel patch was this one: https://github.com/raspberrypi/linux...ment-520269280 ** Bug watch added: github.com/raspberrypi/linux/issues #3093 https://github.com/raspberrypi/linux/issues/3093 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1848790] Re: USB not working under arm64 on Pi4
User on lingon on raspberry pi forum posted the following: The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the issue seen earlier that using more RAM than 3072 MB breaks the USB: https://www.raspberrypi.org/forums/view ... 6=25 The issue was solved by a kernel patch: https://www.raspberrypi.org/forums/view ... 0#p1517839 and the kernel patch was this one: https://github.com/raspberrypi/linux/is ... -520269280 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1827822] Re: kernel null pointer dereference
;48> 89 42 08 48 89 10 48 b8 00 01 00 00 00 00 ad de 48 89 47 d8 May 5 18:06:03 corbin-goul kernel: [ 4650.769909] RIP: rm_hole+0x19/0x70 [drm] RSP: 95fb81f2bd20 May 5 18:06:03 corbin-goul kernel: [ 4650.769910] CR2: 0008 May 5 18:06:03 corbin-goul kernel: [ 4650.769912] ---[ end trace 4488bf4278af9827 ]--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ken2604 F pulseaudio /dev/snd/controlC1: ken2604 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 5 18:18:41 2019 HibernationDevice: RESUME=UUID=d9769aee-0f6e-4d98-8376-a6ba3aa6edf8 InstallationDate: Installed on 2018-10-18 (199 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H87M-D3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=/dev/mapper/system-Ubuntu--18.04.1 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.5 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/24/2013:svnGigabyteTechnologyCo.,Ltd.:pnH87M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H87M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827822/+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 1817225] Re: 18.04.2 breaks xrdp
Confirmed this works in the Hyper-V 18.04 desktop image. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done 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/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xrdp-hwe-18.04 package in Ubuntu: Fix Committed Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+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 1817225] Re: 18.04.2 breaks xrdp
** Changed in: xrdp (Ubuntu) Importance: Undecided => High ** Changed in: xrdp (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xrdp package in Ubuntu: In Progress Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+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 1817225] Re: 18.04.2 breaks xrdp
Confirmed, your staging PPA fixes it for our Hyper-V image -- 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/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xrdp package in Ubuntu: Incomplete Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+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 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
This patch was reverted about a month ago, and made its way into the 5.1 kernel recently. The issue now showing up on my Dell Latitude 7400. -- 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/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: === SRU Justification === [Impact] [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) [Fix] Let HID core allow longer input report length. [Test] User confirmed the fix works. [Regression Potential] Low. Longer input report length is now considered valid, shorter input report length doesn't get touched. === Original Bug Report === Dmesg is a constant barrage of the same error: ``` [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) ``` This does not occur in 4.19 but does occur in all mainline 4.20 releases including 4.20.13 (linux-image-unsigned-4.20.13-042013). Tested with both Ubuntu's included libinput 1.10 and an updated libinput 1.12. Hardware (from lspci) includes a synaptic touchpad. Having the xorg synaptic driver installed makes no difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+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
