[Kernel-packages] [Bug 2043253] Re: zfs-mount-generator results in ZFS Boot Stuck - Please Give Root Password or Press CTRL+D to Continue
For what it is worth, I disabled these in debian/patches/series for my 2.2.0 based ppa at https://launchpad.net/~satadru- umich/+archive/ubuntu/zfs-experimental/ ... #ubuntu/0001-Revert-etc-systemd-zfs-mount-generator-serialise-han.patch #ubuntu/0002-Revert-etc-systemd-zfs-mount-generator-output-tweaks.patch #ubuntu/0003-Revert-etc-systemd-zfs-mount-generator-rewrite-in-C.patch #ubuntu/4000-zsys-support.patch #ubuntu/4100-disable-bpool-upgrade.patch #ubuntu/zfs-mount-container-start.patch #ubuntu/4510-silently-ignore-modprobe-failure.patch #ubuntu/4751-suppress-types.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2043253 Title: zfs-mount-generator results in ZFS Boot Stuck - Please Give Root Password or Press CTRL+D to Continue Status in zfs-linux package in Ubuntu: New Bug description: System Boot is Abnormal. Gives the message "Give root password for maintenance or press CTRL+D to continue". I installed Ubuntu 23.10 on NVME using debootstrap (UEFI install). I tried to re-generate the zfs cache and that seems to be set correctly in /etc/zfs/zfs-list.cache/rpool. It is possible that the /root, /var/log, /home/ folders contained some data already. I tried to empty them and reboot, to make sure that ZFS would mount correctly. Strangely enough zfs mount -a quickly finishes (without errors) while mount -a seems to enter an infinite loop. The culprit issue seems to be (based on log files): ``` Nov 10 14:00:04 UbuntuWorkstation11 systemd[1]: Reloading requested from client PID 1743 (unit emergency.service)... Nov 10 14:00:04 UbuntuWorkstation11 systemd[1]: Reloading... Nov 10 14:00:04 UbuntuWorkstation11 (sd-execu[1747]: /usr/lib/systemd/system-generators/zfs-mount-generator.orig failed with exit status 1. Nov 10 14:00:04 UbuntuWorkstation11 (sd-execu[1747]: /usr/lib/systemd/system-generators/zfs-mount-generator failed with exit status 1. Nov 10 14:00:04 UbuntuWorkstation11 ERROR: zfs-mount-generator failed and you requested a revert: Nov 10 14:00:04 UbuntuWorkstation11 systemd[1]: Reloading finished in 469 ms. Nov 10 14:00:04 UbuntuWorkstation11 systemd[1]: Reloading requested from client PID 1807 (unit emergency.service)... Nov 10 14:00:04 UbuntuWorkstation11 systemd[1]: Reloading... Nov 10 14:00:04 UbuntuWorkstation11 (sd-execu[1811]: /usr/lib/systemd/system-generators/zfs-mount-generator failed with exit status 1. Nov 10 14:00:04 UbuntuWorkstation11 (sd-execu[1811]: /usr/lib/systemd/system-generators/zfs-mount-generator.orig failed with exit status 1. Nov 10 14:00:04 UbuntuWorkstation11 ERROR: zfs-mount-generator failed and you requested a revert: Nov 10 14:00:05 UbuntuWorkstation11 systemd[1]: Reloading finished in 466 ms. Nov 10 14:00:05 UbuntuWorkstation11 systemd[1]: Reloading requested from client PID 1733 (unit emergency.service)... Nov 10 14:00:05 UbuntuWorkstation11 systemd[1]: Reloading... Nov 10 14:00:05 UbuntuWorkstation11 (sd-execu[1873]: /usr/lib/systemd/system-generators/zfs-mount-generator failed with exit status 1. Nov 10 14:00:05 UbuntuWorkstation11 (sd-execu[1873]: /usr/lib/systemd/system-generators/zfs-mount-generator.orig failed with exit status 1. Nov 10 14:00:05 UbuntuWorkstation11 ERROR: zfs-mount-generator failed and you requested a revert: Nov 10 14:00:05 UbuntuWorkstation11 systemd[1]: Reloading finished in 467 ms. Nov 10 14:00:12 UbuntuWorkstation11 systemd[1]: Stopped target emergency.target - Emergency Mode. ``` It's difficult to know where the issue lies exactly, if the script/program doesn't return more informations on where it's actually failing. ``` root@UbuntuWorkstation11:/# zfs list NAMEUSED AVAIL REFER MOUNTPOINT rpool 7.30G 1.75T96K none rpool/ROOT 7.29G 1.75T96K none rpool/ROOT/ubuntu 7.29G 1.75T 6.81G / rpool/ROOT/ubuntu/srv96K 1.75T96K /srv rpool/ROOT/ubuntu/tmp 408K 1.75T 136K /tmp rpool/ROOT/ubuntu/usr 424K 1.75T96K /usr rpool/ROOT/ubuntu/usr/local 328K 1.75T 192K /usr/local rpool/ROOT/ubuntu/var 262M 1.75T96K /var rpool/ROOT/ubuntu/var/games 96K 1.75T96K /var/games rpool/ROOT/ubuntu/var/lib 259M 1.75T 56.4M /var/lib rpool/ROOT/ubuntu/var/lib/AccountsService 224K 1.75T96K /var/lib/AccountsService rpool/ROOT/ubuntu/var/lib/NetworkManager236K 1.75T 116K /var/lib/NetworkManager rpool/ROOT/ubuntu/var/lib/apt 123M 1.75T 122M /var/lib/apt rpool/ROOT/ubuntu/var/lib/dpkg 77.9M 1.75T 65.7M /var/lib/dpkg rpool/ROOT/ubuntu/var/log
[Kernel-packages] [Bug 1981968] Re: bcmwl fails to build on the latest kinetic kernel 5.19
This patch is incomplete. The patches necessary are a combination of these: https://gist.github.com/joanbm/37fd0590f30b41e7e89ade6e242ca16e https://gist.github.com/joanbm/052d8e951ba63d5eb5b6960bfe4e031a (with those patches applied, I don't get any errors in my dmesg and the wireless card works in 5.19-rc8.) With 6.30.223.271+bdcom-0ubuntu9 I'm getting this error: [ 11.155980] netdevice: wlp3s0: Incorrect netdev->dev_addr [ 11.155994] WARNING: CPU: 5 PID: 1767 at net/core/dev_addr_lists.c:519 dev_addr_check.cold+0x65/0x9f [ 11.156000] Modules linked in: qrtr cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal snd_hda_codec_cirrus intel_powerclamp snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec kvm_intel snd_hda_core btusb snd_hwdep btrtl btbcm sch_fq_codel kvm snd_pcm sbs btintel rapl sbshc mei_pxp btmtk joydev mei_hdcp applesmc snd_seq_midi wl(POE) intel_cstate snd_seq_midi_event bluetooth snd_rawmidi input_leds snd_seq cmdlinepart ecdh_generic snd_seq_device ecc spi_nor bcm5974 apple_mfi_fastcharge snd_timer snd cfg80211 mei_me soundcore mei acpi_als industrialio_triggered_buffer kfifo_buf industrialio apple_gmux mac_hid apple_bl facetimehd(OE) videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc coretemp ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport ramoops reed_solomon pstore_blk pstore_zone mtd efi_pstore ip_tables x_tables autofs4 [ 11.156079] zfs(POE) zunicode(POE) zzstd(OE) zlua(OE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) z3fold lz4 lz4_compress hid_apple hid_generic uas usbhid hid usb_storage i915 nouveau mxm_wmi wmi drm_buddy i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper syscopyarea sysfillrect crct10dif_pclmul spi_intel_platform crc32_pclmul ghash_clmulni_intel spi_intel aesni_intel sysimgblt i2c_i801 fb_sys_fops crypto_simd nvme cryptd i2c_smbus drm nvme_core thunderbolt lpc_ich xhci_pci xhci_pci_renesas video [ 11.156144] Unloaded tainted modules: mtdpstore():1 chromeos_pstore():1 chromeos_pstore():1 mtdpstore():1 chromeos_pstore():1 mtdpstore():1 fjes():1 asus_ec_sensors():1 chromeos_pstore():1 mtdpstore():1 asus_ec_sensors():1 fjes():1 mtdpstore():1 chromeos_pstore():1 fjes():1 fjes():1 [ 11.156165] CPU: 5 PID: 1767 Comm: NetworkManager Tainted: P OE 5.19.0-rc8 #1 [ 11.156168] Hardware name: Apple Inc. MacBookPro11,3/Mac-2BD1B31983FE1663, BIOS 432.60.3.0.0 10/27/2021 [ 11.156170] RIP: 0010:dev_addr_check.cold+0x65/0x9f [ 11.156174] Code: 01 e8 2d 00 f6 ff 0f 0b 49 c7 c4 4c 9b 65 ac 80 3b 00 75 30 48 c7 c6 57 9b 65 ac 4c 89 e2 48 c7 c7 38 ff 6e ac e8 09 00 f6 ff <0f> 0b e9 13 af d5 ff 4c 8b 24 c5 80 96 35 ac eb d4 49 c7 c4 4c 9b [ 11.156176] RSP: 0018:b9e987a676e8 EFLAGS: 00010282 [ 11.156179] RAX: RBX: 917280fa5000 RCX: 0027 [ 11.156181] RDX: 9175ef360568 RSI: 0001 RDI: 9175ef360560 [ 11.156183] RBP: b9e987a676f8 R08: 0003 R09: fffd4b30 [ 11.156184] R10: R11: 002f R12: ac60b141 [ 11.156186] R13: c1950540 R14: 0001 R15: 917280fa5000 [ 11.156188] FS: 7f9b3e2994c0() GS:9175ef34() knlGS: [ 11.156190] CS: 0010 DS: ES: CR0: 80050033 [ 11.156192] CR2: 559309a0d846 CR3: 000126245004 CR4: 001706e0 [ 11.156194] Call Trace: [ 11.156196] [ 11.156199] __dev_open+0x45/0x1c0 [ 11.156203] __dev_change_flags+0x1a0/0x220 [ 11.156208] dev_change_flags+0x26/0x60 [ 11.156210] do_setlink+0x290/0x11d0 [ 11.156214] ? dbuf_rele_and_unlock+0x7e0/0x7e0 [zfs] [ 11.156311] ? __nla_validate_parse+0x5b/0xc10 [ 11.156316] ? spl_kmem_cache_alloc+0x10f/0x770 [spl] [ 11.156329] __rtnl_newlink+0x580/0xa10 [ 11.156333] ? spl_kmem_cache_free+0x71/0x1d0 [spl] [ 11.156343] ? kmem_cache_alloc_trace+0x1a6/0x310 [ 11.156347] rtnl_newlink+0x49/0x70 [ 11.156350] rtnetlink_rcv_msg+0x179/0x430 [ 11.156354] ? locked_inode_to_wb_and_lock_list+0x61/0x170 [ 11.156358] ? rtnl_calcit.isra.0+0x130/0x130 [ 11.156361] netlink_rcv_skb+0x53/0x100 [ 11.156366] rtnetlink_rcv+0x15/0x20 [ 11.156369] netlink_unicast+0x230/0x340 [ 11.156373] netlink_sendmsg+0x25e/0x4d0 [ 11.156376] sock_sendmsg+0x3a/0x50 [ 11.156380] sys_sendmsg+0x23a/0x260 [ 11.156382] ? import_iovec+0x1b/0x20 [ 11.156385] ? sendmsg_copy_msghdr+0x7b/0xa0 [ 11.156388] ? kfree+0xe7/0x320 [ 11.156392] ___sys_sendmsg+0x81/0xc0 [ 11.156395] ? proc_sys_write+0x13/0x20 [ 11.156398] ? new_sync_write+0xfb/0x170 [ 11.156401] ? icl_get_event_constraints+0x80/0x80 [ 11.156406] ? __fget_light+0xa3/0x120 [ 11.156411] __sys_sendmsg+0x5c/0xa0 [ 11.156414] __x64_sys_sendmsg+0x1d/0x20 [ 11.156417]
[Kernel-packages] [Bug 1964827] Re: zfs-linux upstream at 2.1.4, jammy has 2.1.2
Since the 2.1 branch is itself cherry-picks of updates backported from zfs master, it might make sense to just follow the 2.1 series for jammy, as opposed to re-cherry-picking from the upstream cherry-pick backports to the 2.1? Otherwise, there will be a lot of duplicated work... The zfs-devs appear to be pretty conservative with what they choose to backport... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964827 Title: zfs-linux upstream at 2.1.4, jammy has 2.1.2 Status in zfs-linux package in Ubuntu: Triaged Bug description: I know Jammy is in freeze zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues I have noticed (such as zfs complaining when waking for sleep, and also patches to support 5.16 better and also for the support of 5.17.) Please peruse the large number of important patches, which will make supporting this in LTS much easier: https://github.com/openzfs/zfs/pull/13063 I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev systems, and it works beautifully. I have attached the debian dir I put on top of the 2.1.3 source release which I used to generate debs for this release, which I have tested on a server and client desktop x86_64 machine running Ubuntu Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964827/+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 1964827] Re: zfs-linux upstream at 2.1.4, jammy has 2.1.2
See https://github.com/openzfs/zfs/commits/zfs-2.1.5-staging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964827 Title: zfs-linux upstream at 2.1.4, jammy has 2.1.2 Status in zfs-linux package in Ubuntu: Triaged Bug description: I know Jammy is in freeze zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues I have noticed (such as zfs complaining when waking for sleep, and also patches to support 5.16 better and also for the support of 5.17.) Please peruse the large number of important patches, which will make supporting this in LTS much easier: https://github.com/openzfs/zfs/pull/13063 I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev systems, and it works beautifully. I have attached the debian dir I put on top of the 2.1.3 source release which I used to generate debs for this release, which I have tested on a server and client desktop x86_64 machine running Ubuntu Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964827/+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 1964827] Re: zfs-linux upstream at 2.1.3, jammy has 2.1.2
Here's a ppa with working packages: https://launchpad.net/~satadru- umich/+archive/ubuntu/zfs-experimental -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964827 Title: zfs-linux upstream at 2.1.3, jammy has 2.1.2 Status in zfs-linux package in Ubuntu: Confirmed Bug description: I know Jammy is in freeze zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues I have noticed (such as zfs complaining when waking for sleep, and also patches to support 5.16 better and also for the support of 5.17.) Please peruse the large number of important patches, which will make supporting this in LTS much easier: https://github.com/openzfs/zfs/pull/13063 I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev systems, and it works beautifully. I have attached the debian dir I put on top of the 2.1.3 source release which I used to generate debs for this release, which I have tested on a server and client desktop x86_64 machine running Ubuntu Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964827/+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 1964827] [NEW] zfs-linux upstream at 2.1.3, jammy has 2.1.2
Public bug reported: I know Jammy is in freeze zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues I have noticed (such as zfs complaining when waking for sleep, and also patches to support 5.16 better and also for the support of 5.17.) Please peruse the large number of important patches, which will make supporting this in LTS much easier: https://github.com/openzfs/zfs/pull/13063 I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev systems, and it works beautifully. I have attached the debian dir I put on top of the 2.1.3 source release which I used to generate debs for this release, which I have tested on a server and client desktop x86_64 machine running Ubuntu Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "debian dir with relevant patches to make 2.1.3 work with ubuntu jammy" https://bugs.launchpad.net/bugs/1964827/+attachment/5568775/+files/zfs-linux_2.1.3ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964827 Title: zfs-linux upstream at 2.1.3, jammy has 2.1.2 Status in zfs-linux package in Ubuntu: New Bug description: I know Jammy is in freeze zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues I have noticed (such as zfs complaining when waking for sleep, and also patches to support 5.16 better and also for the support of 5.17.) Please peruse the large number of important patches, which will make supporting this in LTS much easier: https://github.com/openzfs/zfs/pull/13063 I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev systems, and it works beautifully. I have attached the debian dir I put on top of the 2.1.3 source release which I used to generate debs for this release, which I have tested on a server and client desktop x86_64 machine running Ubuntu Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964827/+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 1961801] Re: bcmwl builds with Kernel 5.17 w/ one small patch
The patch at https://gist.github.com/joanbm/37fd0590f30b41e7e89ade6e242ca16e from Joan Bruguera completely solves the issue. (Patch is attached.) ** Patch added: "broadcom-wl-fix-linux-5.17.patch" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+attachment/5564828/+files/broadcom-wl-fix-linux-5.17.patch ** Patch removed: "0030-add-support-for-Linux-5.17.patch" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+attachment/5562847/+files/0030-add-support-for-Linux-5.17.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1961801 Title: bcmwl builds with Kernel 5.17 w/ one small patch Status in bcmwl package in Ubuntu: New Bug description: At the very minimum, 5.17 replaces PDE_DATA with pde_data as per https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u The attached patch addresses that issue, but the module still doesn't work... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 Uname: Linux 5.16.10-051610-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 09:24:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+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 1961801] Re: bcmwl does not build with Kernel 5.17
This is my attempt at getting around the warning message, but clearly, more work will need to be done to update the driver for post-5.17. With just the following part of the patch the driver builds and runs fine on kernel 5.17-rc5. diff -Npaur a/src/wl/sys/wl_linux.c b/src/wl/sys/wl_linux.c --- a/src/wl/sys/wl_linux.c 2015-09-18 18:47:30.0 -0400 +++ b/src/wl/sys/wl_linux.c 2022-02-22 13:49:55.219274100 -0500 @@ -73,6 +74,10 @@ #error "No support for Kernel Rev <= 2.4.5, As the older kernel revs doesn't support Tasklets" #endif +#if (LINUX_VERSION_CODE >= KERNEL_VERSION(5, 17, 0)) +#define PDE_DATA pde_data +#endif + #include #include #include ** Patch removed: "Updated patch which allows compile but still causes a warning" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+attachment/5562822/+files/0030-add-support-for-Linux-5.17.patch ** Patch added: "0030-add-support-for-Linux-5.17.patch" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+attachment/5562847/+files/0030-add-support-for-Linux-5.17.patch ** Summary changed: - bcmwl does not build with Kernel 5.17 + bcmwl builds with Kernel 5.17 w/ one small patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1961801 Title: bcmwl builds with Kernel 5.17 w/ one small patch Status in bcmwl package in Ubuntu: New Bug description: At the very minimum, 5.17 replaces PDE_DATA with pde_data as per https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u The attached patch addresses that issue, but the module still doesn't work... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 Uname: Linux 5.16.10-051610-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 09:24:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+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 1961801] Re: bcmwl does not build with Kernel 5.17
This happens because of https://github.com/torvalds/linux/commit/adeef3e32146a8d2a73c399dc6f5d76a449131b1 netdev->dev_addr is a const now... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1961801 Title: bcmwl does not build with Kernel 5.17 Status in bcmwl package in Ubuntu: New Bug description: At the very minimum, 5.17 replaces PDE_DATA with pde_data as per https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u The attached patch addresses that issue, but the module still doesn't work... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 Uname: Linux 5.16.10-051610-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 09:24:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+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 1961801] Re: bcmwl does not build with Kernel 5.17
(Worth noting that is a warning, and the network still works.) ** Patch removed: "Fix PDE_DATA change in 5.17" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+attachment/5562741/+files/0030-add-support-for-Linux-5.17.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1961801 Title: bcmwl does not build with Kernel 5.17 Status in bcmwl package in Ubuntu: New Bug description: At the very minimum, 5.17 replaces PDE_DATA with pde_data as per https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u The attached patch addresses that issue, but the module still doesn't work... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 Uname: Linux 5.16.10-051610-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 09:24:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+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 1961801] Re: bcmwl does not build with Kernel 5.17
** Patch added: "Updated patch which allows compile but still causes a warning" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+attachment/5562822/+files/0030-add-support-for-Linux-5.17.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1961801 Title: bcmwl does not build with Kernel 5.17 Status in bcmwl package in Ubuntu: New Bug description: At the very minimum, 5.17 replaces PDE_DATA with pde_data as per https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u The attached patch addresses that issue, but the module still doesn't work... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 Uname: Linux 5.16.10-051610-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 09:24:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+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 1961801] Re: bcmwl does not build with Kernel 5.17
This is the kernel issue I get with the expanded patch. [7.508238] [ cut here ] [7.508239] netdevice: wlp3s0: Incorrect netdev->dev_addr [7.508257] WARNING: CPU: 3 PID: 1710 at net/core/dev_addr_lists.c:517 dev_addr_check.cold+0x65/0x9f [7.508267] Modules linked in: cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr intel_rapl_common joydev mei_hdcp mei_pxp x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_cirrus snd_hda_codec_generic applesmc snd_hda_codec_hdmi ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi btusb snd_hda_codec btrtl snd_hda_core kvm_intel btbcm btintel snd_hwdep btmtk snd_pcm kvm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event ecc rapl wl(POE) snd_rawmidi input_leds snd_seq bcm5974 intel_cstate snd_seq_device sbs snd_timer apple_mfi_fastcharge cfg80211 snd mei_me acpi_als industrialio_triggered_buffer efi_pstore mei kfifo_buf soundcore sbshc industrialio apple_gmux mac_hid apple_bl sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zzstd(OE) zlua(OE) zcommon(POE) znvpair(POE) zavl(POE) icp(POE) spl(OE) hid_apple hid_generic uas ax88179_178a usbhid usbnet usb_storage hid mii [7.508367] nouveau mxm_wmi wmi i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd cec nvme rc_core nvme_core i2c_i801 thunderbolt drm i2c_smbus lpc_ich xhci_pci xhci_pci_renesas video [7.508399] CPU: 3 PID: 1710 Comm: NetworkManager Tainted: P OE 5.17.0-051700rc5-generic #202202202230 [7.508403] Hardware name: Apple Inc. MacBookPro11,3/Mac-2BD1B31983FE1663, BIOS 432.60.3.0.0 10/27/2021 [7.508405] RIP: 0010:dev_addr_check.cold+0x65/0x9f [7.508411] Code: 01 e8 9e 2b f6 ff 0f 0b 49 c7 c4 81 9e 83 aa 80 3b 00 75 30 48 c7 c6 8c 9e 83 aa 4c 89 e2 48 c7 c7 90 5c 8d aa e8 7a 2b f6 ff <0f> 0b e9 8d c8 d5 ff 4c 8b 24 c5 a0 c5 52 aa eb d4 49 c7 c4 81 9e [7.508414] RSP: 0018:bb2287f5b380 EFLAGS: 00010282 [7.508417] RAX: RBX: 98f4810dd000 RCX: 0027 [7.508419] RDX: 98f7ef2e0988 RSI: 0001 RDI: 98f7ef2e0980 [7.508422] RBP: bb2287f5b390 R08: 0003 R09: fffd4a88 [7.508424] R10: R11: 0001 R12: aa7e7338 [7.508425] R13: c12fa460 R14: 0001 R15: 98f4810dd000 [7.508428] FS: 7f579d7664c0() GS:98f7ef2c() knlGS: [7.508431] CS: 0010 DS: ES: CR0: 80050033 [7.508433] CR2: 560784eca498 CR3: 00010bc26006 CR4: 001706e0 [7.508436] Call Trace: [7.508438] [7.508443] __dev_open+0x45/0x1c0 [7.508451] ? nvme_pci_setup_prps+0xe5/0x340 [nvme] [7.508459] __dev_change_flags+0x1a3/0x220 [7.508465] ? wlc_iovar_check+0x152/0x21b [wl] [7.508548] dev_change_flags+0x26/0x60 [7.508553] do_setlink+0x28a/0xc60 [7.508560] ? __nla_parse+0x25/0x30 [7.508566] ? cpumask_next+0x23/0x30 [7.508572] ? __nla_validate_parse+0x4c/0x1a0 [7.508577] ? inet6_set_link_af+0x4e/0xb0 [7.508583] __rtnl_newlink+0x61a/0xa20 [7.508589] ? skb_free_head+0x68/0x80 [7.508595] ? kfree+0xab/0x410 [7.508600] ? __kmalloc_node_track_caller+0x1cd/0x3e0 [7.508605] ? cpumask_next_and+0x24/0x30 [7.508610] ? update_sg_lb_stats+0x78/0x560 [7.508623] ? kmem_cache_alloc_trace+0x1a6/0x320 [7.508627] rtnl_newlink+0x49/0x70 [7.508632] rtnetlink_rcv_msg+0x16e/0x3f0 [7.508637] ? rtnl_calcit.isra.0+0x130/0x130 [7.508641] netlink_rcv_skb+0x55/0x100 [7.508647] rtnetlink_rcv+0x15/0x20 [7.508651] netlink_unicast+0x232/0x340 [7.508655] netlink_sendmsg+0x25e/0x4d0 [7.508659] sock_sendmsg+0x65/0x70 [7.508665] sys_sendmsg+0x24e/0x290 [7.508669] ? import_iovec+0x31/0x40 [7.508672] ? sendmsg_copy_msghdr+0x7b/0xa0 [7.508679] ___sys_sendmsg+0x81/0xc0 [7.508685] ? rtnl_unlock+0xe/0x10 [7.508689] ? kfree+0xab/0x410 [7.508692] ? addrconf_sysctl_forward+0xbc/0xd0 [7.508697] ? __fget_light+0xa3/0x120 [7.508702] __sys_sendmsg+0x62/0xb0 [7.508709] __x64_sys_sendmsg+0x1d/0x20 [7.508714] do_syscall_64+0x5c/0xc0 [7.508717] ? syscall_exit_to_user_mode+0x27/0x50 [7.508722] ? __do_sys_gettid+0x1b/0x20 [7.508728] ? do_syscall_64+0x69/0xc0 [7.508731] ? __rseq_handle_notify_resume+0x2d/0xd0 [7.508736] ? exit_to_user_mode_loop+0x10d/0x160 [7.508742] ? exit_to_user_mode_prepare+0x37/0xb0 [7.508746] ? syscall_exit_to_user_mode+0x27/0x50 [7.508750] ? __x64_sys_close+0x11/0x40 [7.508754] ? do_syscall_64+0x69/0xc0 [7.508756] ? do_syscall_64+0x69/0xc0 [7.508759] ? do_syscall_64+0x69/0xc0 [7.508761] ?
[Kernel-packages] [Bug 1961801] [NEW] bcmwl does not build with Kernel 5.17
Public bug reported: At the very minimum, 5.17 replaces PDE_DATA with pde_data as per https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u The attached patch addresses that issue, but the module still doesn't work... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 Uname: Linux 5.16.10-051610-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 09:24:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Patch added: "Fix PDE_DATA change in 5.17" https://bugs.launchpad.net/bugs/1961801/+attachment/5562741/+files/0030-add-support-for-Linux-5.17.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1961801 Title: bcmwl does not build with Kernel 5.17 Status in bcmwl package in Ubuntu: New Bug description: At the very minimum, 5.17 replaces PDE_DATA with pde_data as per https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u The attached patch addresses that issue, but the module still doesn't work... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 Uname: Linux 5.16.10-051610-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 22 09:24:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+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 1945842] [NEW] Newer kernel still has no display w/ KMS enabled
Public bug reported: This is using KMS, not fKMS... ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-raspi (not installed) ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14 Uname: Linux 5.13.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: satadru1164 F pulseaudio /dev/snd/pcmC1D0p: satadru1164 F...m pulseaudio /dev/snd/controlC0: satadru1164 F pulseaudio CasperMD5CheckResult: unknown Date: Fri Oct 1 20:22:10 2021 ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=vt100 XDG_RUNTIME_DIR= PATH=(custom, user) ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:09:99:D7 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait quiet splash video=HDMI-A-1:1080x1920M@60,rotate=90,panel_orientation=right_side_up drm.edid_firmware=edid/Waveshare5.5Amoled4.bin fbcon=rotate:1 fsck.mode=force fsck.repair=yes RelatedPackageVersions: linux-restricted-modules-5.13.0-1008-raspi N/A linux-backports-modules-5.13.0-1008-raspi N/A linux-firmware 1.201 SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-08-17 (45 days ago) acpidump: ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image impish raspi-image -- 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/1945842 Title: Newer kernel still has no display w/ KMS enabled Status in linux-raspi package in Ubuntu: New Bug description: This is using KMS, not fKMS... ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-raspi (not installed) ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14 Uname: Linux 5.13.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: satadru1164 F pulseaudio /dev/snd/pcmC1D0p: satadru1164 F...m pulseaudio /dev/snd/controlC0: satadru1164 F pulseaudio CasperMD5CheckResult: unknown Date: Fri Oct 1 20:22:10 2021 ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=vt100 XDG_RUNTIME_DIR= PATH=(custom, user) ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:09:99:D7 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait quiet splash video=HDMI-A-1:1080x1920M@60,rotate=90,panel_orientation=right_side_up drm.edid_firmware=edid/Waveshare5.5Amoled4.bin fbcon=rotate:1 fsck.mode=force fsck.repair=yes RelatedPackageVersions: linux-restricted-modules-5.13.0-1008-raspi N/A linux-backports-modules-5.13.0-1008-raspi N/A linux-firmware 1.201 SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-08-17 (45 days ago) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1945842/+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 1944397] [NEW] hdmi-audio error breaks hdmi
Public bug reported: Have a HDMI display w/o audio hooked up to this RPI4B. With the latest kernel update the screen does not turn on due to this. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1007-raspi 5.13.0-1007.8 ProcVersionSignature: Ubuntu 5.13.0-1007.8-raspi 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Sep 20 20:56:14 2021 ImageMediaBuild: 20210421 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=vt100 XDG_RUNTIME_DIR= PATH=(custom, user) SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-08-17 (34 days ago) ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image impish package-from-proposed raspi-image -- 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/1944397 Title: hdmi-audio error breaks hdmi Status in linux-raspi package in Ubuntu: New Bug description: Have a HDMI display w/o audio hooked up to this RPI4B. With the latest kernel update the screen does not turn on due to this. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1007-raspi 5.13.0-1007.8 ProcVersionSignature: Ubuntu 5.13.0-1007.8-raspi 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Sep 20 20:56:14 2021 ImageMediaBuild: 20210421 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=vt100 XDG_RUNTIME_DIR= PATH=(custom, user) SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-08-17 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1944397/+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 1944053] [NEW] linux-image-raspi 5.13 kernels don't boot on rpi4b
Public bug reported: The hirsute 5.11.x linux-image-raspi kernels boot fine on my rpi4b, but the 5.13.x kernels freeze before showing anything on the connected hdmi screen. Reverting to the 5.11.x hirsute kernels fixes boot. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-raspi 5.13.0.1006.12 ProcVersionSignature: Ubuntu 5.11.0-1016.17-raspi 5.11.22 Uname: Linux 5.11.0-1016-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: satadru1129 F pulseaudio /dev/snd/controlC0: satadru1129 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Sep 18 14:32:04 2021 ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, user) ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:640x480M@60 smsc95xx.macaddr=DC:A6:32:09:99:D7 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait quiet splash video=HDMI-A-1:1080x1920M@60,rotate=90,panel_orientation=right_side_up drm.edid_firmware=edid/Waveshare5.5Amoled4.bin fbcon=rotate:1 fsck.mode=force fsck.repair=yes cgroup_enable=cpuset cgroup_enable=memory cgroup_memory=1 intremap=off RelatedPackageVersions: linux-restricted-modules-5.11.0-1016-raspi N/A linux-backports-modules-5.11.0-1016-raspi N/A linux-firmware 1.200 SourcePackage: linux-raspi StagingDrivers: bcm2835_mmal_vchiq bcm2835_v4l2 vc_sm_cma snd_bcm2835 bcm2835_isp bcm2835_codec UpgradeStatus: Upgraded to impish on 2021-08-17 (32 days ago) acpidump: ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image impish raspi-image staging -- 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/1944053 Title: linux-image-raspi 5.13 kernels don't boot on rpi4b Status in linux-raspi package in Ubuntu: New Bug description: The hirsute 5.11.x linux-image-raspi kernels boot fine on my rpi4b, but the 5.13.x kernels freeze before showing anything on the connected hdmi screen. Reverting to the 5.11.x hirsute kernels fixes boot. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-raspi 5.13.0.1006.12 ProcVersionSignature: Ubuntu 5.11.0-1016.17-raspi 5.11.22 Uname: Linux 5.11.0-1016-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: satadru1129 F pulseaudio /dev/snd/controlC0: satadru1129 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Sep 18 14:32:04 2021 ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, user) ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:640x480M@60 smsc95xx.macaddr=DC:A6:32:09:99:D7 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait quiet splash video=HDMI-A-1:1080x1920M@60,rotate=90,panel_orientation=right_side_up drm.edid_firmware=edid/Waveshare5.5Amoled4.bin fbcon=rotate:1 fsck.mode=force fsck.repair=yes cgroup_enable=cpuset cgroup_enable=memory cgroup_memory=1 intremap=off RelatedPackageVersions: linux-restricted-modules-5.11.0-1016-raspi N/A linux-backports-modules-5.11.0-1016-raspi N/A linux-firmware 1.200 SourcePackage: linux-raspi StagingDrivers: bcm2835_mmal_vchiq bcm2835_v4l2 vc_sm_cma snd_bcm2835 bcm2835_isp bcm2835_codec UpgradeStatus: Upgraded to impish on 2021-08-17 (32 days ago) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1944053/+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 1919398] Re: amdgpu error amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0
This is not a problem in the 5.10 kernels. -- 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/1919398 Title: amdgpu error amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0 Status in linux-meta package in Ubuntu: New Bug description: Running 5.11.0-11-lowlatency on radeon RX 5500 XT "[AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5)" Primary application is Kodi, which freezes on start, requiring the process to be restarted (sometimes this requires a reboot of the entire machine.) dmesg shows this error: [ 1567.704562] [drm] amdgpu_dm_irq_schedule_work FAILED src 4 [ 1567.974561] [drm] amdgpu_dm_irq_schedule_work FAILED src 4 [ 1568.704568] [drm] amdgpu_dm_irq_schedule_work FAILED src 4 [ 1570.025161] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:72:crtc-0] flip_done timed out [ 1571.049175] [drm:do_aquire_global_lock.isra.0 [amdgpu]] *ERROR* [CRTC:72:crtc-0] hw_done or flip_done timed out [ 1581.289438] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:72:crtc-0] flip_done timed out [ 1591.529598] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:60:plane-4] flip_done timed out [ 1591.594241] [ cut here ] [ 1591.594243] WARNING: CPU: 1 PID: 54905 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7754 amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0 [amdgpu] [ 1591.594436] Modules linked in: hidp xt_nat rfcomm veth nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 ip6_udp_tunnel udp_tunnel libcurve25519_generic libchacha libblake2s_generic xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink bridge stp llc overlay cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 xfs intel_rapl_msr mei_hdcp btusb btrtl btbcm btintel bluetooth ecdh_generic ecc intel_rapl_common x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm rapl intel_cstate efi_pstore intel_wmi_thunderbolt snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi ee1004 snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec snd_hda_core soundwire_bus [ 1591.594476] snd_soc_core snd_compress snd_usb_audio ac97_bus snd_pcm_dmaengine snd_usbmidi_lib snd_hwdep snd_seq_midi uvcvideo snd_seq_midi_event videobuf2_vmalloc videobuf2_memops snd_pcm videobuf2_v4l2 snd_rawmidi videobuf2_common cdc_acm joydev input_leds snd_seq videodev mc snd_seq_device snd_timer mei_me mei intel_pch_thermal snd soundcore mac_hid acpi_pad sch_fq_codel nct6775 hwmon_vid coretemp msr parport_pc ppdev lp parport binder_linux nfsd ashmem_linux(CE) auth_rpcgss nfs_acl lockd grace sunrpc nfs_ssc ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zzstd(O) zlua(OE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_magicmouse mlx4_ib ib_uverbs ib_core mlx4_en hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid uas usb_storage amdgpu iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm mxm_wmi drm_kms_helper crct10dif_pclmul crc32_pclmul [ 1591.594527] syscopyarea sysfillrect sysimgblt fb_sys_fops ghash_clmulni_intel cec aesni_intel rc_core crypto_simd cryptd glue_helper mpt3sas nvme drm mlx4_core e1000e i2c_i801 i2c_smbus raid_class nvme_core scsi_transport_sas ahci libahci xhci_pci xhci_pci_renesas wmi video [ 1591.594544] CPU: 1 PID: 54905 Comm: kworker/1:2 Tainted: PWC OE 5.11.0-11-lowlatency #12-Ubuntu [ 1591.594546] Hardware name: MSI MS-7998/C236A WORKSTATION (MS-7998), BIOS 2.A0 06/15/2018 [ 1591.594548] Workqueue: events dm_irq_work_func [amdgpu] [ 1591.594689] RIP: 0010:amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0 [amdgpu] [ 1591.594826] Code: ff 48 8b 45 a8 48 c7 c7 12 9f c1 c0 4c 89 55 80 8b b0 f0 03 00 00 e8 e0 04 c9 ff 0f b6 55 a3 4c 8b 55 80 e9 24 fa ff ff 0f 0b <0f> 0b e9 89 fe ff ff 0f 0b e9 a2 fe ff ff e8 9e f3 af f9 66 66 2e [ 1591.594828] RSP: 0018:a84784bf79f0 EFLAGS: 00010002 [ 1591.594830] RAX: 0287 RBX: 0004 RCX: 0461 [ 1591.594831] RDX: 0001 RSI: 0293 RDI: 908517ea0188 [ 1591.594832] RBP: a84784bf7ab0 R08: 0002 R09: 0001 [ 1591.594833] R10: R11: 90851a35b918 R12: 0287 [ 1591.594834] R13: 90851a35b800 R14: 9085eb9d9d00 R15: 9087e43c7600 [ 1591.594835] FS: ()
[Kernel-packages] [Bug 1919398] Re: amdgpu error amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0
upstream bug opened at https://gitlab.freedesktop.org/drm/amd/-/issues/1531 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1531 https://gitlab.freedesktop.org/drm/amd/-/issues/1531 -- 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/1919398 Title: amdgpu error amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0 Status in linux-meta package in Ubuntu: New Bug description: Running 5.11.0-11-lowlatency on radeon RX 5500 XT "[AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5)" Primary application is Kodi, which freezes on start, requiring the process to be restarted (sometimes this requires a reboot of the entire machine.) dmesg shows this error: [ 1567.704562] [drm] amdgpu_dm_irq_schedule_work FAILED src 4 [ 1567.974561] [drm] amdgpu_dm_irq_schedule_work FAILED src 4 [ 1568.704568] [drm] amdgpu_dm_irq_schedule_work FAILED src 4 [ 1570.025161] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:72:crtc-0] flip_done timed out [ 1571.049175] [drm:do_aquire_global_lock.isra.0 [amdgpu]] *ERROR* [CRTC:72:crtc-0] hw_done or flip_done timed out [ 1581.289438] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:72:crtc-0] flip_done timed out [ 1591.529598] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:60:plane-4] flip_done timed out [ 1591.594241] [ cut here ] [ 1591.594243] WARNING: CPU: 1 PID: 54905 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7754 amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0 [amdgpu] [ 1591.594436] Modules linked in: hidp xt_nat rfcomm veth nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 ip6_udp_tunnel udp_tunnel libcurve25519_generic libchacha libblake2s_generic xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink bridge stp llc overlay cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 xfs intel_rapl_msr mei_hdcp btusb btrtl btbcm btintel bluetooth ecdh_generic ecc intel_rapl_common x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm rapl intel_cstate efi_pstore intel_wmi_thunderbolt snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi ee1004 snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec snd_hda_core soundwire_bus [ 1591.594476] snd_soc_core snd_compress snd_usb_audio ac97_bus snd_pcm_dmaengine snd_usbmidi_lib snd_hwdep snd_seq_midi uvcvideo snd_seq_midi_event videobuf2_vmalloc videobuf2_memops snd_pcm videobuf2_v4l2 snd_rawmidi videobuf2_common cdc_acm joydev input_leds snd_seq videodev mc snd_seq_device snd_timer mei_me mei intel_pch_thermal snd soundcore mac_hid acpi_pad sch_fq_codel nct6775 hwmon_vid coretemp msr parport_pc ppdev lp parport binder_linux nfsd ashmem_linux(CE) auth_rpcgss nfs_acl lockd grace sunrpc nfs_ssc ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zzstd(O) zlua(OE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_magicmouse mlx4_ib ib_uverbs ib_core mlx4_en hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid uas usb_storage amdgpu iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm mxm_wmi drm_kms_helper crct10dif_pclmul crc32_pclmul [ 1591.594527] syscopyarea sysfillrect sysimgblt fb_sys_fops ghash_clmulni_intel cec aesni_intel rc_core crypto_simd cryptd glue_helper mpt3sas nvme drm mlx4_core e1000e i2c_i801 i2c_smbus raid_class nvme_core scsi_transport_sas ahci libahci xhci_pci xhci_pci_renesas wmi video [ 1591.594544] CPU: 1 PID: 54905 Comm: kworker/1:2 Tainted: PWC OE 5.11.0-11-lowlatency #12-Ubuntu [ 1591.594546] Hardware name: MSI MS-7998/C236A WORKSTATION (MS-7998), BIOS 2.A0 06/15/2018 [ 1591.594548] Workqueue: events dm_irq_work_func [amdgpu] [ 1591.594689] RIP: 0010:amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0 [amdgpu] [ 1591.594826] Code: ff 48 8b 45 a8 48 c7 c7 12 9f c1 c0 4c 89 55 80 8b b0 f0 03 00 00 e8 e0 04 c9 ff 0f b6 55 a3 4c 8b 55 80 e9 24 fa ff ff 0f 0b <0f> 0b e9 89 fe ff ff 0f 0b e9 a2 fe ff ff e8 9e f3 af f9 66 66 2e [ 1591.594828] RSP: 0018:a84784bf79f0 EFLAGS: 00010002 [ 1591.594830] RAX: 0287 RBX: 0004 RCX: 0461 [ 1591.594831] RDX: 0001 RSI: 0293 RDI: 908517ea0188 [ 1591.594832] RBP: a84784bf7ab0 R08: 0002 R09: 0001 [ 1591.594833] R10: R11: 90851a35b918 R12:
[Kernel-packages] [Bug 1919398] [NEW] amdgpu error amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0
Public bug reported: Running 5.11.0-11-lowlatency on radeon RX 5500 XT "[AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5)" Primary application is Kodi, which freezes on start, requiring the process to be restarted (sometimes this requires a reboot of the entire machine.) dmesg shows this error: [ 1567.704562] [drm] amdgpu_dm_irq_schedule_work FAILED src 4 [ 1567.974561] [drm] amdgpu_dm_irq_schedule_work FAILED src 4 [ 1568.704568] [drm] amdgpu_dm_irq_schedule_work FAILED src 4 [ 1570.025161] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:72:crtc-0] flip_done timed out [ 1571.049175] [drm:do_aquire_global_lock.isra.0 [amdgpu]] *ERROR* [CRTC:72:crtc-0] hw_done or flip_done timed out [ 1581.289438] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:72:crtc-0] flip_done timed out [ 1591.529598] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:60:plane-4] flip_done timed out [ 1591.594241] [ cut here ] [ 1591.594243] WARNING: CPU: 1 PID: 54905 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7754 amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0 [amdgpu] [ 1591.594436] Modules linked in: hidp xt_nat rfcomm veth nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 ip6_udp_tunnel udp_tunnel libcurve25519_generic libchacha libblake2s_generic xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink bridge stp llc overlay cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 xfs intel_rapl_msr mei_hdcp btusb btrtl btbcm btintel bluetooth ecdh_generic ecc intel_rapl_common x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm rapl intel_cstate efi_pstore intel_wmi_thunderbolt snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi ee1004 snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec snd_hda_core soundwire_bus [ 1591.594476] snd_soc_core snd_compress snd_usb_audio ac97_bus snd_pcm_dmaengine snd_usbmidi_lib snd_hwdep snd_seq_midi uvcvideo snd_seq_midi_event videobuf2_vmalloc videobuf2_memops snd_pcm videobuf2_v4l2 snd_rawmidi videobuf2_common cdc_acm joydev input_leds snd_seq videodev mc snd_seq_device snd_timer mei_me mei intel_pch_thermal snd soundcore mac_hid acpi_pad sch_fq_codel nct6775 hwmon_vid coretemp msr parport_pc ppdev lp parport binder_linux nfsd ashmem_linux(CE) auth_rpcgss nfs_acl lockd grace sunrpc nfs_ssc ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zzstd(O) zlua(OE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_magicmouse mlx4_ib ib_uverbs ib_core mlx4_en hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid uas usb_storage amdgpu iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm mxm_wmi drm_kms_helper crct10dif_pclmul crc32_pclmul [ 1591.594527] syscopyarea sysfillrect sysimgblt fb_sys_fops ghash_clmulni_intel cec aesni_intel rc_core crypto_simd cryptd glue_helper mpt3sas nvme drm mlx4_core e1000e i2c_i801 i2c_smbus raid_class nvme_core scsi_transport_sas ahci libahci xhci_pci xhci_pci_renesas wmi video [ 1591.594544] CPU: 1 PID: 54905 Comm: kworker/1:2 Tainted: PWC OE 5.11.0-11-lowlatency #12-Ubuntu [ 1591.594546] Hardware name: MSI MS-7998/C236A WORKSTATION (MS-7998), BIOS 2.A0 06/15/2018 [ 1591.594548] Workqueue: events dm_irq_work_func [amdgpu] [ 1591.594689] RIP: 0010:amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0 [amdgpu] [ 1591.594826] Code: ff 48 8b 45 a8 48 c7 c7 12 9f c1 c0 4c 89 55 80 8b b0 f0 03 00 00 e8 e0 04 c9 ff 0f b6 55 a3 4c 8b 55 80 e9 24 fa ff ff 0f 0b <0f> 0b e9 89 fe ff ff 0f 0b e9 a2 fe ff ff e8 9e f3 af f9 66 66 2e [ 1591.594828] RSP: 0018:a84784bf79f0 EFLAGS: 00010002 [ 1591.594830] RAX: 0287 RBX: 0004 RCX: 0461 [ 1591.594831] RDX: 0001 RSI: 0293 RDI: 908517ea0188 [ 1591.594832] RBP: a84784bf7ab0 R08: 0002 R09: 0001 [ 1591.594833] R10: R11: 90851a35b918 R12: 0287 [ 1591.594834] R13: 90851a35b800 R14: 9085eb9d9d00 R15: 9087e43c7600 [ 1591.594835] FS: () GS:90903ec8() knlGS: [ 1591.594837] CS: 0010 DS: ES: CR0: 80050033 [ 1591.594838] CR2: 7fb1c0e74d12 CR3: 000c23810004 CR4: 003706e0 [ 1591.594839] Call Trace: [ 1591.594842] amdgpu_dm_atomic_commit_tail+0xc66/0x1280 [amdgpu] [ 1591.594980] ? wake_up_klogd.part.0+0x3b/0x50 [ 1591.594983] ? vprintk_emit+0xae/0x110 [ 1591.594987]
[Kernel-packages] [Bug 1872908] Re: bcmwl kernel module does not build with 5.6.0 kernel or later
Arch has patches for kernels through 5.10:
See
https://github.com/archlinux/svntogit-community/tree/packages/broadcom-wl-dkms/trunk
and also
https://github.com/archlinux/svntogit-community/blob/packages/broadcom-wl-dkms/trunk/PKGBUILD
Note the patch for 5.10:
https://github.com/archlinux/svntogit-community/blob/packages/broadcom-wl-dkms/trunk/011-linux59.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1872908
Title:
bcmwl kernel module does not build with 5.6.0 kernel or later
Status in bcmwl package in Ubuntu:
Fix Released
Status in bcmwl source package in Focal:
Triaged
Bug description:
After kernel update to 5.6.0-1007-oem wifi stopped working.
Turned out dkms is unable to build the bcmwl module.
The make log shows:
ubuntu@ubuntu-inspiron-5482:~$ cat
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64)
ons 15 apr 2020 09:19:05 CEST
make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
|^~~
|ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18:
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a
cast [-Wint-conversion]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15:
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58:
error: passing argument 4 of
[Kernel-packages] [Bug 1896348] Re: wifi not working due to bcmwl-kernel-source
*** This bug is a duplicate of bug 1878045 *** https://bugs.launchpad.net/bugs/1878045 Fix also mentioned here: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/comments/7 ** This bug has been marked a duplicate of bug 1878045 doing dist-upgrade got error related do Broadcom -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1896348 Title: wifi not working due to bcmwl-kernel-source Status in bcmwl package in Ubuntu: Confirmed Bug description: wifi not working installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 18:07:20 2020 InstallationDate: Installed on 2020-09-18 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to groovy on 2020-09-19 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1896348/+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 1896348] Re: wifi not working due to bcmwl-kernel-source
*** This bug is a duplicate of bug 1878045 *** https://bugs.launchpad.net/bugs/1878045 The problem is due to 0028-add-support-for-linux-5.6.patch having many of a/src/src/... instead of a/src/... Fixing that patch solves this for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1896348 Title: wifi not working due to bcmwl-kernel-source Status in bcmwl package in Ubuntu: Confirmed Bug description: wifi not working installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 18:07:20 2020 InstallationDate: Installed on 2020-09-18 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to groovy on 2020-09-19 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1896348/+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 1895615] Re: Backlight adjustment doesn't work on Google Pixel Slate
Thanks! I've submitted a version to intel-gfx mailing list as [RFC PATCH 1/1] Remove DPCD Aux Backlight Control PWM_PIN check after discussions with Redhat's Lyude Paul. https://lists.freedesktop.org/archives/intel- gfx/2020-September/248938.html -- 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/1895615 Title: Backlight adjustment doesn't work on Google Pixel Slate Status in linux package in Ubuntu: Confirmed Bug description: The Pixel Slate/nocturne backlight does not work due to DPCD logic not identifying the DPCD backlight connection since there is no PWM on the nocturne or eve devices. ChromeOS documentation of disconnected PWM: https://chromium- review.googlesource.com/c/chromiumos/overlays/board-overlays/+/1171922 Discussion of issue & solution: https://github.com/EmbeddedAndroid /linux-eve/issues/2#issuecomment-561382927 This can be fixed with a simple patch which I have applied successfully to mainline 5.9-rc5: https://gist.github.com/satmandu/d6c2192f66cd14525049fd34d356d71d Luckily the Ubuntu kernel patches set i915.enable_psr=0 which keeps Panel Self Refresh from dimming the backlight at boot, but that isn't even needed for this device once the backlight is hooked up correctly. (As a bonus the keyboard backlight also starts working properly at boot.) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-lowlatency 5.8.0.18.22 ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4 Uname: Linux 5.8.0-18-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Mon Sep 14 23:52:45 2020 InstallationDate: Installed on 2020-08-24 (21 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200728) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 18d1:5030 Google Inc. Hammer Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nocturne ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-lowlatency root=UUID=90e26b2a-aaad-4576-8e90-1962b97d4e96 ro fsck.repair=yes fsck.mode=force PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-18-lowlatency N/A linux-backports-modules-5.8.0-18-lowlatency N/A linux-firmware 1.190 SourcePackage: linux StagingDrivers: ipu3_imgu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.bios.version: Google_Nocturne.10984.90.0 dmi.board.name: Nocturne dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrGoogle_Nocturne.10984.90.0:bd06/04/2019:br4.0:efr0.0:svnGoogle:pnNocturne:pvr1.0:rvnGoogle:rnNocturne:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nocturne dmi.product.name: Nocturne dmi.product.version: 1.0 dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895615/+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 1895615] [NEW] Backlight adjustment doesn't work on Google Pixel Slate
Public bug reported: The Pixel Slate/nocturne backlight does not work due to DPCD logic not identifying the DPCD backlight connection since there is no PWM on the nocturne or eve devices. ChromeOS documentation of disconnected PWM: https://chromium- review.googlesource.com/c/chromiumos/overlays/board-overlays/+/1171922 Discussion of issue & solution: https://github.com/EmbeddedAndroid /linux-eve/issues/2#issuecomment-561382927 This can be fixed with a simple patch which I have applied successfully to mainline 5.9-rc5: https://gist.github.com/satmandu/d6c2192f66cd14525049fd34d356d71d Luckily the Ubuntu kernel patches set i915.enable_psr=0 which keeps Panel Self Refresh from dimming the backlight at boot, but that isn't even needed for this device once the backlight is hooked up correctly. (As a bonus the keyboard backlight also starts working properly at boot.) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-lowlatency 5.8.0.18.22 ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4 Uname: Linux 5.8.0-18-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Mon Sep 14 23:52:45 2020 InstallationDate: Installed on 2020-08-24 (21 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200728) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 18d1:5030 Google Inc. Hammer Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Nocturne ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-lowlatency root=UUID=90e26b2a-aaad-4576-8e90-1962b97d4e96 ro fsck.repair=yes fsck.mode=force PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-18-lowlatency N/A linux-backports-modules-5.8.0-18-lowlatency N/A linux-firmware 1.190 SourcePackage: linux StagingDrivers: ipu3_imgu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.bios.version: Google_Nocturne.10984.90.0 dmi.board.name: Nocturne dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrGoogle_Nocturne.10984.90.0:bd06/04/2019:br4.0:efr0.0:svnGoogle:pnNocturne:pvr1.0:rvnGoogle:rnNocturne:rvr1.0:cvnGoogle:ct3:cvr: dmi.product.family: Google_Nocturne dmi.product.name: Nocturne dmi.product.version: 1.0 dmi.sys.vendor: Google ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy staging ** Patch added: "DPCD Backlight enablement for Google nocturne (and possibly Google eve device as well.)" https://bugs.launchpad.net/bugs/1895615/+attachment/5410883/+files/dpcd59.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895615 Title: Backlight adjustment doesn't work on Google Pixel Slate Status in linux package in Ubuntu: New Bug description: The Pixel Slate/nocturne backlight does not work due to DPCD logic not identifying the DPCD backlight connection since there is no PWM on the nocturne or eve devices. ChromeOS documentation of disconnected PWM: https://chromium- review.googlesource.com/c/chromiumos/overlays/board-overlays/+/1171922 Discussion of issue & solution: https://github.com/EmbeddedAndroid /linux-eve/issues/2#issuecomment-561382927 This can be fixed with a simple patch which I have applied successfully to mainline 5.9-rc5: https://gist.github.com/satmandu/d6c2192f66cd14525049fd34d356d71d Luckily the Ubuntu kernel patches set i915.enable_psr=0 which keeps Panel Self Refresh from dimming the backlight at boot, but that isn't even needed for this device once the backlight is hooked up correctly. (As a bonus the keyboard backlight also starts working properly at boot.) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-lowlatency 5.8.0.18.22 ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4 Uname: Linux 5.8.0-18-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Mon Sep 14 23:52:45 2020 InstallationDate: Installed on 2020-08-24 (21 days ago) Ins
[Kernel-packages] [Bug 1882975] Re: crypttab not found error causes boot failure with changes in zfs-initramfs_0.8.4-1ubuntu5
I suspect this is due to my not having cryptsetup-initramfs installed. Without that, cryptroot never gets created. cryptsetup-initramfs's /usr/share/local-top/cryptroot has this: mkdir -p /cryptroot # might not exist yet if the main system has no crypttab -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1882975 Title: crypttab not found error causes boot failure with changes in zfs- initramfs_0.8.4-1ubuntu5 Status in zfs-linux package in Ubuntu: New Bug description: boot ends before rpool loads with a failure to find the crypttab file, which doesn't exist. Maybe this has a dependency upon a package that makes that? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41 Uname: Linux 5.4.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu38 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 10 11:42:55 2020 InstallationDate: Installed on 2019-10-19 (235 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1882975/+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 1882975] [NEW] crypttab not found error causes boot failure with changes in zfs-initramfs_0.8.4-1ubuntu5
Public bug reported: boot ends before rpool loads with a failure to find the crypttab file, which doesn't exist. Maybe this has a dependency upon a package that makes that? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41 Uname: Linux 5.4.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu38 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 10 11:42:55 2020 InstallationDate: Installed on 2019-10-19 (235 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy package-from-proposed ** Summary changed: - crypttab not found error causes boot failure + crypttab not found error causes boot failure with new zfs-initramfs ** Summary changed: - crypttab not found error causes boot failure with new zfs-initramfs + crypttab not found error causes boot failure with changes in zfs-initramfs_0.8.4-1ubuntu5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1882975 Title: crypttab not found error causes boot failure with changes in zfs- initramfs_0.8.4-1ubuntu5 Status in zfs-linux package in Ubuntu: New Bug description: boot ends before rpool loads with a failure to find the crypttab file, which doesn't exist. Maybe this has a dependency upon a package that makes that? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41 Uname: Linux 5.4.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu38 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 10 11:42:55 2020 InstallationDate: Installed on 2019-10-19 (235 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1882975/+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 1874519] Re: ZFS installation on Raspberry Pi is problematic
This suggested policy change is welcome. As per https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1852119/comments/2 the argument was that the RPI4 only has 4Gb of ram. "we do not support ZFS unless you have at least 4GB of memory free. Today the 8Gb RPI4 was announced. https://www.raspberrypi.org/blog/8gb-raspberry-pi-4-on-sale-now-at-75/ I'm no expert, but I suspect that this device will be able to handle 4GB of memory free with ease... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1874519 Title: ZFS installation on Raspberry Pi is problematic Status in zfs-linux package in Ubuntu: New Bug description: Version: Ubuntu Server 20.04 - preinstalled 64-bit image for Raspberry Pi. ZFS on the Pi under 20.04 is currently a bit problematic. Upon issuing the command 'zpool status', I'm helpfully directed to install zfsutils-linux. When I do this, it complains that it cannot find the ZFS module, then errors out. Worse than that, the zfsutils-linux package does not depend on the zfs-dkms package, so it doesn't attempt to build the ZFS kernel modules automatically. The workaround is to install zfs-dkms, which builds the required kernel modules. (Once this has been done, the usual errors when installing the zfsutils-linux package, caused by there being no ZFS pools on the system, can be worked around by creating a zpool, then rerunning 'sudo apt install zfsutils-linux', as with previous versions of Ubuntu and Debian). I have not tested on other hardware platforms - this problem may also exist on other platforms where the user has not selected to install to ZFS. I have selected 'zfsutils' as the affected package, which is not the name of an actual current package, since launchpad won't let me submit the bug without selecting a package, however it's not clear to me that the problem is caused by that package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1874519/+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 1872373] Re: zfs patches needed for 5.7
Thanks. Please consider adding https://github.com/openzfs/zfs/pull/10163 and https://github.com/openzfs/zfs/pull/10184 When I made my patch series to get zfs 0.84 working on focal here is what I used: #0001-Prevent-manual-builds-in-the-DKMS-source.patch #0002-Check-for-META-and-DCH-consistency-in-autoconf.patch 0003-relocate-zvol_wait.patch enable-zed.patch #1004-zed-service-bindir.patch 2101-zfs-load-module.patch #2200-add-zfs-0.6.x-ioctl-compat-shim.patch 3100-remove-libzfs-module-timeout.patch 3302-Use-obj-m-instead-of-subdir-m.patch 4001-zsys-support.patch 4100-disable-bpool-upgrade.patch force-verbose-rules.patch #unapplied/init-debian-openrc-workaround.patch # OpenRC users can apply this locally #4550-Linux-5.5-compat-blkg_tryget.patch #4600-Linux-5.6-compat-struct-proc_ops.patch #4601-Linux-5.6-compat-timestamp_truncate.patch #4602-Linux-5.6-compat-ktime_get_raw_ts64.patch #4603-Linux-5.6-compat-time_t.patch zfs-mount-container-start.patch pr10163.patch pr10184.patch overlay.patch ** Patch added: "my patch to get 0.8.4 working on focal" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1872373/+attachment/5372739/+files/zfs.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1872373 Title: zfs patches needed for 5.7 Status in zfs-linux package in Ubuntu: In Progress Bug description: As per https://github.com/openzfs/zfs/pull/10187 there is now a patch for Linux 5.7 compat: blk_alloc_queue(). Of course there may be more patches for the 5.7 series. I've hacked up the patch to backport it to work with the 0.8.x series. It appears to work: zfs, 0.8.3, 5.7.0-050700rc1-generic, x86_64: installed The changes to zvol.c may be somewhat questionable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1872373/+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 1872908] Re: bcmwl kernel module does not build with 5.6.0 kernel
The patch in 6.30.223.271+bdcom-0ubuntu6 doesn't appear to work when
installed on focal:
sudo dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu6_amd64.deb
(Reading database ... 170331 files and directories currently installed.)
Preparing to unpack bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu6_amd64.deb
...
Removing all DKMS Modules
Done.
Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu6) over
(6.30.223.271+bdcom-0ubuntu6) ...
Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu6) ...
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building for 5.4.0-31-generic
Building for architecture x86_64
Building initial module for 5.4.0-31-generic
Error! Application of patch 0028-add-support-for-linux-5.6.patch failed.
Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information.
dpkg: error processing package bcmwl-kernel-source (--install):
installed bcmwl-kernel-source package post-installation script subprocess
returned error exit status 6
Errors were encountered while processing:
bcmwl-kernel-source
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1872908
Title:
bcmwl kernel module does not build with 5.6.0 kernel
Status in bcmwl package in Ubuntu:
Fix Released
Status in bcmwl source package in Focal:
Triaged
Bug description:
After kernel update to 5.6.0-1007-oem wifi stopped working.
Turned out dkms is unable to build the bcmwl module.
The make log shows:
ubuntu@ubuntu-inspiron-5482:~$ cat
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64)
ons 15 apr 2020 09:19:05 CEST
make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
|^~~
|ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18:
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a
cast [-Wint-conversion]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
[Kernel-packages] [Bug 1872373] Re: zfs patches needed for 5.7
Linux 5.7 patches have now gone into https://github.com/openzfs/zfs/tree/zfs-0.8-release with the release of 0.8.4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1872373 Title: zfs patches needed for 5.7 Status in zfs-linux package in Ubuntu: New Bug description: As per https://github.com/openzfs/zfs/pull/10187 there is now a patch for Linux 5.7 compat: blk_alloc_queue(). Of course there may be more patches for the 5.7 series. I've hacked up the patch to backport it to work with the 0.8.x series. It appears to work: zfs, 0.8.3, 5.7.0-050700rc1-generic, x86_64: installed The changes to zvol.c may be somewhat questionable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1872373/+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 1866730] Re: Need patch for post 5.5 low-latency kernels
FYI this patch is part of the just released 0.8.4 in https://github.com/openzfs/zfs/tree/zfs-0.8-release as per the patch pull request: https://github.com/openzfs/zfs/pull/10209 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1866730 Title: Need patch for post 5.5 low-latency kernels Status in zfs-linux package in Ubuntu: Fix Released Bug description: CONFIG_PREEMPT_RCU=y enabled post 5.4.x kernels have __rcu_read_lock exposed as GPL-ONLY, which breaks zfs compilation on kernels with that enabled. (Ubuntu low-latency kernels have that enabled IIRC.) The patch for the .8 series implementing this inside zfs to circumvent this issue is here: https://github.com/openzfs/zfs/commit/2fcab8795c7c493845bfa277d44bc443802000b8 This is from this comment in the relevant issue: https://github.com/openzfs/zfs/issues/9745#issuecomment-592617605 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1866730/+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 1872373] Re: zfs patches needed for 5.7
FYI it looks like support for 5.7 this will be part of the 0.8.4 release as per https://github.com/openzfs/zfs/pull/10209 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1872373 Title: zfs patches needed for 5.7 Status in zfs-linux package in Ubuntu: New Bug description: As per https://github.com/openzfs/zfs/pull/10187 there is now a patch for Linux 5.7 compat: blk_alloc_queue(). Of course there may be more patches for the 5.7 series. I've hacked up the patch to backport it to work with the 0.8.x series. It appears to work: zfs, 0.8.3, 5.7.0-050700rc1-generic, x86_64: installed The changes to zvol.c may be somewhat questionable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1872373/+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 1874519] Re: ZFS installation on Raspberry Pi is problematic
Maybe it makes sense to create a virtual package dependency which can pull in zfs-dkms for the non-arm64 architectures which get zfsutils- linux installed? For instance aufs-dkms is a virtual package which is satisfied by the official kernel packages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1874519 Title: ZFS installation on Raspberry Pi is problematic Status in zfs-linux package in Ubuntu: New Bug description: Version: Ubuntu Server 20.04 - preinstalled 64-bit image for Raspberry Pi. ZFS on the Pi under 20.04 is currently a bit problematic. Upon issuing the command 'zpool status', I'm helpfully directed to install zfsutils-linux. When I do this, it complains that it cannot find the ZFS module, then errors out. Worse than that, the zfsutils-linux package does not depend on the zfs-dkms package, so it doesn't attempt to build the ZFS kernel modules automatically. The workaround is to install zfs-dkms, which builds the required kernel modules. (Once this has been done, the usual errors when installing the zfsutils-linux package, caused by there being no ZFS pools on the system, can be worked around by creating a zpool, then rerunning 'sudo apt install zfsutils-linux', as with previous versions of Ubuntu and Debian). I have not tested on other hardware platforms - this problem may also exist on other platforms where the user has not selected to install to ZFS. I have selected 'zfsutils' as the affected package, which is not the name of an actual current package, since launchpad won't let me submit the bug without selecting a package, however it's not clear to me that the problem is caused by that package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1874519/+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 1872908] Re: bcmwl kernel module does not build with 5.6.0 kernel
So until the package gets updated do this:
Add this line to /usr/src/bcmwl-6.30.223.271+bdcom/dkms.conf
PATCH[13]="0028-add-support-for-Linux-5.6.patch"
Save the patch at
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1872908/+attachment/5356260/+files
/broadcom-wl-dkms-arch-patch as this file:
/usr/src/bcmwl-6.30.223.271+bdcom/patches/0028-add-support-for-
Linux-5.6.patch
then do this:
sudo dkms install bcmwl/6.30.223.271+bdcom -k all
(this appears to work for 5.7-rc1 too.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1872908
Title:
bcmwl kernel module does not build with 5.6.0 kernel
Status in bcmwl package in Ubuntu:
New
Bug description:
After kernel update to 5.6.0-1007-oem wifi stopped working.
Turned out dkms is unable to build the bcmwl module.
The make log shows:
ubuntu@ubuntu-inspiron-5482:~$ cat
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64)
ons 15 apr 2020 09:19:05 CEST
make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
|^~~
|ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18:
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a
cast [-Wint-conversion]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15:
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
[Kernel-packages] [Bug 1872908] Re: bcmwl kernel module does not build with 5.6.0 kernel
There is an arch patch for this:
https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages
/broadcom-wl-dkms=e78ab887e946418baac2abcaad24b9df19f22945
** Attachment added: "patch for 5.6"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1872908/+attachment/5356260/+files/broadcom-wl-dkms-arch-patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1872908
Title:
bcmwl kernel module does not build with 5.6.0 kernel
Status in bcmwl package in Ubuntu:
New
Bug description:
After kernel update to 5.6.0-1007-oem wifi stopped working.
Turned out dkms is unable to build the bcmwl module.
The make log shows:
ubuntu@ubuntu-inspiron-5482:~$ cat
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64)
ons 15 apr 2020 09:19:05 CEST
make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
|^~~
|ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18:
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a
cast [-Wint-conversion]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15:
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58:
error: passing argument 4 of ‘proc_create_data’ from incompatible pointer type
[-Werror=incompatible-pointer-types]
3376 | if ((wl->proc_entry =
[Kernel-packages] [Bug 1872373] Re: zfs patches needed for 5.7
This is a script which can be used to update the zfs-dkms package locally. I imagine it doesn't make sense to update the final package until later in the 5.7 rc series... ** Attachment added: "zfs-dkms updater" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1872373/+attachment/5352869/+files/update_zfs-dkms.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1872373 Title: zfs patches needed for 5.7 Status in zfs-linux package in Ubuntu: New Bug description: As per https://github.com/openzfs/zfs/pull/10187 there is now a patch for Linux 5.7 compat: blk_alloc_queue(). Of course there may be more patches for the 5.7 series. I've hacked up the patch to backport it to work with the 0.8.x series. It appears to work: zfs, 0.8.3, 5.7.0-050700rc1-generic, x86_64: installed The changes to zvol.c may be somewhat questionable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1872373/+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 1872373] [NEW] zfs patches needed for 5.7
Public bug reported: As per https://github.com/openzfs/zfs/pull/10187 there is now a patch for Linux 5.7 compat: blk_alloc_queue(). Of course there may be more patches for the 5.7 series. I've hacked up the patch to backport it to work with the 0.8.x series. It appears to work: zfs, 0.8.3, 5.7.0-050700rc1-generic, x86_64: installed The changes to zvol.c may be somewhat questionable. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Patch added: "Patch tested with 5.7.0-050700rc1-generic & zfs-dkms_0.8.3-1ubuntu11" https://bugs.launchpad.net/bugs/1872373/+attachment/5352868/+files/k5.7-rc1-zfs.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1872373 Title: zfs patches needed for 5.7 Status in zfs-linux package in Ubuntu: New Bug description: As per https://github.com/openzfs/zfs/pull/10187 there is now a patch for Linux 5.7 compat: blk_alloc_queue(). Of course there may be more patches for the 5.7 series. I've hacked up the patch to backport it to work with the 0.8.x series. It appears to work: zfs, 0.8.3, 5.7.0-050700rc1-generic, x86_64: installed The changes to zvol.c may be somewhat questionable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1872373/+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 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
Definitely still seeing this, but over 12 hours later I can immediately use the devices again in mainline 5.6.3. dmesg | grep 'magic\|apple' [68065.162639] apple *:*:*.*: unknown main item tag 0x0 [68065.163407] apple *:*:*.*: input,hidraw5: BLUETOOTH HID v0.50 Keyboard [satadru’s keyboard] on *:*:*:*:*:* [68086.650551] magicmouse *:*:*.*: unknown main item tag 0x0 [68086.650753] magicmouse *:*:*.*: input,hidraw6: BLUETOOTH HID v1.60 Mouse [satadru's Trackpad] on *:*:*:*:*:* -- 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/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
Definitely still get the error message, at least right at first connection, using mainline 5.6.3 on focal beta: magicmouse *:*:*:*: unknown main item tag 0x0 -- 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/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
I think this is the same issue as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113 has anybody submitted this upstream to the linux-input mailing list yet? It's definitely happening with 5.4.0-23-lowlatency on focal beta and my magicmouse trackpad. I will try with a mainline kernel next... -- 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/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding
[Kernel-packages] [Bug 1849522] Re: imported non-rpool/bpool zpools are not being reimported after reboot
I don't think this is fixed, because now grub.cfg has NO entries in it aside from that for accessing the bios menu. (Is this related to corresponding grub-common changes?) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1849522 Title: imported non-rpool/bpool zpools are not being reimported after reboot Status in zfs-linux package in Ubuntu: Fix Released Bug description: Installed ubuntu 19.10 onto a zfs bpool/rpool. Installed zsys. Did a "zpool import" of my existing zfs pools. Rebooted. The previously imported zpools are not imported at boot! I am currently using this hacky workaround: https://gist.github.com/satmandu/4da5e900c2c80c93da38c76537291507 I would expect that local zpools I have manually imported would re-import when the system is rebooted. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: zsys 0.2.2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Wed Oct 23 11:40:36 2019 InstallationDate: Installed on 2019-10-19 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1849522/+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 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
I'm not sure which package to file a bug report on, but I have multiple pools, and after this last update, bpool wouldn't mount properly due to files on /boot, and as a result update-grub updated grub.cfg with no info about my kernels. :/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+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 1866730] [NEW] Need patch for post 5.5 low-latency kernels
Public bug reported: CONFIG_PREEMPT_RCU=y enabled post 5.4.x kernels have __rcu_read_lock exposed as GPL-ONLY, which breaks zfs compilation on kernels with that enabled. (Ubuntu low-latency kernels have that enabled IIRC.) The patch for the .8 series implementing this inside zfs to circumvent this issue is here: https://github.com/openzfs/zfs/commit/2fcab8795c7c493845bfa277d44bc443802000b8 This is from this comment in the relevant issue: https://github.com/openzfs/zfs/issues/9745#issuecomment-592617605 ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1866730 Title: Need patch for post 5.5 low-latency kernels Status in zfs-linux package in Ubuntu: New Bug description: CONFIG_PREEMPT_RCU=y enabled post 5.4.x kernels have __rcu_read_lock exposed as GPL-ONLY, which breaks zfs compilation on kernels with that enabled. (Ubuntu low-latency kernels have that enabled IIRC.) The patch for the .8 series implementing this inside zfs to circumvent this issue is here: https://github.com/openzfs/zfs/commit/2fcab8795c7c493845bfa277d44bc443802000b8 This is from this comment in the relevant issue: https://github.com/openzfs/zfs/issues/9745#issuecomment-592617605 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1866730/+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 1852119] Re: Please add zfs modules to linux-raspi2
Thanks for the policy clarification. But as I understand it "4 GiB of memory is recommended for normal performance in basic workloads" referred to 4Gb of memory in total, not 4gb of free memory. I'll ask again once there is a device with more than 4Gb of RAM, but FYI, since the raspberry pi may often be used for single tasks, a 4Gb ram machine might be just fine with that zfs overhead. (I haven't seen any memory pressure issues with multiple headless 4Gb Pi4 machines running with ubuntu on zfs.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1852119 Title: Please add zfs modules to linux-raspi2 Status in linux-raspi2 package in Ubuntu: Won't Fix Bug description: The 4gb RPI4 is more than capable of handling zfs. ( Even zfs root can be enabled manually with arm64 eoan builds using a variant of the steps at https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS . ) Currently one has to install zfs-dkms for zfs support, but ideally one would have zfs modules come with the standard arm64 kernel so that one does not have to recompile zfs on the pi. Example: uname -a Linux rpi4 5.3.0-1011-raspi2 #12-Ubuntu SMP Fri Nov 1 09:07:06 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux @rpi4:~$ zpool status pool: bpool state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(5) for details. scan: scrub repaired 0B in 0 days 00:00:00 with 0 errors on Mon Nov 11 13:50:14 2019 config: NAME STATE READ WRITE CKSUM bpool ONLINE 0 0 0 usb-Samsung_Flash_Drive_FIT_0309318110004882-0:0-part3 ONLINE 0 0 0 errors: No known data errors pool: rpool state: ONLINE scan: scrub repaired 0B in 0 days 00:01:21 with 0 errors on Mon Nov 11 13:51:39 2019 config: NAMESTATE READ WRITE CKSUM rpool ONLINE 0 0 0 sda4 ONLINE 0 0 0 errors: No known data errors dkms status zfs, 0.8.1, 5.3.0-1011-raspi2, aarch64: installed @rpi4:~$ cat /proc/cpuinfo processor : 0 BogoMIPS: 108.00 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd08 CPU revision: 3 processor : 1 BogoMIPS: 108.00 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd08 CPU revision: 3 processor : 2 BogoMIPS: 108.00 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd08 CPU revision: 3 processor : 3 BogoMIPS: 108.00 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd08 CPU revision: 3 Hardware: BCM2835 Revision: c03111 Serial : --- Model : Raspberry Pi 4 Model B Rev 1.1 @rpi4:~$ free -m totalusedfree shared buff/cache available Mem: 3791 8832612 18 295 2836 Swap: 4095 04095 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852119/+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 1863136] Re: zfs-dkms will not compile on kernel 5.6rc1
Patch updated for 5.6rc3: https://gist.github.com/satmandu/67cbae9c4d461be0e64428a1707aef1c Adapted from zfs PR PR #9961 & #10064 https://github.com/openzfs/zfs/pull/9961 https://github.com/openzfs/zfs/pull/10064 $ dkms status zfs, 0.8.3, 5.6.0-050600rc2-generic, x86_64: installed zfs, 0.8.3, 5.6.0-050600rc3-generic, x86_64: installed ** Patch added: "Kernel 5.6rc3 cumulative zfs 0.8 branch patch" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1863136/+attachment/5331651/+files/k5.6.3.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1863136 Title: zfs-dkms will not compile on kernel 5.6rc1 Status in zfs-linux package in Ubuntu: In Progress Bug description: Bug mentioned here: https://github.com/zfsonlinux/zfs/issues/10001 Patch for zfs master branch here: https://github.com/zfsonlinux/zfs/pull/9961 Patch modified for zfs-dkms_0.8.3-1ubuntu3 here: https://paste.ubuntu.com/p/wsS9GFHjyv/ This is working for me in getting a 5.5.x kernel to access zpools on arm64 and 5.5.2 mainline & 5.6rc1 mainline kernels to access zpools on amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1863136/+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 1863136] Re: zfs-dkms will not compile on kernel 5.6rc1
I added a comment to the PR here: https://github.com/openzfs/zfs/pull/9961#issuecomment-591076133 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1863136 Title: zfs-dkms will not compile on kernel 5.6rc1 Status in zfs-linux package in Ubuntu: In Progress Bug description: Bug mentioned here: https://github.com/zfsonlinux/zfs/issues/10001 Patch for zfs master branch here: https://github.com/zfsonlinux/zfs/pull/9961 Patch modified for zfs-dkms_0.8.3-1ubuntu3 here: https://paste.ubuntu.com/p/wsS9GFHjyv/ This is working for me in getting a 5.5.x kernel to access zpools on arm64 and 5.5.2 mainline & 5.6rc1 mainline kernels to access zpools on amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1863136/+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 1863136] Re: zfs-dkms will not compile on kernel 5.6rc1
Thanks. As I understand it there are no new changes needed for 5.5 support though, aside from modifying the META file and rerunning ./autogen.sh. I've been running with just such changes on arm64 and amd64 (literally sed -i 's/5.4/5.5/' META) with focal builds and 5.5 kernels for a bit now with no issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1863136 Title: zfs-dkms will not compile on kernel 5.6rc1 Status in zfs-linux package in Ubuntu: Confirmed Bug description: Bug mentioned here: https://github.com/zfsonlinux/zfs/issues/10001 Patch for zfs master branch here: https://github.com/zfsonlinux/zfs/pull/9961 Patch modified for zfs-dkms_0.8.3-1ubuntu3 here: https://paste.ubuntu.com/p/wsS9GFHjyv/ This is working for me in getting a 5.5.x kernel to access zpools on arm64 and 5.5.2 mainline & 5.6rc1 mainline kernels to access zpools on amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1863136/+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 1863136] Re: zfs-dkms will not compile on kernel 5.6rc1
(after patching source I had to run ./autogen.sh in the module folder.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1863136 Title: zfs-dkms will not compile on kernel 5.6rc1 Status in zfs-linux package in Ubuntu: New Bug description: Bug mentioned here: https://github.com/zfsonlinux/zfs/issues/10001 Patch for zfs master branch here: https://github.com/zfsonlinux/zfs/pull/9961 Patch modified for zfs-dkms_0.8.3-1ubuntu3 here: https://paste.ubuntu.com/p/wsS9GFHjyv/ This is working for me in getting a 5.5.x kernel to access zpools on arm64 and 5.5.2 mainline & 5.6rc1 mainline kernels to access zpools on amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1863136/+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 1863136] [NEW] zfs-dkms will not compile on kernel 5.6rc1
Public bug reported: Bug mentioned here: https://github.com/zfsonlinux/zfs/issues/10001 Patch for zfs master branch here: https://github.com/zfsonlinux/zfs/pull/9961 Patch modified for zfs-dkms_0.8.3-1ubuntu3 here: https://paste.ubuntu.com/p/wsS9GFHjyv/ This is working for me in getting a 5.5.x kernel to access zpools on arm64 and 5.5.2 mainline & 5.6rc1 mainline kernels to access zpools on amd64. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Patch added: "zfs-dkms-0.8.3-kernel-5.6.patch" https://bugs.launchpad.net/bugs/1863136/+attachment/5328019/+files/zfs-dkms-0.8.3-kernel-5.6.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1863136 Title: zfs-dkms will not compile on kernel 5.6rc1 Status in zfs-linux package in Ubuntu: New Bug description: Bug mentioned here: https://github.com/zfsonlinux/zfs/issues/10001 Patch for zfs master branch here: https://github.com/zfsonlinux/zfs/pull/9961 Patch modified for zfs-dkms_0.8.3-1ubuntu3 here: https://paste.ubuntu.com/p/wsS9GFHjyv/ This is working for me in getting a 5.5.x kernel to access zpools on arm64 and 5.5.2 mainline & 5.6rc1 mainline kernels to access zpools on amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1863136/+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 1852119] [NEW] Please add zfs modules to linux-raspi2
Public bug reported: The 4gb RPI4 is more than capable of handling zfs. ( Even zfs root can be enabled manually with arm64 eoan builds using a variant of the steps at https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS . ) Currently one has to install zfs-dkms for zfs support, but ideally one would have zfs modules come with the standard arm64 kernel so that one does not have to recompile zfs on the pi. Example: uname -a Linux rpi4 5.3.0-1011-raspi2 #12-Ubuntu SMP Fri Nov 1 09:07:06 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux @rpi4:~$ zpool status pool: bpool state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(5) for details. scan: scrub repaired 0B in 0 days 00:00:00 with 0 errors on Mon Nov 11 13:50:14 2019 config: NAME STATE READ WRITE CKSUM bpool ONLINE 0 0 0 usb-Samsung_Flash_Drive_FIT_0309318110004882-0:0-part3 ONLINE 0 0 0 errors: No known data errors pool: rpool state: ONLINE scan: scrub repaired 0B in 0 days 00:01:21 with 0 errors on Mon Nov 11 13:51:39 2019 config: NAMESTATE READ WRITE CKSUM rpool ONLINE 0 0 0 sda4 ONLINE 0 0 0 errors: No known data errors dkms status zfs, 0.8.1, 5.3.0-1011-raspi2, aarch64: installed @rpi4:~$ cat /proc/cpuinfo processor : 0 BogoMIPS: 108.00 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd08 CPU revision: 3 processor : 1 BogoMIPS: 108.00 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd08 CPU revision: 3 processor : 2 BogoMIPS: 108.00 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd08 CPU revision: 3 processor : 3 BogoMIPS: 108.00 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd08 CPU revision: 3 Hardware: BCM2835 Revision: c03111 Serial : --- Model : Raspberry Pi 4 Model B Rev 1.1 @rpi4:~$ free -m totalusedfree shared buff/cache available Mem: 3791 8832612 18 2952836 Swap: 4095 04095 ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1852119 Title: Please add zfs modules to linux-raspi2 Status in linux-raspi2 package in Ubuntu: New Bug description: The 4gb RPI4 is more than capable of handling zfs. ( Even zfs root can be enabled manually with arm64 eoan builds using a variant of the steps at https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS . ) Currently one has to install zfs-dkms for zfs support, but ideally one would have zfs modules come with the standard arm64 kernel so that one does not have to recompile zfs on the pi. Example: uname -a Linux rpi4 5.3.0-1011-raspi2 #12-Ubuntu SMP Fri Nov 1 09:07:06 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux @rpi4:~$ zpool status pool: bpool state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(5) for details. scan: scrub repaired 0B in 0 days 00:00:00 with 0 errors on Mon Nov 11 13:50:14 2019 config: NAME STATE READ WRITE CKSUM bpool ONLINE 0 0 0 usb-Samsung_Flash_Drive_FIT_0309318110004882-0:0-part3 ONLINE 0 0 0 errors: No known data errors pool: rpool state: ONLINE scan: scrub repaired 0B in 0 days 00:01:21 with 0 errors on Mon Nov 11 13:51:39 2019 config: NAMESTATE READ WRITE CKSUM rpool ONLINE 0 0 0 sda4 ONLINE 0 0 0 errors: No known data errors dkms status zfs, 0.8.1, 5.3.0-1011-raspi2,
[Kernel-packages] [Bug 1822797] Re: ZFS module is installed for wrong kernel on arm64-raspi3 systems (19.04 beta)
For what it is worth, zfs works quite well for a root fs rpool on a 4Gb RPI4b. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1822797 Title: ZFS module is installed for wrong kernel on arm64-raspi3 systems (19.04 beta) Status in linux-raspi2 package in Ubuntu: Triaged Bug description: Platform: Raspberry Pi 3 running ubuntu-19.04-beta-preinstalled- server-arm64+raspi3.img Kernel: Default (Linux ubuntu 4.18.0-1010-raspi2 #12-Ubuntu SMP PREEMPT Tue Feb 12 12:17:11 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux) Problem: The ZFS module is installed for a kernel that can not be used. apt-get install zfs-initramfs Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvpair1linux libuutil1linux libzfs2linux libzpool2linux linux-image-unsigned-5.0.0-8-snapdragon linux-modules-5.0.0-8-snapdragon zfs-zed zfsutils-linux Suggested packages: fdutils linux-doc-5.0.0 | linux-source-5.0.0 linux-tools linux-headers-5.0.0-8-snapdragon nfs-kernel-server samba-common-bin The following NEW packages will be installed: libnvpair1linux libuutil1linux libzfs2linux libzpool2linux linux-image-unsigned-5.0.0-8-snapdragon linux-modules-5.0.0-8-snapdragon zfs-initramfs zfs-zed zfsutils-linux 0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 55.7 MB of archives. After this operation, 305 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 linux-modules-5.0.0-8-snapdragon arm64 5.0.0-8.9 [47.5 MB] Get:2 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 linux-image-unsigned-5.0.0-8-snapdragon arm64 5.0.0-8.9 [7169 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libnvpair1linux arm64 0.7.12-1ubuntu5 [42.8 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libuutil1linux arm64 0.7.12-1ubuntu5 [50.7 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libzpool2linux arm64 0.7.12-1ubuntu5 [498 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libzfs2linux arm64 0.7.12-1ubuntu5 [121 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfsutils-linux arm64 0.7.12-1ubuntu5 [267 kB] Get:8 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfs-initramfs arm64 0.7.12-1ubuntu5 [22.2 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfs-zed arm64 0.7.12-1ubuntu5 [57.5 kB] Fetched 55.7 MB in 37s (1486 kB/s) Selecting previously unselected package linux-modules-5.0.0-8-snapdragon. (Reading database ... 61671 files and directories currently installed.) Preparing to unpack .../0-linux-modules-5.0.0-8-snapdragon_5.0.0-8.9_arm64.deb ... Unpacking linux-modules-5.0.0-8-snapdragon (5.0.0-8.9) ... Selecting previously unselected package linux-image-unsigned-5.0.0-8-snapdragon. Preparing to unpack .../1-linux-image-unsigned-5.0.0-8-snapdragon_5.0.0-8.9_arm64.deb ... Unpacking linux-image-unsigned-5.0.0-8-snapdragon (5.0.0-8.9) ... Selecting previously unselected package libnvpair1linux. Preparing to unpack .../2-libnvpair1linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking libnvpair1linux (0.7.12-1ubuntu5) ... Selecting previously unselected package libuutil1linux. Preparing to unpack .../3-libuutil1linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking libuutil1linux (0.7.12-1ubuntu5) ... Selecting previously unselected package libzpool2linux. Preparing to unpack .../4-libzpool2linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking libzpool2linux (0.7.12-1ubuntu5) ... Selecting previously unselected package libzfs2linux. Preparing to unpack .../5-libzfs2linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking libzfs2linux (0.7.12-1ubuntu5) ... Selecting previously unselected package zfsutils-linux. Preparing to unpack .../6-zfsutils-linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking zfsutils-linux (0.7.12-1ubuntu5) ... Selecting previously unselected package zfs-initramfs. Preparing to unpack .../7-zfs-initramfs_0.7.12-1ubuntu5_arm64.deb ... Unpacking zfs-initramfs (0.7.12-1ubuntu5) ... Selecting previously unselected package zfs-zed. Preparing to unpack .../8-zfs-zed_0.7.12-1ubuntu5_arm64.deb ... Unpacking zfs-zed (0.7.12-1ubuntu5) ... Setting up libuutil1linux (0.7.12-1ubuntu5) ... Setting up linux-modules-5.0.0-8-snapdragon (5.0.0-8.9) ... Setting up linux-image-unsigned-5.0.0-8-snapdragon (5.0.0-8.9) ... I: /boot/vmlinuz is now a symlink to vmlinuz-5.0.0-8-snapdragon I: /boot/initrd.img is now a symlink to initrd.img-5.0.0-8-snapdragon Setting up libnvpair1linux (0.7.12-1ubuntu5) ... Setting up libzpool2linux (0.7.12-1ubuntu5) ... Setting up libzfs2linux
[Kernel-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
Thanks all! Mainline builds of daily and 5.3-rc1 appear to have been generated for amd64 last night. -- 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/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in gcc-9 package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Won't Fix Status in xtables-addons package in Ubuntu: Won't Fix Bug description: Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+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 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
Any chance someone could get the recipes fixed for the mainline builds, which also need the -fcf-protection=none retpoline flags added since they're being built using "schroot -c eoan-amd64"? (I'm not sure who needs to be looped in for that to happen.) -- 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/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in gcc-9 package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Won't Fix Status in xtables-addons package in Ubuntu: Won't Fix Bug description: Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+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 1836291] Re: 5.2.0-8-generic regresses KMS edid file support, resulting in no video
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux-meta (Ubuntu) Status: Incomplete => Invalid -- 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/1836291 Title: 5.2.0-8-generic regresses KMS edid file support, resulting in no video Status in linux package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Bug description: I have the kernel load an EDID file so that when connecting my amd64 machine to a tv and speaker bar through hdmi I get the full setup information even if the speaker bar and tv might be off. The relevant kernel cmdline is "drm.edid_firmware=HDMI-A-1:edid/edid.bin" In most recent kernel versions this hasn't been a problem. The mainline 5.2.0-rc7 generic kernel at https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.2-rc7/ works properly. The 5.2.0.8.9 kernel in eoan/proposed at https://bugs.launchpad.net/ubuntu/+source/linux-meta/5.2.0.8.9 however does not work, insofar as I get no video output at all after grub loads the kernel. (I would test with the 5.2.0 mainline generic kernel, but the mainline kernel builds are currently broken due to issues with gcc-9.1 flags.) dmesg and Xorg log for boots for both kernels (working and not working) are attached. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic (not installed) ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Jul 11 23:43:12 2019 HibernationDevice: RESUME=UUID=102ff483-9121-4be7-af0d-e2599a7c1cf8 InstallationDate: Installed on 2016-08-03 (1073 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: MSI MS-7998 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=89506e95-35b5-4f17-8095-aa2aeb09c5c5 ro intel_pstate=skylake_hwp i915.disable_power_well=0 i915.enable_dc=2 i915.enable_fbc=1 i915.enable_guc=3 i915.modeset=1 video=HDMI-A-1:e video=DP-1:d video=HDMI-A-2:d video=HDMI-A-3:d drm.edid_firmware=HDMI-A-1:edid/edid.bin video=efifb:off i915.fastboot=1 video=1920x1080@60 ipti=off spectre_v2=off l1tf=off mds=off nospec_store_bypass_disable no_stf_barrier noibrs noibpb nopti nospectre_v2 nospectre_v1 mpt3sas.msix_disable=1 mpt3sas.logging_level=1 pcie_aspm=off fsck.mode=force fsck.repair=yes cpuidle.governor=teo crashkernel=512M-:192M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2018-03-02 (496 days ago) dmi.bios.date: 06/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.A0 dmi.board.asset.tag: Default string dmi.board.name: C236A WORKSTATION (MS-7998) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.A0:bd06/15/2018:svnMSI:pnMS-7998:pvr1.0:rvnMSI:rnC236AWORKSTATION(MS-7998):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7998 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836291/+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 1836291] Re: 5.2.0-8-generic regresses KMS edid file support, resulting in no video
Thanks @kaihengfeng! I can't believe I missed that. [headdesk] Indeed I just needed linux-modules-extra installed. That indeed fixes my issue, which was clearly PEBCAK. -- 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/1836291 Title: 5.2.0-8-generic regresses KMS edid file support, resulting in no video Status in linux package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Bug description: I have the kernel load an EDID file so that when connecting my amd64 machine to a tv and speaker bar through hdmi I get the full setup information even if the speaker bar and tv might be off. The relevant kernel cmdline is "drm.edid_firmware=HDMI-A-1:edid/edid.bin" In most recent kernel versions this hasn't been a problem. The mainline 5.2.0-rc7 generic kernel at https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.2-rc7/ works properly. The 5.2.0.8.9 kernel in eoan/proposed at https://bugs.launchpad.net/ubuntu/+source/linux-meta/5.2.0.8.9 however does not work, insofar as I get no video output at all after grub loads the kernel. (I would test with the 5.2.0 mainline generic kernel, but the mainline kernel builds are currently broken due to issues with gcc-9.1 flags.) dmesg and Xorg log for boots for both kernels (working and not working) are attached. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic (not installed) ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Jul 11 23:43:12 2019 HibernationDevice: RESUME=UUID=102ff483-9121-4be7-af0d-e2599a7c1cf8 InstallationDate: Installed on 2016-08-03 (1073 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: MSI MS-7998 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=89506e95-35b5-4f17-8095-aa2aeb09c5c5 ro intel_pstate=skylake_hwp i915.disable_power_well=0 i915.enable_dc=2 i915.enable_fbc=1 i915.enable_guc=3 i915.modeset=1 video=HDMI-A-1:e video=DP-1:d video=HDMI-A-2:d video=HDMI-A-3:d drm.edid_firmware=HDMI-A-1:edid/edid.bin video=efifb:off i915.fastboot=1 video=1920x1080@60 ipti=off spectre_v2=off l1tf=off mds=off nospec_store_bypass_disable no_stf_barrier noibrs noibpb nopti nospectre_v2 nospectre_v1 mpt3sas.msix_disable=1 mpt3sas.logging_level=1 pcie_aspm=off fsck.mode=force fsck.repair=yes cpuidle.governor=teo crashkernel=512M-:192M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2018-03-02 (496 days ago) dmi.bios.date: 06/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.A0 dmi.board.asset.tag: Default string dmi.board.name: C236A WORKSTATION (MS-7998) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.A0:bd06/15/2018:svnMSI:pnMS-7998:pvr1.0:rvnMSI:rnC236AWORKSTATION(MS-7998):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7998 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836291/+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 1836291] Re: 5.2.0-8-generic regresses KMS edid file support, resulting in no video
** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- 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/1836291 Title: 5.2.0-8-generic regresses KMS edid file support, resulting in no video Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Bug description: I have the kernel load an EDID file so that when connecting my amd64 machine to a tv and speaker bar through hdmi I get the full setup information even if the speaker bar and tv might be off. The relevant kernel cmdline is "drm.edid_firmware=HDMI-A-1:edid/edid.bin" In most recent kernel versions this hasn't been a problem. The mainline 5.2.0-rc7 generic kernel at https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.2-rc7/ works properly. The 5.2.0.8.9 kernel in eoan/proposed at https://bugs.launchpad.net/ubuntu/+source/linux-meta/5.2.0.8.9 however does not work, insofar as I get no video output at all after grub loads the kernel. (I would test with the 5.2.0 mainline generic kernel, but the mainline kernel builds are currently broken due to issues with gcc-9.1 flags.) dmesg and Xorg log for boots for both kernels (working and not working) are attached. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic (not installed) ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Jul 11 23:43:12 2019 HibernationDevice: RESUME=UUID=102ff483-9121-4be7-af0d-e2599a7c1cf8 InstallationDate: Installed on 2016-08-03 (1073 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: MSI MS-7998 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=89506e95-35b5-4f17-8095-aa2aeb09c5c5 ro intel_pstate=skylake_hwp i915.disable_power_well=0 i915.enable_dc=2 i915.enable_fbc=1 i915.enable_guc=3 i915.modeset=1 video=HDMI-A-1:e video=DP-1:d video=HDMI-A-2:d video=HDMI-A-3:d drm.edid_firmware=HDMI-A-1:edid/edid.bin video=efifb:off i915.fastboot=1 video=1920x1080@60 ipti=off spectre_v2=off l1tf=off mds=off nospec_store_bypass_disable no_stf_barrier noibrs noibpb nopti nospectre_v2 nospectre_v1 mpt3sas.msix_disable=1 mpt3sas.logging_level=1 pcie_aspm=off fsck.mode=force fsck.repair=yes cpuidle.governor=teo crashkernel=512M-:192M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2018-03-02 (496 days ago) dmi.bios.date: 06/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.A0 dmi.board.asset.tag: Default string dmi.board.name: C236A WORKSTATION (MS-7998) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.A0:bd06/15/2018:svnMSI:pnMS-7998:pvr1.0:rvnMSI:rnC236AWORKSTATION(MS-7998):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7998 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836291/+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 1836291] [NEW] 5.2.0-8-generic regresses KMS edid file support, resulting in no video
Public bug reported: I have the kernel load an EDID file so that when connecting my amd64 machine to a tv and speaker bar through hdmi I get the full setup information even if the speaker bar and tv might be off. The relevant kernel cmdline is "drm.edid_firmware=HDMI-A-1:edid/edid.bin" In most recent kernel versions this hasn't been a problem. The mainline 5.2.0-rc7 generic kernel at https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.2-rc7/ works properly. The 5.2.0.8.9 kernel in eoan/proposed at https://bugs.launchpad.net/ubuntu/+source/linux-meta/5.2.0.8.9 however does not work, insofar as I get no video output at all after grub loads the kernel. (I would test with the 5.2.0 mainline generic kernel, but the mainline kernel builds are currently broken due to issues with gcc-9.1 flags.) dmesg and Xorg log for boots for both kernels (working and not working) are attached. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic (not installed) ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Jul 11 23:43:12 2019 HibernationDevice: RESUME=UUID=102ff483-9121-4be7-af0d-e2599a7c1cf8 InstallationDate: Installed on 2016-08-03 (1073 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: MSI MS-7998 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=89506e95-35b5-4f17-8095-aa2aeb09c5c5 ro intel_pstate=skylake_hwp i915.disable_power_well=0 i915.enable_dc=2 i915.enable_fbc=1 i915.enable_guc=3 i915.modeset=1 video=HDMI-A-1:e video=DP-1:d video=HDMI-A-2:d video=HDMI-A-3:d drm.edid_firmware=HDMI-A-1:edid/edid.bin video=efifb:off i915.fastboot=1 video=1920x1080@60 ipti=off spectre_v2=off l1tf=off mds=off nospec_store_bypass_disable no_stf_barrier noibrs noibpb nopti nospectre_v2 nospectre_v1 mpt3sas.msix_disable=1 mpt3sas.logging_level=1 pcie_aspm=off fsck.mode=force fsck.repair=yes cpuidle.governor=teo crashkernel=512M-:192M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2018-03-02 (496 days ago) dmi.bios.date: 06/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.A0 dmi.board.asset.tag: Default string dmi.board.name: C236A WORKSTATION (MS-7998) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.A0:bd06/15/2018:svnMSI:pnMS-7998:pvr1.0:rvnMSI:rnC236AWORKSTATION(MS-7998):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7998 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug edid eoan ** Attachment added: "dmesg and Xorg log" https://bugs.launchpad.net/bugs/1836291/+attachment/5276615/+files/Broken%20video%20dmesg%20and%20Xorg.zip -- 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/1836291 Title: 5.2.0-8-generic regresses KMS edid file support, resulting in no video Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Bug description: I have the kernel load an EDID file so that when connecting my amd64 machine to a tv and speaker bar through hdmi I get the full setup information even if the speaker bar and tv might be off. The relevant kernel cmdline is "drm.edid_firmware=HDMI-A-1:edid/edid.bin" In most recent kernel versions this hasn't been a problem. The mainline 5.2.0-rc7 generic kernel at https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.2-rc7/ works properly. The 5.2.0.8.9 kernel in eoan/proposed at https://bugs.launchpad.net/ubuntu/+source/linux-meta/5.2.0.8.9 however does not work, insofar as I get no video output at all after grub loads the kernel. (I would test with the 5.2.0 mainline generic kernel, but the mainline kernel builds are currently broken due to issues with gcc-9.1 flags.) dmesg and Xorg log for boots
[Kernel-packages] [Bug 1835883] Re: Wrong ZFS module version built into eoan kernel
FYI 5.2.0-8-generic in eoan/proposed has 0.8.1 strings /lib/modules/5.2.0-8-generic/kernel/zfs/zfs.ko | grep 0.8 version=0.8.1-1ubuntu5 Also you can install zfs-dkms... -- 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/1835883 Title: Wrong ZFS module version built into eoan kernel Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 18.04 but tested latest ZFS from eoan and discovered the following 1. I installed 5.0.0-21-generic from eoan-proposed (tried eoan as well) 2. I installed zfs userland tools from eoan, no problems here ii libnvpair1linux 0.8.1-1ubuntu5 amd64Solaris name-value library for Linux ii libuutil1linux0.8.1-1ubuntu5 amd64Solaris userland utility library for Linux ii libzfs2linux 0.8.1-1ubuntu5 amd64OpenZFS filesystem library for Linux ii libzpool2linux0.8.1-1ubuntu5 amd64OpenZFS pool library for Linux ii zfs-zed 0.8.1-1ubuntu5 amd64OpenZFS Event Daemon ii zfsutils-linux0.8.1-1ubuntu5 amd64command-line tools to manage OpenZFS filesystems 3. Reboot 4. Expect v0.8.1 ZFS module to be loaded 5. ZFS 0.7.12-1ubuntu5 is loaded instead Looking at the kmod strings output it seems that the build system is for some reason using old version of the ZFS kernel module? # strings /lib/modules/5.0.0-21-generic/kernel/zfs/zfs.ko|grep 0.7 0.7.12 /build/linux-RipFyD/linux-5.0.0/debian/build/build-generic/_dkms/build/zfs/0.7.12/build/module/zfs/abd.c ... --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 9 08:10 seq crw-rw 1 root audio 116, 33 Jul 9 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 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: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=2e7a22f4-95e7-11e9-a1bc-525400d6d724 ro ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.11.0-1.fc28 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.11.0-1.fc28:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-3.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835883/+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 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
It looks like this is being addressed in recent linux packages. As per https://launchpad.net/ubuntu/+source/linux/5.2.0-8.9 "SAUCE: add -fcf-protection=none to retpoline flags" -- 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/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in gcc-9 package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Committed Status in virtualbox package in Ubuntu: Confirmed Status in xtables-addons package in Ubuntu: New Bug description: Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+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 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
The origin of this bug is the change in the gcc-9 package on 26 May 2019. Shouldn't the fcf-protection change there just be reverted? As per the changelog: gcc-9 (9.1.0-3) experimental; urgency=medium * Update to SVN 20190526 (r271629) from the gcc-9-branch. - Fix PR libgomp/90527, PR c++/90532, PR libstdc++/90299, PR libstdc++/90454, PR debug/90197, PR pch/90326, PR c++/90484, PR tree-optimization/90385, PR c++/90383, PR tree-optimization/90303, PR tree-optimization/90316, PR tree-optimization/90316, PR libstdc++/90220, PR libstdc++/90557, PR sanitizer/90570, PR target/90547 (x86), PR libfortran/90038, PR fortran/90498, PR libfortran/90038, PR libfortran/90038, PR fortran/54613, PR fortran/54613, PR libstdc++/85965, PR target/90530 (PARISC), PR c++/90572. * Turn on -fstack-clash-protection and -fcf-protection in Ubuntu 19.10 on supported architectures. * Fix PR bootstrap/87338 on ia64 (James Clarke). Addresses: #927976. * Enable LTO builds on 64bit architectures. * Update libstdc++ symbols files for gcc-4-compatible builds. * Build the nvptx offload compiler on ppc64el. * Build the libgomp-hsa plugin. -- Matthias Klose Sun, 26 May 2019 17:59:59 +0200 -- 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/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in gcc-9 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Committed Status in virtualbox package in Ubuntu: Confirmed Status in xtables-addons package in Ubuntu: New Bug description: Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+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 1665447] Re: kernel ppa is building amd64 files inside mainline ppc64el package
I know that these mainline builds are unsupported in any way, but there have been some efforts to quickly patch this problem for cross- compiling. Examples: https://bugs.launchpad.net/ubuntu/+source/linux-ti- omap4/+bug/666267/comments/16 Also, I wrote up a quick hacky post-install script to workaround this issue, which works for arm64 mainline builds, here: https://gist.github.com/satmandu/b60a804fa2275615c88367bc68e4bad0 As a quick summary of the problem, it appears that these files are needed in the target architecture to build modules, but are in the cross-compile host architecture: scripts/recordmcount scripts/mod/modpost scripts/basic/fixdep "make scripts" does everything except make modpost, so I use "make modules_prepare" which errors out, but does make everything one needs. Oh, and unfortunately the packaging scripts seem to leave out these header files which are needed for the aforementioned compile process: security/selinux/include/classmap.h security/selinux/include/initial_sid_to_string.h tools/include/tools/be_byteshift.h tools/include/tools/le_byteshift.h So I download those first too. If any of that process could be eliminated, it would be appreciated. :) -- 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/1665447 Title: kernel ppa is building amd64 files inside mainline ppc64el package Status in linux package in Ubuntu: Incomplete Bug description: Kernel PPA contains a files that are compiled against amd64 instead of ppc64el. This makes this kernel unusable: Example: PPA: http://kernel.ubuntu.com/~kernel-ppa/mainline/ Kernel: http://kernel.ubuntu.com/\~kernel-ppa/mainline/v4.10-rc8 /linux- headers-4.10.0-041000rc8-generic_4.10.0-041000rc8.201702121731_ppc64el.deb ➜ ppa dpkg-deb -x linux- headers-4.10.0-041000rc8-generic_4.10.0-041000rc8.201702121731_ppc64el.deb . ➜ ppa find . -name fixdep ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep ➜ ppa file ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=438d1c0255e4943c4af1b9568a4cbe83d9034737, not stripped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665447/+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 1827750] Re: Not boot with EFI
FYI the mainline arm64 kernels at https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.1.1/ boot on the 3B running arm64 on disco, with grub- efi-arm64-bin installed and a commandline of modprobe.blacklist=vc,vc4 (but I haven't tried without using the module blacklist for some time.) Since the default RPI bootloader doesn't seem to handle kernels with an EFI stub though, enabling the EFI stub will cause boot problems on kernels using the built-in RPI bootloader, no? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1827750 Title: Not boot with EFI Status in linux-raspi2 package in Ubuntu: Fix Committed Bug description: Hello. I can't boot with linux-raspi2 kernel, but linux-generic work fine. Please add support kernel option CONFIG_U(EFI)_STUB=y as default. Thanks. os: ubuntu 18.04 lts arm64 hw: raspberry pi 3b (+ tiano core uefi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1827750/+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 1803206] Re: Please enable CONFIG_DMA_CMA=y on arm64
On the flip side, I am able to use dtoverlay=vc4-kms-v3d,cma-256 to boot my 3B+ on the disco kernel, which appears to allow me to use hardware accelerated decoding on the RPI. -- 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/1803206 Title: Please enable CONFIG_DMA_CMA=y on arm64 Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: Using the generic arm64 kernel on my raspberry pi 3 it seems impossible to use any apps that require 3D graphics. The X session crashes and a reboot is needed to make it bootable again. Inspecting dmesg, there are a lot of "failed to allocate CMA" messages. Adding cma=256M to the kernel command line has no effect. Dropping resolution allows firefox to start, but 3D apps still fail. I believe the vc4 driver needs CONFIG_DMA_CMA=y, which currently the generic kernel does not set. The raspi2 kernel has this and 3D graphics works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803206/+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
