/srv/irclogs.ubuntu.com/2023/05/08/#ubuntu-kernel.txt

kashyapHi, folks.  Is "ubuntu-kernel" the right package to tag for a potential kernel issue?  This was found in a CI of upstream OpenStack - https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/201861209:39
-ubottu:#ubuntu-kernel- Launchpad bug 2018612 in OpenStack Compute (nova) "Guest kernel crashes with GPF on volume attach" [Undecided, Triaged]09:39
kashyap(There's a rough reproducer in the description.  And I've added some environment details)09:43
=== ben__ is now known as ben_r
juerghkashyap: 5.3.0-26-generic is old and unsupported.11:48
juerghcan you upgrade that machine?11:49
juerghOh it's a guest kernel. Sorry, you need to upgrade your guest image. 11:52
kashyapjuergh: Oh, is it?  I was told that kernel (5.3.0-26-generic) from CirrOS 0.5.2 is part of Ubuntu LTS11:52
kashyapjuergh: But yeah; I think it might be possible to use a newer CirrOS image 0.6.1 (which has 5.15.0-48-generic)11:52
kashyapjuergh: Yeah, it's the guest kernel indeed.11:53
kashyapjuergh: Right; the current guest image is 0.5.2.  I made a quick comparison here: https://kashyapc.fedorapeople.org/CirrOS_segfault/CirrOS-0.5.2-vs-0.6.1-kernel.txt11:53
juerghPresumable 5.3 was the HWE at the time the image was cut but it's no longer supported. It's 5.4 now, same as focal.11:53
kashyapAh-ha11:53
kashyapWhy do you say "Presumable"? :-) Isn't it confirmed that it is 5.3 in this case?11:54
kashyapOr maybe you're saying was "5.3 was presumably the HWE at the time of image cut"11:55
juerghhrm. the image was built in 2021 so I'm not sure why it pulled in a 5.3 kernel. 11:56
juerghwould be good to understand how that image is built11:56
juergheven though it's not Ubuntu and you're on your own ;-)11:57
kashyapjuergh: I think it's just plain vanilla 0.5.1 - https://download.cirros-cloud.net/0.5.1/cirros-0.5.1-x86_64-disk.img11:57
kashyapjuergh: If you have time, mind adding some of your observations on the bug?11:59
juerghoh yes. 0.5.1 was built in march 2020, before focal release which can explain the 5.3 kernel.12:01
juergh0.5.2 didn't upgrade the kernel apparently12:01
juerghyes, will update the bug and mark it invalid...12:01
juerghbtw, for future bug reports, the package to report kernel bugs for is linux12:02
kashyapjuergh: Ah, so the CirrOS 0.5.2 image should update the kernel.  Thanks12:09
kashyapjuergh: Also, noted: the package name.  "Qlinux" is rather cryptic pacakge name; it's impossible to discover it from the list of possible options when you type "kernel" in the launchpad12:10
juerghyes if that is still a supported image it should be updated to include a supported kernel12:10
juerghwell. if you open a bug from an Ubuntu system it is smart. you're running something (cirros) that is not really Ubuntu...12:11
juerghbut yes, LP is not easy to navigate.12:11
kashyapjuergh: I'm running neither; I'm on Fedora.  And these bugs occur in a CI system, so no way file "a bug from that system".  I'm just retroactively "piecing together the scene from the explosion"12:12
kashyap(Maybe there is some ABRT-style reporting system (that Fedora uses) on Ubuntu too, to auto-report certain kinds of crashes.  Haven't looked into it)12:13
kashyapjuergh: Thank you for looking.12:14
juerghkashyap: the bug should really be filed against cirros and not ubuntu: https://github.com/cirros-dev/cirros/issues12:17
kashyapjuergh: Okay ... me goes to file.  So the issue in short is 0.5.2 image should update to LTS kernel 5.4 (from Focal) -- yeah?12:18
kashyapAny other detail to add?12:18
juerghbug then again, that's only the build recipes. who build/owns the openstack cirros images?12:18
kashyapjuergh: I don't think the CI infra builds custom CirrOS images; just pull 'em from CirrOS upstream.  (But I'll double-check)12:19
juerghkashyap: oh they do build images from github. ok, then ask them to update 0.5 and pull in updated packages.12:22
kashyapjuergh: "they" == CirrOS?12:22
kashyapOr OpenStack CI?12:22
juerghkashyap: cirros-dev on github12:22
kashyapAh, right; also how do they know what _other_ packages to update?12:23
kashyapYou say "pull in updated packages" -- how do they discover it?  (I know, it's "not my problem"; but I'm curious :))12:23
kashyapMaybe you just mean "pull in kernel and whatever dependent packages"12:24
kashyapThanks for your comment in the LP bug!12:24
juerghkashyap: don't know how they build that image but I assume they point at an Ubuntu mirror so when they rebuild the image they should get latest package versions. they should periodically refresh the images anyways...12:25
kashyapNoted.  They do have a 0.6.1 version image, though (as noted earlier).12:26
* kashyap goes to file the issue for cirros-0.5.2. I'll quote your comment verbatim from the LP bug, with context; hope that's fine.12:26
kashyapjuergh: If you got the full 5.4 kernel version of Focal handy, can you please post it here?12:27
juerghkashyap: https://launchpad.net/ubuntu/+source/linux12:29
juerghall the versions of the different series12:29
kashyapjuergh: Very handy list; thank you.12:31
kashyapjuergh: Hope that reads fine to you: https://github.com/cirros-dev/cirros/issues/10212:47
-ubottu:#ubuntu-kernel- Issue 102 in cirros-dev/cirros "Update CirrOS 0.5.2 kernel image to a supported version (kernel-5.4; from Focal)" [Open]12:47
=== halvors1 is now known as halvors
lotuspsychjejuergh: seems like Bug #2018128 package got back to linux18:10
-ubottu:#ubuntu-kernel- Bug 2018128 in linux (Ubuntu) "Apport does not collect all logs when the package is HWE kernel" [Undecided, Confirmed] https://launchpad.net/bugs/201812818:10
=== NotEickmeyer is now known as Eickmeyer

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!