[Kernel-packages] [Bug 1848496] Re: [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX failed: Device or resource busy" against devices owned by ZFS

2020-05-10 Thread fermulator
Agree w/ @rlaager, this SHOULD NOT be functionally impacting in any way. The update-grub command is not actually failing, just spewing errors during os-prober. We want to clean it up (it is cosmetic). -- You received this bug notification because you are a member of Kernel Packages, which is sub

[Kernel-packages] [Bug 1848496] Re: [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX failed: Device or resource busy" against devices owned by ZFS

2020-05-30 Thread fermulator
@chilewskirbuu that is a reasonable workaround - NOTE: it would break dual-boot though, so WARNING: don't use that as a workaround unless you are sure you are not using dual boot; -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux i

[Kernel-packages] [Bug 1848496] Re: [zfs-root] device-mapper: reload ioctl on osprober-linux-sda5 failed: Device or resource busy

2020-01-26 Thread fermulator
Please also see https://github.com/zfsonlinux/zfs/issues/9801 - it has a full set of technical details related to this topic. ** Bug watch added: Github Issue Tracker for ZFS #9801 https://github.com/zfsonlinux/zfs/issues/9801 -- You received this bug notification because you are a member of

[Kernel-packages] [Bug 1860228] [NEW] addition of zfsutils-linux scrib every 2nd sunday

2020-01-18 Thread fermulator
Public bug reported: FULL REF: https://github.com/zfsonlinux/zfs/issues/9858 (initially submitted there mistakenly) ==System information== {{{ TypeVersion/Name Distribution Name Ubuntu Distribution Version18.04.3 LTS Linux Kernel4.15.0-73-generic Architecturex86_64 ZFS Versi

[Kernel-packages] [Bug 1860228] Re: addition of zfsutils-linux scrib every 2nd sunday

2020-01-19 Thread fermulator
@rlaager ref for "long time ago"? (Looking for release notes and specific version) I've been reasonably diligent in monitoring my pool scrub activity, I would "guess" that maybe in the last 2-3 months I may have lost track. But also I only upgraded from Ubuntu 16.04 LTS sometime late-2019 Fall (ii

[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode

2018-04-14 Thread fermulator
fwiw, I too experience this issue on Dell LATITUDE E4310 $ cat /etc/issue Linux Mint 18.3 Sylvia \n \l $ uname -a Linux fermmy-notebook 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- since this has been closed as "invalid", is this to mea

[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode

2018-04-14 Thread fermulator
(PS: as per typical recommendations, I have submitted a unique bug report for my specific system https://bugs.launchpad.net/dell- sputnik/+bug/1763968) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

2020-09-15 Thread fermulator
"me too" - Dell Latitude w/ a Dell WD16 USB-C dock. After recent firmware updates it got significantly worse and nearly never properly re-attaches after suspend/resume. Dell 5400 Latitude: (0.1.9.1=same, 0.1.7.4=older, 0.1.6.5=older, 0.1.5.1=older, 0.1.4.2=older) dock: ``` No upgrades for RTS541

[Kernel-packages] [Bug 1170697] Re: Sound not working after upgrading to 3.8.0-19

2013-08-11 Thread fermulator
*** This bug is a duplicate of bug 1169984 *** https://bugs.launchpad.net/bugs/1169984 Interesting. I am also experiencing this same bug on Ubuntu 12.04 (3.2 kernel...) -- did we accidentally back-merge the bug? {{{ multimedia@fermmy-media:~$ uname -a Linux fermmy-media 3.2.0-51-generic-pae #

[Kernel-packages] [Bug 1169984] Re: 3.8.0-18 HDMI/DisplayPort audio regression: Either oops or opening device fails with -ENODEV

2013-08-11 Thread fermulator
(oops, posted in the Dup'd bug #1170697) - reposting here Interesting. I am also experiencing this same bug on Ubuntu 12.04 (3.2 kernel...) -- did we accidentally back-merge the bug? {{{ multimedia@fermmy-media:~$ uname -a Linux fermmy-media 3.2.0-51-generic-pae #77-Ubuntu SMP Wed Jul 24 20:40:32

[Kernel-packages] [Bug 1169984] Re: 3.8.0-18 HDMI/DisplayPort audio regression: Either oops or opening device fails with -ENODEV

2013-08-11 Thread fermulator
Also, it's worthy to note, that after disabling the HDMI kernel module as recommended as workaround, Pulse no longer crashes, and I can successfully use my Creative SB card again -- /not/ using HDMI audio on the Graphics Card. -- You received this bug notification because you are a member of Kern

[Kernel-packages] [Bug 1848496] Re: [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX failed: Device or resource busy" against devices owned by ZFS

2020-03-10 Thread fermulator
** Summary changed: - [zfs-root] device-mapper: reload ioctl on osprober-linux-sda5 failed: Device or resource busy + [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX failed: Device or resource busy" against devices owned by ZFS -- You received this bug notification because you

[Kernel-packages] [Bug 1936573] Re: logitech-djreceiver spams Dmesg (Unexpected input report number 128)

2022-04-02 Thread fermulator
@Hans de Goede / @Filipe LaĆ­ns https://lkml.iu.edu/hypermail/linux/kernel/2103.1/04435.html Who would be the code owner here to fix the issue? ** Summary changed: - logitech-djreceiver spams Dmesg + logitech-djreceiver spams Dmesg (Unexpected input report number 128) -- You received this bug

[Kernel-packages] [Bug 1936573] Re: logitech-djreceiver spams Dmesg (Unexpected input report number 128)

2022-04-02 Thread fermulator
Submitted actual kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=215796 ** Bug watch added: Linux Kernel Bug Tracker #215796 https://bugzilla.kernel.org/show_bug.cgi?id=215796 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed

[Kernel-packages] [Bug 1936573] Re: logitech-djreceiver spams Dmesg

2022-03-20 Thread fermulator
There are loads of issue reports that complain about this with Logitech hardware. https://linuxlists.cc/l/1/linux- kernel/t/3934117/logitech_g602_wireless_mouse_kernel_error_messages_in_5.10.11+_kernels ^ This thread _claims_ a fix was put in but it has not been (running 5.13 kernel) I have repo

[Kernel-packages] [Bug 1936573] Re: logitech-djreceiver spams Dmesg

2022-03-20 Thread fermulator
I tried adding /etc/rsyslog.d/50-default.conf :msg, contains, "Unexpected input report number" stop but it doesn't work :( -- 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/1936573 Title:

[Kernel-packages] [Bug 1936573] Re: logitech-djreceiver spams Dmesg

2022-03-20 Thread fermulator
For now sudo modprobe -r hid_logitech_dj and /etc/modprobe.d/blacklist.conf # Logitech HID driver sucks for G602 # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936573/ # https://github.com/libratbag/libratbag/issues/832 blacklist hid-logitech-dj -- You received this bug notification b