[Bug 1182552] New: Kernel update after 5.3.18-lp152.57.1 causes USB microphone to loose connection / stop functioning
https://bugzilla.suse.com/show_bug.cgi?id=1182552 Bug ID: 1182552 Summary: Kernel update after 5.3.18-lp152.57.1 causes USB microphone to loose connection / stop functioning Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: cschinabeck@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Updating mid-Jan 2021 caused the USB headset microphone to stop working erratically. Sometimes re-initializing the application, swapping between microphones temporarily resolved the issue; unplugging and re-plugging the USB headset always resolved the microphone being dead but again only temporarily. It seemed that if there is no noise/feedback from the microphone it kills the connection and does not reinitialize. Different USB headsets/microphones in addition to different laptops/docks have been tested and all behaved the same. Eventually the issue was tracked down to the kernel being at fault: 5.3.18-lp152.57.1 is the last one that worked successfully. Booting the .60 or .63 kernel immediately brings back the problem. i+ | kernel-default | package | 5.3.18-lp152.63.1 | x86_64 | Main Update Repository i+ | kernel-default | package | 5.3.18-lp152.60.1 | x86_64 | Main Update Repository i+ | kernel-default | package | 5.3.18-lp152.57.1 | x86_64 | Main Update Repository The parameter "usbcore.autosuspend=-1" does not provide any improvement. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 Claus Schinabeck <cschinabeck@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cschinabeck@suse.com, | |kim.frederiksen@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=1182552 Claus Schinabeck <cschinabeck@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andreas.taschner@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=1182552 Roger Whittaker <roger.whittaker@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roger.whittaker@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=1182552 Chenzi Cao <chcao@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Kernel Assignee|screening-team-bugs@suse.de |kernel-bugs@opensuse.org -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com Flags| |needinfo?(cschinabeck@suse. | |com) --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- How "stop working"? Please elaborate. Does the device disappear or it doesn't react, or how? Please give the hardware details and logs, e.g. the dmesg output on both working and non-working kernels (indicating the problem). Also, hwinfo output as well as alsa-info.sh outputs (run it with --no-upload option). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c2 --- Comment #2 from Kim Frederiksen <kim.frederiksen@suse.com> --- Some further information about the issue. Using .57 kernel and MS Teams - all you would need to do is set MS Teams to use the Plantronics C320 as Speaker and Microphone. I always did this in MS Teams itself. Making and receiving calls works just fine - as expected. Upgrading to .60/63 kernel - what happens is that the headset speakers are working but the microphone very often doesn't work. The solution is to unplug the headset and plug it back in - while on the MS Teams call. After this, the speaker and microphone is working via the headset during the rest of the duration of the call. Upon next call, you really never know if the microphone is working or not - sometimes it does - sometimes not. I haven't been able to find any pattern - sometimes, a new call immediately afterwards the microphone would not work - other times it does. The more times goes by after the last call - the more likely it seems that the microphone doesn't work. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c3 --- Comment #3 from Kim Frederiksen <kim.frederiksen@suse.com> --- Created attachment 846408 --> https://bugzilla.suse.com/attachment.cgi?id=846408&action=edit alsa-info, dmesg and hwinfo from working kernel 57 alsa-info, dmesg and hwinfo from working kernel 57 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c4 --- Comment #4 from Kim Frederiksen <kim.frederiksen@suse.com> --- After collecting the requested info in comment 2, I did a poweroff of the laptop. Selected kernel 63 during boot - once desktop was up I started MS Teams and did a test call from within Teams. Headset speakers was working but microphone was not. I then phoned a colleague, again speaker OK, microphone not working. Colleague then phoned me back, again, speaker OK, microphone not working. I then collected the requested files. After having collected the files, colleague phoned me again and the microphone was working. At a subsequent call about 5-7 minutes later to another colleague - the microphone was NOT working again. Resolved by re-plugging USB headset - extra dmesg output is in file dmesg-kernel-63-2.txt. As mentioned - very unpredictable behavior. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c5 --- Comment #5 from Kim Frederiksen <kim.frederiksen@suse.com> --- Created attachment 846412 --> https://bugzilla.suse.com/attachment.cgi?id=846412&action=edit alsa-info, dmesg, dmesg-2 and hwinfo from non working kernel 63 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c6 Kim Frederiksen <kim.frederiksen@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(cschinabeck@suse. | |com) | --- Comment #6 from Kim Frederiksen <kim.frederiksen@suse.com> --- Just clearing the needinfo request -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c7 --- Comment #7 from Takashi Iwai <tiwai@suse.com> --- Thanks. So there have been no relevant error message or anything suspicious in the logs. What's still not clear is what exactly "not working", though: when the problem happens, is the PulseAudio input pointing to the right profile (USB audio microphone)? And the input doesn't work (that is only silent) even with the right input profile? FWIW, you can check via pavucontrol to see what's the current state and change the profile, too. If the above assumption is true, it's more likely a problem in USB-audio driver. The "big volume range" warning is a known problem with the devices from this vendor, and it's harmless. So something else that doesn't show up as the kernel error must be the issue. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c8 --- Comment #8 from Kim Frederiksen <kim.frederiksen@suse.com> --- Correct, all the input devices are there but there is just silence, like in MS Teams the selecting for Plantronics C320 is still available. A suggestion from a Google research was to change the profile for the Plantronics C320 from "Analog Stereo Duplex" to "Digital Stereo IEC958) Output + Analog Stereo Input" didn't change the behavior. I left the profile at "Digitial Ste... + Analog .. Input". In pavucontrol under "Recording" - I have noticed that when the microphone is not working there is no "activity bar" below Silence. Re-plugging the headset causes the "activity bar" to show up and also the microphone to work again (even during active calls). I hope that makes sense and helps. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c9 --- Comment #9 from Takashi Iwai <tiwai@suse.com> --- Hm, then it could be specific to some headset models. I have a Plantronics 3220 that has a slightly different device ID, but haven't seen the problem. Alas, I have newer PulseAudio and other stuff on my machine, so this might be the difference. Could you give lsusb -v output of the device? I'd like to compare with mine. And, for the problem, please try the following: - Create /lib/modules/$VERSION/updates directory where $VERSION is the latest kernel you're using, % mkdir -p /lib/modules/5.3.18-lp152.63-default/updates - Copy or symlink the old working snd-usb-audio.ko from the old kernel modules directory, e.g. % ln -s /lib/modules/5.3.18-lp152.57-default/kernel/sound/usb/snd-usb-audio.ko /lib/modules/5.3.18-lp152.63/updates/ - Run depmod, reboot and retest with *.63 kernel. This will make the old driver module loaded on the new kernel. If this makes the device working consistently, it indicates that the problem is in that driver. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c10 --- Comment #10 from Takashi Iwai <tiwai@suse.com> --- Oh, before doing the above: if you get the broken state again with the latest kernel, please check the following at first. - Get alsa-info.sh snapshot again at the broken state - Test the recording directly via arecord without Pulseaudio. It's done like: % pasuspender -- arecord -Dplughw:1 -vv foo.wav where I assume the card 1 corresponds to the device. Check the right card number by checking "cat /proc/asound/cards". - If the arecord also give only the silence, try to turn on the debug print of the usb-audio driver: % echo -n "module snd_usb_audio +p" > /sys/kernel/debug/dynamic_debug/control ... and retest arecord. This should give more debug prints in dmesg output, and attach the dmesg output to Bugzilla. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs@opensuse.org |tiwai@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=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c11 --- Comment #11 from Kim Frederiksen <kim.frederiksen@suse.com> --- Some more info from my testing today: - MS Teams test call fails - Start and check with pavucontrol - no "activity bar" - pasuspender -- arecord -Dplughw:1 -vv foo.wav does record audio - pavucontrol now shows the Silence "activity bar" - MS Teams test call now successful - As a test - I left pavucontrol open. (09:42) - MS Teams test successful at 10:00 - Closed pavucontrol at 10:00 (screen saver kicked in) - MS Teams test call working (10:20) - MS Teams test call not working (10:33) - ran the alsa-info - ran pasuspender - audio working - MS Teams test call working again (10:34) - MS Teams test call NOT working (10:35) - Started pavucontrol - again no "activity bar" under Silence - ran pasuspender again - audio working - pavucontrol now shows "activity bar" under Silence (left pavucontrol running) - MS Teams working again (10:37) In all cases, the headset speakers are working - it's only the microphone that doesn't work. I'll be attaching the alsa-info and screenshots of pavucontrol. Please note that I have _not_ done any of the suggestions from comment #9. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c12 --- Comment #12 from Kim Frederiksen <kim.frederiksen@suse.com> --- Created attachment 846431 --> https://bugzilla.suse.com/attachment.cgi?id=846431&action=edit alsa-info, pavucontrol screenshots -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c13 --- Comment #13 from Takashi Iwai <tiwai@suse.com> --- The picture with non-working state showed no level indicator bar at all, even not zero level. It looks strange to me. Does this state remain even if you switch the input device? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c14 --- Comment #14 from Kim Frederiksen <kim.frederiksen@suse.com> --- (In reply to Takashi Iwai from comment #13)
The picture with non-working state showed no level indicator bar at all, even not zero level. It looks strange to me. Does this state remain even if you switch the input device?
Yes, no change even when switching input. If I however run the "pasuspender -- arecord -Dplughw:1 -vv broken.wav" - the audio works again - even with MS Teams. To me, it almost looks like some sort of "sleep mode" for the microphone when it's not being used and MS Teams (and similar applications) doesn't to be able to "wake it up again". pasusoender however is able to "wake up" the microphone. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c15 --- Comment #15 from Takashi Iwai <tiwai@suse.com> --- Wait, even if you switch to other device (e.g. the onboard audio), doesn't the input work yet (at least the volume level appears and responding)? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c16 --- Comment #16 from Kim Frederiksen <kim.frederiksen@suse.com> --- (In reply to Takashi Iwai from comment #15)
Wait, even if you switch to other device (e.g. the onboard audio), doesn't the input work yet (at least the volume level appears and responding)?
I would normally unplug the USB headset at which point there is fallback to built-in laptop speakers/microphone which is working. I would then plug the headset back in and both audio's would transfer to the USB headset. I would do this while the MS Teams call is active. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c17 --- Comment #17 from Takashi Iwai <tiwai@suse.com> --- OK, but if you switch the device in the pavucontrol Recording tab for Skype ("Input from" menu) to the built-in device on the fly, does the volume meter start working? If yes, selecting back to Plantronics after that again, does the volume meter disappear again? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c18 --- Comment #18 from Kim Frederiksen <kim.frederiksen@suse.com> --- (In reply to Takashi Iwai from comment #17)
OK, but if you switch the device in the pavucontrol Recording tab for Skype ("Input from" menu) to the built-in device on the fly, does the volume meter start working? If yes, selecting back to Plantronics after that again, does the volume meter disappear again?
When switching with pavucontrol to built-in device, the volume meter starts working again. Switching back to Plantronics, volume meter stays but doesn't work. I suspect that just a display issue with pavucontrol because when restarting pavucontrol, the volume meter for the Plantronics input is missing again. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c19 --- Comment #19 from Takashi Iwai <tiwai@suse.com> --- Then let's try to gather the debug messages from usb-audio driver. It can be enabled as in comment 10, but maybe a safer way would be to boot with snd_usb_audio.dyndbg=+p boot option. Then the debug prints are enabled from the beginning. At first, get the dmesg output from the bad kernel (with the option above) while Teams is working fine. Then, later on, when Teams gets broken, get the dmesg output again, and we can compare the logs. At the same time, please try to get the contents of /proc/asound/card1/pcm0c/sub0/* files in both situations. (The card1 should correspond to Plantoronics headset, check the contents of /proc/asound/cards beforehand.) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c20 --- Comment #20 from Kim Frederiksen <kim.frederiksen@suse.com> --- (In reply to Takashi Iwai from comment #19)
Then let's try to gather the debug messages from usb-audio driver. It can be enabled as in comment 10, but maybe a safer way would be to boot with snd_usb_audio.dyndbg=+p boot option. Then the debug prints are enabled from the beginning.
At first, get the dmesg output from the bad kernel (with the option above) while Teams is working fine. Then, later on, when Teams gets broken, get the dmesg output again, and we can compare the logs.
At the same time, please try to get the contents of /proc/asound/card1/pcm0c/sub0/* files in both situations. (The card1 should correspond to Plantoronics headset, check the contents of /proc/asound/cards beforehand.)
As my headset was already not working, I used the "echo -n "module snd_usb_audio +p" > /sys/kernel/debug/dynamic_debug/control" to enable debug. I then did a MS Teams test call and the microphone was not working. See attached file "not-working-comment20.txt" I then re-plugged the headset and tried the MS Teams again - still not working. I then started the MS Teams test call - while active, I re-plugged the headset and microphone was working. Please see attach file "working-comment20.txt". -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c21 --- Comment #21 from Kim Frederiksen <kim.frederiksen@suse.com> --- Created attachment 846559 --> https://bugzilla.suse.com/attachment.cgi?id=846559&action=edit File mentioned in comment 20 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c22 --- Comment #22 from Kim Frederiksen <kim.frederiksen@suse.com> --- Created attachment 846560 --> https://bugzilla.suse.com/attachment.cgi?id=846560&action=edit File mentioned in comment 20 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c23 --- Comment #23 from Kim Frederiksen <kim.frederiksen@suse.com> --- Created attachment 846563 --> https://bugzilla.suse.com/attachment.cgi?id=846563&action=edit Output _while_ on the MS Teams test call and microphone not working: -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c24 --- Comment #24 from Kim Frederiksen <kim.frederiksen@suse.com> --- (In reply to Takashi Iwai from comment #9)
Hm, then it could be specific to some headset models. I have a Plantronics 3220 that has a slightly different device ID, but haven't seen the problem. Alas, I have newer PulseAudio and other stuff on my machine, so this might be the difference.
Could you give lsusb -v output of the device? I'd like to compare with mine.
And, for the problem, please try the following: - Create /lib/modules/$VERSION/updates directory where $VERSION is the latest kernel you're using, % mkdir -p /lib/modules/5.3.18-lp152.63-default/updates
- Copy or symlink the old working snd-usb-audio.ko from the old kernel modules directory, e.g. % ln -s /lib/modules/5.3.18-lp152.57-default/kernel/sound/usb/snd-usb-audio.ko /lib/modules/5.3.18-lp152.63/updates/
- Run depmod, reboot and retest with *.63 kernel.
This will make the old driver module loaded on the new kernel. If this makes the device working consistently, it indicates that the problem is in that driver.
Since Monday morning, I've been running the 63 kernel with the 57 kernel's snd-usb-audio.ko module and I have _not_ had any issues. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c25 --- Comment #25 from Takashi Iwai <tiwai@suse.com> --- OK, it's good to know that the old code is working fine. I'm building a test kernel with the latest upstream fixes wrt usb-audio, with a little hope that it fixes as well. The package is being built in OBS home:tiwai:bsc1182552 repo, will be available later at: http://download.opensuse.org/repositories/home:/tiwai:/bsc1182552/standard/ Please give it a try later. Note that this is a package with unofficial key, so Secure Boot won't work with this kernel. Disable Secure Boot on BIOS if you enabled it on your machine. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c26 --- Comment #26 from Kim Frederiksen <kim.frederiksen@suse.com> --- Tried the test kernel but unfortunately it does not resolve the issue. MS Teams failed on first test call. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c27 --- Comment #27 from Takashi Iwai <tiwai@suse.com> --- Hrm, then I'm not sure what went wrong. Just to make things straight: before you start Teams, open pavucontrol, and see that Plantronics headset recording works (in "Input Devices", VU meter moves with the voice). Then start Teams, check the test call or such. At this stage, it still works? We need to identify the problem happening in which situation. The symptom ("just stop working") is way too ambiguous, unfortunately... And the next step would be to get the more verbose log from pulseaudio. Stop pulseaudio once, and restart with verbose debug options: % systemctl --user stop pulseaudio.socket % systemctl --user stop pulseaudio.service % pulseaudio -vvv > pa.log 2>&1 And get the point where the problem happens. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c28 --- Comment #28 from Kim Frederiksen <kim.frederiksen@suse.com> --- (In reply to Takashi Iwai from comment #27)
Hrm, then I'm not sure what went wrong.
Just to make things straight: before you start Teams, open pavucontrol, and see that Plantronics headset recording works (in "Input Devices", VU meter moves with the voice). Then start Teams, check the test call or such. At this stage, it still works?
After installing the test kernel, I did a poweroff. Upon restart, I started Teams and pavucontrol at the same time. In pavucontrol there was _no_ VU meter - hence also Teams test call was unsuccessful (as always, speakers are working, microphone not). I did a poweroff again, booted using the 63 kernel with 57 kernel snd-usb-audio.ko and a Teams test call was successful. I'll try and get the other requested information tomorrow. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c29 --- Comment #29 from Takashi Iwai <tiwai@suse.com> --- I got a fix patch for a similar headset (Plantronics C320-M) right now, and this might be applied to C320, too. A new test kernel with those fixes is currently being built in OBS home:tiwai:bsc1182552-2 repo. It'll be available at http://download.opensuse.org/repositories/home:/tiwai:/bsc1182552-2/standard... Please give this one a try again later. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c30 --- Comment #30 from Kim Frederiksen <kim.frederiksen@suse.com> --- Good news, with the "-2" test kernel it seems the issue is resolved. Installed on 2 different laptops - check with pavucontrol and Teams - microphone was working on the first test call right after cold boot. I'll be running the test kernel today and report back tomorrow (Friday). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c31 --- Comment #31 from Takashi Iwai <tiwai@suse.com> --- Good to hear, finally! Let's hope that it'll keep working. FWIW, the bug seems to be present in the earlier kernels, but it didn't surface because of the different access pattern to the hardware. When the USB control packet is sent too quickly, the Plantronics devices seem ignoring them or silently failing. The workaround was to add a certain delay before each control message handling. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c32 --- Comment #32 from Kim Frederiksen <kim.frederiksen@suse.com> --- Good news, I was using the "-2" test kernel the whole of yesterday and everything was working fine. Right after booting this morning, things were also working as expected. Thanks for all your efforts - such a pleasure to have a working headset again :-) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c33 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #33 from Takashi Iwai <tiwai@suse.com> --- The fixes have been pushed to SLE15-SP2 branch and will be merged soon later. Unfortunately, it slipped from the upcoming update kernel, so it'll be merged likely in the next update in April. Until then, you can keep my patched kernel or use the workaround by copying the old kernel module. I close this bug now. Thank you for patient testing! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c34 --- Comment #34 from Takashi Iwai <tiwai@suse.com> --- Created attachment 846816 --> https://bugzilla.suse.com/attachment.cgi?id=846816&action=edit Fix patch -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c39 --- Comment #39 from OBSbugzilla Bot <bwiedemann+obsbugzillabot@suse.com> --- This is an autogenerated message for OBS integration: This bug (1182552) was mentioned in https://build.opensuse.org/request/show/883472 15.2 / kernel-source -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c43 --- Comment #43 from Swamp Workflow Management <swamp@suse.de> --- openSUSE-SU-2021:0532-1: An update that solves 21 vulnerabilities and has 74 fixes is now available. Category: security (important) Bug References: 1152472,1152489,1153274,1154353,1155518,1156256,1159280,1160634,1167773,1168777,1169514,1169709,1171295,1173485,1177326,1178163,1178330,1179454,1180197,1180980,1181383,1181674,1181862,1182011,1182077,1182485,1182552,1182574,1182591,1182595,1182715,1182716,1182717,1182770,1182989,1183015,1183018,1183022,1183023,1183048,1183252,1183277,1183278,1183279,1183280,1183281,1183282,1183283,1183284,1183285,1183286,1183287,1183288,1183366,1183369,1183386,1183412,1183416,1183427,1183428,1183445,1183447,1183501,1183509,1183530,1183534,1183540,1183593,1183596,1183598,1183637,1183646,1183662,1183686,1183692,1183696,1183750,1183757,1183775,1183843,1183859,1183871,1184167,1184168,1184170,1184176,1184192,1184193,1184196,1184198,1184217,1184218,1184219,1184220,1184224 CVE References: CVE-2019-18814,CVE-2019-19769,CVE-2020-27170,CVE-2020-27171,CVE-2020-27815,CVE-2020-35519,CVE-2021-27363,CVE-2021-27364,CVE-2021-27365,CVE-2021-28038,CVE-2021-28375,CVE-2021-28660,CVE-2021-28688,CVE-2021-28964,CVE-2021-28971,CVE-2021-28972,CVE-2021-29264,CVE-2021-29265,CVE-2021-29647,CVE-2021-3428,CVE-2021-3444 JIRA References: Sources used: openSUSE Leap 15.2 (src): kernel-debug-5.3.18-lp152.69.1, kernel-default-5.3.18-lp152.69.1, kernel-default-base-5.3.18-lp152.69.1.lp152.8.28.1, kernel-docs-5.3.18-lp152.69.1, kernel-kvmsmall-5.3.18-lp152.69.1, kernel-obs-build-5.3.18-lp152.69.1, kernel-obs-qa-5.3.18-lp152.69.1, kernel-preempt-5.3.18-lp152.69.1, kernel-source-5.3.18-lp152.69.1, kernel-syms-5.3.18-lp152.69.1 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c45 --- Comment #45 from Swamp Workflow Management <swamp@suse.de> --- SUSE-SU-2021:1177-1: An update that solves 21 vulnerabilities and has 74 fixes is now available. Category: security (important) Bug References: 1152472,1152489,1153274,1154353,1155518,1156256,1159280,1160634,1167773,1168777,1169514,1169709,1171295,1173485,1177326,1178163,1178330,1179454,1180197,1180980,1181383,1181674,1181862,1182011,1182077,1182485,1182552,1182574,1182591,1182595,1182715,1182716,1182717,1182770,1182989,1183015,1183018,1183022,1183023,1183048,1183252,1183277,1183278,1183279,1183280,1183281,1183282,1183283,1183284,1183285,1183286,1183287,1183288,1183366,1183369,1183386,1183412,1183416,1183427,1183428,1183445,1183447,1183501,1183509,1183530,1183534,1183540,1183593,1183596,1183598,1183637,1183646,1183662,1183686,1183692,1183696,1183750,1183757,1183775,1183843,1183859,1183871,1184167,1184168,1184170,1184176,1184192,1184193,1184196,1184198,1184217,1184218,1184219,1184220,1184224 CVE References: CVE-2019-18814,CVE-2019-19769,CVE-2020-27170,CVE-2020-27171,CVE-2020-27815,CVE-2020-35519,CVE-2021-27363,CVE-2021-27364,CVE-2021-27365,CVE-2021-28038,CVE-2021-28375,CVE-2021-28660,CVE-2021-28688,CVE-2021-28964,CVE-2021-28971,CVE-2021-28972,CVE-2021-29264,CVE-2021-29265,CVE-2021-29647,CVE-2021-3428,CVE-2021-3444 JIRA References: Sources used: SUSE Linux Enterprise Module for Public Cloud 15-SP2 (src): kernel-azure-5.3.18-18.41.1, kernel-source-azure-5.3.18-18.41.1, kernel-syms-azure-5.3.18-18.41.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=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c50 --- Comment #50 from Swamp Workflow Management <swamp@suse.de> --- SUSE-SU-2021:1211-1: An update that solves 32 vulnerabilities and has 85 fixes is now available. Category: security (important) Bug References: 1047233,1065729,1113295,1152472,1152489,1153274,1154353,1155518,1156256,1156395,1159280,1160634,1167773,1168777,1169514,1169709,1171295,1173485,1177326,1178163,1178181,1178330,1179454,1180197,1180980,1181383,1181507,1181674,1181862,1182011,1182077,1182485,1182552,1182574,1182591,1182595,1182712,1182713,1182715,1182716,1182717,1182770,1182989,1183015,1183018,1183022,1183023,1183048,1183252,1183277,1183278,1183279,1183280,1183281,1183282,1183283,1183284,1183285,1183286,1183287,1183288,1183366,1183369,1183386,1183405,1183412,1183416,1183427,1183428,1183445,1183447,1183501,1183509,1183530,1183534,1183540,1183593,1183596,1183598,1183637,1183646,1183662,1183686,1183692,1183696,1183750,1183757,1183775,1183843,1183859,1183871,1184074,1184120,1184167,1184168,1184170,1184176,1184192,1184193,1184194,1184196,1184198,1184211,1184217,1184218,1184219,1184220,1184224,1184388,1184391,1184393,1184509,1184511,1184512,1184514,1184583,1184647 CVE References: CVE-2019-18814,CVE-2019-19769,CVE-2020-25670,CVE-2020-25671,CVE-2020-25672,CVE-2020-25673,CVE-2020-27170,CVE-2020-27171,CVE-2020-27815,CVE-2020-35519,CVE-2020-36310,CVE-2020-36311,CVE-2020-36312,CVE-2021-27363,CVE-2021-27364,CVE-2021-27365,CVE-2021-28038,CVE-2021-28375,CVE-2021-28660,CVE-2021-28688,CVE-2021-28950,CVE-2021-28964,CVE-2021-28971,CVE-2021-28972,CVE-2021-29154,CVE-2021-29264,CVE-2021-29265,CVE-2021-29647,CVE-2021-30002,CVE-2021-3428,CVE-2021-3444,CVE-2021-3483 JIRA References: Sources used: SUSE Linux Enterprise Module for Realtime 15-SP2 (src): kernel-rt-5.3.18-33.1, kernel-rt_debug-5.3.18-33.1, kernel-source-rt-5.3.18-33.1, kernel-syms-rt-5.3.18-33.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=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c51 --- Comment #51 from Swamp Workflow Management <swamp@suse.de> --- SUSE-SU-2021:1238-1: An update that solves 33 vulnerabilities and has 86 fixes is now available. Category: security (important) Bug References: 1047233,1065729,1113295,1152472,1152489,1153274,1154353,1155518,1156256,1156395,1159280,1160634,1167574,1167773,1168777,1169514,1169709,1171295,1173485,1175995,1177326,1178163,1178181,1178330,1179454,1180197,1180980,1181383,1181507,1181674,1181862,1182011,1182077,1182485,1182552,1182574,1182591,1182595,1182715,1182716,1182717,1182770,1182989,1183015,1183018,1183022,1183023,1183048,1183252,1183277,1183278,1183279,1183280,1183281,1183282,1183283,1183284,1183285,1183286,1183287,1183288,1183366,1183369,1183386,1183405,1183412,1183416,1183427,1183428,1183445,1183447,1183501,1183509,1183530,1183534,1183540,1183593,1183596,1183598,1183637,1183646,1183662,1183686,1183692,1183696,1183750,1183757,1183775,1183843,1183859,1183871,1184074,1184120,1184167,1184168,1184170,1184176,1184192,1184193,1184194,1184196,1184198,1184211,1184217,1184218,1184219,1184220,1184224,1184388,1184391,1184393,1184485,1184509,1184511,1184512,1184514,1184583,1184585,1184647 CVE References: CVE-2019-18814,CVE-2019-19769,CVE-2020-25670,CVE-2020-25671,CVE-2020-25672,CVE-2020-25673,CVE-2020-27170,CVE-2020-27171,CVE-2020-27815,CVE-2020-35519,CVE-2020-36310,CVE-2020-36311,CVE-2020-36312,CVE-2020-36322,CVE-2021-27363,CVE-2021-27364,CVE-2021-27365,CVE-2021-28038,CVE-2021-28375,CVE-2021-28660,CVE-2021-28688,CVE-2021-28950,CVE-2021-28964,CVE-2021-28971,CVE-2021-28972,CVE-2021-29154,CVE-2021-29264,CVE-2021-29265,CVE-2021-29647,CVE-2021-30002,CVE-2021-3428,CVE-2021-3444,CVE-2021-3483 JIRA References: Sources used: SUSE MicroOS 5.0 (src): kernel-default-5.3.18-24.61.1, kernel-default-base-5.3.18-24.61.1.9.26.4 SUSE Linux Enterprise Workstation Extension 15-SP2 (src): kernel-default-5.3.18-24.61.1, kernel-preempt-5.3.18-24.61.1 SUSE Linux Enterprise Module for Live Patching 15-SP2 (src): kernel-default-5.3.18-24.61.1, kernel-livepatch-SLE15-SP2_Update_12-1-5.3.4 SUSE Linux Enterprise Module for Legacy Software 15-SP2 (src): kernel-default-5.3.18-24.61.1 SUSE Linux Enterprise Module for Development Tools 15-SP2 (src): kernel-docs-5.3.18-24.61.1, kernel-obs-build-5.3.18-24.61.1, kernel-preempt-5.3.18-24.61.1, kernel-source-5.3.18-24.61.1, kernel-syms-5.3.18-24.61.1 SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): kernel-default-5.3.18-24.61.1, kernel-default-base-5.3.18-24.61.1.9.26.4, kernel-preempt-5.3.18-24.61.1, kernel-source-5.3.18-24.61.1 SUSE Linux Enterprise High Availability 15-SP2 (src): kernel-default-5.3.18-24.61.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=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c53 --- Comment #53 from Swamp Workflow Management <swamp@suse.de> --- SUSE-SU-2021:1625-1: An update that solves 32 vulnerabilities and has 85 fixes is now available. Category: security (important) Bug References: 1047233,1065729,1113295,1152472,1152489,1153274,1154353,1155518,1156256,1156395,1159280,1160634,1167773,1168777,1169514,1169709,1171295,1173485,1177326,1178163,1178181,1178330,1179454,1180197,1180980,1181383,1181507,1181674,1181862,1182011,1182077,1182485,1182552,1182574,1182591,1182595,1182712,1182713,1182715,1182716,1182717,1182770,1182989,1183015,1183018,1183022,1183023,1183048,1183252,1183277,1183278,1183279,1183280,1183281,1183282,1183283,1183284,1183285,1183286,1183287,1183288,1183366,1183369,1183386,1183405,1183412,1183416,1183427,1183428,1183445,1183447,1183501,1183509,1183530,1183534,1183540,1183593,1183596,1183598,1183637,1183646,1183662,1183686,1183692,1183696,1183750,1183757,1183775,1183843,1183859,1183871,1184074,1184120,1184167,1184168,1184170,1184176,1184192,1184193,1184194,1184196,1184198,1184211,1184217,1184218,1184219,1184220,1184224,1184388,1184391,1184393,1184509,1184511,1184512,1184514,1184583,1184647 CVE References: CVE-2019-18814,CVE-2019-19769,CVE-2020-25670,CVE-2020-25671,CVE-2020-25672,CVE-2020-25673,CVE-2020-27170,CVE-2020-27171,CVE-2020-27815,CVE-2020-35519,CVE-2020-36310,CVE-2020-36311,CVE-2020-36312,CVE-2021-27363,CVE-2021-27364,CVE-2021-27365,CVE-2021-28038,CVE-2021-28375,CVE-2021-28660,CVE-2021-28688,CVE-2021-28950,CVE-2021-28964,CVE-2021-28971,CVE-2021-28972,CVE-2021-29154,CVE-2021-29264,CVE-2021-29265,CVE-2021-29647,CVE-2021-30002,CVE-2021-3428,CVE-2021-3444,CVE-2021-3483 JIRA References: Sources used: SUSE MicroOS 5.0 (src): kernel-rt-5.3.18-8.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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c54 --- Comment #54 from Swamp Workflow Management <swamp@suse.de> --- openSUSE-SU-2021:0758-1: An update that solves 32 vulnerabilities and has 85 fixes is now available. Category: security (important) Bug References: 1047233,1065729,1113295,1152472,1152489,1153274,1154353,1155518,1156256,1156395,1159280,1160634,1167773,1168777,1169514,1169709,1171295,1173485,1177326,1178163,1178181,1178330,1179454,1180197,1180980,1181383,1181507,1181674,1181862,1182011,1182077,1182485,1182552,1182574,1182591,1182595,1182712,1182713,1182715,1182716,1182717,1182770,1182989,1183015,1183018,1183022,1183023,1183048,1183252,1183277,1183278,1183279,1183280,1183281,1183282,1183283,1183284,1183285,1183286,1183287,1183288,1183366,1183369,1183386,1183405,1183412,1183416,1183427,1183428,1183445,1183447,1183501,1183509,1183530,1183534,1183540,1183593,1183596,1183598,1183637,1183646,1183662,1183686,1183692,1183696,1183750,1183757,1183775,1183843,1183859,1183871,1184074,1184120,1184167,1184168,1184170,1184176,1184192,1184193,1184194,1184196,1184198,1184211,1184217,1184218,1184219,1184220,1184224,1184388,1184391,1184393,1184509,1184511,1184512,1184514,1184583,1184647 CVE References: CVE-2019-18814,CVE-2019-19769,CVE-2020-25670,CVE-2020-25671,CVE-2020-25672,CVE-2020-25673,CVE-2020-27170,CVE-2020-27171,CVE-2020-27815,CVE-2020-35519,CVE-2020-36310,CVE-2020-36311,CVE-2020-36312,CVE-2021-27363,CVE-2021-27364,CVE-2021-27365,CVE-2021-28038,CVE-2021-28375,CVE-2021-28660,CVE-2021-28688,CVE-2021-28950,CVE-2021-28964,CVE-2021-28971,CVE-2021-28972,CVE-2021-29154,CVE-2021-29264,CVE-2021-29265,CVE-2021-29647,CVE-2021-30002,CVE-2021-3428,CVE-2021-3444,CVE-2021-3483 JIRA References: Sources used: openSUSE Leap 15.2 (src): kernel-rt-5.3.18-lp152.3.8.1, kernel-rt_debug-5.3.18-lp152.3.8.1, kernel-source-rt-5.3.18-lp152.3.8.1, kernel-syms-rt-5.3.18-lp152.3.8.1 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 Andreas Taschner <andreas.taschner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|andreas.taschner@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=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c60 --- Comment #60 from Swamp Workflow Management <swamp@suse.de> --- SUSE-SU-2021:1975-1: An update that solves 52 vulnerabilities and has 250 fixes is now available. Category: security (important) Bug References: 1043990,1047233,1055117,1065729,1087082,1113295,1133021,1152457,1152472,1152489,1153274,1154353,1155518,1156256,1156395,1159280,1160634,1164648,1167260,1167574,1167773,1168777,1168838,1169709,1171295,1173485,1174416,1174426,1175995,1176447,1176774,1177028,1177326,1177411,1177437,1177666,1178089,1178134,1178163,1178181,1178330,1178378,1178418,1178612,1179243,1179454,1179458,1179519,1179825,1179827,1179851,1180100,1180197,1180814,1180846,1180980,1181104,1181161,1181383,1181507,1181674,1181862,1182077,1182257,1182377,1182378,1182552,1182574,1182591,1182613,1182712,1182713,1182715,1182716,1182717,1182999,1183022,1183048,1183069,1183077,1183095,1183120,1183203,1183249,1183252,1183277,1183278,1183279,1183280,1183281,1183282,1183283,1183284,1183285,1183286,1183287,1183288,1183289,1183310,1183311,1183312,1183313,1183314,1183315,1183316,1183317,1183318,1183319,1183320,1183321,1183322,1183323,1183324,1183325,1183326,1183346,1183366,1183369,1183386,1183405,1183412,1183427,1183428,1183445,118344 7,1183491,1183501,1183509,1183530,1183534,1183540,1183593,1183596,1183598,1183637,1183646,1183658,1183662,1183686,1183692,1183696,1183750,1183757,1183775,1183815,1183843,1183859,1183868,1183871,1183873,1183932,1183947,1183976,1184074,1184081,1184082,1184120,1184167,1184168,1184170,1184171,1184176,1184192,1184193,1184194,1184196,1184197,1184198,1184199,1184208,1184209,1184211,1184217,1184218,1184219,1184220,1184224,1184259,1184264,1184386,1184388,1184391,1184393,1184436,1184485,1184509,1184511,1184512,1184514,1184583,1184585,1184611,1184615,1184650,1184710,1184724,1184728,1184730,1184731,1184736,1184737,1184738,1184740,1184741,1184742,1184760,1184769,1184811,1184855,1184893,1184934,1184942,1184943,1184952,1184953,1184955,1184957,1184969,1184984,1185010,1185041,1185110,1185113,1185233,1185269,1185365,1185428,1185454,1185472,1185491,1185495,1185497,1185549,1185550,1185558,1185573,1185581,1185586,1185587,1185589,1185606,1185640,1185641,1185642,1185645,1185670,1185677,1185680,1185703,118 5725,1185736,1185758,1185796,1185840,1185857,1185859,1185860,1185861,1185862,1185863,1185898,1185899,1185911,1185938,1185950,1185954,1185980,1185982,1185987,1185988,1186009,1186060,1186061,1186062,1186111,1186118,1186219,1186285,1186320,1186349,1186352,1186353,1186354,1186355,1186356,1186357,1186390,1186401,1186408,1186416,1186439,1186441,1186451,1186460,1186467,1186479,1186484,1186498,1186501,1186512,1186573,1186681 CVE References: CVE-2019-18814,CVE-2019-19769,CVE-2020-24586,CVE-2020-24587,CVE-2020-24588,CVE-2020-25670,CVE-2020-25671,CVE-2020-25672,CVE-2020-25673,CVE-2020-26139,CVE-2020-26141,CVE-2020-26145,CVE-2020-26147,CVE-2020-27170,CVE-2020-27171,CVE-2020-27673,CVE-2020-27815,CVE-2020-35519,CVE-2020-36310,CVE-2020-36311,CVE-2020-36312,CVE-2020-36322,CVE-2021-20268,CVE-2021-23134,CVE-2021-27363,CVE-2021-27364,CVE-2021-27365,CVE-2021-28038,CVE-2021-28375,CVE-2021-28660,CVE-2021-28688,CVE-2021-28950,CVE-2021-28952,CVE-2021-28964,CVE-2021-28971,CVE-2021-28972,CVE-2021-29154,CVE-2021-29155,CVE-2021-29264,CVE-2021-29265,CVE-2021-29647,CVE-2021-29650,CVE-2021-30002,CVE-2021-32399,CVE-2021-33034,CVE-2021-33200,CVE-2021-3428,CVE-2021-3444,CVE-2021-3483,CVE-2021-3489,CVE-2021-3490,CVE-2021-3491 JIRA References: Sources used: SUSE Linux Enterprise Module for Public Cloud 15-SP3 (src): kernel-azure-5.3.18-38.3.1, kernel-source-azure-5.3.18-38.3.1, kernel-syms-azure-5.3.18-38.3.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=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c61 --- Comment #61 from Swamp Workflow Management <swamp@suse.de> --- SUSE-SU-2021:1977-1: An update that solves 52 vulnerabilities and has 187 fixes is now available. Category: security (important) Bug References: 1055117,1065729,1087082,1113295,1133021,1152457,1152472,1152489,1153274,1154353,1155518,1156395,1160634,1164648,1167260,1167574,1167773,1168777,1168838,1169709,1171295,1173485,1174416,1174426,1175995,1176447,1176774,1177028,1177326,1177666,1178089,1178134,1178163,1178330,1178378,1178418,1179243,1179519,1179825,1179827,1179851,1180197,1180814,1180846,1181104,1181383,1181507,1181674,1181862,1182077,1182257,1182377,1182552,1182574,1182613,1182712,1182715,1182717,1182999,1183022,1183069,1183252,1183277,1183278,1183279,1183280,1183281,1183282,1183283,1183284,1183285,1183286,1183287,1183288,1183289,1183310,1183311,1183312,1183313,1183314,1183315,1183316,1183317,1183318,1183319,1183320,1183321,1183322,1183323,1183324,1183326,1183346,1183366,1183369,1183386,1183405,1183412,1183427,1183428,1183445,1183447,1183491,1183501,1183509,1183530,1183534,1183540,1183593,1183596,1183598,1183637,1183646,1183658,1183662,1183686,1183692,1183750,1183757,1183775,1183815,1183868,1183871,1183873,1183947,118397 6,1184074,1184081,1184082,1184120,1184167,1184168,1184170,1184171,1184192,1184193,1184194,1184196,1184197,1184198,1184199,1184208,1184209,1184211,1184217,1184218,1184219,1184220,1184224,1184264,1184386,1184388,1184391,1184393,1184436,1184485,1184514,1184585,1184611,1184615,1184650,1184710,1184724,1184728,1184730,1184731,1184736,1184737,1184738,1184740,1184741,1184742,1184769,1184811,1184855,1184934,1184942,1184943,1184955,1184969,1184984,1185010,1185113,1185233,1185269,1185428,1185491,1185495,1185549,1185550,1185558,1185573,1185581,1185586,1185587,1185606,1185640,1185641,1185642,1185645,1185670,1185680,1185703,1185725,1185736,1185758,1185796,1185840,1185857,1185898,1185899,1185911,1185938,1185950,1185980,1185988,1186009,1186061,1186111,1186118,1186219,1186285,1186320,1186349,1186352,1186353,1186354,1186355,1186356,1186357,1186401,1186408,1186439,1186441,1186479,1186484,1186498,1186501,1186512,1186681 CVE References: CVE-2019-18814,CVE-2019-19769,CVE-2020-24586,CVE-2020-24587,CVE-2020-24588,CVE-2020-25670,CVE-2020-25671,CVE-2020-25672,CVE-2020-25673,CVE-2020-26139,CVE-2020-26141,CVE-2020-26145,CVE-2020-26147,CVE-2020-27170,CVE-2020-27171,CVE-2020-27673,CVE-2020-27815,CVE-2020-35519,CVE-2020-36310,CVE-2020-36311,CVE-2020-36312,CVE-2020-36322,CVE-2021-20268,CVE-2021-23134,CVE-2021-27363,CVE-2021-27364,CVE-2021-27365,CVE-2021-28038,CVE-2021-28375,CVE-2021-28660,CVE-2021-28688,CVE-2021-28950,CVE-2021-28952,CVE-2021-28964,CVE-2021-28971,CVE-2021-28972,CVE-2021-29154,CVE-2021-29155,CVE-2021-29264,CVE-2021-29265,CVE-2021-29647,CVE-2021-29650,CVE-2021-30002,CVE-2021-32399,CVE-2021-33034,CVE-2021-33200,CVE-2021-3428,CVE-2021-3444,CVE-2021-3483,CVE-2021-3489,CVE-2021-3490,CVE-2021-3491 JIRA References: Sources used: SUSE Linux Enterprise Workstation Extension 15-SP3 (src): kernel-default-5.3.18-59.5.2, kernel-preempt-5.3.18-59.5.2 SUSE Linux Enterprise Module for Live Patching 15-SP3 (src): kernel-default-5.3.18-59.5.2, kernel-livepatch-SLE15-SP3_Update_1-1-7.5.1 SUSE Linux Enterprise Module for Legacy Software 15-SP3 (src): kernel-default-5.3.18-59.5.2 SUSE Linux Enterprise Module for Development Tools 15-SP3 (src): kernel-docs-5.3.18-59.5.2, kernel-obs-build-5.3.18-59.5.1, kernel-preempt-5.3.18-59.5.2, kernel-source-5.3.18-59.5.2, kernel-syms-5.3.18-59.5.1 SUSE Linux Enterprise Module for Basesystem 15-SP3 (src): kernel-64kb-5.3.18-59.5.2, kernel-default-5.3.18-59.5.2, kernel-default-base-5.3.18-59.5.2.18.2.2, kernel-preempt-5.3.18-59.5.2, kernel-source-5.3.18-59.5.2, kernel-zfcpdump-5.3.18-59.5.2 SUSE Linux Enterprise High Availability 15-SP3 (src): kernel-default-5.3.18-59.5.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=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c63 --- Comment #63 from Swamp Workflow Management <swamp@suse.de> --- openSUSE-SU-2021:1975-1: An update that solves 52 vulnerabilities and has 250 fixes is now available. Category: security (important) Bug References: 1043990,1047233,1055117,1065729,1087082,1113295,1133021,1152457,1152472,1152489,1153274,1154353,1155518,1156256,1156395,1159280,1160634,1164648,1167260,1167574,1167773,1168777,1168838,1169709,1171295,1173485,1174416,1174426,1175995,1176447,1176774,1177028,1177326,1177411,1177437,1177666,1178089,1178134,1178163,1178181,1178330,1178378,1178418,1178612,1179243,1179454,1179458,1179519,1179825,1179827,1179851,1180100,1180197,1180814,1180846,1180980,1181104,1181161,1181383,1181507,1181674,1181862,1182077,1182257,1182377,1182378,1182552,1182574,1182591,1182613,1182712,1182713,1182715,1182716,1182717,1182999,1183022,1183048,1183069,1183077,1183095,1183120,1183203,1183249,1183252,1183277,1183278,1183279,1183280,1183281,1183282,1183283,1183284,1183285,1183286,1183287,1183288,1183289,1183310,1183311,1183312,1183313,1183314,1183315,1183316,1183317,1183318,1183319,1183320,1183321,1183322,1183323,1183324,1183325,1183326,1183346,1183366,1183369,1183386,1183405,1183412,1183427,1183428,1183445,118344 7,1183491,1183501,1183509,1183530,1183534,1183540,1183593,1183596,1183598,1183637,1183646,1183658,1183662,1183686,1183692,1183696,1183750,1183757,1183775,1183815,1183843,1183859,1183868,1183871,1183873,1183932,1183947,1183976,1184074,1184081,1184082,1184120,1184167,1184168,1184170,1184171,1184176,1184192,1184193,1184194,1184196,1184197,1184198,1184199,1184208,1184209,1184211,1184217,1184218,1184219,1184220,1184224,1184259,1184264,1184386,1184388,1184391,1184393,1184436,1184485,1184509,1184511,1184512,1184514,1184583,1184585,1184611,1184615,1184650,1184710,1184724,1184728,1184730,1184731,1184736,1184737,1184738,1184740,1184741,1184742,1184760,1184769,1184811,1184855,1184893,1184934,1184942,1184943,1184952,1184953,1184955,1184957,1184969,1184984,1185010,1185041,1185110,1185113,1185233,1185269,1185365,1185428,1185454,1185472,1185491,1185495,1185497,1185549,1185550,1185558,1185573,1185581,1185586,1185587,1185589,1185606,1185640,1185641,1185642,1185645,1185670,1185677,1185680,1185703,118 5725,1185736,1185758,1185796,1185840,1185857,1185859,1185860,1185861,1185862,1185863,1185898,1185899,1185911,1185938,1185950,1185954,1185980,1185982,1185987,1185988,1186009,1186060,1186061,1186062,1186111,1186118,1186219,1186285,1186320,1186349,1186352,1186353,1186354,1186355,1186356,1186357,1186390,1186401,1186408,1186416,1186439,1186441,1186451,1186460,1186467,1186479,1186484,1186498,1186501,1186512,1186573,1186681 CVE References: CVE-2019-18814,CVE-2019-19769,CVE-2020-24586,CVE-2020-24587,CVE-2020-24588,CVE-2020-25670,CVE-2020-25671,CVE-2020-25672,CVE-2020-25673,CVE-2020-26139,CVE-2020-26141,CVE-2020-26145,CVE-2020-26147,CVE-2020-27170,CVE-2020-27171,CVE-2020-27673,CVE-2020-27815,CVE-2020-35519,CVE-2020-36310,CVE-2020-36311,CVE-2020-36312,CVE-2020-36322,CVE-2021-20268,CVE-2021-23134,CVE-2021-27363,CVE-2021-27364,CVE-2021-27365,CVE-2021-28038,CVE-2021-28375,CVE-2021-28660,CVE-2021-28688,CVE-2021-28950,CVE-2021-28952,CVE-2021-28964,CVE-2021-28971,CVE-2021-28972,CVE-2021-29154,CVE-2021-29155,CVE-2021-29264,CVE-2021-29265,CVE-2021-29647,CVE-2021-29650,CVE-2021-30002,CVE-2021-32399,CVE-2021-33034,CVE-2021-33200,CVE-2021-3428,CVE-2021-3444,CVE-2021-3483,CVE-2021-3489,CVE-2021-3490,CVE-2021-3491 JIRA References: Sources used: openSUSE Leap 15.3 (src): kernel-azure-5.3.18-38.3.1, kernel-source-azure-5.3.18-38.3.1, kernel-syms-azure-5.3.18-38.3.1 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182552 https://bugzilla.suse.com/show_bug.cgi?id=1182552#c64 --- Comment #64 from Swamp Workflow Management <swamp@suse.de> --- openSUSE-SU-2021:1977-1: An update that solves 52 vulnerabilities and has 187 fixes is now available. Category: security (important) Bug References: 1055117,1065729,1087082,1113295,1133021,1152457,1152472,1152489,1153274,1154353,1155518,1156395,1160634,1164648,1167260,1167574,1167773,1168777,1168838,1169709,1171295,1173485,1174416,1174426,1175995,1176447,1176774,1177028,1177326,1177666,1178089,1178134,1178163,1178330,1178378,1178418,1179243,1179519,1179825,1179827,1179851,1180197,1180814,1180846,1181104,1181383,1181507,1181674,1181862,1182077,1182257,1182377,1182552,1182574,1182613,1182712,1182715,1182717,1182999,1183022,1183069,1183252,1183277,1183278,1183279,1183280,1183281,1183282,1183283,1183284,1183285,1183286,1183287,1183288,1183289,1183310,1183311,1183312,1183313,1183314,1183315,1183316,1183317,1183318,1183319,1183320,1183321,1183322,1183323,1183324,1183326,1183346,1183366,1183369,1183386,1183405,1183412,1183427,1183428,1183445,1183447,1183491,1183501,1183509,1183530,1183534,1183540,1183593,1183596,1183598,1183637,1183646,1183658,1183662,1183686,1183692,1183750,1183757,1183775,1183815,1183868,1183871,1183873,1183947,118397 6,1184074,1184081,1184082,1184120,1184167,1184168,1184170,1184171,1184192,1184193,1184194,1184196,1184197,1184198,1184199,1184208,1184209,1184211,1184217,1184218,1184219,1184220,1184224,1184264,1184386,1184388,1184391,1184393,1184436,1184485,1184514,1184585,1184611,1184615,1184650,1184710,1184724,1184728,1184730,1184731,1184736,1184737,1184738,1184740,1184741,1184742,1184769,1184811,1184855,1184934,1184942,1184943,1184955,1184969,1184984,1185010,1185113,1185233,1185269,1185428,1185491,1185495,1185549,1185550,1185558,1185573,1185581,1185586,1185587,1185606,1185640,1185641,1185642,1185645,1185670,1185680,1185703,1185725,1185736,1185758,1185796,1185840,1185857,1185898,1185899,1185911,1185938,1185950,1185980,1185988,1186009,1186061,1186111,1186118,1186219,1186285,1186320,1186349,1186352,1186353,1186354,1186355,1186356,1186357,1186401,1186408,1186439,1186441,1186479,1186484,1186498,1186501,1186512,1186681 CVE References: CVE-2019-18814,CVE-2019-19769,CVE-2020-24586,CVE-2020-24587,CVE-2020-24588,CVE-2020-25670,CVE-2020-25671,CVE-2020-25672,CVE-2020-25673,CVE-2020-26139,CVE-2020-26141,CVE-2020-26145,CVE-2020-26147,CVE-2020-27170,CVE-2020-27171,CVE-2020-27673,CVE-2020-27815,CVE-2020-35519,CVE-2020-36310,CVE-2020-36311,CVE-2020-36312,CVE-2020-36322,CVE-2021-20268,CVE-2021-23134,CVE-2021-27363,CVE-2021-27364,CVE-2021-27365,CVE-2021-28038,CVE-2021-28375,CVE-2021-28660,CVE-2021-28688,CVE-2021-28950,CVE-2021-28952,CVE-2021-28964,CVE-2021-28971,CVE-2021-28972,CVE-2021-29154,CVE-2021-29155,CVE-2021-29264,CVE-2021-29265,CVE-2021-29647,CVE-2021-29650,CVE-2021-30002,CVE-2021-32399,CVE-2021-33034,CVE-2021-33200,CVE-2021-3428,CVE-2021-3444,CVE-2021-3483,CVE-2021-3489,CVE-2021-3490,CVE-2021-3491 JIRA References: Sources used: openSUSE Leap 15.3 (src): kernel-64kb-5.3.18-59.5.2, kernel-debug-5.3.18-59.5.2, kernel-default-5.3.18-59.5.2, kernel-default-base-5.3.18-59.5.2.18.2.2, kernel-docs-5.3.18-59.5.2, kernel-kvmsmall-5.3.18-59.5.2, kernel-obs-build-5.3.18-59.5.1, kernel-obs-qa-5.3.18-59.5.1, kernel-preempt-5.3.18-59.5.2, kernel-source-5.3.18-59.5.2, kernel-syms-5.3.18-59.5.1, kernel-zfcpdump-5.3.18-59.5.2 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com