[Bug 1225352] New: [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting?
https://bugzilla.suse.com/show_bug.cgi?id=1225352 Bug ID: 1225352 Summary: [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting? Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://openqa.opensuse.org/tests/4217406/modules/prep are_firstboot/steps/1 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Live Medium Assignee: fvogt@suse.com Reporter: fvogt@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: openQA Blocker: --- The Leap 15.5 JeOS image fails to boot in openQA for some time now. Initially it looked to me like an issue with the test infra, but the TW and 15.6 images boot while 15.5 fails consistently. I tried to reproduce the issue locally and except for a slow boot due to no ethernet cable it worked. The package diff between last working and latest build shows changes in aaa_base, coreutils, kernel, less, protobuf, libsemanage, perl, rpm and yast. Could be a kernel issue? ## Observation openQA test in scenario opensuse-15.5-JeOS-for-RPi-aarch64-jeos@RPi3 fails in [prepare_firstboot](https://openqa.opensuse.org/tests/4217406/modules/prepare_firstboot/steps/1) ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [13.183](https://openqa.opensuse.org/tests/4120363) ## Expected result Last good: [13.182](https://openqa.opensuse.org/tests/4119085) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensuse&flavor=JeOS-for-RPi&machine=RPi3&test=jeos&version=15.5) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c1 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(guillaume.gardet@ | |arm.com) CC| |guillaume.gardet@arm.com --- Comment #1 from Fabian Vogt <fvogt@suse.com> --- Could you have a look what the SUT is doing when the test fails? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c2 --- Comment #2 from Guillaume GARDET <guillaume.gardet@arm.com> --- I would guess a problem with network. I will have deeper look. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c3 Guillaume GARDET <guillaume.gardet@arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(guillaume.gardet@ | |arm.com) | --- Comment #3 from Guillaume GARDET <guillaume.gardet@arm.com> --- Created attachment 875139 --> https://bugzilla.suse.com/attachment.cgi?id=875139&action=edit 15.5 boot log on serial (from openQA run) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c4 Guillaume GARDET <guillaume.gardet@arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #875139|0 |1 is obsolete| | --- Comment #4 from Guillaume GARDET <guillaume.gardet@arm.com> --- Created attachment 875148 --> https://bugzilla.suse.com/attachment.cgi?id=875148&action=edit 15.5 serial boot log with a longer timeout With a longer timeout, it manages to boot until login prompt and starts jeos-fisrtboot on serial. I think jeos-fisrtboot should not be started as it blocks the start of the ssh server. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c5 --- Comment #5 from Fabian Vogt <fvogt@suse.com> --- (In reply to Guillaume GARDET from comment #4)
Created attachment 875148 [details] 15.5 serial boot log with a longer timeout
With a longer timeout, it manages to boot until login prompt and starts jeos-fisrtboot on serial.
I think jeos-fisrtboot should not be started as it blocks the start of the ssh server.
Why does it start jeos-firstboot? AFAIK it shouldn't be enabled in this image? In my local test run it did not. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(guillaume.gardet@ | |arm.com) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c6 Guillaume GARDET <guillaume.gardet@arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(guillaume.gardet@ | |arm.com) | --- Comment #6 from Guillaume GARDET <guillaume.gardet@arm.com> --- (In reply to Fabian Vogt from comment #5)
(In reply to Guillaume GARDET from comment #4)
Created attachment 875148 [details] 15.5 serial boot log with a longer timeout
With a longer timeout, it manages to boot until login prompt and starts jeos-fisrtboot on serial.
I think jeos-fisrtboot should not be started as it blocks the start of the ssh server.
Why does it start jeos-firstboot? AFAIK it shouldn't be enabled in this image?
In my local test run it did not.
Ah no, sorry, an additional boot from a Tumbleweed test polluted the serial log. It hanged after: ********** [ OK ] Listening on Load/Save RF …itch Status /dev/rfkill Watch. Starting Security Auditing Service... Starting Rebuild Journal Catalog... [ OK ] Finished Commit a transient machine-id on disk. Starting Load/Save RF Kill Switch Status... ********** -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c7 --- Comment #7 from Fabian Vogt <fvogt@suse.com> --- (In reply to Guillaume GARDET from comment #6)
(In reply to Fabian Vogt from comment #5)
(In reply to Guillaume GARDET from comment #4)
Created attachment 875148 [details] 15.5 serial boot log with a longer timeout
With a longer timeout, it manages to boot until login prompt and starts jeos-fisrtboot on serial.
I think jeos-fisrtboot should not be started as it blocks the start of the ssh server.
Why does it start jeos-firstboot? AFAIK it shouldn't be enabled in this image?
In my local test run it did not.
Ah no, sorry, an additional boot from a Tumbleweed test polluted the serial log.
It hanged after: ********** [ OK ] Listening on Load/Save RF …itch Status /dev/rfkill Watch. Starting Security Auditing Service... Starting Rebuild Journal Catalog... [ OK ] Finished Commit a transient machine-id on disk. Starting Load/Save RF Kill Switch Status... **********
Did it completely hang or just take a long time? Can you get the full journal? Smells like a kernel issue. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(guillaume.gardet@ | |arm.com) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c8 Guillaume GARDET <guillaume.gardet@arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(guillaume.gardet@ | |arm.com) | --- Comment #8 from Guillaume GARDET <guillaume.gardet@arm.com> --- (In reply to Fabian Vogt from comment #7)
(In reply to Guillaume GARDET from comment #6)
(In reply to Fabian Vogt from comment #5)
(In reply to Guillaume GARDET from comment #4)
Created attachment 875148 [details] 15.5 serial boot log with a longer timeout
With a longer timeout, it manages to boot until login prompt and starts jeos-fisrtboot on serial.
I think jeos-fisrtboot should not be started as it blocks the start of the ssh server.
Why does it start jeos-firstboot? AFAIK it shouldn't be enabled in this image?
In my local test run it did not.
Ah no, sorry, an additional boot from a Tumbleweed test polluted the serial log.
It hanged after: ********** [ OK ] Listening on Load/Save RF …itch Status /dev/rfkill Watch. Starting Security Auditing Service... Starting Rebuild Journal Catalog... [ OK ] Finished Commit a transient machine-id on disk. Starting Load/Save RF Kill Switch Status... **********
Did it completely hang or just take a long time? Can you get the full journal?
Looks like a hang. I waited more than 10 min after the boot and the serial was unresponsive after those lines. (No login prompt) I will try to get more traces on serial. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fvogt@suse.com |kernel-bugs@opensuse.org Hardware|Other |aarch64 Component|Live Medium |Kernel -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 Ivan Ivanov <ivan.ivanov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ivan.ivanov@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c9 Guillaume GARDET <guillaume.gardet@arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian.glaubitz@suse.com --- Comment #9 from Guillaume GARDET <guillaume.gardet@arm.com> --- *** Bug 1225787 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 Robert Munteanu <rombert@apache.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rombert@apache.org -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 Miroslav Beneš <mbenes@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arm-bugs@suse.de, | |mbenes@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 Ivan Ivanov <ivan.ivanov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrea.porta@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c11 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major --- Comment #11 from Fabian Vogt <fvogt@suse.com> --- Ping. Raising severity as well. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 Dominik Heidler <dheidler@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dheidler@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c12 Zaoliang Luo <zluo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zluo@suse.com --- Comment #12 from Zaoliang Luo <zluo@suse.com> --- I tested today for both RPi 3 and 4, no issue at all. https://paste.opensuse.org/pastes/6733655a325c or Mac-mini:.ssh Zaoliang$ ssh zaoliang@192.168.8.187 The authenticity of host '192.168.8.187 (192.168.8.187)' can't be established. ED25519 key fingerprint is SHA256:xWM/Nt3SdkZ7W1YyOnG4FEbB/WdAXrGDMlGfFopQWYM. This key is not known by any other names. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '192.168.8.187' (ED25519) to the list of known hosts. (zaoliang@192.168.8.187) Password: Have a lot of fun... zaoliang@localhost:~> cat /etc/os-release NAME="openSUSE Leap" VERSION="15.5" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.5" PRETTY_NAME="openSUSE Leap 15.5" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.5" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Leap" LOGO="distributor-logo-Leap" -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c13 --- Comment #13 from Zaoliang Luo <zluo@suse.com> --- openSUSE-Leap-15.5-ARM-JeOS-raspberrypi.aarch64-2023.03.31-Build13.217.raw.xz is used. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c14 --- Comment #14 from Zaoliang Luo <zluo@suse.com> --- I checked this on another device, in this case RPi 400. It boots up from grub menu, but never reached prompt or desktop. This is quite strange. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c15 --- Comment #15 from Andrea della Porta <andrea.porta@suse.com> --- Hi, is there at least one report of non-booting Rpi4 or does it hangs only on Rpi3? Furthermore, doers runnign it on CM4 make any difference wrt running it on straight model B? Thanks -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c16 --- Comment #16 from Fabian Vogt <fvogt@suse.com> --- (In reply to Andrea della Porta from comment #15)
Hi, is there at least one report of non-booting Rpi4 or does it hangs only on Rpi3? Furthermore, doers runnign it on CM4 make any difference wrt running it on straight model B?
Thanks
I'm not aware of any issues on RPi 4, but on my RPi 3 the image works fine so it might just be random... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c17 --- Comment #17 from Andrea della Porta <andrea.porta@suse.com> --- Rpi4 works just fine, rpi3 is hanging somewhat randomly. Some investigation is needed. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c18 --- Comment #18 from Andrea della Porta <andrea.porta@suse.com> --- For the record, I'm testing openSUSE-Leap-15.5-ARM-JeOS-raspberrypi.aarch64-2023.03.31-Build13.217.raw.xz. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c19 --- Comment #19 from Andrea della Porta <andrea.porta@suse.com> --- (In reply to Robert Munteanu from comment #10)
To echo the comments from bug #1225787
- kernel 5.14.21-150500.55.52-default was the last known working kernel from me - same system does not boot with kernel-default-5.14.21-150500.55.59.1.aarch64
5.14.21-150500.55.52-default does not work for me either. May I ask you how did you test the older kernel? Did you just burn an older Leap raw image on SD or did you just downgrade the kernel via commandline with something like: zypper install --oldpackage kernel-default=5.14.21-150500.55.52.1 Many thanks -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c20 --- Comment #20 from Zaoliang Luo <zluo@suse.com> --- (In reply to Andrea della Porta from comment #19)
(In reply to Robert Munteanu from comment #10)
To echo the comments from bug #1225787
- kernel 5.14.21-150500.55.52-default was the last known working kernel from me - same system does not boot with kernel-default-5.14.21-150500.55.59.1.aarch64
5.14.21-150500.55.52-default does not work for me either. May I ask you how did you test the older kernel? Did you just burn an older Leap raw image on SD or did you just downgrade the kernel via commandline with something like:
zypper install --oldpackage kernel-default=5.14.21-150500.55.52.1
Many thanks
5.14.21-150500.55.65-default(In reply to Andrea della Porta from comment #19)
(In reply to Robert Munteanu from comment #10)
To echo the comments from bug #1225787
- kernel 5.14.21-150500.55.52-default was the last known working kernel from me - same system does not boot with kernel-default-5.14.21-150500.55.59.1.aarch64
5.14.21-150500.55.52-default does not work for me either. May I ask you how did you test the older kernel? Did you just burn an older Leap raw image on SD or did you just downgrade the kernel via commandline with something like:
zypper install --oldpackage kernel-default=5.14.21-150500.55.52.1
Many thanks
openSUSE-Leap-15.5-ARM-JeOS-raspberrypi.aarch64-2023.03.31-Build13.217.raw.xz is working fine, 5.14.21-150500.55.65-default. maybe an issue with SD card? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c21 --- Comment #21 from Andrea della Porta <andrea.porta@suse.com> ---
openSUSE-Leap-15.5-ARM-JeOS-raspberrypi.aarch64-2023.03.31-Build13.217.raw. xz is working fine, 5.14.21-150500.55.65-default.
you tested it on rpi4 or also on rpi3? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c22 --- Comment #22 from Zaoliang Luo <zluo@suse.com> --- (In reply to Andrea della Porta from comment #21)
openSUSE-Leap-15.5-ARM-JeOS-raspberrypi.aarch64-2023.03.31-Build13.217.raw. xz is working fine, 5.14.21-150500.55.65-default.
you tested it on rpi4 or also on rpi3?
yes, both. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c23 --- Comment #23 from Robert Munteanu <rombert@apache.org> --- (In reply to Andrea della Porta from comment #19)
(In reply to Robert Munteanu from comment #10)
To echo the comments from bug #1225787
- kernel 5.14.21-150500.55.52-default was the last known working kernel from me - same system does not boot with kernel-default-5.14.21-150500.55.59.1.aarch64
5.14.21-150500.55.52-default does not work for me either. May I ask you how did you test the older kernel? Did you just burn an older Leap raw image on SD or did you just downgrade the kernel via commandline with something like:
zypper install --oldpackage kernel-default=5.14.21-150500.55.52.1
Many thanks
I had the old kernel installed, it was not cleaned up. There was no manipulation of the SD card or reinstallation. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c25 --- Comment #25 from Andrea della Porta <andrea.porta@suse.com> --- I confirm that build 13.224 does not work (hangs as expected by the ticket), just like 13.217: in fact they share the exact same kernel. Some further info: adding modprobe.blacklist=vc4 avoid the issue and let the Rpi3 boot correctly (albeit without monitor support). On rpi4, everything is ok and vc4 module does not hang. Also, on rpi3, this is the ftrace stack when it hangs (on vc4 module only: "echo '*:mod:vc4' > set_ftrace_filter"): 2) | vc4_drm_register [vc4]() { 2) + 12.813 us | vc4_hvs_dev_probe [vc4](); 2) + 30.521 us | vc4_hdmi_dev_probe [vc4](); 2) + 54.844 us | vc4_vec_dev_probe [vc4](); 2) + 21.146 us | vc4_txp_probe [vc4](); 2) + 18.855 us | vc4_crtc_dev_probe [vc4](); 2) 7.656 us | vc4_crtc_dev_prob there's report in this ticket that 15.6 works (I've not tried it by myself yet), and from 15.5 (kernel 5.14) to 15.6 (kernel 6.4) there's plenty of kernel commits related to vc4, two of which (at least) may be worth our attention since solve crashes: 797d72ce8e0f8 and c86b41214362e8e. Reassigning to the HW enablement team. Many thanks, Andrea -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 Andrea della Porta <andrea.porta@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c26 --- Comment #26 from Patrik Jakobsson <patrik.jakobsson@suse.com> --- At a quick glance this might be a mismatch between kernel and DTB. Perhaps the RPi firmware package changed (or needs to be updated)? The firmware lives on the SD-card so I'm not sure how this is updated in QA. Ivan, since you know the platform better, do you have any thoughts? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c28 Ivan Ivanov <ivan.ivanov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com --- Comment #28 from Ivan Ivanov <ivan.ivanov@suse.com> --- Devicetree's for RPi's are provided by raspberrypi-firmware-dt package. Which hasn't been updated in a while(5 months). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c29 --- Comment #29 from Andrea della Porta <andrea.porta@suse.com> --- Sorry Patrick, any update or findings on your side? Many thanks, Andrea -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 Andrea della Porta <andrea.porta@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(patrik.jakobsson@ | |suse.com) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c30 Patrik Jakobsson <patrik.jakobsson@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(patrik.jakobsson@ | |suse.com) | --- Comment #30 from Patrik Jakobsson <patrik.jakobsson@suse.com> --- I found a potential issue in [1]. I'm building a test kernel at [2]. Please test and report back. [1] suse-commit: 048f829d4b52520058c31bae2ef1ec08563c460a [2] https://build.opensuse.org/project/show/home:patrikjakobsson:bsc1225352 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c31 --- Comment #31 from Andrea della Porta <andrea.porta@suse.com> --- (In reply to Patrik Jakobsson from comment #30)
I found a potential issue in [1]. I'm building a test kernel at [2]. Please test and report back.
[1] suse-commit: 048f829d4b52520058c31bae2ef1ec08563c460a [2] https://build.opensuse.org/project/show/home:patrikjakobsson:bsc1225352
Hi Patrik, the kernel you've built with your patch is working fine...nice one! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c32 --- Comment #32 from Patrik Jakobsson <patrik.jakobsson@suse.com> --- Great, then I'll push the fix to SLE15-SP5 kernel branch. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c37 --- Comment #37 from Maintenance Automation <maint-coord+maintenance-robot@suse.de> --- SUSE-SU-2024:3190-1: An update that solves 292 vulnerabilities, contains two features and has 45 security fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2024/suse-su-20243190-1 Category: security (important) Bug References: 1193629, 1194111, 1194765, 1194869, 1196261, 1196516, 1196894, 1198017, 1203329, 1203330, 1203360, 1205462, 1206006, 1206258, 1206843, 1207158, 1208783, 1210644, 1213580, 1213632, 1214285, 1216834, 1220428, 1220877, 1220962, 1221269, 1221326, 1221630, 1221645, 1222335, 1222350, 1222372, 1222387, 1222634, 1222808, 1222967, 1223074, 1223191, 1223508, 1223720, 1223742, 1223777, 1223803, 1223807, 1224105, 1224415, 1224496, 1224510, 1224542, 1224578, 1224639, 1225162, 1225352, 1225428, 1225524, 1225578, 1225582, 1225773, 1225814, 1225827, 1225832, 1225903, 1226168, 1226530, 1226613, 1226742, 1226765, 1226798, 1226801, 1226874, 1226885, 1227079, 1227623, 1227761, 1227830, 1227863, 1227867, 1227929, 1227937, 1227958, 1228020, 1228065, 1228114, 1228410, 1228426, 1228427, 1228429, 1228446, 1228447, 1228449, 1228450, 1228452, 1228456, 1228463, 1228466, 1228467, 1228469, 1228480, 1228481, 1228482, 1228483, 1228484, 1228485, 1228487, 1228489, 1228491, 1228493, 1228494, 1228495, 1228496, 1228501, 1228503, 1228509, 1228513, 1228515, 1228516, 1228526, 1228531, 1228563, 1228564, 1228567, 1228576, 1228579, 1228584, 1228588, 1228590, 1228615, 1228616, 1228635, 1228636, 1228654, 1228656, 1228658, 1228660, 1228662, 1228667, 1228673, 1228677, 1228687, 1228706, 1228708, 1228710, 1228718, 1228720, 1228721, 1228722, 1228724, 1228726, 1228727, 1228733, 1228748, 1228766, 1228779, 1228801, 1228850, 1228857, 1228959, 1228964, 1228966, 1228967, 1228979, 1228988, 1228989, 1228991, 1228992, 1229042, 1229054, 1229086, 1229136, 1229154, 1229187, 1229188, 1229190, 1229287, 1229290, 1229292, 1229296, 1229297, 1229301, 1229303, 1229304, 1229305, 1229307, 1229309, 1229312, 1229314, 1229315, 1229317, 1229318, 1229319, 1229327, 1229341, 1229345, 1229346, 1229347, 1229349, 1229350, 1229351, 1229354, 1229356, 1229357, 1229358, 1229359, 1229360, 1229366, 1229370, 1229373, 1229374, 1229381, 1229382, 1229383, 1229386, 1229388, 1229391, 1229392, 1229395, 1229398, 1229399, 1229400, 1229407, 1229409, 1229410, 1229411, 1229413, 1229414, 1229417, 1229418, 1229444, 1229453, 1229454, 1229481, 1229482, 1229488, 1229489, 1229490, 1229493, 1229495, 1229497, 1229500, 1229503, 1229506, 1229507, 1229508, 1229509, 1229510, 1229512, 1229516, 1229521, 1229522, 1229523, 1229524, 1229525, 1229526, 1229527, 1229528, 1229529, 1229531, 1229533, 1229535, 1229536, 1229537, 1229540, 1229544, 1229545, 1229546, 1229547, 1229548, 1229554, 1229557, 1229558, 1229559, 1229560, 1229562, 1229564, 1229565, 1229566, 1229568, 1229569, 1229572, 1229573, 1229576, 1229581, 1229588, 1229598, 1229603, 1229604, 1229605, 1229608, 1229611, 1229612, 1229613, 1229614, 1229615, 1229616, 1229617, 1229620, 1229622, 1229623, 1229624, 1229625, 1229626, 1229628, 1229629, 1229630, 1229631, 1229632, 1229635, 1229636, 1229637, 1229638, 1229639, 1229641, 1229642, 1229643, 1229645, 1229657, 1229658, 1229662, 1229664, 1229707, 1229739, 1229743, 1229746, 1229754, 1229755, 1229756, 1229759, 1229761, 1229767, 1229768, 1229781, 1229784, 1229787, 1229788, 1229789, 1229792, 1229820 CVE References: CVE-2021-4441, CVE-2021-47106, CVE-2021-47517, CVE-2021-47546, CVE-2022-38457, CVE-2022-40133, CVE-2022-48645, CVE-2022-48706, CVE-2022-48808, CVE-2022-48865, CVE-2022-48868, CVE-2022-48869, CVE-2022-48870, CVE-2022-48871, CVE-2022-48872, CVE-2022-48873, CVE-2022-48875, CVE-2022-48878, CVE-2022-48880, CVE-2022-48881, CVE-2022-48882, CVE-2022-48883, CVE-2022-48884, CVE-2022-48885, CVE-2022-48886, CVE-2022-48887, CVE-2022-48888, CVE-2022-48889, CVE-2022-48890, CVE-2022-48891, CVE-2022-48893, CVE-2022-48896, CVE-2022-48898, CVE-2022-48899, CVE-2022-48903, CVE-2022-48904, CVE-2022-48905, CVE-2022-48906, CVE-2022-48907, CVE-2022-48909, CVE-2022-48910, CVE-2022-48912, CVE-2022-48913, CVE-2022-48914, CVE-2022-48915, CVE-2022-48916, CVE-2022-48917, CVE-2022-48918, CVE-2022-48919, CVE-2022-48920, CVE-2022-48921, CVE-2022-48923, CVE-2022-48924, CVE-2022-48925, CVE-2022-48926, CVE-2022-48927, CVE-2022-48928, CVE-2022-48929, CVE-2022-48930, CVE-2022-48931, CVE-2022-48932, CVE-2022-48934, CVE-2022-48937, CVE-2022-48938, CVE-2022-48939, CVE-2022-48940, CVE-2022-48941, CVE-2022-48942, CVE-2022-48943, CVE-2023-3610, CVE-2023-52458, CVE-2023-52489, CVE-2023-52498, CVE-2023-52581, CVE-2023-52859, CVE-2023-52887, CVE-2023-52889, CVE-2023-52893, CVE-2023-52894, CVE-2023-52896, CVE-2023-52898, CVE-2023-52899, CVE-2023-52900, CVE-2023-52901, CVE-2023-52904, CVE-2023-52905, CVE-2023-52906, CVE-2023-52907, CVE-2023-52908, CVE-2023-52909, CVE-2023-52910, CVE-2023-52911, CVE-2023-52912, CVE-2023-52913, CVE-2024-26631, CVE-2024-26668, CVE-2024-26669, CVE-2024-26677, CVE-2024-26735, CVE-2024-26808, CVE-2024-26812, CVE-2024-26835, CVE-2024-26851, CVE-2024-27010, CVE-2024-27011, CVE-2024-27016, CVE-2024-27024, CVE-2024-27079, CVE-2024-27403, CVE-2024-31076, CVE-2024-35897, CVE-2024-35902, CVE-2024-35945, CVE-2024-35971, CVE-2024-36009, CVE-2024-36013, CVE-2024-36270, CVE-2024-36286, CVE-2024-36489, CVE-2024-36929, CVE-2024-36933, CVE-2024-36936, CVE-2024-36962, CVE-2024-38554, CVE-2024-38602, CVE-2024-38662, CVE-2024-39489, CVE-2024-40905, CVE-2024-40978, CVE-2024-40980, CVE-2024-40995, CVE-2024-41000, CVE-2024-41007, CVE-2024-41009, CVE-2024-41011, CVE-2024-41016, CVE-2024-41020, CVE-2024-41022, CVE-2024-41035, CVE-2024-41036, CVE-2024-41038, CVE-2024-41039, CVE-2024-41042, CVE-2024-41045, CVE-2024-41056, CVE-2024-41060, CVE-2024-41062, CVE-2024-41065, CVE-2024-41068, CVE-2024-41073, CVE-2024-41079, CVE-2024-41080, CVE-2024-41087, CVE-2024-41088, CVE-2024-41089, CVE-2024-41092, CVE-2024-41093, CVE-2024-41095, CVE-2024-41097, CVE-2024-41098, CVE-2024-42069, CVE-2024-42074, CVE-2024-42076, CVE-2024-42077, CVE-2024-42080, CVE-2024-42082, CVE-2024-42085, CVE-2024-42086, CVE-2024-42087, CVE-2024-42089, CVE-2024-42090, CVE-2024-42092, CVE-2024-42095, CVE-2024-42097, CVE-2024-42098, CVE-2024-42101, CVE-2024-42104, CVE-2024-42106, CVE-2024-42107, CVE-2024-42110, CVE-2024-42114, CVE-2024-42115, CVE-2024-42119, CVE-2024-42120, CVE-2024-42121, CVE-2024-42126, CVE-2024-42127, CVE-2024-42130, CVE-2024-42137, CVE-2024-42139, CVE-2024-42142, CVE-2024-42143, CVE-2024-42148, CVE-2024-42152, CVE-2024-42155, CVE-2024-42156, CVE-2024-42157, CVE-2024-42158, CVE-2024-42162, CVE-2024-42223, CVE-2024-42225, CVE-2024-42228, CVE-2024-42229, CVE-2024-42230, CVE-2024-42232, CVE-2024-42236, CVE-2024-42237, CVE-2024-42238, CVE-2024-42239, CVE-2024-42240, CVE-2024-42244, CVE-2024-42246, CVE-2024-42247, CVE-2024-42268, CVE-2024-42271, CVE-2024-42274, CVE-2024-42276, CVE-2024-42277, CVE-2024-42280, CVE-2024-42281, CVE-2024-42283, CVE-2024-42284, CVE-2024-42285, CVE-2024-42286, CVE-2024-42287, CVE-2024-42288, CVE-2024-42289, CVE-2024-42291, CVE-2024-42292, CVE-2024-42295, CVE-2024-42301, CVE-2024-42302, CVE-2024-42308, CVE-2024-42309, CVE-2024-42310, CVE-2024-42311, CVE-2024-42312, CVE-2024-42313, CVE-2024-42315, CVE-2024-42318, CVE-2024-42319, CVE-2024-42320, CVE-2024-42322, CVE-2024-43816, CVE-2024-43818, CVE-2024-43819, CVE-2024-43821, CVE-2024-43823, CVE-2024-43829, CVE-2024-43830, CVE-2024-43831, CVE-2024-43834, CVE-2024-43837, CVE-2024-43839, CVE-2024-43841, CVE-2024-43842, CVE-2024-43846, CVE-2024-43849, CVE-2024-43853, CVE-2024-43854, CVE-2024-43856, CVE-2024-43858, CVE-2024-43860, CVE-2024-43861, CVE-2024-43863, CVE-2024-43866, CVE-2024-43867, CVE-2024-43871, CVE-2024-43872, CVE-2024-43873, CVE-2024-43879, CVE-2024-43880, CVE-2024-43882, CVE-2024-43883, CVE-2024-43884, CVE-2024-43889, CVE-2024-43892, CVE-2024-43893, CVE-2024-43894, CVE-2024-43895, CVE-2024-43899, CVE-2024-43900, CVE-2024-43902, CVE-2024-43903, CVE-2024-43904, CVE-2024-43905, CVE-2024-43907, CVE-2024-43908, CVE-2024-43909, CVE-2024-44938, CVE-2024-44939, CVE-2024-44947 Jira References: PED-8491, PED-8779 Maintenance Incident: [SUSE:Maintenance:35523](https://smelt.suse.de/incident/35523/) Sources used: openSUSE Leap 15.5 (src): kernel-syms-azure-5.14.21-150500.33.66.1, kernel-source-azure-5.14.21-150500.33.66.1 Public Cloud Module 15-SP5 (src): kernel-syms-azure-5.14.21-150500.33.66.1, kernel-source-azure-5.14.21-150500.33.66.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c39 --- Comment #39 from Maintenance Automation <maint-coord+maintenance-robot@suse.de> --- SUSE-SU-2024:3209-1: An update that solves 292 vulnerabilities, contains two features and has 45 security fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2024/suse-su-20243209-1 Category: security (important) Bug References: 1193629, 1194111, 1194765, 1194869, 1196261, 1196516, 1196894, 1198017, 1203329, 1203330, 1203360, 1205462, 1206006, 1206258, 1206843, 1207158, 1208783, 1210644, 1213580, 1213632, 1214285, 1216834, 1220428, 1220877, 1220962, 1221269, 1221326, 1221630, 1221645, 1222335, 1222350, 1222372, 1222387, 1222634, 1222808, 1222967, 1223074, 1223191, 1223508, 1223720, 1223742, 1223777, 1223803, 1223807, 1224105, 1224415, 1224496, 1224510, 1224542, 1224578, 1224639, 1225162, 1225352, 1225428, 1225524, 1225578, 1225582, 1225773, 1225814, 1225827, 1225832, 1225903, 1226168, 1226530, 1226613, 1226742, 1226765, 1226798, 1226801, 1226874, 1226885, 1227079, 1227623, 1227761, 1227830, 1227863, 1227867, 1227929, 1227937, 1227958, 1228020, 1228065, 1228114, 1228410, 1228426, 1228427, 1228429, 1228446, 1228447, 1228449, 1228450, 1228452, 1228456, 1228463, 1228466, 1228467, 1228469, 1228480, 1228481, 1228482, 1228483, 1228484, 1228485, 1228487, 1228489, 1228491, 1228493, 1228494, 1228495, 1228496, 1228501, 1228503, 1228509, 1228513, 1228515, 1228516, 1228526, 1228531, 1228563, 1228564, 1228567, 1228576, 1228579, 1228584, 1228588, 1228590, 1228615, 1228616, 1228635, 1228636, 1228654, 1228656, 1228658, 1228660, 1228662, 1228667, 1228673, 1228677, 1228687, 1228706, 1228708, 1228710, 1228718, 1228720, 1228721, 1228722, 1228724, 1228726, 1228727, 1228733, 1228748, 1228766, 1228779, 1228801, 1228850, 1228857, 1228959, 1228964, 1228966, 1228967, 1228979, 1228988, 1228989, 1228991, 1228992, 1229042, 1229054, 1229086, 1229136, 1229154, 1229187, 1229188, 1229190, 1229287, 1229290, 1229292, 1229296, 1229297, 1229301, 1229303, 1229304, 1229305, 1229307, 1229309, 1229312, 1229314, 1229315, 1229317, 1229318, 1229319, 1229327, 1229341, 1229345, 1229346, 1229347, 1229349, 1229350, 1229351, 1229354, 1229356, 1229357, 1229358, 1229359, 1229360, 1229366, 1229370, 1229373, 1229374, 1229381, 1229382, 1229383, 1229386, 1229388, 1229391, 1229392, 1229395, 1229398, 1229399, 1229400, 1229407, 1229409, 1229410, 1229411, 1229413, 1229414, 1229417, 1229418, 1229444, 1229453, 1229454, 1229481, 1229482, 1229488, 1229489, 1229490, 1229493, 1229495, 1229497, 1229500, 1229503, 1229506, 1229507, 1229508, 1229509, 1229510, 1229512, 1229516, 1229521, 1229522, 1229523, 1229524, 1229525, 1229526, 1229527, 1229528, 1229529, 1229531, 1229533, 1229535, 1229536, 1229537, 1229540, 1229544, 1229545, 1229546, 1229547, 1229548, 1229554, 1229557, 1229558, 1229559, 1229560, 1229562, 1229564, 1229565, 1229566, 1229568, 1229569, 1229572, 1229573, 1229576, 1229581, 1229588, 1229598, 1229603, 1229604, 1229605, 1229608, 1229611, 1229612, 1229613, 1229614, 1229615, 1229616, 1229617, 1229620, 1229622, 1229623, 1229624, 1229625, 1229626, 1229628, 1229629, 1229630, 1229631, 1229632, 1229635, 1229636, 1229637, 1229638, 1229639, 1229641, 1229642, 1229643, 1229645, 1229657, 1229658, 1229662, 1229664, 1229707, 1229739, 1229743, 1229746, 1229754, 1229755, 1229756, 1229759, 1229761, 1229767, 1229768, 1229781, 1229784, 1229787, 1229788, 1229789, 1229792, 1229820 CVE References: CVE-2021-4441, CVE-2021-47106, CVE-2021-47517, CVE-2021-47546, CVE-2022-38457, CVE-2022-40133, CVE-2022-48645, CVE-2022-48706, CVE-2022-48808, CVE-2022-48865, CVE-2022-48868, CVE-2022-48869, CVE-2022-48870, CVE-2022-48871, CVE-2022-48872, CVE-2022-48873, CVE-2022-48875, CVE-2022-48878, CVE-2022-48880, CVE-2022-48881, CVE-2022-48882, CVE-2022-48883, CVE-2022-48884, CVE-2022-48885, CVE-2022-48886, CVE-2022-48887, CVE-2022-48888, CVE-2022-48889, CVE-2022-48890, CVE-2022-48891, CVE-2022-48893, CVE-2022-48896, CVE-2022-48898, CVE-2022-48899, CVE-2022-48903, CVE-2022-48904, CVE-2022-48905, CVE-2022-48906, CVE-2022-48907, CVE-2022-48909, CVE-2022-48910, CVE-2022-48912, CVE-2022-48913, CVE-2022-48914, CVE-2022-48915, CVE-2022-48916, CVE-2022-48917, CVE-2022-48918, CVE-2022-48919, CVE-2022-48920, CVE-2022-48921, CVE-2022-48923, CVE-2022-48924, CVE-2022-48925, CVE-2022-48926, CVE-2022-48927, CVE-2022-48928, CVE-2022-48929, CVE-2022-48930, CVE-2022-48931, CVE-2022-48932, CVE-2022-48934, CVE-2022-48937, CVE-2022-48938, CVE-2022-48939, CVE-2022-48940, CVE-2022-48941, CVE-2022-48942, CVE-2022-48943, CVE-2023-3610, CVE-2023-52458, CVE-2023-52489, CVE-2023-52498, CVE-2023-52581, CVE-2023-52859, CVE-2023-52887, CVE-2023-52889, CVE-2023-52893, CVE-2023-52894, CVE-2023-52896, CVE-2023-52898, CVE-2023-52899, CVE-2023-52900, CVE-2023-52901, CVE-2023-52904, CVE-2023-52905, CVE-2023-52906, CVE-2023-52907, CVE-2023-52908, CVE-2023-52909, CVE-2023-52910, CVE-2023-52911, CVE-2023-52912, CVE-2023-52913, CVE-2024-26631, CVE-2024-26668, CVE-2024-26669, CVE-2024-26677, CVE-2024-26735, CVE-2024-26808, CVE-2024-26812, CVE-2024-26835, CVE-2024-26851, CVE-2024-27010, CVE-2024-27011, CVE-2024-27016, CVE-2024-27024, CVE-2024-27079, CVE-2024-27403, CVE-2024-31076, CVE-2024-35897, CVE-2024-35902, CVE-2024-35945, CVE-2024-35971, CVE-2024-36009, CVE-2024-36013, CVE-2024-36270, CVE-2024-36286, CVE-2024-36489, CVE-2024-36929, CVE-2024-36933, CVE-2024-36936, CVE-2024-36962, CVE-2024-38554, CVE-2024-38602, CVE-2024-38662, CVE-2024-39489, CVE-2024-40905, CVE-2024-40978, CVE-2024-40980, CVE-2024-40995, CVE-2024-41000, CVE-2024-41007, CVE-2024-41009, CVE-2024-41011, CVE-2024-41016, CVE-2024-41020, CVE-2024-41022, CVE-2024-41035, CVE-2024-41036, CVE-2024-41038, CVE-2024-41039, CVE-2024-41042, CVE-2024-41045, CVE-2024-41056, CVE-2024-41060, CVE-2024-41062, CVE-2024-41065, CVE-2024-41068, CVE-2024-41073, CVE-2024-41079, CVE-2024-41080, CVE-2024-41087, CVE-2024-41088, CVE-2024-41089, CVE-2024-41092, CVE-2024-41093, CVE-2024-41095, CVE-2024-41097, CVE-2024-41098, CVE-2024-42069, CVE-2024-42074, CVE-2024-42076, CVE-2024-42077, CVE-2024-42080, CVE-2024-42082, CVE-2024-42085, CVE-2024-42086, CVE-2024-42087, CVE-2024-42089, CVE-2024-42090, CVE-2024-42092, CVE-2024-42095, CVE-2024-42097, CVE-2024-42098, CVE-2024-42101, CVE-2024-42104, CVE-2024-42106, CVE-2024-42107, CVE-2024-42110, CVE-2024-42114, CVE-2024-42115, CVE-2024-42119, CVE-2024-42120, CVE-2024-42121, CVE-2024-42126, CVE-2024-42127, CVE-2024-42130, CVE-2024-42137, CVE-2024-42139, CVE-2024-42142, CVE-2024-42143, CVE-2024-42148, CVE-2024-42152, CVE-2024-42155, CVE-2024-42156, CVE-2024-42157, CVE-2024-42158, CVE-2024-42162, CVE-2024-42223, CVE-2024-42225, CVE-2024-42228, CVE-2024-42229, CVE-2024-42230, CVE-2024-42232, CVE-2024-42236, CVE-2024-42237, CVE-2024-42238, CVE-2024-42239, CVE-2024-42240, CVE-2024-42244, CVE-2024-42246, CVE-2024-42247, CVE-2024-42268, CVE-2024-42271, CVE-2024-42274, CVE-2024-42276, CVE-2024-42277, CVE-2024-42280, CVE-2024-42281, CVE-2024-42283, CVE-2024-42284, CVE-2024-42285, CVE-2024-42286, CVE-2024-42287, CVE-2024-42288, CVE-2024-42289, CVE-2024-42291, CVE-2024-42292, CVE-2024-42295, CVE-2024-42301, CVE-2024-42302, CVE-2024-42308, CVE-2024-42309, CVE-2024-42310, CVE-2024-42311, CVE-2024-42312, CVE-2024-42313, CVE-2024-42315, CVE-2024-42318, CVE-2024-42319, CVE-2024-42320, CVE-2024-42322, CVE-2024-43816, CVE-2024-43818, CVE-2024-43819, CVE-2024-43821, CVE-2024-43823, CVE-2024-43829, CVE-2024-43830, CVE-2024-43831, CVE-2024-43834, CVE-2024-43837, CVE-2024-43839, CVE-2024-43841, CVE-2024-43842, CVE-2024-43846, CVE-2024-43849, CVE-2024-43853, CVE-2024-43854, CVE-2024-43856, CVE-2024-43858, CVE-2024-43860, CVE-2024-43861, CVE-2024-43863, CVE-2024-43866, CVE-2024-43867, CVE-2024-43871, CVE-2024-43872, CVE-2024-43873, CVE-2024-43879, CVE-2024-43880, CVE-2024-43882, CVE-2024-43883, CVE-2024-43884, CVE-2024-43889, CVE-2024-43892, CVE-2024-43893, CVE-2024-43894, CVE-2024-43895, CVE-2024-43899, CVE-2024-43900, CVE-2024-43902, CVE-2024-43903, CVE-2024-43904, CVE-2024-43905, CVE-2024-43907, CVE-2024-43908, CVE-2024-43909, CVE-2024-44938, CVE-2024-44939, CVE-2024-44947 Jira References: PED-8491, PED-8779 Maintenance Incident: [SUSE:Maintenance:35569](https://smelt.suse.de/incident/35569/) Sources used: SUSE Linux Enterprise Live Patching 15-SP5 (src): kernel-livepatch-SLE15-SP5-RT_Update_19-1-150500.11.3.2 SUSE Real Time Module 15-SP5 (src): kernel-syms-rt-5.14.21-150500.13.67.1, kernel-source-rt-5.14.21-150500.13.67.3 openSUSE Leap 15.5 (src): kernel-livepatch-SLE15-SP5-RT_Update_19-1-150500.11.3.2, kernel-syms-rt-5.14.21-150500.13.67.1, kernel-source-rt-5.14.21-150500.13.67.3 SUSE Linux Enterprise Micro 5.5 (src): kernel-source-rt-5.14.21-150500.13.67.3 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c44 Ivan Ivanov <ivan.ivanov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #44 from Ivan Ivanov <ivan.ivanov@suse.com> --- As per comment#31 lets mark it as fixe. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c45 --- Comment #45 from Maintenance Automation <maint-coord+maintenance-robot@suse.de> --- SUSE-SU-2024:3483-1: An update that solves 296 vulnerabilities, contains two features and has 42 security fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2024/suse-su-20243483-1 Category: security (important) Bug References: 1193629, 1194111, 1194765, 1194869, 1196261, 1196516, 1196894, 1198017, 1203329, 1203330, 1203360, 1205462, 1206006, 1206258, 1206843, 1207158, 1208783, 1210644, 1213580, 1213632, 1214285, 1216834, 1220428, 1220877, 1220962, 1221269, 1221326, 1221630, 1221645, 1222335, 1222350, 1222372, 1222387, 1222634, 1222808, 1222967, 1223074, 1223191, 1223508, 1223720, 1223742, 1223777, 1223803, 1223807, 1224105, 1224415, 1224496, 1224510, 1224542, 1224578, 1224639, 1225162, 1225352, 1225428, 1225524, 1225578, 1225582, 1225773, 1225814, 1225827, 1225832, 1225903, 1226168, 1226530, 1226613, 1226742, 1226765, 1226798, 1226801, 1226874, 1226885, 1227079, 1227623, 1227761, 1227830, 1227863, 1227867, 1227929, 1227937, 1227958, 1228020, 1228065, 1228114, 1228410, 1228426, 1228427, 1228429, 1228446, 1228447, 1228449, 1228450, 1228452, 1228456, 1228463, 1228466, 1228467, 1228469, 1228480, 1228481, 1228482, 1228483, 1228484, 1228485, 1228487, 1228489, 1228491, 1228493, 1228494, 1228495, 1228496, 1228501, 1228503, 1228509, 1228513, 1228515, 1228516, 1228526, 1228531, 1228563, 1228564, 1228567, 1228576, 1228579, 1228584, 1228588, 1228590, 1228615, 1228616, 1228635, 1228636, 1228654, 1228656, 1228658, 1228660, 1228662, 1228667, 1228673, 1228677, 1228687, 1228706, 1228708, 1228710, 1228718, 1228720, 1228721, 1228722, 1228724, 1228726, 1228727, 1228733, 1228748, 1228766, 1228779, 1228801, 1228850, 1228857, 1228959, 1228964, 1228966, 1228967, 1228979, 1228988, 1228989, 1228991, 1228992, 1229042, 1229054, 1229086, 1229136, 1229154, 1229187, 1229188, 1229190, 1229287, 1229290, 1229292, 1229296, 1229297, 1229301, 1229303, 1229304, 1229305, 1229307, 1229309, 1229312, 1229314, 1229315, 1229317, 1229318, 1229319, 1229327, 1229341, 1229345, 1229346, 1229347, 1229349, 1229350, 1229351, 1229354, 1229356, 1229357, 1229358, 1229359, 1229360, 1229366, 1229370, 1229373, 1229374, 1229381, 1229382, 1229383, 1229386, 1229388, 1229391, 1229392, 1229395, 1229398, 1229399, 1229400, 1229407, 1229409, 1229410, 1229411, 1229413, 1229414, 1229417, 1229418, 1229444, 1229453, 1229454, 1229481, 1229482, 1229488, 1229489, 1229490, 1229493, 1229495, 1229497, 1229500, 1229503, 1229506, 1229507, 1229508, 1229509, 1229510, 1229512, 1229516, 1229521, 1229522, 1229523, 1229524, 1229525, 1229526, 1229527, 1229528, 1229529, 1229531, 1229533, 1229535, 1229536, 1229537, 1229540, 1229544, 1229545, 1229546, 1229547, 1229548, 1229554, 1229557, 1229558, 1229559, 1229560, 1229562, 1229564, 1229565, 1229566, 1229568, 1229569, 1229572, 1229573, 1229576, 1229581, 1229588, 1229598, 1229603, 1229604, 1229605, 1229608, 1229611, 1229612, 1229613, 1229614, 1229615, 1229616, 1229617, 1229620, 1229622, 1229623, 1229624, 1229625, 1229626, 1229628, 1229629, 1229630, 1229631, 1229632, 1229635, 1229636, 1229637, 1229638, 1229639, 1229641, 1229642, 1229643, 1229645, 1229657, 1229658, 1229662, 1229664, 1229707, 1229739, 1229743, 1229746, 1229754, 1229755, 1229756, 1229759, 1229761, 1229767, 1229768, 1229781, 1229784, 1229787, 1229788, 1229789, 1229792, 1229820, 1230413 CVE References: CVE-2021-4204, CVE-2021-4441, CVE-2021-47106, CVE-2021-47517, CVE-2021-47546, CVE-2022-0500, CVE-2022-23222, CVE-2022-38457, CVE-2022-40133, CVE-2022-4382, CVE-2022-48645, CVE-2022-48706, CVE-2022-48808, CVE-2022-48865, CVE-2022-48868, CVE-2022-48869, CVE-2022-48870, CVE-2022-48871, CVE-2022-48872, CVE-2022-48873, CVE-2022-48875, CVE-2022-48878, CVE-2022-48880, CVE-2022-48881, CVE-2022-48882, CVE-2022-48883, CVE-2022-48884, CVE-2022-48885, CVE-2022-48886, CVE-2022-48887, CVE-2022-48888, CVE-2022-48889, CVE-2022-48890, CVE-2022-48891, CVE-2022-48893, CVE-2022-48896, CVE-2022-48898, CVE-2022-48899, CVE-2022-48903, CVE-2022-48904, CVE-2022-48905, CVE-2022-48906, CVE-2022-48907, CVE-2022-48909, CVE-2022-48910, CVE-2022-48912, CVE-2022-48913, CVE-2022-48914, CVE-2022-48915, CVE-2022-48916, CVE-2022-48917, CVE-2022-48918, CVE-2022-48919, CVE-2022-48920, CVE-2022-48921, CVE-2022-48923, CVE-2022-48924, CVE-2022-48925, CVE-2022-48926, CVE-2022-48927, CVE-2022-48928, CVE-2022-48929, CVE-2022-48930, CVE-2022-48931, CVE-2022-48932, CVE-2022-48934, CVE-2022-48937, CVE-2022-48938, CVE-2022-48939, CVE-2022-48940, CVE-2022-48941, CVE-2022-48942, CVE-2022-48943, CVE-2023-3610, CVE-2023-52458, CVE-2023-52489, CVE-2023-52498, CVE-2023-52581, CVE-2023-52859, CVE-2023-52887, CVE-2023-52889, CVE-2023-52893, CVE-2023-52894, CVE-2023-52896, CVE-2023-52898, CVE-2023-52899, CVE-2023-52900, CVE-2023-52901, CVE-2023-52904, CVE-2023-52905, CVE-2023-52906, CVE-2023-52907, CVE-2023-52908, CVE-2023-52909, CVE-2023-52910, CVE-2023-52911, CVE-2023-52912, CVE-2023-52913, CVE-2024-26631, CVE-2024-26668, CVE-2024-26669, CVE-2024-26677, CVE-2024-26735, CVE-2024-26808, CVE-2024-26812, CVE-2024-26835, CVE-2024-26851, CVE-2024-27010, CVE-2024-27011, CVE-2024-27016, CVE-2024-27024, CVE-2024-27079, CVE-2024-27403, CVE-2024-31076, CVE-2024-35897, CVE-2024-35902, CVE-2024-35945, CVE-2024-35971, CVE-2024-36009, CVE-2024-36013, CVE-2024-36270, CVE-2024-36286, CVE-2024-36489, CVE-2024-36929, CVE-2024-36933, CVE-2024-36936, CVE-2024-36962, CVE-2024-38554, CVE-2024-38602, CVE-2024-38662, CVE-2024-39489, CVE-2024-40905, CVE-2024-40978, CVE-2024-40980, CVE-2024-40995, CVE-2024-41000, CVE-2024-41007, CVE-2024-41009, CVE-2024-41011, CVE-2024-41016, CVE-2024-41020, CVE-2024-41022, CVE-2024-41035, CVE-2024-41036, CVE-2024-41038, CVE-2024-41039, CVE-2024-41042, CVE-2024-41045, CVE-2024-41056, CVE-2024-41060, CVE-2024-41062, CVE-2024-41065, CVE-2024-41068, CVE-2024-41073, CVE-2024-41079, CVE-2024-41080, CVE-2024-41087, CVE-2024-41088, CVE-2024-41089, CVE-2024-41092, CVE-2024-41093, CVE-2024-41095, CVE-2024-41097, CVE-2024-41098, CVE-2024-42069, CVE-2024-42074, CVE-2024-42076, CVE-2024-42077, CVE-2024-42080, CVE-2024-42082, CVE-2024-42085, CVE-2024-42086, CVE-2024-42087, CVE-2024-42089, CVE-2024-42090, CVE-2024-42092, CVE-2024-42095, CVE-2024-42097, CVE-2024-42098, CVE-2024-42101, CVE-2024-42104, CVE-2024-42106, CVE-2024-42107, CVE-2024-42110, CVE-2024-42114, CVE-2024-42115, CVE-2024-42119, CVE-2024-42120, CVE-2024-42121, CVE-2024-42126, CVE-2024-42127, CVE-2024-42130, CVE-2024-42137, CVE-2024-42139, CVE-2024-42142, CVE-2024-42143, CVE-2024-42148, CVE-2024-42152, CVE-2024-42155, CVE-2024-42156, CVE-2024-42157, CVE-2024-42158, CVE-2024-42162, CVE-2024-42223, CVE-2024-42225, CVE-2024-42228, CVE-2024-42229, CVE-2024-42230, CVE-2024-42232, CVE-2024-42236, CVE-2024-42237, CVE-2024-42238, CVE-2024-42239, CVE-2024-42240, CVE-2024-42244, CVE-2024-42246, CVE-2024-42247, CVE-2024-42268, CVE-2024-42271, CVE-2024-42274, CVE-2024-42276, CVE-2024-42277, CVE-2024-42280, CVE-2024-42281, CVE-2024-42283, CVE-2024-42284, CVE-2024-42285, CVE-2024-42286, CVE-2024-42287, CVE-2024-42288, CVE-2024-42289, CVE-2024-42291, CVE-2024-42292, CVE-2024-42295, CVE-2024-42301, CVE-2024-42302, CVE-2024-42308, CVE-2024-42309, CVE-2024-42310, CVE-2024-42311, CVE-2024-42312, CVE-2024-42313, CVE-2024-42315, CVE-2024-42318, CVE-2024-42319, CVE-2024-42320, CVE-2024-42322, CVE-2024-43816, CVE-2024-43818, CVE-2024-43819, CVE-2024-43821, CVE-2024-43823, CVE-2024-43829, CVE-2024-43830, CVE-2024-43831, CVE-2024-43834, CVE-2024-43837, CVE-2024-43839, CVE-2024-43841, CVE-2024-43842, CVE-2024-43846, CVE-2024-43849, CVE-2024-43853, CVE-2024-43854, CVE-2024-43856, CVE-2024-43858, CVE-2024-43860, CVE-2024-43861, CVE-2024-43863, CVE-2024-43866, CVE-2024-43867, CVE-2024-43871, CVE-2024-43872, CVE-2024-43873, CVE-2024-43879, CVE-2024-43880, CVE-2024-43882, CVE-2024-43883, CVE-2024-43884, CVE-2024-43889, CVE-2024-43892, CVE-2024-43893, CVE-2024-43894, CVE-2024-43895, CVE-2024-43899, CVE-2024-43900, CVE-2024-43902, CVE-2024-43903, CVE-2024-43904, CVE-2024-43905, CVE-2024-43907, CVE-2024-43908, CVE-2024-43909, CVE-2024-44938, CVE-2024-44939, CVE-2024-44947 Jira References: PED-8491, PED-8779 Maintenance Incident: [SUSE:Maintenance:35521](https://smelt.suse.de/incident/35521/) Sources used: openSUSE Leap 15.5 (src): kernel-obs-build-5.14.21-150500.55.80.1, kernel-syms-5.14.21-150500.55.80.1, kernel-source-5.14.21-150500.55.80.2, kernel-livepatch-SLE15-SP5_Update_19-1-150500.11.3.2, kernel-obs-qa-5.14.21-150500.55.80.1, kernel-default-base-5.14.21-150500.55.80.2.150500.6.35.6 openSUSE Leap Micro 5.5 (src): kernel-default-base-5.14.21-150500.55.80.2.150500.6.35.6 SUSE Linux Enterprise Micro 5.5 (src): kernel-default-base-5.14.21-150500.55.80.2.150500.6.35.6 Basesystem Module 15-SP5 (src): kernel-source-5.14.21-150500.55.80.2, kernel-default-base-5.14.21-150500.55.80.2.150500.6.35.6 Development Tools Module 15-SP5 (src): kernel-obs-build-5.14.21-150500.55.80.1, kernel-syms-5.14.21-150500.55.80.1, kernel-source-5.14.21-150500.55.80.2 SUSE Linux Enterprise Live Patching 15-SP5 (src): kernel-livepatch-SLE15-SP5_Update_19-1-150500.11.3.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c47 --- Comment #47 from Guillaume GARDET <guillaume.gardet@arm.com> --- (In reply to Patrik Jakobsson from comment #46)
Why is the test still failing? Shouldn't QA have the fix by now?
There is a regression, since the test passed 9 days ago: https://openqa.opensuse.org/tests/4543603 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c48 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #48 from Fabian Vogt <fvogt@suse.com> --- (In reply to Guillaume GARDET from comment #47)
(In reply to Patrik Jakobsson from comment #46)
Why is the test still failing? Shouldn't QA have the fix by now?
There is a regression, since the test passed 9 days ago: https://openqa.opensuse.org/tests/4543603
Also affecting 15.5 and 15.6 again. Can you check the serial log? Maybe it's the same cause again, maybe something else. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c49 --- Comment #49 from Guillaume GARDET <guillaume.gardet@arm.com> --- Created attachment 878195 --> https://bugzilla.suse.com/attachment.cgi?id=878195&action=edit 15.5 log for no eth0 A quick check shows eth0 is not found: ********** Welcome to openSUSE Leap 15.5 - Kernel 5.14.21-150500.55.83-default (ttyS0). wlan0: localhost login: ********** -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c50 --- Comment #50 from Guillaume GARDET <guillaume.gardet@arm.com> --- Created attachment 878201 --> https://bugzilla.suse.com/attachment.cgi?id=878201&action=edit dmesg 15.6 for no eth0 Same problem on Leap 15.6, no eth0: ********** Welcome to openSUSE Leap 15.6 - Kernel 6.4.0-150600.23.25-default (ttyS0). wlan0: localhost login: ********** -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c51 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|REOPENED |RESOLVED --- Comment #51 from Fabian Vogt <fvogt@suse.com> --- (In reply to Guillaume GARDET from comment #49)
Created attachment 878195 [details] 15.5 log for no eth0
A quick check shows eth0 is not found:
That's bad. Can you create a new bug report for this? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com