Created attachment 859644 [details]
Alsa-info

I have both a 500 GB SSD and a 60 GB SSD
Both have the exact same opensuse tumbleweed on them

I use the 60 GB SSD one for testing purposes, and im prepared to perform any/all tests for devs to help them resolve
the bug

Im also prepared to re-install an earlier .ISO image for opensuse tumbleweed to get a system when all things were working
(Im not sure about the last few hardware firmware upgrade though via OS package updates)
If this will also help facilitate the devs in tracking down what packages and/or firmware updates created this issue

Could you give the full dmesg output?  It indicates the error with i915 component just before the codec3 config error, and that must be the cause.

Created attachment 859652 [details]
DMESG OUTPUT

Hm, there is no error from i915 itself.

Did HDMI audio on i915 work with 5.17 kernel?  You may still find it in TW history repo, and try to install it and test with it:
  http://download.opensuse.org/history/

If no 5.17 kernel is found there, you can try my unofficial kernel in OBS home:tiwai:kernel:5.17 repo.

If HDMI audio works with this kernel, boot with drm.debug=0x1e boot option, and  upload alsa-info.sh and dmesg outputs again from that.  Ditto for the broken 5.18.x kernel, boot with drm.debug=0x1e and give the dmesg output again.

Created attachment 859660 [details]
DMESG with Kernel drm.debug=0x1e boot option for Kernel Version 5.18.2-1-default (64-bit)

DMESG with Kernel drm.debug=0x1e boot option for Kernel Version 5.18.2-1-default (64-bit).txt

Argh, it's too big and the important bits are gone.
Could you retry with log_buf_len=16MB boot option?

Created attachment 859661 [details]
DMESG OUTPUT - splash=silent quiet security=apparmor drm.debug=0x1e log_buf_len=16MB - Kernel Version 5.18.2-1-default (64-bit).txt

DMESG OUTPUT - splash=silent quiet security=apparmor drm.debug=0x1e log_buf_len=16MB - Kernel Version 5.18.2-1-default (64-bit).txt

i915 has always worked perfectly for the last 2 1/2 years - 0 issues until the last major updates which also includes
hardware firmware updates
I have a .TXT file log of 96 updates as well that i can also upload - not sure how relevant/helpful it will be

As for the older kernels, i dont see any packages for kernels in the official repository lists
Why would that be ?

I will review your link for the 5.17 kernel

