[Kernel-packages] [Bug 1788321] Re: swapon failed: invalid argument
Good News! This bug is still here. Same error on Dell Inspiron 13-7353, Ubuntu 20.04.1 (Upgraded from 18.05.5), Kernel: Linux NOMIS-inspiron 5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Filesystem btrfs, Storage: Samsung 650 SSD (1TB). Was working properly on 18.04, and 20.04.1 on earlier kernels. I did not try late kernels. It seems like I have the worst combination of configuration but innocently walked into this . I reduced vm.swapiness to ZERO. in the hope I will encouner fewer crashes. Please advise. Thanx. -- 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/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+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 1895502] [NEW] nouveau keeps crashing in nvkm_pmu_init
You have been subscribed to a public bug: screen brightness automatically gets full even if I reduce it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 14 09:59:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3963] Subsystem: Lenovo GP108M [GeForce MX150] [17aa:3963] InstallationDate: Installed on 2019-01-10 (612 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:241a Syntek Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=b5321cab-9053-41be-abdd-7ac822fa43b9 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- nouveau keeps crashing in nvkm_pmu_init https://bugs.launchpad.net/bugs/1895502 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895434] Re: Display corruption after suspend with recent kernel update
Same problem after resuming from hibernation or suspend. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895434 Title: Display corruption after suspend with recent kernel update Status in linux package in Ubuntu: Confirmed Bug description: For the last few days, after suspending and resuming, I get display corruption in Google Chrome. Parts of the UI are replaces with black boxes. Resizing the window causes it to redraw but if I switch back to the original size then it goes back to black. I noticed it on 5.4.0-47 and backed down to 5.4.0-45 but still see the same. Looks like 5.4.0-45 was only released a few days before 5.4.0-47 so maybe I didn't reboot in that time. Those are the only upgrades I can see in the right timeframe. I had a look in dmesg and saw some warnings; not sure if they're related: [ 59.251347] [ cut here ] [ 59.251357] WARNING: CPU: 6 PID: 4533 at drivers/media/v4l2-core/v4l2-ioctl.c:1069 v4l_querycap+0x8f/0xa0 [videodev] [ 59.251358] Modules linked in: msr nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter rfcomm ccm typec_displayport cmac algif_hash algif_skcipher af_alg xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc aufs overlay bnep binfmt_misc nls_iso8859_1 btusb btrtl btbcm btintel snd_usb_audio bluetooth snd_usbmidi_lib ecdh_generic ecc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common dell_rbtn snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp mei_hdcp snd_hda_ext_core snd_hda_codec_hdmi snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_msr snd_soc_core snd_compress ac97_bus snd_hda_codec_realtek snd_pcm_dmaengine x86_pkg_temp_thermal intel_powerclamp [ 59.251391] snd_hda_codec_generic coretemp snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm dell_laptop ledtrig_audio snd_seq_midi snd_seq_midi_event kvm_intel kvm iwlmvm snd_rawmidi rapl mac80211 snd_seq dell_wmi dell_smbios input_leds dcdbas intel_cstate libarc4 snd_seq_device serio_raw snd_timer iwlwifi snd dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof rtsx_pci_ms mxm_wmi cfg80211 memstick soundcore mei_me hid_multitouch mei joydev processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal ucsi_acpi typec_ucsi typec int3403_thermal int340x_thermal_zone dell_smo8800 intel_hid int3400_thermal acpi_thermal_rel mac_hid acpi_pad sparse_keymap nvidia_uvm(OE) sch_fq_codel v4l2loopback(OE) videodev mc dell_smm_hwmon parport_pc nfsd ppdev auth_rpcgss nfs_acl lockd lp parport grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c [ 59.251428] raid1 raid0 multipath linear wacom usbhid hid_generic nvidia_drm(POE) nvidia_modeset(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) rtsx_pci_sdmmc i915 aesni_intel crypto_simd cryptd i2c_algo_bit glue_helper drm_kms_helper nvme syscopyarea sysfillrect sysimgblt fb_sys_fops nvme_core i2c_i801 rtsx_pci intel_lpss_pci drm ahci intel_lpss ipmi_devintf idma64 libahci ipmi_msghandler virt_dma i2c_hid hid video pinctrl_cannonlake wmi pinctrl_intel [ 59.251451] CPU: 6 PID: 4533 Comm: chrome Tainted: P U W OE 5.4.0-45-generic #49-Ubuntu [ 59.251452] Hardware name: Dell Inc. Precision 5530/0FP2W2, BIOS 1.15.0 12/25/2019 [ 59.251460] RIP: 0010:v4l_querycap+0x8f/0xa0 [videodev] [ 59.251462] Code: 00 00 80 48 b9 00 00 20 00 00 00 20 00 48 0b 4b 54 21 d6 39 f2 75 13 48 89 4b 54 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b eb d0 <0f> 0b 48 89 4b 54 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 1f 44 00 00 [ 59.251464] RSP: 0018:b367c518fc70 EFLAGS: 00010202 [ 59.251466] RAX: RBX: b367c518fd88 RCX: 8520800285208002 [ 59.251467] RDX: 85008003 RSI: 85008002 RDI: [ 59.251469] RBP: b367c518fc98 R08: R09: 000a [ 59.251470] R10: R11: R12: 995c57b5e000 [ 59.251471] R13: 995c4b2ff600 R14: 995b6de87980 R15: c04dc380 [ 59.251474] FS: 7fab7ada6340() GS:995c5c38() knlGS: [ 59.251475] CS: 0010 DS: ES: CR0: 80050033 [ 59.251477] CR2: 2f5a17d09008 CR3: 000717140001 CR4: 003606e0 [ 59.251478] DR0: DR1: DR2: [ 59.251479] DR3: DR6: fffe0ff0 DR7
[Kernel-packages] [Bug 1895502] Re: the screen is hanging frequently and i am unable to perform any typing work on the screen due to the huge delay between my typing and characters appearing on the sc
You seem to be experiencing recurring kernel crashes in the 'nouveau' driver. Rather than waiting for a fix I suggest just installing the proprietary Nvidia driver from the 'Additional Drivers' app. ** Summary changed: - the screen is hanging frequently and i am unable to perform any typing work on the screen due to the huge delay between my typing and characters appearing on the screen + nouveau keeps crashing in nvkm_pmu_init ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: nouveau -- 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/1895502 Title: nouveau keeps crashing in nvkm_pmu_init Status in linux package in Ubuntu: New Bug description: screen brightness automatically gets full even if I reduce it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 14 09:59:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3963] Subsystem: Lenovo GP108M [GeForce MX150] [17aa:3963] InstallationDate: Installed on 2019-01-10 (612 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:241a Syntek Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=b5321cab-9053-41be-abdd-7ac822fa43b9 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895502/+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 1812824] Re: Multiple TRACE_syscall related failures in seccomp test from ubuntu_kernel_selftests found on B s390x
Didn't see this on B-s390x (LPAR / zVM) Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Bionic) 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/1812824 Title: Multiple TRACE_syscall related failures in seccomp test from ubuntu_kernel_selftests found on B s390x Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: There are multiple failures related to the TRACE_SYSCALL: [ FAIL ] TRACE_syscall.skip_after_RET_TRACE [ FAIL ] TRACE_syscall.kill_after_RET_TRACE [ FAIL ] TRACE_syscall.skip_after_ptrace [ FAIL ] TRACE_syscall.kill_after_ptrace TRACE_syscall.ptrace_syscall_dropped: Test failed at step #223 TRACE_syscall.syscall_dropped: Test failed at step #2 seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(20) (9627) seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12 TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 0) seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(20) (9627) seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_ptrace: Test failed at step #15 TAP version 13 selftests: seccomp_bpf seccomp_bpf.c:608:global.KILL_one_arg_six:Expected ((void *) -1) (18446744073709551615) != map1 (18446744073709551615) [==] Running 64 tests from 1 test cases. [ RUN ] global.mode_strict_support [ OK ] global.mode_strict_support [ RUN ] global.mode_strict_cannot_call_prctl [ OK ] global.mode_strict_cannot_call_prctl [ RUN ] global.no_new_privs_support [ OK ] global.no_new_privs_support [ RUN ] global.mode_filter_support [ OK ] global.mode_filter_support [ RUN ] global.mode_filter_without_nnp [ OK ] global.mode_filter_without_nnp [ RUN ] global.filter_size_limits [ OK ] global.filter_size_limits [ RUN ] global.filter_chain_limits [ OK ] global.filter_chain_limits [ RUN ] global.mode_filter_cannot_move_to_strict [ OK ] global.mode_filter_cannot_move_to_strict [ RUN ] global.mode_filter_get_seccomp [ OK ] global.mode_filter_get_seccomp [ RUN ] global.ALLOW_all [ OK ] global.ALLOW_all [ RUN ] global.empty_prog [ OK ] global.empty_prog [ RUN ] global.log_all [ OK ] global.log_all [ RUN ] global.unknown_ret_is_kill_inside [ OK ] global.unknown_ret_is_kill_inside [ RUN ] global.unknown_ret_is_kill_above_allow [ OK ] global.unknown_ret_is_kill_above_allow [ RUN ] global.KILL_all [ OK ] global.KILL_all [ RUN ] global.KILL_one [ OK ] global.KILL_one [ RUN ] global.KILL_one_arg_one [ OK ] global.KILL_one_arg_one [ RUN ] global.KILL_one_arg_six [ OK ] global.KILL_one_arg_six [ RUN ] global.KILL_thread TRACE_syscall.ptrace_syscall_dropped: Test failed at step #223 TRACE_syscall.syscall_dropped: Test failed at step #2 seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(20) (9627) seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12 TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 0) seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(20) (9627) seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_ptrace: Test failed at step #15 [==] Running 64 tests from 1 test cases. [ RUN ] global.mode_strict_support [ OK ] global.mode_strict_support [ RUN ] global.mode_strict_cannot_call_prctl [ OK ] global.mode_strict_cannot_call_prctl [ RUN ] global.no_new_privs_support [ OK ] global.no_new_privs_support [ RUN ] global.mode_filter_support [ OK ] global.mode_filter_support [ RUN ] global.mode_filter_without_nnp [ OK ] global.mode_filter_without_nnp [ RUN ] global.filter_size_limits [ OK ] global.filter_size_limits [ RUN ] global.filter_chain_limits [ OK ] global.filter_chain_limits [ RUN ] global.mode_filter_cannot_move_to_strict [ OK ] global.mode_filter_cannot_move_to_strict [ RUN ] global.mode_filter_get_seccomp [ OK ] global.mode_filter_get_seccomp [ RUN ] global.ALLOW_all [ OK ] global.ALLOW_all [ RUN ] global.empty_prog [ OK ]
[Kernel-packages] [Bug 1812843] Re: reuseport_dualstack in net from ubuntu_kernel_selftests failed on s390x
Didn't see this with Bionic / Focal s390x LPAR and zVM. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu Cosmic) 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/1812843 Title: reuseport_dualstack in net from ubuntu_kernel_selftests failed on s390x Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: Won't Fix Bug description: This failure was only spotted on Bionic s390x, passed on other arches. $ sudo ./reuseport_dualstack UDP IPv4 created before IPv6 ./reuseport_dualstack: expected to receive on v4 socket but got v6 (1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Jan 22 11:22:40 2019 HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812843/+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 1895502] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895502 Title: nouveau keeps crashing in nvkm_pmu_init Status in linux package in Ubuntu: Confirmed Bug description: screen brightness automatically gets full even if I reduce it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 14 09:59:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3963] Subsystem: Lenovo GP108M [GeForce MX150] [17aa:3963] InstallationDate: Installed on 2019-01-10 (612 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:241a Syntek Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=b5321cab-9053-41be-abdd-7ac822fa43b9 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895502/+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 1880508] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1880508 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Status in nvidia-graphics-drivers-440 source package in Focal: Confirmed Status in nvidia-graphics-drivers-340 source package in Groovy: Confirmed Status in nvidia-graphics-drivers-440 source package in Groovy: Confirmed Bug description: I can not connect my MackBook Pro to monitor and I need some feedback ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 08:10:28 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 InstallationDate: Installed on 2020-05-23 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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.3 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 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-340/+bug/1880508/+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 1880508] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1880508 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Status in nvidia-graphics-drivers-440 source package in Focal: Confirmed Status in nvidia-graphics-drivers-340 source package in Groovy: Confirmed Status in nvidia-graphics-drivers-440 source package in Groovy: Confirmed Bug description: I can not connect my MackBook Pro to monitor and I need some feedback ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 08:10:28 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 InstallationDate: Installed on 2020-05-23 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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.3 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 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-340/+bug/1880508/+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 1880508] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1880508 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Status in nvidia-graphics-drivers-440 source package in Focal: Confirmed Status in nvidia-graphics-drivers-340 source package in Groovy: Confirmed Status in nvidia-graphics-drivers-440 source package in Groovy: Confirmed Bug description: I can not connect my MackBook Pro to monitor and I need some feedback ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 08:10:28 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 InstallationDate: Installed on 2020-05-23 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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.3 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 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-340/+bug/1880508/+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 1883065] Re: Dell Latitude/Precision, sig=0x806ec/20090609: Linux hangs without plugged in power cable
** Tags added: oem-priority ** Also affects: oem-priority 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/1883065 Title: Dell Latitude/Precision, sig=0x806ec/20090609: Linux hangs without plugged in power cable Status in OEM Priority Project: New Status in intel-microcode package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Already present reported in project *dell-sputnik*. (Note, it happened here also without suspend/resume.): 1. https://bugs.launchpad.net/dell-sputnik/+bug/1661741 2. Quote from https://bugs.launchpad.net/dell-sputnik/+bug/1661741/comments/26: > A similar bug affects several Dell laptop models: > - Dell 5480/5488 : > https://bugs.launchpad.net/dell-sputnik/+bug/1866343 > - Dell E5470 : > https://bugs.launchpad.net/dell-sputnik/+bug/1661741 > (Note that the bug https://bugs.launchpad.net/dell-sputnik/+bug/1661741 is not fixed; it has been changed, by error, to fixed. Please, it will be nice if somebody can change the status to "confirmed") > - Dell 7740 : > https://bugs.launchpad.net/dell-sputnik/+bug/1871491 > > I suppose that the bug can also affect Dell precision 7730 After experiencing this already on the Dell Latitude 5480/5488 (https://bugs.launchpad.net/dell-sputnik/+bug/1866343), we have seen this now too with the Dell Precision 3540 (with dedicated AMD graphics card). Without the power cord plugged in, the system started fine, then updating packages, including the Linux kernel, turning the system off, and right back on, it went to GRUB, and GRUB was able to load Linux and initrd, and starting Linux it hung. Num lock key didn’t respond (but also didn’t blink – no idea if this should work), and Ctrl + Alt + Del didn’t work either. So, the system had to be powered off by pressing the power button for some (ten(?)) seconds. Subsequent tries didn’t help, until we remembered the issues with the other device, and plugging in the power cord fixed it. With the power cable unplugged, it didn’t boot. The state of the connected power cable only mattered, when starting the Linux kernel. That means, plugging it in, when GRUB was active, the system booted. Removing the cable, when GRUB was running, Linux hung. I tried to get Linux messages, but `debug nomodeset earlyprintk=efi` didn’t get Linux to output any messages. ### Workarounds ### I was able to get Linux booting by adding either one of the following Linux kernel parameters. 1. `maxcpus=1` (once it started with `maxcpus=2`) 2. `nosmp` 2. `acpi=off` 3. `nolapic` In this state, there was only one CPU online. Trying to bring one more online, the system always froze instantly. echo 1 | sudo tee /sys/devices/system/cpu/cpu1/online (Nothing in pstore either.) (Where maxcpus=2` worked, we were able to bring a third CPU online, but the system froze when trying the fourth.) ### Reproducibilty ### Letting the system sit over night, and trying again in the morning, unfortunately, we did *not* test without a power cable plugged in, as we had an idea to test the non-USB-Type-C power cable. With that the system started. Powering the system off, and unplugging the cable, the system booted without issues. So something changed. We weren’t able to get it into a state, where it doesn’t boot in the last hour, but we would like this investigated, as we are giving these systems to our users. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1883065/+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 1803179]
(In reply to Ranjith Hegde from comment #172) > New problems in an old thread > > After using @Matthias Fulz's method (bumblebee without bbswitch + pm with > powertop+tlp) its quite simple to run any software requiring nvidia. with > his patch. > > The problem is in preventing any other software from using nvidia when not > run with optirun/primusrun. For example, any software that calls for EGL > automatically turns on nvidia. Mpv is one of those. > > Is there any way to ensure EGL calls intel instead? There is solution in > arch wiki with env-variable > "__EGL_VENDOR_LIBRARY_FILENAMES="/usr/share/glvnd/egl_vendor.d/50_mesa.json" > " > > but it does not work. I have tried adding it in all possible places > (/etc/environment, /etc/profile, bash-profile, zsh-profile-equivalent etc..) Hey, I was also struggling with those problems. What I do is that instead of removing the nvidia-audio from the PCIe Bus, I remove the nvidia card: % cat /usr/local/bin/remove_nvidia #!/usr/bin/bash echo 1 > /sys/bus/pci/devices/:01:00.1/remove echo 1 > /sys/bus/pci/devices/:01:00.0/remove I do this at boot via systemd. There is a post earlier that describes how to do it. You should also make sure that the nvidia modules are not loaded (should be taken care if you use bumblebee). In order to re-enable the nvidia card when you need it, use: % cat /usr/local/bin/add_nvidia #!/usr/bin/env bash echo 1 > /sys/bus/pci/rescan You can modify your bumbleebee/optimus/primus scripts accordingly. -- 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/1803179 Title: System does not reliably come out of suspend Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+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 1895520] [NEW] package linux-image-5.4.0-47-generic 5.4.0-47.51 failed to install/upgrade: installed linux-image-5.4.0-47-generic package pre-removal script subprocess returned
Public bug reported: I was installing the additional package of virtualbox as follows and an error has occurred. sudo apt -yV install virtualbox-guest-additions-iso virtualbox-guest- dkms-hwe virtualbox-guest-utils-hwe virtualbox-guest-x11-hwe ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core edac_mce_amd radeon wmi_bmof k10temp asus_atk0110 mac_hid hid_logitech_hidpp hid_logitech_dj r8169 pata_acpi pata_atiixp realtek i2c_piix4 pata_via wmi ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: takuya 1423 F pulseaudio /dev/snd/controlC1: takuya 1423 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip Date: Mon Sep 14 18:41:59 2020 ErrorMessage: installed linux-image-5.4.0-47-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-09-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 "Focal Fossa" - Release amd64(20200808.1) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=0fdd3258-4c08-4293-ac28-87a2a4169389 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. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.3 RfKill: SourcePackage: linux Title: package linux-image-5.4.0-47-generic 5.4.0-47.51 failed to install/upgrade: installed linux-image-5.4.0-47-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88TD-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895520 Title: package linux-image-5.4.0-47-generic 5.4.0-47.51 failed to install/upgrade: installed linux-image-5.4.0-47-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: I was installing the additional package of virtualbox as follows and an error has occurred. sudo apt -yV install virtualbox-guest-additions-iso virtualbox-guest- dkms-hwe virtualbox-guest-utils-hwe virtualbox-guest-x11-hwe ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core edac_mce_amd radeon wmi_bmof k10temp asus_atk0110 mac_hid hid_logitech_hidpp hid_logitech_dj r8169 pata_acpi pata_atiixp realtek i2c_piix4 pata_via wmi ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: takuya 1423 F pulseaudio /dev/snd/controlC1: takuya 1423 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip Date: Mon Sep 14 18:41:59 2020 ErrorMessage: installed linux-image-5.4.0-47-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-09-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 "Focal Fossa" - Release amd64(20200808.
[Kernel-packages] [Bug 1799184] Re: [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding
** Tags added: ssc
--
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/1799184
Title:
[18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic
driver binding
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
APQN tags in the zcrypt device driver are required to support
deterministic driver binding
With the introduction of KVM hw crypto virtualization (on s390x) the driver
bound to an AP queue device is no longer unique determined.
Therefore a deterministic hot plugging semantics of AP queues that may be
bound to multiple drivers is needed.
With the three listed commits here it will be possible to configure an AP
queue (APQN) as being bound to a particular driver even if the associate hw
gets intermittently lost and reconnected.
== Fixes ==
ac2b96f351d7d222 ("s390/zcrypt: code beautify")
7e0bdbe5c21cb831 ("s390/zcrypt: AP bus support for alternate driver(s)")
3d8f60d38e249f98 ("s390/zcrypt: hex string mask improvements for apmask and
aqmask")
== Patches ==
Git-commit: ac2b96f351d7d222
https://github.com/torvalds/linux/commit/ac2b96f351d7d222c46e524feca03005f3fa8d75
Author: Harald Freudenberger
Date: Fri Aug 17 12:36:01 2018 +0200
s390/zcrypt: code beautify
Code beautify by following most of the checkpatch suggestions:
- SPDX license identifier line complains by checkpatch
- missing space or newline complains by checkpatch
- octal numbers for permssions complains by checkpatch
- renaming of static sysfs functions complains by checkpatch
- fix of block comment complains by checkpatch
- fix printf like calls where function name instead of %s __func__
was used
- __packed instead of __attribute__((packed))
- init to zero for static variables removed
- use of DEVICE_ATTR_RO and DEVICE_ATTR_RW macros
No functional code changes or API changes!
Signed-off-by: Harald Freudenberger
Signed-off-by: Martin Schwidefsky
===
Git-commit 7e0bdbe5c21cb831
https://github.com/torvalds/linux/commit/7e0bdbe5c21cb8316a694e46ad5aad339f6894a6
Author: Harald Freudenberger
Date: Fri Jul 20 08:36:53 2018 +0200
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_
[Kernel-packages] [Bug 1895434] Re: Display corruption after suspend with recent kernel update
Tried baking down to kernel -42, which is much older but I'm still seeing the problem. Maybe the issue is not with the kernel, it just happened to occur at the same time :-( -- 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/1895434 Title: Display corruption after suspend with recent kernel update Status in linux package in Ubuntu: Confirmed Bug description: For the last few days, after suspending and resuming, I get display corruption in Google Chrome. Parts of the UI are replaces with black boxes. Resizing the window causes it to redraw but if I switch back to the original size then it goes back to black. I noticed it on 5.4.0-47 and backed down to 5.4.0-45 but still see the same. Looks like 5.4.0-45 was only released a few days before 5.4.0-47 so maybe I didn't reboot in that time. Those are the only upgrades I can see in the right timeframe. I had a look in dmesg and saw some warnings; not sure if they're related: [ 59.251347] [ cut here ] [ 59.251357] WARNING: CPU: 6 PID: 4533 at drivers/media/v4l2-core/v4l2-ioctl.c:1069 v4l_querycap+0x8f/0xa0 [videodev] [ 59.251358] Modules linked in: msr nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter rfcomm ccm typec_displayport cmac algif_hash algif_skcipher af_alg xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc aufs overlay bnep binfmt_misc nls_iso8859_1 btusb btrtl btbcm btintel snd_usb_audio bluetooth snd_usbmidi_lib ecdh_generic ecc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common dell_rbtn snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp mei_hdcp snd_hda_ext_core snd_hda_codec_hdmi snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_msr snd_soc_core snd_compress ac97_bus snd_hda_codec_realtek snd_pcm_dmaengine x86_pkg_temp_thermal intel_powerclamp [ 59.251391] snd_hda_codec_generic coretemp snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm dell_laptop ledtrig_audio snd_seq_midi snd_seq_midi_event kvm_intel kvm iwlmvm snd_rawmidi rapl mac80211 snd_seq dell_wmi dell_smbios input_leds dcdbas intel_cstate libarc4 snd_seq_device serio_raw snd_timer iwlwifi snd dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof rtsx_pci_ms mxm_wmi cfg80211 memstick soundcore mei_me hid_multitouch mei joydev processor_thermal_device intel_rapl_common intel_soc_dts_iosf intel_pch_thermal ucsi_acpi typec_ucsi typec int3403_thermal int340x_thermal_zone dell_smo8800 intel_hid int3400_thermal acpi_thermal_rel mac_hid acpi_pad sparse_keymap nvidia_uvm(OE) sch_fq_codel v4l2loopback(OE) videodev mc dell_smm_hwmon parport_pc nfsd ppdev auth_rpcgss nfs_acl lockd lp parport grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c [ 59.251428] raid1 raid0 multipath linear wacom usbhid hid_generic nvidia_drm(POE) nvidia_modeset(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) rtsx_pci_sdmmc i915 aesni_intel crypto_simd cryptd i2c_algo_bit glue_helper drm_kms_helper nvme syscopyarea sysfillrect sysimgblt fb_sys_fops nvme_core i2c_i801 rtsx_pci intel_lpss_pci drm ahci intel_lpss ipmi_devintf idma64 libahci ipmi_msghandler virt_dma i2c_hid hid video pinctrl_cannonlake wmi pinctrl_intel [ 59.251451] CPU: 6 PID: 4533 Comm: chrome Tainted: P U W OE 5.4.0-45-generic #49-Ubuntu [ 59.251452] Hardware name: Dell Inc. Precision 5530/0FP2W2, BIOS 1.15.0 12/25/2019 [ 59.251460] RIP: 0010:v4l_querycap+0x8f/0xa0 [videodev] [ 59.251462] Code: 00 00 80 48 b9 00 00 20 00 00 00 20 00 48 0b 4b 54 21 d6 39 f2 75 13 48 89 4b 54 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b eb d0 <0f> 0b 48 89 4b 54 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 1f 44 00 00 [ 59.251464] RSP: 0018:b367c518fc70 EFLAGS: 00010202 [ 59.251466] RAX: RBX: b367c518fd88 RCX: 8520800285208002 [ 59.251467] RDX: 85008003 RSI: 85008002 RDI: [ 59.251469] RBP: b367c518fc98 R08: R09: 000a [ 59.251470] R10: R11: R12: 995c57b5e000 [ 59.251471] R13: 995c4b2ff600 R14: 995b6de87980 R15: c04dc380 [ 59.251474] FS: 7fab7ada6340() GS:995c5c38() knlGS: [ 59.251475] CS: 0010 DS: ES: CR0: 80050033 [ 59.251477] CR2: 2f5a17d09008 CR3: 000717140001 CR4: 003606e0 [ 59.251478] DR0:
[Kernel-packages] [Bug 1836701] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1836701
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: 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/1836701
Title:
ubuntu18.04: ipmitool failed: Could not open device at /dev/ipmi0 : No
such file or directory
Status in ipmitool package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Incomplete
Bug description:
ipmitool failed in-band
#ipmitool lan print
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such
file or directory
And it work out-band:
# ipmitool -H {theip} -I lanplus -U {user} -P {passwd} lan print
Set in Progress : Set Complete
Auth Type Support : NONE MD2 MD5 PASSWORD
Auth Type Enable: Callback : MD2 MD5 PASSWORD
: User : MD2 MD5 PASSWORD
: Operator : MD2 MD5 PASSWORD
: Admin: MD2 MD5 PASSWORD
: OEM : MD2 MD5 PASSWORD
IP Address Source : DHCP Address
...
But the file exist:
# ls -al /dev/ipmi0
crw--- 1 root root 240, 0 Jul 16 13:55 /dev/ipmi0
# cat /proc/devices | grep ipmidev
240 ipmidev
packages that I installed:
# dpkg -l | grep ipmi
ii freeipmi-common 1.4.11-1.1ubuntu4.1
amd64GNU implementation of the IPMI protocol - common files
ii ipmitool 1.8.18-5ubuntu0.1
amd64utility for IPMI control with kernel driver or LAN interface
(daemon)
ii libfreeipmi16 1.4.11-1.1ubuntu4.1
amd64GNU IPMI - libraries
ii libopenipmi0 2.0.22-1.1ubuntu2.1
amd64Intelligent Platform Management Interface - runtime
ii openipmi 2.0.22-1.1ubuntu2.1
amd64Intelligent Platform Management Interface (for servers)
the mods:
# lsmod| grep ipmi_
ipmi_devintf 20480 0
ipmi_poweroff 16384 0
ipmi_watchdog 28672 0
ipmi_ssif 32768 0
ipmi_si61440 0
ipmi_msghandler53248 6
ipmi_devintf,ipmi_si,nvidia,ipmi_watchdog,ipmi_ssif,ipmi_poweroff
the kernel:
# uname -a
Linux A16969628514217 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
the ubuntu version:
# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1836701/+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 1895520] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895520 Title: package linux-image-5.4.0-47-generic 5.4.0-47.51 failed to install/upgrade: installed linux-image-5.4.0-47-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: I was installing the additional package of virtualbox as follows and an error has occurred. sudo apt -yV install virtualbox-guest-additions-iso virtualbox-guest- dkms-hwe virtualbox-guest-utils-hwe virtualbox-guest-x11-hwe ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core edac_mce_amd radeon wmi_bmof k10temp asus_atk0110 mac_hid hid_logitech_hidpp hid_logitech_dj r8169 pata_acpi pata_atiixp realtek i2c_piix4 pata_via wmi ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: takuya 1423 F pulseaudio /dev/snd/controlC1: takuya 1423 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip Date: Mon Sep 14 18:41:59 2020 ErrorMessage: installed linux-image-5.4.0-47-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-09-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 "Focal Fossa" - Release amd64(20200808.1) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=0fdd3258-4c08-4293-ac28-87a2a4169389 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. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.3 RfKill: SourcePackage: linux Title: package linux-image-5.4.0-47-generic 5.4.0-47.51 failed to install/upgrade: installed linux-image-5.4.0-47-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88TD-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. 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/1895520/+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 1836701] Re: ubuntu18.04: ipmitool failed: Could not open device at /dev/ipmi0 : No such file or directory
>From a machine with actual ipmi support:
$ lsmod | grep ipmi
ipmi_ssif 36864 0
ipmi_si65536 0
ipmi_devintf 20480 0
ipmi_msghandler 106496 3 ipmi_devintf,ipmi_si,ipmi_ssif
$ ll /dev/ipmi0 /dev/ipmi/0 /dev/ipmidev/0
ls: cannot access '/dev/ipmi/0': No such file or directory
ls: cannot access '/dev/ipmidev/0': No such file or directory
crw--- 1 root root 238, 0 Aug 24 06:27 /dev/ipmi0
$ sudo ipmitool lan print
Set in Progress : Set Complete
Auth Type Support :
Auth Type Enable: Callback :
...
But as one would expect without sudo:
$ ipmitool lan print
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such
file or directory
But the same also triggers on systems without ipmi (obviously).
So when I run it in a container or VM for example.
So we now know this can happen:
a) without root permissions (user error)
b) on a system without ipmi (well, that is ok then)
c) odd error we need to find (this would be worth to debug).
Does your kernel create and populate any of these?
$ ls -laF /dev/ipmi0 /dev/ipmi/0 /dev/ipmidev/0
And which modules are loaded?
$ lsmod | grep ipmi
Adding a kernel task for your reply to be seen there
** Also 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/1836701
Title:
ubuntu18.04: ipmitool failed: Could not open device at /dev/ipmi0 : No
such file or directory
Status in ipmitool package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Incomplete
Bug description:
ipmitool failed in-band
#ipmitool lan print
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such
file or directory
And it work out-band:
# ipmitool -H {theip} -I lanplus -U {user} -P {passwd} lan print
Set in Progress : Set Complete
Auth Type Support : NONE MD2 MD5 PASSWORD
Auth Type Enable: Callback : MD2 MD5 PASSWORD
: User : MD2 MD5 PASSWORD
: Operator : MD2 MD5 PASSWORD
: Admin: MD2 MD5 PASSWORD
: OEM : MD2 MD5 PASSWORD
IP Address Source : DHCP Address
...
But the file exist:
# ls -al /dev/ipmi0
crw--- 1 root root 240, 0 Jul 16 13:55 /dev/ipmi0
# cat /proc/devices | grep ipmidev
240 ipmidev
packages that I installed:
# dpkg -l | grep ipmi
ii freeipmi-common 1.4.11-1.1ubuntu4.1
amd64GNU implementation of the IPMI protocol - common files
ii ipmitool 1.8.18-5ubuntu0.1
amd64utility for IPMI control with kernel driver or LAN interface
(daemon)
ii libfreeipmi16 1.4.11-1.1ubuntu4.1
amd64GNU IPMI - libraries
ii libopenipmi0 2.0.22-1.1ubuntu2.1
amd64Intelligent Platform Management Interface - runtime
ii openipmi 2.0.22-1.1ubuntu2.1
amd64Intelligent Platform Management Interface (for servers)
the mods:
# lsmod| grep ipmi_
ipmi_devintf 20480 0
ipmi_poweroff 16384 0
ipmi_watchdog 28672 0
ipmi_ssif 32768 0
ipmi_si61440 0
ipmi_msghandler53248 6
ipmi_devintf,ipmi_si,nvidia,ipmi_watchdog,ipmi_ssif,ipmi_poweroff
the kernel:
# uname -a
Linux A16969628514217 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
the ubuntu version:
# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1836701/+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 1895523] [NEW] cant use the trackpad
Public bug reported: cant use the trackpad ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: thao 1393 F pulseaudio /dev/snd/controlC0: thao 1393 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 14 16:50:56 2020 InstallationDate: Installed on 2020-09-12 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81W3 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=b16872b7-b0e5-485f-9477-ab193ad9d221 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DZCN19WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55756WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDZCN19WW:bd04/13/2020:svnLENOVO:pn81W3:pvrIdeaPad314ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrIdeaPad314ARE05: dmi.product.family: IdeaPad 3 14ARE05 dmi.product.name: 81W3 dmi.product.sku: LENOVO_MT_81W3_BU_idea_FM_IdeaPad 3 14ARE05 dmi.product.version: IdeaPad 3 14ARE05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895523 Title: cant use the trackpad Status in linux package in Ubuntu: New Bug description: cant use the trackpad ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: thao 1393 F pulseaudio /dev/snd/controlC0: thao 1393 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 14 16:50:56 2020 InstallationDate: Installed on 2020-09-12 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81W3 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=b16872b7-b0e5-485f-9477-ab193ad9d221 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DZCN19WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55756WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDZCN19WW:bd04/13/2020:svnLENOVO:pn81W3:pvrIdeaPad314ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrIdeaPad314ARE05: dmi.product.family: IdeaPad 3 14ARE05 dmi.product.name: 81W3 dmi.product.sku: LENOVO_MT_81W3_BU_idea_FM_IdeaPad 3 14ARE05 dmi.product.version: IdeaPad 3 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895523/+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 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
(This post uses md syntax), ### Software Ubuntu 20.04. < bug still on 20.04. Agree with #103 #101 #94 #78 ### Hardware Several posts above mentioned hardware, RAM or RAM updates, so I will document mine as well. Initial > ASUS K401UB : - Intel Core i5-6200U (2.3GHz) - 4GB DDR3L - 1TB HDD, - NVIDIA GeForce 940M 2GB DDR3 Improvements > RAM : - Crucial CT102464BF160B : 8Go (DDR3L, 1600 MT/s, PC3L-12800, SODIMM, 204-Pin) - Product page: https://www.amazon.com/gp/product/B006YG8X9Y - Date: 2 months ago. - Now: 4+8=12GB. ### Symptomns: Past week, I copy large GIS files to my SSD. It starts super fast as expected, then fan runs wild and either : - transfer and UI slows down - transfer freeze temporarily, then restarts ; UI is fine - transfer and UI freeze temporarily, then restarts - transfers and UI totally freeze, after 10mins+ I reboot This `top` output was when it was lagging: $top top - 12:11:32 up 1 day, 18:23, 1 user, load average: 6,77, 4,46, 3,81 Tasks: 320 total, 5 running, 315 sleeping, 0 stopped, 0 zombie %Cpu(s): 66,0 us, 13,7 sy, 0,0 ni, 6,9 id, 13,4 wa, 0,0 hi, 0,0 si, 0,0 st MiB Mem : 11880,7 total,156,0 free, 5664,9 used, 6059,8 buff/cache MiB Swap: 0,0 total, 0,0 free, 0,0 used. 5324,5 avail Mem ### My little secret dirty hack While copying, unmount the disk. The copying UI box pop an error. Under the hood it seems to clears something. Mount back the disk. Then on the copying UI box pop an error, click "retry". It start again at full speed. ### Observations This shows again that it's not a single file bug but a cache/cumulative issue. While solid leads are shown above, no solution above solved it all so far. After 6 years it may needs a professional dedicated on the case for a definitive diagnostic and fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB Status in linux package in Ubuntu: Confirmed Bug description: Hi While copying many and large files to and from a USB drive, the system becomes incredibly slow and sometimes hangs. I watched the system monitor while it was running slowly but cpu was not above 50% at any time, the same for memory. I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD" laptop. Description: Ubuntu 13.04 Release: 13.04 nautilus: Installed: 1:3.6.3-0ubuntu16 Candidate: 1:3.6.3-0ubuntu16 Version table: *** 1:3.6.3-0ubuntu16 0 500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Aquire many large files (like your totally legit moviecollection) 2) Copy files to external HD 3) Open your browser and be sad when your system becomes incredibly slow after a few minutes This is my first bugreport so if I'm missing something, please tell me. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Aug 6 22:56:34 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-05-31 (67 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208993/+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 1895333] [NEW] cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
You have been subscribed to a public bug:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the regulatory
domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0
reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0
reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100
chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs
0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100
chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs
0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5290 - 5310 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5310 - 5330 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5490 - 5510 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5510 - 5530 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5530 - 5550 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5550 - 5570 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5570 -
[Kernel-packages] [Bug 1895523] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895523 Title: cant use the trackpad Status in linux package in Ubuntu: Confirmed Bug description: cant use the trackpad ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: thao 1393 F pulseaudio /dev/snd/controlC0: thao 1393 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 14 16:50:56 2020 InstallationDate: Installed on 2020-09-12 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81W3 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=b16872b7-b0e5-485f-9477-ab193ad9d221 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DZCN19WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55756WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDZCN19WW:bd04/13/2020:svnLENOVO:pn81W3:pvrIdeaPad314ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrIdeaPad314ARE05: dmi.product.family: IdeaPad 3 14ARE05 dmi.product.name: 81W3 dmi.product.sku: LENOVO_MT_81W3_BU_idea_FM_IdeaPad 3 14ARE05 dmi.product.version: IdeaPad 3 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895523/+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 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
** No longer affects: ubuntu
** Package changed: linux-hwe-5.4 (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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
New
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5290 - 5310 @ 80), (6, 22), (0 ms), DFS, AUTO-BW,
[Kernel-packages] [Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
[EDIT]: * PC hard drive is an SSD as well (upgraded 2 years ago). * Transfer speed from internal SSD to external SSD. (See attached image) ** declared: 40MB/s ** observed: 12kB/s (I hand measured 87sec/1MBs) ** slowing factor: 3000+ * Dirty little hack : unmount then remount external disk hack did NOT work when done over heavy 457MB GIS file. Likely over flooded the cache as it started. ** Attachment added: "File transfer box, showing optimistic time while observable transfer speed is 10kb/s" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208993/+attachment/5410695/+files/Screenshot_2020-09-14_12-58-19.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB Status in linux package in Ubuntu: Confirmed Bug description: Hi While copying many and large files to and from a USB drive, the system becomes incredibly slow and sometimes hangs. I watched the system monitor while it was running slowly but cpu was not above 50% at any time, the same for memory. I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD" laptop. Description: Ubuntu 13.04 Release: 13.04 nautilus: Installed: 1:3.6.3-0ubuntu16 Candidate: 1:3.6.3-0ubuntu16 Version table: *** 1:3.6.3-0ubuntu16 0 500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Aquire many large files (like your totally legit moviecollection) 2) Copy files to external HD 3) Open your browser and be sad when your system becomes incredibly slow after a few minutes This is my first bugreport so if I'm missing something, please tell me. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Aug 6 22:56:34 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-05-31 (67 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208993/+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 1895523] Re: cant use the trackpad
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895523 Title: cant use the trackpad Status in linux package in Ubuntu: Fix Released Bug description: cant use the trackpad ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: thao 1393 F pulseaudio /dev/snd/controlC0: thao 1393 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 14 16:50:56 2020 InstallationDate: Installed on 2020-09-12 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81W3 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=b16872b7-b0e5-485f-9477-ab193ad9d221 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DZCN19WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55756WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDZCN19WW:bd04/13/2020:svnLENOVO:pn81W3:pvrIdeaPad314ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrIdeaPad314ARE05: dmi.product.family: IdeaPad 3 14ARE05 dmi.product.name: 81W3 dmi.product.sku: LENOVO_MT_81W3_BU_idea_FM_IdeaPad 3 14ARE05 dmi.product.version: IdeaPad 3 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895523/+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 1895333] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1895333
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A
[Kernel-packages] [Bug 1895142] Re: Toshiba Satellite A300 restarts after waking from suspend mode
I tested this bug with the Linux kernel version 4.15.0-112-generic (i686) that
I thought was OK. It is not. My computer has problems with resuming from the
suspend mode and the behaviour is not always the same. As I used the 112
version for longer time before and nothing happened, it seems to me that now it
is some hardware error as my Toshiba is quite old.
I apologize for disturbing.
Please, close this bug as not relevant.
--
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/1895142
Title:
Toshiba Satellite A300 restarts after waking from suspend mode
Status in linux package in Ubuntu:
Confirmed
Bug description:
I suspend the laptop either by closing the lid or by GUI clicking on Suspend
option (Pohotovostný režim in Slovak).
I resume from suspend either by opening the lid or by pressing the power
button.
In either case the PC resumes for about a second then power goes off (I hear
the hard disk going off) and the system restarts. Then it is OK.
I think that the problem started after updating the kernel to version Linux
4.15.0-115-generic (i686). Now I use the version 4.15.0-117-generic (i686).
I have never faced this problem before and I run Lubuntu on this PC for more
than year.
I cannot provide information required by Ubuntu Wiki in section
DebuggingKernelSuspend as I have not installed the nondaily mainline kernel.
Issuing the command "sudo cat /sys/kernel/debug/suspend_stats" I obtained the
following output:
viktor@Toshiba:~$ sudo cat /sys/kernel/debug/suspend_stats
[sudo] heslo pre používateľa viktor:
success: 0
fail: 0
failed_freeze: 0
failed_prepare: 0
failed_suspend: 0
failed_suspend_late: 0
failed_suspend_noirq: 0
failed_resume: 0
failed_resume_early: 0
failed_resume_noirq: 0
failures:
last_failed_dev:
last_failed_errno: 0
0
last_failed_step:
viktor@Toshiba:~$
That's all so far.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-117-generic 4.15.0-117.118
ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18
Uname: Linux 4.15.0-117-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-117-generic.
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0c: viktor 966 F...m pulseaudio
/dev/snd/pcmC0D0p: viktor 966 F...m pulseaudio
/dev/snd/controlC0: viktor 966 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd470 irq 25'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,1179ff1e,0013
HDA:11c11040,11790001,00100200'
Controls : 28
Simple ctrls : 12
CurrentDesktop: LXDE
Date: Thu Sep 10 14:19:52 2020
MachineType: TOSHIBA Satellite A300
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic
root=UUID=3c3d339c-33ce-486d-b55e-4fe4154e7815 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-117-generic N/A
linux-backports-modules-4.15.0-117-generic N/A
linux-firmware 1.173.19
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/14/2008
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.60
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnINSYDE:bvr1.60:bd10/14/2008:svnTOSHIBA:pnSatelliteA300:pvrPSAG8E-01L00JSK:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: Satellite A300
dmi.product.version: PSAG8E-01L00JSK
dmi.sys.vendor: TOSHIBA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895142/+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 1895333] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410716/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
[Kernel-packages] [Bug 1895333] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410717/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE
[Kernel-packages] [Bug 1895527] [NEW] [linux-azure] [SRU] UBUNTU: SAUCE: Drivers: hv: vmbus: Add timeout to vmbus_wait_for_unload
Public bug reported:
This is a request to inclue a patch, submitted to the upstream linux-
hyperv mailing list, in the linux-azure kernels.
Microsoft would like to request this patch in the 16.04 (4.15) and newer
azure kernels. This patch fixes a prior commit, hence the SRU request:
Fixes: 415719160de3 ("Drivers: hv: vmbus: avoid scheduling in interrupt
context in vmbus_initiate_unload()")
The patch specfically performs the following:
"vmbus_wait_for_unload() looks for a CHANNELMSG_UNLOAD_RESPONSE message
coming from Hyper-V. But if the message isn't found for some reason,
the panic path gets hung forever. Add a timeout of 10 seconds to
prevent this."
The requested patch can be found at:
https://lkml.org/lkml/2020/9/13/196
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1895527
Title:
[linux-azure] [SRU] UBUNTU: SAUCE: Drivers: hv: vmbus: Add timeout to
vmbus_wait_for_unload
Status in linux-azure package in Ubuntu:
New
Bug description:
This is a request to inclue a patch, submitted to the upstream linux-
hyperv mailing list, in the linux-azure kernels.
Microsoft would like to request this patch in the 16.04 (4.15) and
newer azure kernels. This patch fixes a prior commit, hence the SRU
request:
Fixes: 415719160de3 ("Drivers: hv: vmbus: avoid scheduling in
interrupt context in vmbus_initiate_unload()")
The patch specfically performs the following:
"vmbus_wait_for_unload() looks for a CHANNELMSG_UNLOAD_RESPONSE
message coming from Hyper-V. But if the message isn't found for some
reason, the panic path gets hung forever. Add a timeout of 10 seconds
to prevent this."
The requested patch can be found at:
https://lkml.org/lkml/2020/9/13/196
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1895527/+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 1895333] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410706/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCA
[Kernel-packages] [Bug 1895333] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410702/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(529
[Kernel-packages] [Bug 1895333] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410709/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
[Kernel-packages] [Bug 1895333] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410707/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5
[Kernel-packages] [Bug 1895333] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410715/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
[Kernel-packages] [Bug 1895333] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410708/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
[Kernel-packages] [Bug 1895333] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410703/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PAS
[Kernel-packages] [Bug 1895333] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410704/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCA
[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
apport information
** Tags added: apport-collected
** Description changed:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the regulatory
domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5290 - 5310 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5310 - 5330 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5490 - 5510 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5510 - 5530 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160
[Kernel-packages] [Bug 1895333] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410714/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-S
[Kernel-packages] [Bug 1895333] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410711/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-
[Kernel-packages] [Bug 1895333] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410705/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5
[Kernel-packages] [Bug 1895333] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410713/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSI
[Kernel-packages] [Bug 1895333] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410712/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
[Kernel-packages] [Bug 1895333] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410710/+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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSI
[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
** Attachment removed: "AlsaInfo.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895333/+attachment/5410701/+files/AlsaInfo.txt
** Attachment removed: "CRDA.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895333/+attachment/5410702/+files/CRDA.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/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Confirmed
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[2.896628] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[3.069593] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[4.247469] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.125981] ath10k_pci :04:00.0: unsupported HTC service id: 1536
[7.149519] ath: EEPROM regdomain: 0x0
[7.149520] ath: EEPROM indicates default country code should be used
[7.149520] ath: doing EEPROM country->regdmn map search
[7.149521] ath: country maps to regdmn code: 0x3a
[7.149521] ath: Country alpha2 being used: US
[7.149521] ath: Regpair used: 0x3a
[7.152614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.297494] ath: EEPROM regdomain: 0x0
[7.297495] ath: EEPROM indicates default country code should be used
[7.297495] ath: doing EEPROM country->regdmn map search
[7.297496] ath: country maps to regdmn code: 0x3a
[7.297496] ath: Country alpha2 being used: US
[7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ,
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS,
[Kernel-packages] [Bug 1895426] Re: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Looks like a problem generating a new initramfs: update-initramfs: Generating /boot/initrd.img-5.4.0-47-generic mv: cannot stat '/boot/initrd.img-5.4.0-47-generic.new': No such file or directory I don't see any information about what went wrong though. The disk isn't full, so that's not the problem. Adding initramfs-tools. I don't see any reason to think this is a linux- firmware problem right now, so setting that to invalid. ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1895426 Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Bug description: linux-firmware bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.3 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tirtha 1397 F pulseaudio CasperMD5CheckResult: skip Date: Sun Sep 13 11:45:12 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-09-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=a24d343d-9753-4460-ac8f-43882d4197c7 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.3 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1895426/+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 1892546] Re: Novalink (mkvterm command failure)
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: ubuntu-power-systems Status: Incomplete => Triaged -- 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/1892546 Title: Novalink (mkvterm command failure) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Bug description: -- Problem Description -- drmgr command is failing while trying to open console for IBMi. Log snap shot: Please make sure you have specified a valid locale (check your NLSPATH and LANG environment variables. Your application will use english as the default. 2 07/15/20 16:01:25.393.531 UTC DEBUG pvmutil[12687.70366696995648]: (common/util/HmclDrmgrHelper.cpp:1036) Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 returned 255. Additional messages: /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 Validating I/O DLPAR capability...yes. failed to open /sys/bus/pci/slots/U9080.MHE.218BA37-V1-C8/power: No such file or directory failed to disable hotplug children Isolation failed for 3008 with -9001 Valid outstanding translations exist. ---Steps to Reproduce--- Create a VM from PowerVC on a Novalink managed host. Unmanage and manage the VM, this problem gets reproduced == I've tested a proposed fix and it does fix both the -9001 isolation errors after DLPAR remove and vterm state is still open, as well as the /dev/hcvsX index changing after a DLPAR remove/add. I will get that patch sent out to the upstream mailing list for merging. Patch submitted upstream: https://lore.kernel.org/linuxppc- dev/20200820234643.70412-1-tyr...@linux.ibm.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1892546/+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 1880388] Re: rpi3b+ becomes unresponsive after closing a program
** Also affects: linux-raspi (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid ** No longer affects: linux-raspi (Ubuntu Bionic) ** Also affects: linux-raspi-5.4 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-raspi-5.4 (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux-raspi (Ubuntu Bionic) ** No longer affects: linux-raspi-5.4 (Ubuntu Focal) ** Changed in: linux-raspi-5.4 (Ubuntu) Status: New => Invalid ** Changed in: linux-raspi-5.4 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1880388 Title: rpi3b+ becomes unresponsive after closing a program Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi-5.4 package in Ubuntu: Invalid Status in linux-raspi-5.4 source package in Bionic: Fix Committed Status in linux-raspi source package in Focal: Fix Committed Bug description: I am running ROS2 on this raspberry pi 3B+ that is running as the main computer on a turtlebot3. There is two USB devices connected to the RPi, one is to communicate with the LIDAR and the other is to communicate with the control board, a OpenCR board. After "bringing the robot up" I open a new shell in tmux, and run `ros2 topic echo battery_state` which starts outputting ROS2 messages to the terminal. Upon ctrl+c'ing out of this, the system become unresponsive. I repeated this while connected to the serial console and captured the error messages that are being output. Issue I rose on github: https://github.com/ROBOTIS-GIT/turtlebot3/issues/593 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-1011-raspi 5.4.0-1011.11 ProcVersionSignature: User Name 5.4.0-1011.11-raspi 5.4.34 Uname: Linux 5.4.0-1011-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Sun May 24 10:31:26 2020 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) Serial console output: MMC: mmc@7e202000: 0, mmcnr@7e30: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment In:serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... Bus usb@7e98: scanning bus usb@7e98 for devices... 6 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found ## Info: input data size = 6 = 0x6 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 2603 bytes read in 6 ms (422.9 KiB/s) ## Executing script at 0240 8378005 bytes read in 364 ms (21.9 MiB/s) Total of 1 halfword(s) were the same Decompressing kernel... Uncompressed size: 25905664 = 0x18B4A00 29426757 bytes read in 1262 ms (22.2 MiB/s) Booting Ubuntu (with booti) from mmc 0:... ## Flattened Device Tree blob at 0260 Booting using the fdt blob at 0x260 Using Device Tree in place at 0260, end 02609f2f Starting kernel ... [1.966598] spi-bcm2835 3f204000.spi: could not get clk: -517 ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or directory ext4 Thu Jan 1 00:00:07 UTC 1970 date: invalid date ' Wed Apr 1 17:23:46 2020' -.mount dev-mqueue.mount sys-kernel-debug.mount sys-kernel-tracing.mount kmod-static-nodes.service systemd-modules-load.service systemd-remount-fs.service ufw.service sys-fs-fuse-connections.mount sys-kernel-config.mount systemd-sysctl.service systemd-random-seed.service systemd-sysusers.service keyboard-setup.service systemd-tmpfiles-setup-dev.service swapfile.swap lvm2-monitor.service systemd-udevd.service systemd-journald.service systemd-udev-trigger.service systemd-journal-flush.service [ 14.813759] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 15.128676] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 15.174878] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04 systemd-rfkill.service systemd-udev-settle.service netplan-wpa-wlan0.service multipathd.service [ 17.840942] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled systemd-fsckd.service snap-core18-1708.mount snap-core18-1753.mount snap-lxd-14808.mount snap-lxd-15066.mount snap-snapd-7267.mount systemd-fsck@dev-disk-by\x2dlabel-sy
[Kernel-packages] [Bug 1890808] Re: Build preemptible raspi kernels
** Also affects: linux-raspi (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Bionic) Status: New => Fix Committed ** Also affects: linux-raspi-5.4 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-raspi (Ubuntu Bionic) ** No longer affects: linux-raspi-5.4 (Ubuntu Focal) ** Changed in: linux-raspi-5.4 (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-raspi-5.4 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1890808 Title: Build preemptible raspi kernels Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi-5.4 package in Ubuntu: Invalid Status in linux-raspi-5.4 source package in Bionic: Fix Committed Status in linux-raspi source package in Focal: Fix Committed Bug description: [Impact] Hangs and lockups are observed when lots of USB interrupts occur. The FIQ handling in the dwc_otg driver seems to be particular susceptible to this setting. [Test Case] Connect a USB/serial adapter to the Pi. Run 'minicom -D /dev/ttyUSB0'. Send data over that serial connection from a remote device. The Pi will hang within seconds. [Regression Potential] This change enables full preemption which could uncover all sorts of problems like hangs and/or lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1890808/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
@PowerKiKi That is very odd, mine lasts for hours and hours. I wouldn't think ubuntu and xbuntu would be that different with regard to audio hardware mgmt, but one guess off the top of my head is that before I found this thread I turned off power mgmt for snd_hda_intel to try to get the headphone verb to be sticky. Obviously this will increase power usage some, but I have not noticed any difference in battery life. If you want to try it, here are the steps I tried (it can be reversed easily if it doesn't help)... 1) Go to folder /sys/module/snd_hda_intel/parameters/ 2) modify 2 files sudo gedit power_save change 1 to 0 sudo gedit power_save_controller change Y to N 3) If you still have an alsa-base file (Mike had me delete mine with his patch), you can add these lines too... sudo gedit /etc/modprobe.d/alsa-base.conf Add options snd-hda-intel power_save=0 options snd-hda-intel power_save_controller=N -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, i
[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin20041
--
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/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
waiting for time change
Status in ubuntu-kernel-tests:
New
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Invalid
Bug description:
The hwclock test will fail on the Power9 system "baltar" due to a
<0.02 second difference.
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
Sometimes it will fail because "time out waiting for time change" on the same
node:
$ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
hwclock: Timed out waiting for time change.
Workaround for these is to add "sleep 1".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
min: 2.862 GHz (cpu 159)
max: 2.862 GHz (cpu 1)
avg: 2.862 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel interface to firmware
cpu_smt: SMT=4
-- Firmware information on Baltar --
pnor: P9DSU20190404_IBM_prod_sign.pnor
bmc: SMT_P9_206.bin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+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 1892546] Re: Novalink (mkvterm command failure)
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: Triaged => 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/1892546 Title: Novalink (mkvterm command failure) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Bug description: -- Problem Description -- drmgr command is failing while trying to open console for IBMi. Log snap shot: Please make sure you have specified a valid locale (check your NLSPATH and LANG environment variables. Your application will use english as the default. 2 07/15/20 16:01:25.393.531 UTC DEBUG pvmutil[12687.70366696995648]: (common/util/HmclDrmgrHelper.cpp:1036) Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 returned 255. Additional messages: /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 Validating I/O DLPAR capability...yes. failed to open /sys/bus/pci/slots/U9080.MHE.218BA37-V1-C8/power: No such file or directory failed to disable hotplug children Isolation failed for 3008 with -9001 Valid outstanding translations exist. ---Steps to Reproduce--- Create a VM from PowerVC on a Novalink managed host. Unmanage and manage the VM, this problem gets reproduced == I've tested a proposed fix and it does fix both the -9001 isolation errors after DLPAR remove and vterm state is still open, as well as the /dev/hcvsX index changing after a DLPAR remove/add. I will get that patch sent out to the upstream mailing list for merging. Patch submitted upstream: https://lore.kernel.org/linuxppc- dev/20200820234643.70412-1-tyr...@linux.ibm.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1892546/+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 1895301] [NEW] XrandR does not propose 3440x1440 21:9 resolution
You have been subscribed to a public bug: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- XrandR does not propose 3440x1440 21:9 resolution https://bugs.launchpad.net/bugs/1895301 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891288] Re: arm64 gcov in 5.8 breaks when trying to enable it
Upstream fix 40249c6962075c040fd071339acae524f18bfac9, this has already been picked up by Sash Levin for 5.8, 5.4, 4.19, 4.14, 4.9 and 4.8 on backport stable AUTOSEL. Lets wait for that fix to trickle into the SRU process. ** Changed in: linux (Ubuntu) Status: Won't Fix => 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/1891288 Title: arm64 gcov in 5.8 breaks when trying to enable it Status in Linux: Confirmed Status in linux package in Ubuntu: In Progress Bug description: Running: sudo lcov --zerocounters on a gcov enabled kernel causes a read-only splat: [ 139.798968] Unable to handle kernel write to read-only memory at virtual address b4511ee6bb10 [ 139.803325] Mem abort info: [ 139.804882] ESR = 0x964e [ 139.806265] EC = 0x25: DABT (current EL), IL = 32 bits [ 139.811261] SET = 0, FnV = 0 [ 139.814163] EA = 0, S1PTW = 0 [ 139.816545] Data abort info: [ 139.817852] ISV = 0, ISS = 0x004e [ 139.820023] CM = 0, WnR = 1 [ 139.821350] swapper pgtable: 4k pages, 48-bit VAs, pgdp=5086f000 [ 139.825005] [b4511ee6bb10] pgd=0001b6fff003, p4d=0001b6fff003, pud=0001b6ffe003, pmd=00404e200f91 [ 139.832061] Internal error: Oops: 964e [#1] SMP [ 139.835002] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua efi_pstore qemu_fw_cfg sch_fq_codel drm virtio_rng ip_t ables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c rai d1 raid0 multipath linear crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_net net_failover xhci_pci virtio_blk virtio_scsi failover xhci_pci_ren esas aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [ 139.865929] CPU: 5 PID: 1235 Comm: lcov Tainted: GW 5.8.0-8-generic #9 [ 139.871293] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 139.876248] pstate: 2045 (nzCv daif +PAN -UAO BTYPE=--) [ 139.879993] pc : __memset+0x148/0x188 [ 139.882387] lr : gcov_info_reset+0xa0/0x110 [ 139.885404] sp : 8000122f3bf0 [ 139.887730] x29: 8000122f3bf0 x28: 000167480f40 [ 139.891129] x27: x26: b450e46bc060 [ 139.894688] x25: 0001 x24: b450e46bc040 [ 139.897391] x23: x22: b450e46bc0a8 [ 139.900064] x21: b45122ba5db8 x20: b450e46bc068 [ 139.902681] x19: b450e46bc068 x18: [ 139.905345] x17: x16: [ 139.908016] x15: x14: [ 139.910625] x13: x12: [ 139.913260] x11: x10: [ 139.915922] x9 : x8 : b4511ee6bb10 [ 139.918531] x7 : x6 : 003f [ 139.921196] x5 : 0040 x4 : 0030 [ 139.923852] x3 : 0007235d7fd0 x2 : 0007235d7fd0 [ 139.926460] x1 : x0 : b4511ee6bb10 [ 139.929126] Call trace: [ 139.930349] __memset+0x148/0x188 [ 139.932025] reset_node+0x70/0xc0 [ 139.933662] reset_write+0xc0/0x130 [ 139.935389] full_proxy_write+0x98/0x110 [ 139.937349] vfs_write+0x18c/0x3e0 [ 139.939031] ksys_write+0xc4/0x1f0 [ 139.940766] __arm64_sys_write+0x44/0x60 [ 139.942705] invoke_syscall+0x74/0x150 [ 139.944601] el0_svc_common.constprop.0+0x94/0x264 [ 139.946961] do_el0_svc+0x5c/0x7c [ 139.948651] el0_svc+0x70/0x114 [ 139.950206] el0_sync_handler+0x140/0x39c [ 139.952239] el0_sync+0x17c/0x180 [ 139.953894] Code: f101007f fa45a068 54fffc0b aa0303e2 (a9001d07) [ 139.956946] ---[ end trace 71e2f9cc3eaddf4e ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1891288/+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 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
run 'apport-collect 1895301' ** Package changed: xrandr (Ubuntu) => linux (Ubuntu) ** Package changed: linux (Ubuntu) => xorg-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/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: New Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+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 1891151] Re: md: improve IO accounting
** 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/1891151 Title: md: improve IO accounting Status in linux package in Ubuntu: Confirmed Bug description: Currently reported IO stats may be incorrect or missing. This adds correct statistics about in-flight IOs and IO processing time, interpreted e.g. in iostat as await, svctm, aqu-sz and %util. Commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891151/+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 1893609] Re: SRU: Fix system hang when stress S3 on radeon with TTM
Verified on 5.6.0-1028-oem. Good for 300 times of S3. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1893609 Title: SRU: Fix system hang when stress S3 on radeon with TTM Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] System hang when stress S3 more than 90 times. [Fix] Upstream kernel is good, after bisecting, bad commit is a Ubuntu sauce patch: "vfio -- release device lock before userspace requests" 5.8 kernel got this fix. 5.4 kernel got this commit by stable update LP:#1888560 [Test Case] Verified for 500 times of S3, system runs good. [Regression Potential] Low uptream fix for specific commit, verified with postive result. == [Summary] System got hang during executing the S3-30-cycle test case. [Steps to reproduce] $ sudo checkbox-support-fwts_test -l /home/u/suspend_30_cycles -f none -s s3 --s3-device-check --s3-device-check-delay=60 --s3-sleep-delay=60 --s3-multiple=30 [Expected result] The test script should be finished smoothly. [Actual result] System got hang at the 7th or 8th S3 resumed back. [Failure rate] 100% [Additional information] CPU: Intel(R) Core(TM) i5-10600 CPU @ 3.30GHz (12x) GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:9bc8] 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] (rev 87) kernel-version: 5.6.0-1020-oem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893609/+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 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter
I'm having the same problem with an Huawei Matebook D14 2020 R5 with their
bluetooth mouse.
What I noticed using bluetoothctl is that the mouse device ID changes:
D9:73:24:7E:1A:0E (random)
I've seen 0E, 0F, 0C, 0B, etc.
I don't know if it's suppose to be like that or not.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1887968
Title:
Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD
laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter
Status in bluez package in Ubuntu:
Confirmed
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address
[Kernel-packages] [Bug 1891151] Re: md: improve IO accounting
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891151 Title: md: improve IO accounting Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Status in linux source package in Groovy: Confirmed Bug description: Currently reported IO stats may be incorrect or missing. This adds correct statistics about in-flight IOs and IO processing time, interpreted e.g. in iostat as await, svctm, aqu-sz and %util. Commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891151/+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 1895010] Re: ocfs2 shared volume causing hang
hopefully this ticket gets some notice soon as this bug appears to be a kernel level regression in a "major" kernel level feature: ocfs2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1895010 Title: ocfs2 shared volume causing hang Status in linux package in Ubuntu: Confirmed Status in linux-signed package in Ubuntu: Confirmed Bug description: This vm is running on a vmware backed system with a multiwriter shared volume mounted via ocfs2. in kernel version 4.4.0-187 or -189 any attempt at writting to the volume results in kernel errors root@hostname:/mnt/NewsroomImageShare# touch text.txt Killed kernel version 186 this issue does not occur. root@hostname:~# lsb_release -rd Description:Ubuntu 16.04.7 LTS Release:16.04 package ii linux-image-4.4.0-187-generic 4.4.0-187.217 amd64Signed kernel image generic what I expect to happen: writing to a ocfs2 shared disk should not crash what happens: writting to an ocfs2 shared disk crashes the terminal/ssh session, and make the vm unusable. and logs errors in dmesg [Sep 3 04:09] general protection fault: [#1] SMP [ +0.000346] Modules linked in: mptctl ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs vmw_balloon joydev input_leds serio_raw shpchp i2c_piix4 vmw_vsock_vmci_transport vsock vmw_vmci mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse vmwgfx ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci vmxnet3 libahci mptspi mptscsih drm pata_acpi mptbase scsi_transport_spi fjes [ +0.001534] CPU: 0 PID: 1553 Comm: java Not tainted 4.4.0-189-generic #219-Ubuntu [ +0.49] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018 [ +0.67] task: 880073863900 ti: 8800798e task.ti: 8800798e [ +0.47] RIP: 0010:[] [] _raw_spin_lock+0xe/0x70 [ +0.86] RSP: 0018:8800798e3998 EFLAGS: 00010206 [ +0.35] RAX: 0002 RBX: 6d612d7972616e69 RCX: [ +0.46] RDX: 8000 RSI: 0009 RDI: 6d612d7972616ef1 [ +0.45] RBP: 8800798e3998 R08: R09: [ +0.45] R10: 880075729060 R11: 8000 R12: 6d612d7972616ef1 [ +0.44] R13: 8800748aeaa8 R14: 880076399650 R15: [ +0.46] FS: 7f9a50ad9700() GS:88007b60() knlGS: [ +0.51] CS: 0010 DS: ES: CR0: 80050033 [ +0.37] CR2: 7f9a1d4f2000 CR3: 79936000 CR4: 00160670 [ +0.000160] Stack: [ +0.19] 8800798e39b8 8123953e 0009 8800748ae000 [ +0.55] 8800798e3a38 c057bb77 c053309a [ +0.54] 88007958e498 88007958e4e0 0001 88007958e3c8 [ +0.55] Call Trace: [ +0.25] [] igrab+0x1e/0x50 [ +0.84] [] ocfs2_get_system_file_inode+0x67/0x300 [ocfs2] [ +0.88] [] ? ocfs2_read_virt_blocks+0x1ca/0x310 [ocfs2] [ +0.72] [] ? dx_leaf_sort_swap+0x40/0x40 [ocfs2] [ +0.75] [] ocfs2_reserve_suballoc_bits+0x4e/0x430 [ocfs2] [ +0.74] [] ocfs2_steal_resource+0x9b/0x130 [ocfs2] [ +0.001659] [] ocfs2_reserve_new_inode+0xb5/0x370 [ocfs2] [ +0.001326] [] ocfs2_mknod+0x4be/0x10e0 [ocfs2] [ +0.001622] [] ? ocfs2_should_refresh_lock_res+0x113/0x160 [ocfs2] [ +0.001571] [] ocfs2_create+0x4c/0x160 [ocfs2] [ +0.001318] [] vfs_create+0x12d/0x190 [ +0.001218] [] path_openat+0x1232/0x1360 [ +0.001255] [] ? file_update_time+0xcc/0x110 [ +0.001167] [] do_filp_open+0x91/0x100 [ +0.001132] [] ? new_sync_write+0xa5/0xf0 [ +0.001131] [] ? __alloc_fd+0xc7/0x190 [ +0.001072] [] do_sys_open+0x138/0x2a0 [ +0.001040] [] SyS_open+0x1e/0x20 [ +0.001028] [] entry_SYSCALL_64_fastpath+0x22/0xd0 [ +0.001041] Code: e2 fe 8d 72 02 0f b7 f6 0f 1f 80 00 00 00 00 eb d2 66 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 b8 00 00 02 00 0f c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 41 89 d0 0f b7 [ +0.003174] RIP [] _raw_spin_lock+0xe/0x70 [ +0.001007] RSP [ +0.002867] ---[ end trace 6fd21d2a8e763939 ]--- - [Sep 4 03:56] (java,5847,1):ocfs2_reserve_suballoc_bits:796 ERROR: status = -22 [ +0.98] (java,5847,1):ocfs2_reserve_n
[Kernel-packages] [Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
I can't reproduce the problem in Focal any more (either in my chroot or in my focal installation). Can you? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: In Progress Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: In Progress Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
@paelzer I agree that the fact, i.e. that systemd autpkgtest is failing in Groovy/s390x, but this is a real regression which is not due to flakiness of tests-in-lxd. Please don't reopen this bug, but file a new one or find one already opened. As I see this is still LP: #1878225. I'm filing a hint for it for now. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the dis
[Kernel-packages] [Bug 1893897] Re: [Regression] Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event
** Description changed: - == Comment: #0 - VASANT HEGDE - 2020-09-02 01:00:25 == - --Problem Description--- - Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event. Instead wait for predefined time before initiating shtudown. - - Contact Information = Vasant hegde - Date: Thu Aug 20 11:48:44 2020 +0530 + [Impact] - powerpc/pseries: Do not initiate shutdown when system is running on UPS - + * With commit 79872e35469b "powerpc/pseries: All events of + EPOW_SYSTEM_SHUTDOWN must initiate shutdown" it was introduced that all + EPOW_SYSTEM_SHUTDOWN events cause immediate shutdowns. - Note that I have requested this fix for upstream v4.4 stable tree. This - will hit stable tree soon. + * But on LPARs there is a user space tool (rtas_errd) that monitor for + EPOW_SHUTDOWN_ON_UPS events. - This is impacting all kernel after v4.0. This is critical fix. Hence - I'd like to request to backport to Ubuntu 16.04 LTS release. + * Once rtas_errd gets an event it initiates a shutdown after predefined + time. + * Therefore immediate shutdowns must not be triggered if the system is + running on UPS (means for EPOW_SHUTDOWN_ON_UPS events). - -Vasant + [Fix] + + * 90a9b102eddf6a3f987d15f4454e26a2532c1c98 90a9b102eddf + "powerpc/pseries: Do not initiate shutdown when system is running on + UPS" + + [Test Case] + + * Setup a Power system on (D)LPAR and run it on UPS with Ubuntu 16.04 or + higher (kernel 4.x is needed). + + * Verify that the user space tool (rtas_errd) is active and running. + + * Define a time for a potential shutdown in case an EPOW_SHUTDOWN_ON_UPS + event occurs. + + * Trigger an EPOW_SHUTDOWN_ON_UPS event. + + * Verify if the system got shutdown immediately - or after the pre- + defined time. + + [Regression Potential] + + * The regression risk is very low, because of the very limited + modification in a case statement for EPOW_SHUTDOWN_ON_UPS events. + + * What may happen is that the system doesn't power off anymore if + running on UPS due to the EPOW_SHUTDOWN_ON_UPS case changes - especially + if there is a potential problem with rtas_errd that should monitor for + these events and should initiate the delayed shutdown. + + * Other than that I cannot see much potential harm. + + [Other] + + * The patch got upstream accepted in v5.9-rc2 and already landed in + groovy's kernel 'Ubuntu-5.8.0-18.19', based on the v5.8.4 upstream + stable release ticket LP 1893048. -- 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/1893897 Title: [Regression] Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: [Impact] * With commit 79872e35469b "powerpc/pseries: All events of EPOW_SYSTEM_SHUTDOWN must initiate shutdown" it was introduced that all EPOW_SYSTEM_SHUTDOWN events cause immediate shutdowns. * But on LPARs there is a user space tool (rtas_errd) that monitor for EPOW_SHUTDOWN_ON_UPS events. * Once rtas_errd gets an event it initiates a shutdown after predefined time. * Therefore immediate shutdowns must not be triggered if the system is running on UPS (means for EPOW_SHUTDOWN_ON_UPS events). [Fix] * 90a9b102eddf6a3f987d15f4454e26a2532c1c98 90a9b102eddf "powerpc/pseries: Do not initiate shutdown when system is running on UPS" [Test Case] * Setup a Power system on (D)LPAR and run it on UPS with Ubuntu 16.04 or higher (kernel 4.x is needed). * Verify that the user space tool (rtas_errd) is active and running. * Define a time for a potential shutdown in case an EPOW_SHUTDOWN_ON_UPS event occurs. * Trigger an EPOW_SHUTDOWN_ON_UPS event. * Verify if the system got shutdown immediately - or after the pre- defined time. [Regression Potential] * The regression risk is very low, because of the very limited modification in a case statement for EPOW_SHUTDOWN_ON_UPS events. * What may happen is that the system doesn't power off anymore if running on UPS due to the EPOW_SHUTDOWN_ON_UPS case changes - especially if there is a potential problem with rtas_errd that should monitor for these events and should initiate the delayed shutdown. * Other than that I cannot see much potential harm. [Other] * The patch got upstream accepted in v5.9-rc2 and already landed in groovy's kernel 'Ubuntu-5.8.0-18.19', based on the v5.8.4 upstream stable release ticket LP 1893048. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1893897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1895563] [NEW] Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
Public bug reported: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kernelcrash bionic uec-images ** Attachment added: "cat /proc/version_signature > version.log" https://bugs.launchpad.net/bugs/1895563/+attachment/5410760/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS
[Kernel-packages] [Bug 1894910] Re: fallocate swapfile has holes on 5.8 ext4, causes: swapon failed: Invalid argument
** Merge proposal linked: https://code.launchpad.net/~paride/curtin/+git/curtin/+merge/390692 -- 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/1894910 Title: fallocate swapfile has holes on 5.8 ext4, causes: swapon failed: Invalid argument Status in linux package in Ubuntu: Confirmed Bug description: 1) Groovy 2) root@ubuntu:/home/ubuntu# apt-cache policy linux-image-generic linux-image-generic: Installed: 5.8.0.18.22 Candidate: 5.8.0.18.22 Version table: *** 5.8.0.18.22 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status 3) swapon --verbose /swap.img enables swap file successfully 4) swapon returns error, says swapfile has holes. Curtin creates file-based swap files with fallocate: fallocate -l XXXM /swap.img When booting Groovy (5.8 kernel), the swapfile fails to load, complains it has holes root@ubuntu:/home/ubuntu# swapon --verbose /swap.img swapon: /swap.img: found signature [pagesize=4096, signature=swap] swapon: /swap.img: pagesize=4096, swapsize=1251999744, devsize=1251999744 swapon /swap.img [ 178.283022] swapon: swapfile has holes swapon: /swap.img: swapon failed: Invalid argument root@ubuntu:/home/ubuntu# uname -r 5.8.0-18-generic This configuration works fine on Focal (5.4) and older. Previous Groovy kernels, (5.7) also worked. It may be related to: https://lkml.org/lkml/2020/9/4/259 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.18.22 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 8 21:38 seq crw-rw 1 root audio 116, 33 Sep 8 21:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Tue Sep 8 21:44:13 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic root=UUID=ce45bbaf-5a44-4487-b89e-035c2dd40657 ro console=ttyS0 systemd.mask=snapd.seeded.service systemd.mask=snapd.service panic=-1 softlockup_panic=1 hung_task_panic=1 nmi_watchdog=panic,1 ip=:BOOTIF:dhcp RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894910/+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 1895563] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- Mailin
[Kernel-packages] [Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
** Attachment added: "sudo lspci -vnvn > lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+attachment/5410773/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw---
[Kernel-packages] [Bug 1894378] Re: Cannot boot after updating kernel to version 5.4.0-45
At work, we got quite recently one machine hanging on "ALERT! ... UUID does not exist ..." with kernels 5.4.0-45 and 5.4.0-47. Only 5.4.0-42 is booting now. Adding `rootdelay=5` does not help. I've already updated BIOS to latest version (from 2020-07), does not help. The machine is also using NVMe M2 SSD. It is miniPC `Intel NUC8BEH`. Please: 1) how to workaround this in order to let the user actually use the machine without manually selecting "Advanced boot options"? 2) how to fix this properly? Thanks -- 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/1894378 Title: Cannot boot after updating kernel to version 5.4.0-45 Status in linux package in Ubuntu: Confirmed Bug description: After the kernel update from version 5.4.0-42 to version 5.4.0-45 a few days ago, the boot process is ending in a BusyBox shell. Apparently it cannot properly identify my M.2 NMVe SSD device where my root partition is. Indeed, it is not listed in /dev (precisely: nvme0 is listed in /dev, but nvme0n1 and its partitions are not). For now, I'm solving this problem by booting the previous kernel, 5.4.0-42. This works fine. Also, an earlier attempt ended in a different shell that presented the error message "Gave up on waiting for root file system device". The UUID it indicated as missing is the correct UUID of my root partition, which also appears on /etc/fstab. I tried to re-build initrd.img-5.4.0-45-generic, but to no avail. Let me also mention that in another computer with a non-M.2 SSD, kernel 5.4.0-45 boots properly. This bug seems to be the one mentioned in the following "Unix & Linux" forum question: https://unix.stackexchange.com/questions/607694/ubuntu-20-04-01-not-booting-after-kernel-update Many thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 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.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ami3801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Sep 5 17:42:26 2020 HibernationDevice: RESUME=UUID=dd70dd06-717a-4acf-a85e-a9ad37cb92ea InstallationDate: Installed on 2017-10-04 (1066 days ago) InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1532:022a Razer USA, Ltd Razer Cynosa Chroma Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M |__ Port 8: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=85262f0d-cb92-475a-8174-2d6316e199a9 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-03 (125 days ago) dmi.bios.date: 06/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3807 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3807:bd06/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1894378/+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 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
apport information ** Tags added: apport-collected ** Description changed: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Sep 13 12:53 seq + crw-rw 1 root audio 116, 33 Sep 13 12:53 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.17 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fu
[Kernel-packages] [Bug 1895563] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410783/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13
[Kernel-packages] [Bug 1895563] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410775/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 1
[Kernel-packages] [Bug 1895563] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410785/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:
[Kernel-packages] [Bug 1895563] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410776/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 1
[Kernel-packages] [Bug 1895563] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410778/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116
[Kernel-packages] [Bug 1895563] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410781/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root aud
[Kernel-packages] [Bug 1895563] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410780/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116
[Kernel-packages] [Bug 1895563] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410784/+files/WifiSyslog.txt ** Description changed: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno
[Kernel-packages] [Bug 1895563] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410786/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 1
[Kernel-packages] [Bug 1895563] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410777/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 1
[Kernel-packages] [Bug 1895563] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410782/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116
[Kernel-packages] [Bug 1895563] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410779/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1
[Kernel-packages] [Bug 1895563] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410789/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1
[Kernel-packages] [Bug 1895563] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410793/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13
[Kernel-packages] [Bug 1895563] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410787/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 1
[Kernel-packages] [Bug 1895563] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410788/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 1
[Kernel-packages] [Bug 1895563] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410792/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116
[Kernel-packages] [Bug 1895563] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410794/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116,
[Kernel-packages] [Bug 1895563] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410790/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116
[Kernel-packages] [Bug 1895563] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410791/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root aud
[Kernel-packages] [Bug 1894378] Re: Cannot boot after updating kernel to version 5.4.0-45
PS: I've noticed several nvme related info on boot screen: `nvme nvme0: missing or invalid SUBNQN field.` ... and after 3 lines there is: `nvme nvme0: Identify descriptors failed (2)` could it be related? -- 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/1894378 Title: Cannot boot after updating kernel to version 5.4.0-45 Status in linux package in Ubuntu: Confirmed Bug description: After the kernel update from version 5.4.0-42 to version 5.4.0-45 a few days ago, the boot process is ending in a BusyBox shell. Apparently it cannot properly identify my M.2 NMVe SSD device where my root partition is. Indeed, it is not listed in /dev (precisely: nvme0 is listed in /dev, but nvme0n1 and its partitions are not). For now, I'm solving this problem by booting the previous kernel, 5.4.0-42. This works fine. Also, an earlier attempt ended in a different shell that presented the error message "Gave up on waiting for root file system device". The UUID it indicated as missing is the correct UUID of my root partition, which also appears on /etc/fstab. I tried to re-build initrd.img-5.4.0-45-generic, but to no avail. Let me also mention that in another computer with a non-M.2 SSD, kernel 5.4.0-45 boots properly. This bug seems to be the one mentioned in the following "Unix & Linux" forum question: https://unix.stackexchange.com/questions/607694/ubuntu-20-04-01-not-booting-after-kernel-update Many thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 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.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ami3801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Sep 5 17:42:26 2020 HibernationDevice: RESUME=UUID=dd70dd06-717a-4acf-a85e-a9ad37cb92ea InstallationDate: Installed on 2017-10-04 (1066 days ago) InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1532:022a Razer USA, Ltd Razer Cynosa Chroma Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M |__ Port 8: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=85262f0d-cb92-475a-8174-2d6316e199a9 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-03 (125 days ago) dmi.bios.date: 06/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3807 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3807:bd06/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1894378/+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 1894378] Re: Cannot boot after updating kernel to version 5.4.0-45
no, this is improbable to be related because when 5.4.0-42 is booted, these messages are there id `dmesg`, too. I've made this workaround so far: 1) sudo nano /etc/default/grub * GRUB_TIMEOUT=5 * GRUB_DEFAULT=saved * GRUB_SAVEDEFAULT=true 2) sudo update-grub so booting 5.4.0-42 now and waiting for further info... Thanks -- 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/1894378 Title: Cannot boot after updating kernel to version 5.4.0-45 Status in linux package in Ubuntu: Confirmed Bug description: After the kernel update from version 5.4.0-42 to version 5.4.0-45 a few days ago, the boot process is ending in a BusyBox shell. Apparently it cannot properly identify my M.2 NMVe SSD device where my root partition is. Indeed, it is not listed in /dev (precisely: nvme0 is listed in /dev, but nvme0n1 and its partitions are not). For now, I'm solving this problem by booting the previous kernel, 5.4.0-42. This works fine. Also, an earlier attempt ended in a different shell that presented the error message "Gave up on waiting for root file system device". The UUID it indicated as missing is the correct UUID of my root partition, which also appears on /etc/fstab. I tried to re-build initrd.img-5.4.0-45-generic, but to no avail. Let me also mention that in another computer with a non-M.2 SSD, kernel 5.4.0-45 boots properly. This bug seems to be the one mentioned in the following "Unix & Linux" forum question: https://unix.stackexchange.com/questions/607694/ubuntu-20-04-01-not-booting-after-kernel-update Many thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 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.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ami3801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Sep 5 17:42:26 2020 HibernationDevice: RESUME=UUID=dd70dd06-717a-4acf-a85e-a9ad37cb92ea InstallationDate: Installed on 2017-10-04 (1066 days ago) InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1532:022a Razer USA, Ltd Razer Cynosa Chroma Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M |__ Port 8: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=85262f0d-cb92-475a-8174-2d6316e199a9 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-03 (125 days ago) dmi.bios.date: 06/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3807 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3807:bd06/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1894378/+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 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
# Objective Monitor dirty files memory, Change to more suitable values. What it does: change from default 10 and 50%. My understanding: If `(vm.dirty_background_ratio/100) * memory size > largest file size`, then it should be ok.[reference needed] Note: `memory size` may be *available* memory size. Closing your memory- eating browsers may help.[reference needed] After editing the dirty values, reboot your system. It helped me. # Sources: - https://lonesysadmin.net/2013/12/22/better-linux-disk-caching-performance-vm-dirty_ratio/ - http://fooo.fr/~vjeux/github/github-recommandation/db/doc/manual/html/linux-performance-guide.html # Helpful commands ``` # View one dirty setting sudo sysctl -n vm.dirty_ratio # default 10 sudo sysctl -n vm.dirty_background_ratio# default 50 # View/monitor several settings cat /etc/sysctl.conf | egrep "dirty|writeback" # config file's dirty, if loaded. cat /proc/vmstat | egrep "dirty|writeback" # print dirty cat /proc/vmstat | egrep "nr_" # print all nr # View/monitor several settings : dynamic watch grep -A 1 dirty /proc/vmstat # Soft edit dirty ratios sudo sysctl vm.dirty_background_ratio=50 # set variable's value sudo sysctl vm.dirty_ratio=80 # set variable's value # Hard edit config file sudoedit /etc/sysctl.conf # hard edit config file. #vm.dirty_background_ratio = 50 # add without the hashtag #vm.dirty_ratio = 80 # add without the hashtag # # Save with nano : CTRL+X, then y sudo sysctl -p # reload current config file. Resets soft variables. # Check changes cat /etc/sysctl.conf | egrep "dirty|writeback" # cat /proc/vmstat | egrep "dirty|writeback" # ``` # Proposed diagnosize for your steps Before and after changing dirty values. ``` # 1. System is waiting cat /proc/vmstat | egrep "dirty|writeback" # 2. Just started copy cat /proc/vmstat | egrep "dirty|writeback" # 3. Copy is staled cat /proc/vmstat | egrep "dirty|writeback" # 4. Just cancelled copy via mouse cat /proc/vmstat | egrep "dirty|writeback" # 5. Waiting = nr_dirt goes down cat /proc/vmstat | egrep "dirty|writeback" # 6. Back to normal. cat /etc/sysctl.conf | egrep "dirty|writeback" ``` -- 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/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB Status in linux package in Ubuntu: Confirmed Bug description: Hi While copying many and large files to and from a USB drive, the system becomes incredibly slow and sometimes hangs. I watched the system monitor while it was running slowly but cpu was not above 50% at any time, the same for memory. I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD" laptop. Description: Ubuntu 13.04 Release: 13.04 nautilus: Installed: 1:3.6.3-0ubuntu16 Candidate: 1:3.6.3-0ubuntu16 Version table: *** 1:3.6.3-0ubuntu16 0 500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Aquire many large files (like your totally legit moviecollection) 2) Copy files to external HD 3) Open your browser and be sad when your system becomes incredibly slow after a few minutes This is my first bugreport so if I'm missing something, please tell me. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Aug 6 22:56:34 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-05-31 (67 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208993/+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 1894378] Re: Cannot boot after updating kernel to version 5.4.0-45
@crysman I have a NUC too. Is your nvme controller a Silicon Motion, Inc. Device 2263 (rev 03) (126f:2263)? It seems this controller somehow deviates from the specification. The commit I mentioned above (ea43d9709f) made the driver stricter, causing it to reject the device. A fix is available upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5bedd3afee8eb01ccd256f0cd2cc0fa6f841417a I can see it in Ubuntu's master-next branch: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?h=master-next&id=5ba7812ddae2589c0a4c1ded468ce49de35774d4 Hopefully next time an Ubuntu kernel is released the problem will go away. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894378 Title: Cannot boot after updating kernel to version 5.4.0-45 Status in linux package in Ubuntu: Confirmed Bug description: After the kernel update from version 5.4.0-42 to version 5.4.0-45 a few days ago, the boot process is ending in a BusyBox shell. Apparently it cannot properly identify my M.2 NMVe SSD device where my root partition is. Indeed, it is not listed in /dev (precisely: nvme0 is listed in /dev, but nvme0n1 and its partitions are not). For now, I'm solving this problem by booting the previous kernel, 5.4.0-42. This works fine. Also, an earlier attempt ended in a different shell that presented the error message "Gave up on waiting for root file system device". The UUID it indicated as missing is the correct UUID of my root partition, which also appears on /etc/fstab. I tried to re-build initrd.img-5.4.0-45-generic, but to no avail. Let me also mention that in another computer with a non-M.2 SSD, kernel 5.4.0-45 boots properly. This bug seems to be the one mentioned in the following "Unix & Linux" forum question: https://unix.stackexchange.com/questions/607694/ubuntu-20-04-01-not-booting-after-kernel-update Many thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 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.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ami3801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Sep 5 17:42:26 2020 HibernationDevice: RESUME=UUID=dd70dd06-717a-4acf-a85e-a9ad37cb92ea InstallationDate: Installed on 2017-10-04 (1066 days ago) InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1532:022a Razer USA, Ltd Razer Cynosa Chroma Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M |__ Port 8: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=85262f0d-cb92-475a-8174-2d6316e199a9 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-03 (125 days ago) dmi.bios.date: 06/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3807 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3807:bd06/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1894378/+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 1889282] Re: add pvtime support for arm64 guests
** Changed in: linux-aws (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux-aws-5.4 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1889282 Title: add pvtime support for arm64 guests Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws-5.4 package in Ubuntu: Fix Released Status in linux-aws-5.4 source package in Bionic: Fix Released Status in linux-aws source package in Focal: Fix Released Bug description: The mainline patch set "arm64: Stolen time support" and its prerequisites are required to support future AWS instance types: Reference: https://lore.kernel.org/kvm/20191011125930.40834-1-steven.pr...@arm.com/ The list of patches (from mainline) needed for linux-aws/focal is: e0685fa228fd arm64: Retrieve stolen time as paravirtualized guest ce4d5ca2b9dd arm/arm64: Make use of the SMCCC 1.1 wrapper 541625ac47ce arm/arm64: Provide a wrapper for SMCCC 1.1 calls 58772e9a3db7 KVM: arm64: Provide VCPU attributes for stolen time 8538cb22bbce KVM: Allow kvm_device_ops to be const 8564d6372a7d KVM: arm64: Support stolen time reporting via shared structure cac0f1b7285e KVM: Implement kvm_put_guest() b48c1a45a190 KVM: arm64: Implement PV_TIME_FEATURES call 55009c6ed2d2 KVM: arm/arm64: Factor out hypercall handling from PSCI code 6a7458485b39 KVM: arm64: Document PV-time interface e6ea46511b1a firmware: arm_sdei: use common SMCCC_CONDUIT_* a5520eac4d2d firmware/psci: use common SMCCC_CONDUIT_* 6848253ddeae arm: spectre-v2: use arm_smccc_1_1_get_conduit() c98bd2991728 arm64: errata: use arm_smccc_1_1_get_conduit() 6b7fe77c334a arm/arm64: smccc/psci: add arm_smccc_1_1_get_conduit() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1889282/+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 1892546] Re: Novalink (mkvterm command failure)
Ok. I see the patch got upstream accepted (commit `63ffcbdad738e3d1c857027789a2273df3337624`). We believe this need to be SRUed to Groovy, Focal, Bionic and Xenial. Do you agree? -- 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/1892546 Title: Novalink (mkvterm command failure) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Bug description: -- Problem Description -- drmgr command is failing while trying to open console for IBMi. Log snap shot: Please make sure you have specified a valid locale (check your NLSPATH and LANG environment variables. Your application will use english as the default. 2 07/15/20 16:01:25.393.531 UTC DEBUG pvmutil[12687.70366696995648]: (common/util/HmclDrmgrHelper.cpp:1036) Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 returned 255. Additional messages: /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 Validating I/O DLPAR capability...yes. failed to open /sys/bus/pci/slots/U9080.MHE.218BA37-V1-C8/power: No such file or directory failed to disable hotplug children Isolation failed for 3008 with -9001 Valid outstanding translations exist. ---Steps to Reproduce--- Create a VM from PowerVC on a Novalink managed host. Unmanage and manage the VM, this problem gets reproduced == I've tested a proposed fix and it does fix both the -9001 isolation errors after DLPAR remove and vterm state is still open, as well as the /dev/hcvsX index changing after a DLPAR remove/add. I will get that patch sent out to the upstream mailing list for merging. Patch submitted upstream: https://lore.kernel.org/linuxppc- dev/20200820234643.70412-1-tyr...@linux.ibm.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1892546/+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 1893817] Re: aws: enable PCI write-combine for arm64
Application of this will be deferred pending resolution of upstream discussion. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1893817 Title: aws: enable PCI write-combine for arm64 Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Bionic: Won't Fix Status in linux-aws source package in Focal: Won't Fix Status in linux-aws source package in Groovy: Won't Fix Bug description: To improve PCI performance on arm64 AWS instances, enable arch_can_pci_mmap_wc() via the patch: From: Clint Sbisa Subject: [PATCH] arm64: Enable PCI write-combine resources under sysfs https://lore.kernel.org/linux- pci/20200831151827.pumm2p54fyj7f...@amazon.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1893817/+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 1893817] Re: aws: enable PCI write-combine for arm64
** Changed in: linux-aws (Ubuntu Bionic) Status: In Progress => Won't Fix ** Changed in: linux-aws (Ubuntu Focal) Status: In Progress => Won't Fix ** Changed in: linux-aws (Ubuntu Groovy) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1893817 Title: aws: enable PCI write-combine for arm64 Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Bionic: Won't Fix Status in linux-aws source package in Focal: Won't Fix Status in linux-aws source package in Groovy: Won't Fix Bug description: To improve PCI performance on arm64 AWS instances, enable arch_can_pci_mmap_wc() via the patch: From: Clint Sbisa Subject: [PATCH] arm64: Enable PCI write-combine resources under sysfs https://lore.kernel.org/linux- pci/20200831151827.pumm2p54fyj7f...@amazon.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1893817/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
@paelzer To correct myself this (s390x) regression is not due to the snapd seeding issue, but LP: #1895576 which may have been already fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success rates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubunt
[Kernel-packages] [Bug 1894860] [NEW] Boot fails with newer kernel
You have been subscribed to a public bug: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal ident-mismatch ubiquity-19.10.21 -- Boot fails with newer kernel https://bugs.launchpad.net/bugs/1894860 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
