[07:04] <greenleaf> I am unable to correctly build a module for the 5.11.7 kernel from here: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.7/. Getting "no symbol version for module_layout" which apparently has to do with VERMAGIC mismatch.
[07:05] <greenleaf> modinfo says: vermagic:       5.11.7-051107-generic+ SMP mod_unload modversions
[07:05] <greenleaf> uname says: 5.11.7-051107-generic #202103171746 SMP
[07:06] <greenleaf> which looks the same to me, except for the "+" sign at the end of the modinfo output. modyle VERMAGIC seems to be inherited from the Makefile, which I modified myself and it does not contain the "+" 
[07:33] <greenleaf> ok, i figured out how to get rid of the + by overriding with LOCALVERSION. Now the strings look identical but modprobe still complains.
[19:11] <uschcld> I'm trying to report a kernel bug. hfs+ failure
[19:19] <uschcld> I've never used this hexchat before. Is anyone there?
[19:20] <greenleaf> yes, people see what you write
[19:22] <tomreyn> !bug | uschcld
[19:22] <uschcld> Good! I submitted this bug to bugs.launchpad.net/ August 2020. It expired with nothing done.
[19:22] <tomreyn> that's if oyu think it's ubuntu specific, or you want to report it against ubuntu as a first step
[19:23] <tomreyn> it will expire when there is information missing
[19:23] <uschcld> It is actuallu a kernel bug, not specific to anu distro.
[19:23] <tomreyn> got the bug # ?
[19:23] <uschcld> Bug #1891768
[19:25] <uschcld> i followed up on https://answers.launchpad.net/ no response there, except one person also had the bug
[19:26] <uschcld> I suspect I missed some detail, but do not know what to do to correct it.
[19:27] <tomreyn> uschcld: so the bug you reported was handled by humans in addition to the bot, and you provided all the info requested. however, unfortunately, it was not possible to identify an error condition when the logs you submitted were (manually) reviewed.
[19:28] <uschcld> Did anyone try to duplicate the bug? It fails every time.
[19:29] <uschcld> I have listed some tested kernels that work and fail here.  https://answers.launchpad.net/ubuntu/+source/linux/+question/695770
[19:29] <tomreyn> it seems you didn't do just enough to enable the kernel dev's to reproduce the issue, so the bug report expired automatically.
[19:30] <tomreyn> (i'm referring to the bug report)
[19:30] <uschcld> More details to reproduce the bug in the answers.launchpad.com post
[19:33] <tomreyn> so answers.launchpad.com is, just like irc, mostly a community/self-support tool
[19:34] <tomreyn> bugs.launchpad.net is the bug tracker. since you now have condensed it down to a reproducible recipe, i suggest posting a new bug report where you provide the steps to reproduce on the latest LTS release
[19:35] <uschcld> thanks. Should I update the original bug report or make a new one?
[19:38] <tomreyn> i'd report a new one
[19:39] <tomreyn> you can always link to the old one
[19:39] <tomreyn> but make sure all info needed to reproduce is in the new report
[19:40] <tomreyn> run    ubuntu-bug linux    on your 20.04 LTS system to get started
[19:41] <uschcld> Thanks!