(In reply to Ben Guy from comment #8)
> Created attachment 859661 [details]
> DMESG OUTPUT - splash=silent quiet security=apparmor drm.debug=0x1e
> log_buf_len=16MB - Kernel Version 5.18.2-1-default (64-bit).txt
> 
> DMESG OUTPUT - splash=silent quiet security=apparmor drm.debug=0x1e
> log_buf_len=16MB - Kernel Version 5.18.2-1-default (64-bit).txt

Thanks.  This still doesn't show why the i915 component binding failed.  The i915 driver itself seems handling the HDMI audio, judging from the log, so it's possibly some issue related with the component framework.

In anyway, it'd be helpful if you can verify that 5.17.x kernel still works as is.  If yes, then try the latest 5.19-rc kernel from Kernel:HEAD, too.

If it's confirmed that 5.19-rc kernel is also broken, I'm going to provide a kernel with some debug prints for further analysis.

DMESG OUTPUT FOR TUMBLEWEED NO 2 WITH 5.17 KERNEL RE-INSTALLED:


NOTE: Pastebin complains of the file size exceeding its limits despite my registering on it
      For the record it sais there are currently no more PRO accounts to buy

https://paste.opensuse.org/ appears to stop functioning after i press the create button
So instead this is a MEGA Link i am providing with the file in it:

https://mega.nz/file/1fh0gAqD#VY1f-8_pAJPXo7aczntIlVI2pJisD4h8xeE9me7YbI4

Please don't use pastebin or whatever external services.  Just use the attachment on Bugzilla instead.

@Takashi - Are you sure your specifically looking at/referring to the Internal Motherboard HDMI - The Integrated Intel GPU with Audio
Not to be confused with the PCI-E Video card HDMI ?

Yes!, on my test Tumbleweed installation, i now have HDMI Audio Output once again on my 'Built-in' Audio Devices
Both Digital Stereo (HDMI) AND Digital Surround 5.1 (HDMI) Output BOTH now display in the Audio Volume Applet and Audio Settings

(In reply to Takashi Iwai from comment #12)
> Please don't use pastebin or whatever external services.  Just use the
> attachment on Bugzilla instead.

As i stated above, it's often not possible to use the Bugzilla service because the file contents exceeds Bugzilla's limits
hence why external services are sometimes the only option left

(In reply to Ben Guy from comment #14)
> (In reply to Takashi Iwai from comment #12)
> > Please don't use pastebin or whatever external services.  Just use the
> > attachment on Bugzilla instead.
> 
> As i stated above, it's often not possible to use the Bugzilla service
> because the file contents exceeds Bugzilla's limits
> hence why external services are sometimes the only option left

That's likely the missing HDMI entries, but I can't say exactly unless I get the proper data from the working state.  That's why I asked for testing 5.17 kernel.

The HDMI audio on AMD graphics on your device was detected and configured, at lest, from the kernel POV.  If anything missing for those, it's no kernel problem but a user-space issue.

For the AMD HDMI, there was an issue in the latest alsa-lib and alsa-ucm-conf 1.2.7, and that's been already addressed.

(In reply to Ben Guy from comment #14)
> (In reply to Takashi Iwai from comment #12)
> > Please don't use pastebin or whatever external services.  Just use the
> > attachment on Bugzilla instead.
> 
> As i stated above, it's often not possible to use the Bugzilla service
> because the file contents exceeds Bugzilla's limits
> hence why external services are sometimes the only option left

The kernel log up to a few MB shouldn't matter for Bugzilla attachments.  It's not appropriate to upload the whole kernel crash dump, for example, but pastebin won't work for such a purpose, either.

And, if the log file size really exceeds, you should compress it at first before uploading, in anyway.

Created attachment 859668 [details]
DMESG OUTPUT OS Number 2 - Kernel Version: 5.19.0-rc2-2.gca88599-default (64-bit)

Using this kernel version - the results are identical to Kernel 5.18
Same GUI, no audio from motherboard internal HDMI

Kernel 5.17 - works great

I have 3,458 New Updates
Should i install them ?
Or do you want a list of all the packages and their versions ?

TXT file is 16.6 MB in size

Bugzilla needs to remove its file size limitation
complains:

"The file you are trying to attach is 16993 kilobytes (KB) in size. Attachments cannot be more than 10240 KB.
We recommend that you store your attachment elsewhere and then paste the URL to this file on the attachment creation page in the appropriate text field, which you can access by clicking the "paste text as attachment" link.
Alternately, if your attachment is an image, you could convert it to a compressible format like JPG or PNG and try again. "

I have compressed it to a far far smaller size, .7z file

(In reply to Ben Guy from comment #16)
> Created attachment 859668 [details]
> DMESG OUTPUT OS Number 2 - Kernel Version: 5.19.0-rc2-2.gca88599-default
> (64-bit)
> 
> Using this kernel version - the results are identical to Kernel 5.18
> Same GUI, no audio from motherboard internal HDMI

OK.

> Kernel 5.17 - works great

Then I need the logs from *THIS*.  Please upload both dmesg and alsa-info.sh outputs from the working state.

> I have 3,458 New Updates
> Should i install them ?
> Or do you want a list of all the packages and their versions ?
> 
> TXT file is 16.6 MB in size
> 
> Bugzilla needs to remove its file size limitation
> complains:
> 
> "The file you are trying to attach is 16993 kilobytes (KB) in size.
> Attachments cannot be more than 10240 KB.
> We recommend that you store your attachment elsewhere and then paste the URL
> to this file on the attachment creation page in the appropriate text field,
> which you can access by clicking the "paste text as attachment" link.
> Alternately, if your attachment is an image, you could convert it to a
> compressible format like JPG or PNG and try again. "
> 
> I have compressed it to a far far smaller size, .7z file

Usually xz or gzip is more standard on Linux (maybe nowadays zstd :)

I dont have a particular preferance for compression format when it come to txt files
with many different standards around and app to decompress the various standards it does not really
matter

I use File Krusader (not dolphin) because i see it as far easier and superior
However, there has been a bug report for the compress men options that do not work
with the exception of the optional J7Z krusader plugins which allow me to compress such files

Not sure if this info is relevant anymore because of the already placed info you stated:
"For the AMD HDMI, there was an issue in the latest alsa-lib and alsa-ucm-conf 1.2.7, and that's been already addressed."

My error/mistake was not providing you with the needed alsa-info.sh from the working state
I decided to upgrade all the packages using kernel 5.17, the results were bad
reverted back to the original problem i had under kernel 5.18 - no audio, and the missing GUI settings in profile (but Pro added)

Created attachment 859677 [details]
DMESG - drm.debug=0x1e log_buf_len=16MB - Kernel Version 5.17.9-1.gc1eda89-default (64-bit) - After Updates.7z

Please state if anymore more is needed, even if i re-install of opensuse with kernel 5.17 (or less) is needed

Aha, so 5.17 still doesn't work although it used to work?  Then it could be the alsa-lib issue I mentioned.

Make sure that you upgrade alsa, libasound2 and alsa-ucm-conf package to the latest TW release.

I already am on the latest now
Will these updated packages be released with the
next kernel release after the current 5.18.4-1-default ?

Hm.  The latest alsa.rpm and libasound2.rpm should have the latest rpm changelog like:
- Backport upstream fixes for 32bit inode and ELD parsing:
  0001-conf-Use-ino64_t-to-save-and-compare-inode-numbers.patch
  0002-control-eld-fix-the-decoding-for-older-hw.patch

Verify that the package on your system is with this.

Judging from the dmesg output, 5.17 kernel gives the HDMI output from Intel GPU properly.  So at least there is some regression between 5.17 and 5.18 regarding the i915/HD-audio component binding.

Please give alsa-info.sh output from 5.17 kernel.  Run the script with --no-upload option and attach the output.  It's just for checking more.

BTW, the standard way to compress a text file on Linux is just to run gzip for it, e.g. run like:
  gzip foo.txt
This will convert foo.txt to a compressed file, foo.txt.gz.  Upload in this way at the next time.

Created attachment 859682 [details]
alsa-info.txt.hDHe9HDAZ6.7z for 5.17 Kernel (not working audio state)

Comment on attachment 859682 [details]
alsa-info.txt.hDHe9HDAZ6.7z for 5.17 Kernel (not working audio state)

MISTAKE - ABOVE ATTACHMENT CALLED "alsa-info.txt.hDHe9HDAZ6.7z for 5.17 Kernel (not working audio state)" - IS NOT KERNEL 5.17

It's Kernel 5.19

Created attachment 859683 [details]
alsa-info.txt.FZrMtuqC6j - Kernel Version 5.17.9-1.gc1eda89-default (64-bit).7z

Thats for the audio in its non-working state there

As a side note - with respect to file compression - krusader has not been fixed to utilise the menus designed to allow a file
or files to be compressed using gzip as an option - at the moment there is only 7z as an option - a J7Z - Create context menu

It may have originally been created/designed with windows in mind, but ultimately this does not matter
krusader also decompresses 7z files using a J7Z - Extract context menu

No Terminal needed

https://bugs.kde.org/show_bug.cgi?id=441376

Thanks.  Now there a few things I ask you for further testing:

- Install pavucontrol program, run it on desktop.  This can be used instead of KDE mixer.  Verify with 5.17.x kernel whether HDMI for i915 is present there or not.

- I'm building a test kernel with a revert patch in OBS home:tiwai:bsc1200611 repo.  Once after the build finishes (it takes for an hour or so), the test package will appear at
  http://download.opensuse.org/repositories/home:/tiwai:/bsc1200611/standard/
Please test with this one (5.18.5-based kernel), verify whether i915 HDMI is present or not.

- Please attach the output of "lspci -nv".  It's short, no need for compression :)

Created attachment 859684 [details]
alsa-info.txt.nFR7Ydnh9l - Opensuse Tumbleweed Test OS - Kernel Version 5.17.9-1.gc1eda89-default (64-bit)

This is for Kernel Opensuse Tumbleweed Test OS - Kernel Version 5.17.9-1.gc1eda89-default (64-bit)

Created attachment 859685 [details]
lspci - Opensuse Tumbleweed Test OS - Kernel Version 5.17.9-1.gc1eda89-default (64-bit).txt

lspci - Opensuse Tumbleweed Test OS - Kernel Version 5.17.9-1.gc1eda89-default (64-bit).txt

Created attachment 859686 [details]
KDE Plasma - Audio Volume Control - HDMI & DisplayPort (Built in Audio Digital Surround 5.1 (HDMI))  - Digital Surround 5.1 (HDMI) Output - Opensuse Tumbleweed Test OS - Kernel Version 5.17.9-1.gc1eda

Created attachment 859687 [details]
KDE Plasma - Pavcontrol - Configuration TAB - Built-in Audio Options - Screenshot_20220620_001630 - Opensuse Tumbleweed Test OS - Kernel Version 5.17.9-1.gc1eda89-default (64-bit).png

I can still get audio just fine through my PCI-E Video cards HDMI port connected to my monitor
I played a video from youtube via Firefox
I played a video file using VLC Media Player
Pavcontrol does show audio playing via VU meters despite no sound throughput on the Built-in Audio HDMI output

Created attachment 859689 [details]
lspci - Opensuse Tumbleweed Test OS - Kernel Version 5.17.9-1.gc1eda89-default (64-bit).txt

Created attachment 859690 [details]
alsa-info.txt.6qEsvA4e1U - Kernel Version: 5.18.5-1.g52124ed-default (64-bit)

Created attachment 859691 [details]
lspci - Opensuse Tumbleweed Test OS - Kernel Version: 5.18.5-1.g52124ed-default (64-bit).txt

(In reply to Ben Guy from comment #36)
> Created attachment 859689 [details]
> lspci - Opensuse Tumbleweed Test OS - Kernel Version
> 5.17.9-1.gc1eda89-default (64-bit).txt


- Sorry - perhaps to ignore this one

Kernel 5.18.5 has same issues as in kernel 5.17


Note under Pavcontrol Configuration TAB for both
Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series] (PCI-E Video Card)

and also

Built-in Audio

profiles both have (unplugged) (unavailable)
in them

I have used package kernel-default-5.18.5-1.1.g52124ed.x86_64.rpm

So the test kernel made the Intel HDMI back at least to the equivalent state to 5.17.x kernel.  The remaining question is why Intel HDMI still doesn't work.

Exactly which kernel was running in the working state with Intel HDMI?  I doubt whether it's a kernel issue or not.

Also, let's check with the native aplay with Intel HDMI; connect to the Intel HDMI port, prepare some WAV file containing 2 channel and 44.1 or 48kHz (say it's foo.wav), and run like:
  aplay -Dhdmi:0 -vv foo.wav

If this fails with "device busy" error, wrap it with pasuspender,
  pasuspender -- aplay -Dhdmi:0 -vv foo.wav

I guess this will also result in the silent output.

If the aplay above doesn't work, it's possibly because your BIOS disables a few Intel HDMI ports.  Try to boot with snd_hda_codec_hdmi.enable_all_pins=1 boot option, and check whether this changes positively.

BTW, from now on, you can drop the drm.debug and log_buf_len options.  We don't need the detailed i915 logs for now, and those will make logs noisy.

@Ben , can you provide output of "sudo lspci -tvn" on the system with 5.18 or 5.19 kernel (where Intel HDMI audio is not working at all, i.e. the original problem).

Takashi has identified one patch in upstream that could be causing this, but I just checked the Intel CI and this is passing on Ivy Bridge machines there. So something is different in your setup.

Created attachment 859704 [details]
aplay audio output test under Kernel Version 5.17.9-1.gc1eda89-default (64-bit) - TERMINAL OUTPUT.txt

Created attachment 859706 [details]
aplay audio output test under Kernel Version 5.17.9-1.gc1eda89-default (64-bit) with kernel boot option snd_hda_codec_hdmi.enable_all_pins=1 - TERMINAL OUTPUT.txt

Created attachment 859708 [details]
lspci output under Kernel Version 5.18.5-1.g52124ed-default (64-bit)

(In reply to Kai Vehmanen from comment #43)
> @Ben , can you provide output of "sudo lspci -tvn" on the system with 5.18
> or 5.19 kernel (where Intel HDMI audio is not working at all, i.e. the
> original problem).
> 
> Takashi has identified one patch in upstream that could be causing this, but
> I just checked the Intel CI and this is passing on Ivy Bridge machines
> there. So something is different in your setup.


I do have 2 separate installations of opensuse tumbleweed
each on their own separate respective SSD

I have been updating both of them with all newer packages that come along
After i re-installed the 5.17 kernel on my test OS, then i got back full
funtionality of my audio again - just like the old days

However, i updated all the packages under that same kernel - and made sure to still re-boot into that same kernel - but then i had lost the HDMI audio again

It was my mistake in not providing a alsa-info.sh output under the 5.17 kernel
when the audio was working - i regret that

At a last resort measure, Im prepared to totally re-install my opensuse tumbleweed test OS if need be to help track issues down

Thanks Ben. Takashi, based on the PCI hierachy, I can't see how "ALSA: hda/i915 - skip acomp init if no matching display" in 5.18 can cause a regression on this system. The two PCI devs sit on the same but so connectivity_check() should return true.

Ben, I can see from your most recent "alsa-info.txt" that HDMI is only shown connected to the AMD GPU, not to the Intel integrated HDMI:

""
	control.48 {
		iface CARD
		name 'HDMI/DP,pcm=3 Jack'
		value false
		comment {
			access read
			type BOOLEAN
			count 1
		}
	}
""

That value should be "true" when a audio-capable monitor is connected to the internal display adapter.

The test kernel I provided in comment 30 (5.18.5-based) is just a revert of commit c9db8a30d9f091aa571b5fb7c3f434cde107b02c and 00fd7cfad0548b6b7234c93370076f9b9c2e39f8.  So something wrong certainly there.

I'm afraid that the use of pci_get_class() is wrong for this case.  The function tries to match the full class bits, while we want only check the base class bit.  So the class 0x0380 won't hit because you're looking at the class 0x0300.

(In reply to Kai Vehmanen from comment #49)
> Thanks Ben. Takashi, based on the PCI hierachy, I can't see how "ALSA:
> hda/i915 - skip acomp init if no matching display" in 5.18 can cause a
> regression on this system. The two PCI devs sit on the same but so
> connectivity_check() should return true.
> 
> Ben, I can see from your most recent "alsa-info.txt" that HDMI is only shown
> connected to the AMD GPU, not to the Intel integrated HDMI:
> 
> ""
> 	control.48 {
> 		iface CARD
> 		name 'HDMI/DP,pcm=3 Jack'
> 		value false
> 		comment {
> 			access read
> 			type BOOLEAN
> 			count 1
> 		}
> 	}
> ""
> 
> That value should be "true" when a audio-capable monitor is connected to the
> internal display adapter.


I dont know if this is relevant, but after one of the updates i got for KDE Plasma 5.25.0
meant that only my main Primary monitor displays anything
My 2 other monitors do not display anythinh

The Motherboard HDMI port connects to my Denon AV Home theatre system
The Denon AV has it's own HDMI output connector which is connected to my Sony 40" TV/Monitor

This in itself is a separate bug issue - but...is it possible that because my Denon AV is not recieving a picture
(Except when the PC is first turned on, and it does show the SDDM logon screen) that audio could/would be stopped getting output there ?

(In reply to Ben Guy from comment #51)
> This in itself is a separate bug issue - but...is it possible that because
> my Denon AV is not recieving a picture
> (Except when the PC is first turned on, and it does show the SDDM logon
> screen) that audio could/would be stopped getting output there ?

Yes, it indicates the problem.  The HDMI audio is always tied with the video, and if no video is shown, there is no audio, either.

(In reply to Takashi Iwai from comment #52)
> (In reply to Ben Guy from comment #51)
> > This in itself is a separate bug issue - but...is it possible that because
> > my Denon AV is not recieving a picture
> > (Except when the PC is first turned on, and it does show the SDDM logon
> > screen) that audio could/would be stopped getting output there ?
> 
> Yes, it indicates the problem.  The HDMI audio is always tied with the
> video, and if no video is shown, there is no audio, either.


My BUG Report

BUG - multi-monitor issue - only main primary monitor displaying after update to 5.24.5:

https://bugs.kde.org/show_bug.cgi?id=455300

After Performing the massive update on my test OS, i lost multi-monitor support

@Takashi: Aa, so we miss the ".class_mask = 0xff << 16" bit. And in our CI, the IVB machine has 0300 class, so the test passes. I can make a patch for this.

@Ben: indeed if you don't see the display output, audio won't work either. A good debug tool to separate the problems a bit is to to switch to terminal console (ctrl+alt+f2). This should force output on all monitors you have connected and audio should work to all monitors in this mode as well. You can switch back with ctrl+alt+f7.

Created attachment 859710 [details]
Kernel Version: 5.17.9-1.gc1eda89-default (64-bit)  Denon/TV Monitor & small monitor both displaying SDDM Login Screen

Kernel Version: 5.17.9-1.gc1eda89-default (64-bit)

Denon/TV Monitor & small monitor both displaying SDDM Login Screen

Audio Works Perfectly

After trying the same thing under my main OS with Kernel Version: 5.18.4-1-default (64-bit)
I do not get the HDMI Options for Built-in Audio like i do under Kernel 5.17 (my Test OS)

(In reply to Ben Guy from comment #57)
> After trying the same thing under my main OS with Kernel Version:
> 5.18.4-1-default (64-bit)
> I do not get the HDMI Options for Built-in Audio like i do under Kernel 5.17
> (my Test OS)

This is expected.  5.18.4 kernel you've tested has a regression regarding the Intel HDMI audio.  The test kernel in comment 30 is a kernel with a tentative fix (revert).  So if any, please test with it.

(In reply to Kai Vehmanen from comment #55)
> @Takashi: Aa, so we miss the ".class_mask = 0xff << 16" bit. And in our CI,
> the IVB machine has 0300 class, so the test passes. I can make a patch for
> this.

My current test patch is found in
  https://lore.kernel.org/r/87r13jpec5.wl-tiwai@suse.de

A quick test on my local machine looked OK.

This also successfully works under Kernel 5.18.5
All HDMI Profiles appear under Built-in Audio

HDMI - Stereo
HDMI - 5.1 Surround Sound
HDMI - 7.1 Surround Sound

etc etc

I'm building yet another test kernel with my fix patch.  It's being built in OBS home:tiwai:bsc1200611-2 repo.
Ben, could you give it a try later once after the build finishes?

@Takashi CI runs clean so far for the kernel fix:
 - https://github.com/thesofproject/linux/pull/3705
 - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_105379v1/index.html?
I'll follow-up on alsa-devel once all tests have run and I've gone through the results.

Interestingly, all the Ivy Bridge and Sandy Bridge machines have 0300 as the display PCI device class, explaining why this slipped through to 5.18:
https://intel-gfx-ci.01.org/hardware/fi-ivb-3520m/lspci-s02.log.txt
https://intel-gfx-ci.01.org/hardware/fi-ilk-650/lspci-s02.log.txt
https://intel-gfx-ci.01.org/hardware/pig-snb-2600/lspci-s02.log.txt

It's still a regression and broke Ben's setup. Apologies for this and thank you for the report (and the fix Takashi!).

FYI, the fix patch was merged to stable git branch, and the next TW kernel (likely 5.18.6) will include it.

(In reply to Takashi Iwai from comment #63)
> FYI, the fix patch was merged to stable git branch, and the next TW kernel
> (likely 5.18.6) will include it.

Just to say thank you for your help here, really appreciated
I guess in my case, i will just have to use the technique suggested by
Kai Vehmanen to help me get audio output via HDMI should i want to just listen to
some audio

"Kai Vehmanen

A good debug tool to separate the problems a bit is to to switch to terminal console (ctrl+alt+f2). This should force output on all monitors you have connected and audio should work to all monitors in this mode as well. You can switch back with ctrl+alt+f7."


Right now, under KDE (x11 or Wayland) Im waiting for the multi-monitor bug to be
remedied so i can actually use my other 2 monitors.

There is actually also currently a bug with swtiching to terminal using CTRL+ALT+F2 in that the screen
literally sows garbage instead of the desktop most of the time, sometimes switchching back and forth multiple times correct the display issue

I will create a separate bug report for this issue

I have installed DE MATE so i can use other 2 monitors, and the also have the HDMI sound output

Since the fix was merged to git branch, let's close this bug for now.

For the remaining issue about multi monitor on KDE, please open a dedicated entry and let's track there; it's no kernel issue, after all.

Thanks for your report and quick testing!

SUSE-SU-2022:2520-1: An update that solves 49 vulnerabilities, contains 26 features and has 207 fixes is now available.

Category: security (important)
Bug References: 1055117,1061840,1065729,1071995,1089644,1103269,1118212,1121726,1137728,1156395,1157038,1157923,1175667,1179439,1179639,1180814,1183682,1183872,1184318,1184924,1187716,1188885,1189998,1190137,1190208,1190336,1190497,1190768,1190786,1190812,1191271,1191663,1192483,1193064,1193277,1193289,1193431,1193556,1193629,1193640,1193787,1193823,1193852,1194086,1194111,1194191,1194409,1194501,1194523,1194526,1194583,1194585,1194586,1194625,1194765,1194826,1194869,1195099,1195287,1195478,1195482,1195504,1195651,1195668,1195669,1195775,1195823,1195826,1195913,1195915,1195926,1195944,1195957,1195987,1196079,1196114,1196130,1196213,1196306,1196367,1196400,1196426,1196478,1196514,1196570,1196723,1196779,1196830,1196836,1196866,1196868,1196869,1196901,1196930,1196942,1196960,1197016,1197157,1197227,1197243,1197292,1197302,1197303,1197304,1197362,1197386,1197501,1197601,1197661,1197675,1197761,1197817,1197819,1197820,1197888,1197889,1197894,1197915,1197917,1197918,1197920,1197921,1197922,1197926,1198009,1198010,1198012,1198013,1198014,1198015,1198016,1198017,1198018,1198019,1198020,1198021,1198022,1198023,1198024,1198027,1198030,1198034,1198058,1198217,1198379,1198400,1198402,1198410,1198412,1198413,1198438,1198484,1198577,1198585,1198660,1198802,1198803,1198806,1198811,1198826,1198829,1198835,1198968,1198971,1199011,1199024,1199035,1199046,1199052,1199063,1199163,1199173,1199260,1199314,1199390,1199426,1199433,1199439,1199482,1199487,1199505,1199507,1199605,1199611,1199626,1199631,1199650,1199657,1199674,1199736,1199793,1199839,1199875,1199909,1200015,1200019,1200045,1200046,1200144,1200205,1200211,1200259,1200263,1200284,1200315,1200343,1200420,1200442,1200475,1200502,1200567,1200569,1200571,1200599,1200600,1200608,1200611,1200619,1200692,1200762,1200763,1200806,1200807,1200808,1200809,1200810,1200812,1200813,1200815,1200816,1200820,1200821,1200822,1200824,1200825,1200827,1200828,1200829,1200830,1200845,1200882,1200925,1201050,1201080,1201160,1201171,1201177,1201193,1201196,1201218,1201222,1201228,1201251,1201381,1201471,1201524
CVE References: CVE-2021-26341,CVE-2021-33061,CVE-2021-4204,CVE-2021-44879,CVE-2021-45402,CVE-2022-0264,CVE-2022-0494,CVE-2022-0617,CVE-2022-1012,CVE-2022-1016,CVE-2022-1184,CVE-2022-1198,CVE-2022-1205,CVE-2022-1462,CVE-2022-1508,CVE-2022-1651,CVE-2022-1652,CVE-2022-1671,CVE-2022-1679,CVE-2022-1729,CVE-2022-1734,CVE-2022-1789,CVE-2022-1852,CVE-2022-1966,CVE-2022-1972,CVE-2022-1974,CVE-2022-1998,CVE-2022-20132,CVE-2022-20154,CVE-2022-21123,CVE-2022-21125,CVE-2022-21127,CVE-2022-21166,CVE-2022-21180,CVE-2022-21499,CVE-2022-2318,CVE-2022-23222,CVE-2022-26365,CVE-2022-26490,CVE-2022-29582,CVE-2022-29900,CVE-2022-29901,CVE-2022-30594,CVE-2022-33740,CVE-2022-33741,CVE-2022-33742,CVE-2022-33743,CVE-2022-33981,CVE-2022-34918
JIRA References: SLE-13513,SLE-13521,SLE-15442,SLE-17855,SLE-18194,SLE-18234,SLE-18375,SLE-18377,SLE-18378,SLE-18382,SLE-18385,SLE-18901,SLE-18938,SLE-18978,SLE-19001,SLE-19026,SLE-19242,SLE-19249,SLE-19253,SLE-19924,SLE-21315,SLE-23643,SLE-24072,SLE-24093,SLE-24350,SLE-24549
Sources used:
openSUSE Leap 15.4 (src):    dtb-aarch64-5.14.21-150400.24.11.1, kernel-64kb-5.14.21-150400.24.11.1, kernel-debug-5.14.21-150400.24.11.1, kernel-default-5.14.21-150400.24.11.1, kernel-default-base-5.14.21-150400.24.11.1.150400.24.3.6, kernel-docs-5.14.21-150400.24.11.1, kernel-kvmsmall-5.14.21-150400.24.11.1, kernel-obs-build-5.14.21-150400.24.11.1, kernel-obs-qa-5.14.21-150400.24.11.1, kernel-source-5.14.21-150400.24.11.1, kernel-syms-5.14.21-150400.24.11.1, kernel-zfcpdump-5.14.21-150400.24.11.1
SUSE Linux Enterprise Workstation Extension 15-SP4 (src):    kernel-default-5.14.21-150400.24.11.1
SUSE Linux Enterprise Module for Live Patching 15-SP4 (src):    kernel-default-5.14.21-150400.24.11.1, kernel-livepatch-SLE15-SP4_Update_1-1-150400.9.5.3
SUSE Linux Enterprise Module for Legacy Software 15-SP4 (src):    kernel-default-5.14.21-150400.24.11.1
SUSE Linux Enterprise Module for Development Tools 15-SP4 (src):    kernel-docs-5.14.21-150400.24.11.1, kernel-obs-build-5.14.21-150400.24.11.1, kernel-source-5.14.21-150400.24.11.1, kernel-syms-5.14.21-150400.24.11.1
SUSE Linux Enterprise Module for Basesystem 15-SP4 (src):    kernel-64kb-5.14.21-150400.24.11.1, kernel-default-5.14.21-150400.24.11.1, kernel-default-base-5.14.21-150400.24.11.1.150400.24.3.6, kernel-source-5.14.21-150400.24.11.1, kernel-zfcpdump-5.14.21-150400.24.11.1
SUSE Linux Enterprise High Availability 15-SP4 (src):    kernel-default-5.14.21-150400.24.11.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.

SUSE-SU-2022:2615-1: An update that solves 48 vulnerabilities, contains 26 features and has 202 fixes is now available.

Category: security (important)
Bug References: 1055117,1061840,1065729,1071995,1089644,1103269,1118212,1121726,1137728,1156395,1157038,1157923,1175667,1179439,1179639,1180814,1183682,1183872,1184318,1184924,1187716,1188885,1189998,1190137,1190208,1190336,1190497,1190768,1190786,1190812,1191271,1191663,1192483,1193064,1193277,1193289,1193431,1193556,1193629,1193640,1193787,1193823,1193852,1194086,1194111,1194191,1194409,1194501,1194523,1194526,1194583,1194585,1194586,1194625,1194765,1194826,1194869,1195099,1195287,1195478,1195482,1195504,1195651,1195668,1195669,1195775,1195823,1195826,1195913,1195915,1195926,1195944,1195957,1195987,1196079,1196114,1196130,1196213,1196306,1196367,1196400,1196426,1196478,1196514,1196570,1196723,1196779,1196830,1196836,1196866,1196868,1196869,1196901,1196930,1196942,1196960,1197016,1197157,1197227,1197243,1197292,1197302,1197303,1197304,1197362,1197386,1197501,1197601,1197661,1197675,1197761,1197817,1197819,1197820,1197888,1197889,1197894,1197915,1197917,1197918,1197920,1197921,1197922,1197926,1198009,1198010,1198012,1198013,1198014,1198015,1198016,1198017,1198018,1198019,1198020,1198021,1198022,1198023,1198024,1198027,1198030,1198034,1198058,1198217,1198379,1198400,1198402,1198412,1198413,1198438,1198484,1198577,1198585,1198660,1198802,1198803,1198806,1198811,1198826,1198835,1198968,1198971,1199011,1199024,1199035,1199046,1199052,1199063,1199163,1199173,1199260,1199314,1199390,1199426,1199433,1199439,1199482,1199487,1199505,1199507,1199605,1199611,1199626,1199631,1199650,1199657,1199674,1199736,1199793,1199839,1199875,1199909,1200015,1200019,1200045,1200046,1200144,1200205,1200211,1200259,1200263,1200284,1200315,1200343,1200420,1200442,1200475,1200502,1200567,1200569,1200571,1200572,1200599,1200600,1200608,1200611,1200619,1200692,1200762,1200763,1200806,1200807,1200808,1200809,1200810,1200812,1200815,1200816,1200820,1200822,1200824,1200825,1200827,1200828,1200829,1200830,1200845,1200882,1200925,1201050,1201160,1201171,1201177,1201193,1201196,1201218,1201222,1201228,1201251,150300
CVE References: CVE-2021-26341,CVE-2021-33061,CVE-2021-4204,CVE-2021-44879,CVE-2021-45402,CVE-2022-0264,CVE-2022-0494,CVE-2022-0617,CVE-2022-1012,CVE-2022-1016,CVE-2022-1184,CVE-2022-1198,CVE-2022-1205,CVE-2022-1508,CVE-2022-1651,CVE-2022-1652,CVE-2022-1671,CVE-2022-1679,CVE-2022-1729,CVE-2022-1734,CVE-2022-1789,CVE-2022-1852,CVE-2022-1966,CVE-2022-1972,CVE-2022-1974,CVE-2022-1998,CVE-2022-20132,CVE-2022-20154,CVE-2022-21123,CVE-2022-21125,CVE-2022-21127,CVE-2022-21166,CVE-2022-21180,CVE-2022-21499,CVE-2022-2318,CVE-2022-23222,CVE-2022-26365,CVE-2022-26490,CVE-2022-29582,CVE-2022-29900,CVE-2022-29901,CVE-2022-30594,CVE-2022-33740,CVE-2022-33741,CVE-2022-33742,CVE-2022-33743,CVE-2022-33981,CVE-2022-34918
JIRA References: SLE-13513,SLE-13521,SLE-15442,SLE-17855,SLE-18194,SLE-18234,SLE-18375,SLE-18377,SLE-18378,SLE-18382,SLE-18385,SLE-18901,SLE-18938,SLE-18978,SLE-19001,SLE-19026,SLE-19242,SLE-19249,SLE-19253,SLE-19924,SLE-21315,SLE-23643,SLE-24072,SLE-24093,SLE-24350,SLE-24549
Sources used:
openSUSE Leap 15.4 (src):    kernel-azure-5.14.21-150400.14.7.1, kernel-source-azure-5.14.21-150400.14.7.1, kernel-syms-azure-5.14.21-150400.14.7.1
SUSE Linux Enterprise Module for Public Cloud 15-SP4 (src):    kernel-azure-5.14.21-150400.14.7.1, kernel-source-azure-5.14.21-150400.14.7.1, kernel-syms-azure-5.14.21-150400.14.7.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.