Bugzilla – Bug 1118689
32bit x86 4.19 4.20 5.0 5.1 5.2-rc pae and vanilla kernels randomly lockup or trigger reboot
Last modified: 2022-03-04 21:08:07 UTC
More info in forum thread: https://forums.opensuse.org/showthread.php/534078-Runs-only-with-the-recovery-version # lscpu Architecture: i686 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Thread(s) per core: 2 Core(s) per socket: 1 Socket(s): 1 Vendor ID: GenuineIntel CPU family: 15 Model: 4 Model name: Intel(R) Pentium(R) 4 CPU 3.00GHz Stepping: 3 CPU MHz: 2992.597 BogoMIPS: 5985.19 L1d cache: 16K L2 cache: 2048K Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pebs bts cpuid pni dtes64 monitor ds_cpl est cid cx16 xtpr # free total used free shared buff/cache available Mem: 2062696 279968 1120112 1660 662616 1551448 Swap: 530108 0 530108 # cat /proc/cmdline root=LABEL=osTWst80 ipv6.disable=1 net.ifnames=0 noresume vga=791 video=1024x768@60 video=1440x900@60 5 # uname -a Linux gx151 4.19.5-1-default #1 SMP Tue Nov 27 19:56:09 UTC 2018 (6210279) i686 i686 i386 GNU/Linux PC was working fine on 4.18.15 pae before upgrade to 20181204 that included 4.19.5 pae. With 4.19, lockups or random reboots would occur at any time, sometimes before completion of init, other times after running X for a while, sometimes while running in multi-user. So, I ran memtest for several hours without erros, then installed vanilla and default kernels. Vanilla rebooted virtually as soon as initrd loaded. Default seems to be working as well as 4.18.15-pae works at least so far through upgrade to 20181205. Attempts to catch clues from journal proved fruitless due to journal "file truncation".
I have a similar issue with Pentium 4 and Radeon RV370/RV380: kernel-pae-4.18.15-1.2.i686 works kernel-pae-4.19.x doesn't work: triggers reboot, almost immediately at startup Workarounds: kernel option: nomodeset (system boots up, but Xorg doesn't work) kernel option: nopti (system boots and is usable, but no protection against meltdown) I also tried default kernel 4.19.x: works. Note: The graphics chip is reported either as RV370 (lspci) or RV380 (dmesg) kernel git bisect from 4.18 to 4.19: 7757d607c6b31867777de42e1fb0210b9c5d8b70 is the first bad commit commit 7757d607c6b31867777de42e1fb0210b9c5d8b70 Author: Joerg Roedel <jroedel@suse.de> Date: Wed Jul 18 11:41:14 2018 +0200 x86/pti: Allow CONFIG_PAGE_TABLE_ISOLATION for x86_32 Allow PTI to be compiled on x86_32. Signed-off-by: Joerg Roedel <jroedel@suse.de> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Tested-by: Pavel Machek <pavel@ucw.cz> Cc: "H . Peter Anvin" <hpa@zytor.com> Cc: linux-mm@kvack.org Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Andy Lutomirski <luto@kernel.org> Cc: Dave Hansen <dave.hansen@intel.com> Cc: Josh Poimboeuf <jpoimboe@redhat.com> Cc: Juergen Gross <jgross@suse.com> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Borislav Petkov <bp@alien8.de> Cc: Jiri Kosina <jkosina@suse.cz> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com> Cc: Brian Gerst <brgerst@gmail.com> Cc: David Laight <David.Laight@aculab.com> Cc: Denys Vlasenko <dvlasenk@redhat.com> Cc: Eduardo Valentin <eduval@amazon.com> Cc: Greg KH <gregkh@linuxfoundation.org> Cc: Will Deacon <will.deacon@arm.com> Cc: aliguori@amazon.com Cc: daniel.gruss@iaik.tugraz.at Cc: hughd@google.com Cc: keescook@google.com Cc: Andrea Arcangeli <aarcange@redhat.com> Cc: Waiman Long <llong@redhat.com> Cc: "David H . Gutteridge" <dhgutteridge@sympatico.ca> Cc: joro@8bytes.org Link: https://lkml.kernel.org/r/1531906876-13451-38-git-send-email-joro@8bytes.org :040000 040000 dbab9a897d534d7b14f900f0c6779b6848833892 f0674017544bc95fafa431d1e638f994eca37b51 M security
Created attachment 793388 [details] cpuinfo
Created attachment 793389 [details] dmesg of kernel with option nopti set
Created attachment 793390 [details] gcc version info
Created attachment 793391 [details] iomem as root
Created attachment 793392 [details] ioports as root
Created attachment 793393 [details] lcpci -vvv as root
Created attachment 793394 [details] modules this is all with working kernel / nopti option!
I have to admit that during bisecting I noticed 2 internal compiler errors that just went away after typing make / make bzImage / make modules again. And I noticed some freezes during compilation. Otherwise the machine seems fine; I didn't notice similar problems before. I did the bisecting/compiling with kernel_4.18.15-1-pae
Created attachment 793396 [details] lscpu for easier comparison with original report
additional workaround: disable graphical boot manager in yast2
Created attachment 793426 [details] oops #1, via serial connection Linux version 4.19.12-1.gc634493-pae (geeko@buildhost) (gcc version 8.2.1 20181108 [gcc-8-branch revision 265914] (SUSE Linux)) #1 SMP PREEMPT Sat Dec 22 08:59:36 UTC 2018 (c634493)
Created attachment 793427 [details] oops #2
Created attachment 793428 [details] oops #3
Created attachment 793429 [details] oops #4
Created attachment 793430 [details] oops #5
Created attachment 793431 [details] oops #6, after installing kernel debug package
Created attachment 793432 [details] oops #7
Created attachment 793433 [details] oops #8
workaround: disabling Hyper Threading in BIOS helps (only 1 CPU available) plymouth.enable=0 at kernel command line doesn't help
4.19.11 pae boots to multi-user, but there's no keyboard trying to login. CAD produces many screens of code dumps, then lockup.
kernel-pae-4.20.0-3.1.ga24f9ea failed to get halfway through init before the code dumps and automatic reboot. kernel-default-4.19.11 works normally.
Bug still present with kernel-pae-4.20.1-1.1.g5978cc8.i686 kernel-pae-5.0.rc1-1.1.ga56baa9.i686 here it only happens with hyperthreading enabled (>1 cpu) && graphical boot / vesafb && pti && kernel based modesetting During my tests once one of the last lines shown before lockup was: Console: switching to colour frame buffer device 160x64
bug still exists in kernel-pae-4.20.2-1.1.g036c5c2.i686
bug exists also in: kernel-pae-5.0.rc2-1.1.g879eb5c.i686 kernel-pae-4.20.2-3.1.g036c5c2.i686
On the comment 0 host with 4.19.12 pae I was able to boot, open Plasma and close Plasma without crashing or locking up, but it did go crazy and eventually reboot immediately upon attempting to run an alias that mounts 4 noauto fstab nfs entries. I had already noticed the alias do this at least with the prior 4.19.11 pae kernel if not earlier. The 4.20.2 pae kernel didn't even get halfway through init before going haywire.
bug exists also in: kernel-pae-5.0.rc4-1.1.g8e6abff.i686 kernel-pae-4.20.5-3.1.g0a5bbbc.i686
Created attachment 795781 [details] dmesg output with error: trying to bind memory to uninitialized GART ! 4.20.5-3.g0a5bbbc-pae booted once to usable desktop, however with this: [ 108.453874] trying to bind memory to uninitialized GART ! [ 108.470492] WARNING: CPU: 1 PID: 2716 at drivers/gpu/drm/radeon/radeon_gart.c:296 radeon_gart_bind+0xe5/0xf0 [radeon] showing up multiple times in dmesg output.
Debian Buster's 686-pae 4.19.16 apparently has acquired this bug (on host gx280), triggered instantly by attempting NFS mount, fixed by purging the pae and installing the plain 686 kernel. Fedora 28's 4.20.6 shows pae among its flags but has exhibited no such problem as yet.
also affected: kernel-pae-5.0.rc7-1.1.gb094e66.i686 kernel-pae-4.20.10-2.1.g4c06520.i686
@Felix: 1. could you check if Debian works with pae kernel and the nopti kernel option workaround? 2. could you check if Debian works with pae kernel and "non-graphical" bootloader? (and no other workaround) 3. could you check if Debian works with pae kernel when only 1 CPU enabled / Hyperthreading disabled (in BIOS)? (and no other workaround) could you try to reproduce the problem with fedora: 1. use "graphical" bootloader (I don't know the official definition) 2. check that pti is enabled (check log/dmesg) 3. check that 2nd CPU is enabled 4. check for vesafb entries in dmesg
Virtually all MBR Gnu/Linux "booting" here is via openSUSE 13.1's grub-0.97.194. Plymouth is either not installed, or cmdline option plymouth.enable=0 is applied. (All UEFI booting here is also non-graphical.) # cat /proc/cmdline root=LABEL=f28p22 ro audit=0 ipv6.disable=1 net.ifnames=0 selinux=0 plymouth.enable=0 noresume vga=791 video=1440x900@60 3 # uname -a Linux gx280 4.20.6-100.fc28.i686 #1 SMP Thu Jan 31 15:54:55 UTC 2019 i686 i686 i386 GNU/Linux # dmesg | egrep -i 'pti|vesafb' [ 0.000000] DMI: Dell Inc. OptiPlex GX280 /0G5611, BIOS A08 03/03/2006 [ 2.242347] vesafb: mode is 1024x768x16, linelength=2048, pages=4 [ 2.242357] vesafb: scrolling: redraw [ 2.242364] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0 [ 2.242389] vesafb: framebuffer at 0xc0000000, mapped to 0x(ptrval), using 3072k, total 7872k intel_rng: RNG, try using the 'no_fwh_detect' option. [ 41.869537] EXT4-fs (sda3): Mount option "noacl" will be removed by 3.5 Both nopti and HT disabled produced normal functionality with Buster's 4.19.0-2-i686-pae (4.19.16-1) on host gx280. Sessions were about 6 minutes long including startx/TDE and opening Firefox. I saved the Debian sessions' screens via "script" command to files in case you want more detail.
@Felix: plymouth.enable=0 didn't help on my side, too. (comment 20) With "graphical boot" I mean the boot menu is in high-resolution. You can switch to textmode in Yast -> system -> bootloader -> tab: kernel parameter -> box: [] Use graphical console / Graphik-Konsole benutzen UnSelecting the bootloader "graphical console" is a sufficient workaround on my side. To check if PTI is enabled on your fedora installation you have to look for a line Kernel/User page tables isolation: enabled in dmesg output. According your description your CPU supports 64bit, too. Did you try a 64bit operating system?
(In reply to Andreas Stenglein from comment #33) > With "graphical boot" I mean the boot menu is in high-resolution. You can > switch to textmode in Yast -> system -> bootloader -> tab: kernel parameter > -> box: [] Use graphical console / Graphik-Konsole benutzen > UnSelecting the bootloader "graphical console" is a sufficient workaround on > my side. I'm still not sure what you want from me here. Ever since Grub as an option was terminated, the only time I see a YaST Bootloader screen on my own hardware is during installation, where, except on UEFI systems, I customarily select to install no bootloader. With the exception of UEFI, all Gnu Linux operating systems here are booted using an openSUSE Grub 0.97 version, usually 0.97.194. > To check if PTI is enabled on your fedora installation you have to look for > a line > Kernel/User page tables isolation: enabled > in dmesg output. dmesg | grep -i 'page table' and dmesg | grep -i isola both return null with 4.20.6-100.fc28.i686 > According your description your CPU supports 64bit, too. > Did you try a 64bit operating system? I don't know how to answer this. I have hundreds of bootable operating system installations. Whether half or more are using 64bit kernels I have no idea. I didn't do my first 64bit installation on any of my own PCs until around the time openSUSE announced there would be no 32bit Leap. I think I have at most 4 PCs with both 32bit and 64bit installed, more than I care to have already, so I intend to create no more purposely. Comment #29 & #32 host gx280 was selected for the test that resulted in comment #29 because it has the fastest CPU clock on hardware on which I have running 32bit versions of openSUSE and Fedora and Debian, along with a gfxchip supported by a KMS Xorg driver, not because of its CPU's optimal arch. None of my 64bit installations exhibit this bug.
also affected: kernel-pae-5.0.rc8-1.1.g4ddf057.i686 kernel-pae-4.20.13-1.1.gfb7c4a5.i686
(In reply to Felix Miata from comment #34) > (In reply to Andreas Stenglein from comment #33) > > With "graphical boot" I mean the boot menu is in high-resolution. You can > > switch to textmode in Yast -> system -> bootloader -> tab: kernel parameter > > -> box: [] Use graphical console / Graphik-Konsole benutzen > > UnSelecting the bootloader "graphical console" is a sufficient workaround on > > my side. > > I'm still not sure what you want from me here. Ever since Grub as an option > was terminated, the only time I see a YaST Bootloader screen on my own > hardware is during installation, where, except on UEFI systems, I > customarily select to install no bootloader. With the exception of UEFI, all > Gnu Linux operating systems here are booted using an openSUSE Grub 0.97 > version, usually 0.97.194. I don't mean some "YaST Bootloader screen" that shows up during boot, but the configuration of the bootloader inside YaST: You have to start the OS you usually configure the bootloader with, and start YaST using the menu, or by typing /usr/bin/xdg-su -c /sbin/yast2 into an xterm, then find the setting as mentioned above. > > To check if PTI is enabled on your fedora installation you have to look for > > a line > > Kernel/User page tables isolation: enabled > > in dmesg output. > > dmesg | grep -i 'page table' and dmesg | grep -i isola both return null with > 4.20.6-100.fc28.i686 So PTI seems not enabled on your fedora(kernel). To check if fedora is in principle also affected from the bug you would have to enable PTI in your fedora(kernel) or use fedoras pae-kernel, if available; or compile yourself. > > According your description your CPU supports 64bit, too. > > Did you try a 64bit operating system? > > I don't know how to answer this. I have hundreds of bootable operating > system installations. Whether half or more are using 64bit kernels I have no Until now I had the opinion you have one system with different partitions and operating systems on them. And the bug only occurs on your machine with its special components and mine (both with Pentium 4 CPU, both with AMD Radeon graphics), and nobody else cares since this setup is so unusual nowadays... > idea. I didn't do my first 64bit installation on any of my own PCs until > around the time openSUSE announced there would be no 32bit Leap. I think I > have at most 4 PCs with both 32bit and 64bit installed, more than I care to > have already, so I intend to create no more purposely. Comment #29 & #32 > host gx280 was selected for the test that resulted in comment #29 because it > has the fastest CPU clock on hardware on which I have running 32bit versions > of openSUSE and Fedora and Debian, along with a gfxchip supported by a KMS > Xorg driver, not because of its CPU's optimal arch. None of my 64bit > installations exhibit this bug. So in reality you have 4 different machines which all exhibit this bug: provided that a 32bit pae kernel is used, PTI is enabled, kernel-modeset is active and Hyperthreading is enabled, right? Do you have a box with a real multicore CPU, where you can switch Hyperthreading off and still have more threads in parallel: for checking if Hyperthreading is the culprit or just using a multi core system.
Created attachment 798612 [details] inxi -bxx output
(In reply to Andreas Stenglein from comment #36) I think I'm lost as to why the subject of YaST Bootloader is in this discussion. I use YaST relatively little for anything, and never on MBR installations for bootloader except as it is present in in the installation system. I purposely have nothing I know of, other than Grub Legacy Gfxboot, that pertains to graphical boot installed anywhere it's not forced. I like my boots to have no resemblance to booting Windows, seeing that something seems to actually be happening via the kernel's nice legible boldish framebuffer font, even though it's usually too fleeting to read in real time. I don't compile anything, or use OBS other than for installing and running various packages others have built there. I do have installations other than Fedora and openSUSE, but except for some Mandrake and its progeny, are all Debian or Debian-based. I do have spare rv370 and rv380 ATI PCIe cards that might be pressed into service to help resolve this. > So in reality you have 4 different machines which all exhibit this bug: > provided that a 32bit pae kernel is used, PTI is enabled, kernel-modeset is > active and Hyperthreading is enabled, right? I'm not sure, due to lack of inventory of what has PTI enabled. Otherwise, true. > Do you have a box with a real multicore CPU, where you can switch > Hyperthreading off and still have more threads in parallel: for checking if > Hyperthreading is the culprit or just using a multi core system. I'm pretty sure every openSUSE here newer than 13.2 that's also genuinely multicore has been switched to 64 bit. Would it help if I tried Kernel:/stable/standard/i686/kernel-pae in a 13.2 or older installation, assuming it's possible? One of those I /might/ be able to locate.
> > So in reality you have 4 different machines which all exhibit this bug: > > provided that a 32bit pae kernel is used, PTI is enabled, kernel-modeset is > > active and Hyperthreading is enabled, right? > I'm not sure, due to lack of inventory of what has PTI enabled. Otherwise, > true. I'm not sure about the 4 "machines" part either. I see here I've apparently only typed 2 hostnames. All my machines are multiboot, but several, including comment 0 host gx151, have only openSUSE distros installed. I noticed commonality between comment 0 host gx151's X600 and comment 37 attachment, rv370 Radeon, so I took the X600 out of gx151 and tried to boot its pae kernel. It wasted little time filling the screen with debris and halting.
also affected: kernel-pae-5.0.0-4.1.g6bc6477.i686
(In reply to Felix Miata from comment #39) > I noticed commonality between comment 0 host gx151's X600 and comment 37 > attachment, rv370 Radeon, so I took the X600 out of gx151 and tried to boot > its pae kernel. It wasted little time filling the screen with debris and > halting. Am I right, you used some other graphics card and the problem persists. Whats the type of 2nd graphics card that shows the problem, too?
I uninstalled gfxboot and the problem persists. However I use grub2 that already contains framebuffer/graphics console. In /etc/default/grub I changed the line GRUB_GFXMODE=auto to some configurations and run grub2-mkconfig -o /boot/grub2/grub.cfg and rebooted the machine. (one could change the setting using YAST also) 640x480 -> works 800x600x24 -> works 1024x768x16 -> as far as I remember it bootet once, than 3x lockup 1280x1024x8 -> works 1280x1024x16 -> lockup auto -> lockup (1280x1024x32 gets chosen as shown by grub console)
(In reply to Andreas Stenglein from comment #41) > Whats the type of 2nd graphics card that shows the problem, too? Comment 0 Prescott host gx151: Normal use: # inxi -Gxx Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RV370 [Radeon X600/X600 SE] driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:5b62 ... Temporary change for purpose of comment 39: # inxi -Gxx Graphics: Device-1: Intel 82945G/GZ Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2772 ... Comment 29 Northwood host gx280: # inxi -Gxx Graphics: Device-1: Intel 82915G/GV/910GL Integrated Graphics driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2582 ...
(In reply to Andreas Stenglein from comment #42) Except on my two PCs with UEFI enabled, virtually all booting here is via openSUSE Grub Legacy Gfxboot. Most stanzas have these cmdline inclusions: vga=791 video=1440x900@60
Last couple of gx151 TW20190307 boots with PAE 4.20.13 with vga= and video= omitted from cmdline and hyperthreading disabled failed to produce this bug in about an hour's time. I then switched hyperthreading back on. That was well over an hour ago, and still this bug has remained apparently absent while digressing through Plasma trouble: https://lists.opensuse.org/opensuse-support/2019-03/msg00075.html
also affected: kernel-pae-5.2.rc3-3.1.gb4eda05.i686
(In reply to Andreas Stenglein from comment #46) > also affected: > kernel-pae-5.2.rc3-3.1.gb4eda05.i686 Does blacklisting the radeon driver make the problem disappear too? It looks like radeon does not play with PTI well -- the reason is unknown to date.
*** Bug 1120186 has been marked as a duplicate of this bug. ***
It looks like there is some bad interaction between the PTI code and the DRM subsystem. I'll try to reproduce it myself next week.
Some of the CR2s are interesting: $ perl -e 'print pack("H*", "0a29286f"), "\n"' )(o $ perl -e 'print pack("H*", "6d006576"), "\n"' mev $ perl -e 'print pack("H*", "4f52445b"), "\n"' ORD[ It looks like pieces of source codes which corrupted that memory. I have no idea where they got from.
For reproduction please refer to https://bugzilla.suse.com/show_bug.cgi?id=1120186#c3 where I described how to use openQA to reproduce. Also we could use openQA to crosscheck any potential fixes.
(In reply to Jiri Slaby from comment #47) > (In reply to Andreas Stenglein from comment #46) > > also affected: > > kernel-pae-5.2.rc3-3.1.gb4eda05.i686 > > Does blacklisting the radeon driver make the problem disappear too? It looks > like radeon does not play with PTI well -- the reason is unknown to date. Comment 39 suggests this applies to Intel GFX as well as Radeon.
(In reply to Jiri Slaby from comment #47) > Does blacklisting the radeon driver make the problem disappear too? It looks > like radeon does not play with PTI well -- the reason is unknown to date. yes, blacklisting radeon kernel driver using modprobe.blacklist=radeon in kernel command line makes the problem disappear: system booted at least once without oops. I tried this with kernel 5.1.9-5.ge68f829-pae
also affected: kernel-pae-5.2.rc4-2.1.gad82a9a.i686 kernel-pae-5.1.9-5.1.ge68f829.i686 Maybe this is also of interest: During start-up, before you can enter the bios configuration or grub gets loaded, there is a low resolution "intel inside Pentium 4 HT" graphic splash screen shown.
Created attachment 807684 [details] journalctl -b -1 on host gx151 with TW 5.1.7 and i945G gfx Using host gx151 and X600 Radeon I installed kernel 5.1.7 pae while booted to 5.1.7 default. It went haywire most of the way through boot to 5.1.7 pae, so I pulled the plug, removed the Radeon, and tried booting using the onboard Intel 82945G/GZ Integrated Graphics chip ID: 8086:2772. Using 5.1.7 pae it consistently locks up shortly after systemd-journald[422]: Time spent on flushing to /var.
Can you please try to boot the systems with 'nohugeiomap' and report whether the problem disappears? Thanks!
(In reply to Joerg Roedel from comment #56) > Can you please try to boot the systems with 'nohugeiomap' and report whether > the problem disappears? Yes, with nohugeiomap the problem disappears on my system. I booted the system three times: no oops. I tried this with kernel 5.1.9-5.ge68f829-pae
Seems to be OK with 5.1.9 and nohugeiomap on host gx151, uptime 37 minutes so far trying to get upstream Firefox to not complain about missing libatomic.so.1.
typo: s/5.1.9/5.1.7/
(In reply to Andreas Stenglein from comment #57) > (In reply to Joerg Roedel from comment #56) > > Can you please try to boot the systems with 'nohugeiomap' and report whether > > the problem disappears? > Yes, with nohugeiomap the problem disappears on my system. > I booted the system three times: no oops. > I tried this with kernel 5.1.9-5.ge68f829-pae Thanks for testing, I think I know where the problem is now. Do you guys prefer a test-kernel with a fix or can I just attach a patch here for testing once I have something?
(In reply to Joerg Roedel from comment #60) > Do you guys prefer a test-kernel with a fix I do.
Kernel with potential fix is currently building here: https://build.opensuse.org/project/monitor/home:joro:bsc1118689 Please test it when the build is finished and report back.
Created attachment 807836 [details] Potential Fix Patch Potential Fix - If testing is successful I will send it upstream.
Build is almost done. Packages for kernel-pae can be found here: https://build.opensuse.org/package/binaries/home:joro:bsc1118689/kernel-pae/standard
Negative: kernel-pae-5.1.11-1.1.g32b9efd.i686.rpm is no improvement on comment 0 host gx151. Some messages (not in order or complete): _raw_spin_lock preempt_schedule_common pgd_free watchdog: BUG: soft lockup CPU#1 stuck for 22s do_fast_syscall_32 sort_range EIP: multi_cpu_stop EIP: native_queued_spin_lock_slowpath rewind_stack_do_exit
(In reply to Joerg Roedel from comment #64) > https://build.opensuse.org/package/binaries/home:joro:bsc1118689/kernel-pae/ > standard With this kernel I still get an oops, but now it looks always the same: 3 times same oops Workarounds nohugeiomap and nopti still work. Workaround modprobe.blacklist=radeon doesn't work with this kernel.
Created attachment 808032 [details] photo of oops with first test kernel this also occurs with modprobe.blacklist=radeon
(In reply to Andreas Stenglein from comment #66) > (In reply to Joerg Roedel from comment #64) > > https://build.opensuse.org/package/binaries/home:joro:bsc1118689/kernel-pae/ > > standard > > With this kernel I still get an oops, but now it looks always the same: 3 > times same oops > Workarounds nohugeiomap and nopti still work. > Workaround modprobe.blacklist=radeon doesn't work with this kernel. Thanks for testing. I am looking again into the problem this week.
Here is an update from my side. I tried to reproduce the problem on different hosts, but didn't succeed so far. I also tried on a P4 (but without HT support). Meanwhile I verified my patch with some more debug code and confirmed that it does what it should do. This probably means there is another issue besides the one fixed with my patch. I am further looking into this.
Created attachment 810336 [details] Updated Version of Potential Fix After some more debugging with a test machine I found another problem in the code which prevented the previous fix from working. Here is the updated fix patch. Kernel packages with this fix included are currently building here: https://build.opensuse.org/project/monitor/home:joro:bsc1118689 Can you please test the new kernel-pae packages once they are ready? Thanks!
Created attachment 810338 [details] Updated Potential Fix Sorry, uploaded wrong file. Here is the updated fix.
PAE Kernel is built and can be downloaded here: https://download.opensuse.org/repositories/home:/joro:/bsc1118689/standard/i686/
http://download.opensuse.org/repositories/home:/joro:/bsc1118689/standard/i686/kernel-pae-5.2.0-1.1.ga58fb14.i686.rpm on comment 0 host gx151 produced no obvious errors during boot. # uname -a Linux gx151 5.2.0-1.ga58fb14-pae #1 SMP Fri Jul 12 15:38:59 UTC 2019 (a58fb14) i686 i686 i386 GNU/Linux # dmesg | egrep -i 'Failed|Oops' [ 3.602775] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument [ 4.128312] scsi_dh_alua: module verification failed: signature and/or required key missing - tainting kernel [ 19.083048] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument Much better! :)
Unfortunately this kernel 5.2.0-1.ga58fb14-pae doesn't fix the problem. However the workarounds nohugeiomap nopti modprobe.blacklist=radeon work with this kernel.
(In reply to Andreas Stenglein from comment #74) > Unfortunately this kernel 5.2.0-1.ga58fb14-pae doesn't fix the problem. > However the workarounds > nohugeiomap > nopti > modprobe.blacklist=radeon > work with this kernel. So you still see spontaneous reboots with this kernel? Or is there a different kind of problem you see with it?
Created attachment 810376 [details] screenshot of Plasma running 5.2.0-1.ga58fb14-pae I had it up 8+ hours before putting the station to better use.
(In reply to Joerg Roedel from comment #75) > (In reply to Andreas Stenglein from comment #74) > > Unfortunately this kernel 5.2.0-1.ga58fb14-pae doesn't fix the problem. > > However the workarounds > > nohugeiomap > > nopti > > modprobe.blacklist=radeon > > work with this kernel. > > So you still see spontaneous reboots with this kernel? Or is there a > different kind of problem you see with it? With previous/vanilla pae kernels I almost ever got lockup/oops and most of the time I could see something going on on the screen for some time. Sometimes screen was black. With this kernel when the lockup occurs the screen goes black, nothing is visible. I tried about 10 times and can't remember seeing something going on on the screen after the lockup/oops. Once it was possible to switch the NumLock LED after lockup, and once both CapsLock and ScrollLock LEDs began blinking after some time; both happened with black screen. And this kernel booted twice (out of about 10 times) with radeon/drm error, but working desktop and software GL renderer. [ 16.601558] [drm:r100_ib_test [radeon]] *ERROR* radeon: ib test failed (scratch(0x15E8)=0xCAFEDEAD) [ 16.610832] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-22). [ 16.620090] [drm:radeon_device_init [radeon]] *ERROR* ib ring test failed (-22). I'm going to attach full dmesg output. I have to check if this kernel reboots automatically after some time.
Created attachment 810377 [details] dmesg of patched kernel 5.2.0-1.ga58fb14-pae with drm/radeon error
Created attachment 810378 [details] dmesg of patched kernel 5.2.0-1.ga58fb14-pae with drm/radeon error, occurence #2
I did some more tests. The patched kernel also sometimes reboots automatically. This happens during boot. If the lockup occurs, the screen goes black. Sometimes I pressed/long pressed the power button to restart the machine after some waiting. However I have to admit that the patched kernel 5.2.0-1.ga58fb14-pae is an improvement: I had the impression that the more I rebooted, the more it "worked", but then with some next reboot, it locked up / rebooted automatically during boot. Of 10 bootups it was possible at least 5 times to boot to a somewhat working desktop, however with errors and call traces in the dmesg log. One time I even didn't find a regarding error in the dmesg. I'm going to attach dmesg logs. The original kernel 5.2.0-10.gb11a4ae-pae didn't boot to a working desktop after at least 5 tries. With original kernel you sometimes can watch the oops and traces on the screen, however its to fast to really follow. Sometimes the screen goes black. After some time it automatically reboots; as I remember I sometimes also had to press/long press the power button to get it restarted.
Created attachment 810379 [details] dmesg of patched kernel 5.2.0-1.ga58fb14-pae with radeon and gart problem
Created attachment 810380 [details] dmesg of patched kernel 5.2.0-1.ga58fb14-pae with call trace but somewhat working machine
Created attachment 810381 [details] dmesg of patched kernel 5.2.0-1.ga58fb14-pae with ERROR but somewhat working machine
Created attachment 810382 [details] dmesg of patched kernel 5.2.0-1.ga58fb14-pae with unknown symbol -2 but somewhat working machine
(In reply to Andreas Stenglein from comment #80) > I did some more tests. > The patched kernel also sometimes reboots automatically. This happens during > boot. But the same kernel with 'nopti' booted works every time?
(In reply to Joerg Roedel from comment #85) > (In reply to Andreas Stenglein from comment #80) > > I did some more tests. > > The patched kernel also sometimes reboots automatically. This happens during > > boot. > > But the same kernel with 'nopti' booted works every time? I can try this on Thursday evening; I'm going to try 10 times booting with nopti, if you think it's necessary I can try more. Usually now I'm using the nohugeiomap workaround if I want to boot to a working system, since this has the least impact on features.
Hi Andreas, (In reply to Andreas Stenglein from comment #86) > I can try this on Thursday evening; I'm going to try 10 times booting with > nopti, if you think it's necessary I can try more. > Usually now I'm using the nohugeiomap workaround if I want to boot to a > working system, since this has the least impact on features. Upstream review found another bug in the patch. I fixed it and re-built the kernel-packages. Can you please try the latest kernel-pae from https://download.opensuse.org/repositories/home:/joro:/bsc1118689/standard/i686/ Thanks a lot!
(In reply to Joerg Roedel from comment #87) > Upstream review found another bug in the patch. I fixed it and re-built the > kernel-packages. Can you please try the latest kernel-pae from Hello Jörg, I booted kernel 5.2.1-1.g121429f-pae 5 times without finding oops in dmesg. Then I did zypper dup, without issues. Booted another 5 times without noticing issues. It looks like you fixed the bug for me, so from my side you can close the bug when the patch is in the opensuse kernel. Thanks a lot! If I still should try with the nopti option, let me know. Otherwise I think this test isn't necessary any more.
Fixes are upstream in Liunx v5.2: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=51b75b5b563a2637f9d8dc5bd02a31b2ff9e5ea0 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8e998fc24de47c55b47a887f6c95ab91acd4a720 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3f8fd02b1bf1d7ba964485a56f2f4b53ae88c167 Unfortunatly they did not get picked up by stable, so I submitted them manually for stable today.
Stable kernel 5.2.9 contains the fixes and got released. Once it is picked up by Tumbleweed the issue will be fixed there as well.
(In reply to Joerg Roedel from comment #90) > Stable kernel 5.2.9 contains the fixes and got released. Once it is picked > up by Tumbleweed the issue will be fixed there as well. 5.2.9 is in TW already.
This is an autogenerated message for OBS integration: This bug (1118689) was mentioned in https://build.opensuse.org/request/show/731541 15.0 / kernel-source
This is an autogenerated message for OBS integration: This bug (1118689) was mentioned in https://build.opensuse.org/request/show/732033 15.1 / kernel-source
SUSE-SU-2019:2414-1: An update that solves 39 vulnerabilities and has 180 fixes is now available. Category: security (important) Bug References: 1047238,1050911,1051510,1054914,1055117,1056686,1060662,1061840,1061843,1064597,1064701,1065600,1065729,1066369,1071009,1071306,1078248,1082555,1085030,1085536,1085539,1086103,1087092,1090734,1091171,1093205,1102097,1104902,1106061,1106284,1106434,1108382,1112894,1112899,1112902,1112903,1112905,1112906,1112907,1113722,1114279,1114542,1118689,1119086,1120876,1120902,1120937,1123105,1123959,1124370,1129424,1129519,1129664,1131107,1131281,1131565,1133021,1134291,1134881,1134882,1135219,1135642,1135897,1136261,1137811,1137884,1138539,1139020,1139021,1139101,1139500,1140012,1140426,1140487,1141450,1141543,1141554,1142019,1142076,1142109,1142117,1142118,1142119,1142496,1142541,1142635,1142685,1142701,1142857,1143300,1143466,1143765,1143841,1143843,1144123,1144333,1144474,1144518,1144718,1144813,1144880,1144886,1144912,1144920,1144979,1145010,1145051,1145059,1145189,1145235,1145300,1145302,1145388,1145389,1145390,1145391,1145392,1145393,1145394,1145395,1145396,1145397,1145408,1145409,1145661,1145678,1145687,1145920,1145922,1145934,1145937,1145940,1145941,1145942,1146074,1146084,1146163,1146285,1146346,1146351,1146352,1146361,1146376,1146378,1146381,1146391,1146399,1146413,1146425,1146512,1146514,1146516,1146519,1146524,1146526,1146529,1146531,1146543,1146547,1146550,1146575,1146589,1146678,1146938,1148031,1148032,1148033,1148034,1148035,1148093,1148133,1148192,1148196,1148198,1148202,1148303,1148363,1148379,1148394,1148527,1148574,1148616,1148617,1148619,1148859,1148868,1149053,1149083,1149104,1149105,1149106,1149197,1149214,1149224,1149325,1149376,1149413,1149418,1149424,1149522,1149527,1149539,1149552,1149591,1149602,1149612,1149626,1149652,1149713,1149940,1149976,1150025,1150033,1150112,1150562,1150727,1150860,1150861,1150933 CVE References: CVE-2017-18551,CVE-2018-20976,CVE-2018-21008,CVE-2019-10207,CVE-2019-14814,CVE-2019-14815,CVE-2019-14816,CVE-2019-14835,CVE-2019-15030,CVE-2019-15031,CVE-2019-15090,CVE-2019-15098,CVE-2019-15117,CVE-2019-15118,CVE-2019-15211,CVE-2019-15212,CVE-2019-15214,CVE-2019-15215,CVE-2019-15216,CVE-2019-15217,CVE-2019-15218,CVE-2019-15219,CVE-2019-15220,CVE-2019-15221,CVE-2019-15222,CVE-2019-15239,CVE-2019-15290,CVE-2019-15292,CVE-2019-15538,CVE-2019-15666,CVE-2019-15902,CVE-2019-15917,CVE-2019-15919,CVE-2019-15920,CVE-2019-15921,CVE-2019-15924,CVE-2019-15926,CVE-2019-15927,CVE-2019-9456 Sources used: SUSE Linux Enterprise Module for Live Patching 15 (src): kernel-default-4.12.14-150.35.1, kernel-livepatch-SLE15_Update_14-1-1.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.
SUSE-SU-2019:2412-1: An update that solves 40 vulnerabilities and has 184 fixes is now available. Category: security (important) Bug References: 1047238,1050911,1051510,1054914,1055117,1056686,1060662,1061840,1061843,1064597,1064701,1065600,1065729,1066369,1071009,1071306,1078248,1082555,1085030,1085536,1085539,1086103,1087092,1090734,1091171,1093205,1102097,1104902,1106061,1106284,1106434,1108382,1112178,1112894,1112899,1112902,1112903,1112905,1112906,1112907,1113722,1114279,1114542,1118689,1119086,1120876,1120902,1120937,1123105,1123959,1124370,1129424,1129519,1129664,1131107,1131281,1131565,1133021,1134291,1134881,1134882,1135219,1135642,1135897,1136261,1137069,1137884,1138539,1139020,1139021,1139101,1139500,1140012,1140426,1140487,1141013,1141450,1141543,1141554,1142019,1142076,1142109,1142117,1142118,1142119,1142496,1142541,1142635,1142685,1142701,1142857,1143300,1143466,1143765,1143841,1143843,1144123,1144333,1144474,1144518,1144718,1144813,1144880,1144886,1144912,1144920,1144979,1145010,1145024,1145051,1145059,1145189,1145235,1145300,1145302,1145388,1145389,1145390,1145391,1145392,1145393,1145394,1145395,1145396,1145397,1145408,1145409,1145661,1145678,1145687,1145920,1145922,1145934,1145937,1145940,1145941,1145942,1146074,1146084,1146163,1146285,1146346,1146351,1146352,1146361,1146368,1146376,1146378,1146381,1146391,1146399,1146413,1146425,1146516,1146519,1146524,1146526,1146529,1146531,1146543,1146547,1146550,1146575,1146589,1146678,1146938,1148031,1148032,1148033,1148034,1148035,1148093,1148133,1148192,1148196,1148198,1148202,1148303,1148363,1148379,1148394,1148527,1148574,1148616,1148617,1148619,1148698,1148859,1148868,1149053,1149083,1149104,1149105,1149106,1149197,1149214,1149224,1149325,1149376,1149413,1149418,1149424,1149522,1149527,1149539,1149552,1149591,1149602,1149612,1149626,1149652,1149713,1149940,1149959,1149963,1149976,1150025,1150033,1150112,1150562,1150727,1150860,1150861,1150933 CVE References: CVE-2017-18551,CVE-2018-20976,CVE-2018-21008,CVE-2019-10207,CVE-2019-14814,CVE-2019-14815,CVE-2019-14816,CVE-2019-14835,CVE-2019-15030,CVE-2019-15031,CVE-2019-15090,CVE-2019-15098,CVE-2019-15099,CVE-2019-15117,CVE-2019-15118,CVE-2019-15211,CVE-2019-15212,CVE-2019-15214,CVE-2019-15215,CVE-2019-15216,CVE-2019-15217,CVE-2019-15218,CVE-2019-15219,CVE-2019-15220,CVE-2019-15221,CVE-2019-15222,CVE-2019-15239,CVE-2019-15290,CVE-2019-15292,CVE-2019-15538,CVE-2019-15666,CVE-2019-15902,CVE-2019-15917,CVE-2019-15919,CVE-2019-15920,CVE-2019-15921,CVE-2019-15924,CVE-2019-15926,CVE-2019-15927,CVE-2019-9456 Sources used: SUSE Linux Enterprise Workstation Extension 12-SP4 (src): kernel-default-4.12.14-95.32.1 SUSE Linux Enterprise Software Development Kit 12-SP4 (src): kernel-docs-4.12.14-95.32.1, kernel-obs-build-4.12.14-95.32.1 SUSE Linux Enterprise Server 12-SP4 (src): kernel-default-4.12.14-95.32.1, kernel-source-4.12.14-95.32.1, kernel-syms-4.12.14-95.32.1 SUSE Linux Enterprise High Availability 12-SP4 (src): kernel-default-4.12.14-95.32.1 SUSE Linux Enterprise Desktop 12-SP4 (src): kernel-default-4.12.14-95.32.1, kernel-source-4.12.14-95.32.1, kernel-syms-4.12.14-95.32.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-2019:2412-1: An update that solves 40 vulnerabilities and has 184 fixes is now available. Category: security (important) Bug References: 1047238,1050911,1051510,1054914,1055117,1056686,1060662,1061840,1061843,1064597,1064701,1065600,1065729,1066369,1071009,1071306,1078248,1082555,1085030,1085536,1085539,1086103,1087092,1090734,1091171,1093205,1102097,1104902,1106061,1106284,1106434,1108382,1112178,1112894,1112899,1112902,1112903,1112905,1112906,1112907,1113722,1114279,1114542,1118689,1119086,1120876,1120902,1120937,1123105,1123959,1124370,1129424,1129519,1129664,1131107,1131281,1131565,1133021,1134291,1134881,1134882,1135219,1135642,1135897,1136261,1137069,1137884,1138539,1139020,1139021,1139101,1139500,1140012,1140426,1140487,1141013,1141450,1141543,1141554,1142019,1142076,1142109,1142117,1142118,1142119,1142496,1142541,1142635,1142685,1142701,1142857,1143300,1143466,1143765,1143841,1143843,1144123,1144333,1144474,1144518,1144718,1144813,1144880,1144886,1144912,1144920,1144979,1145010,1145024,1145051,1145059,1145189,1145235,1145300,1145302,1145388,1145389,1145390,1145391,1145392,1145393,1145394,1145395,1145396,1145397,1145408,1145409,1145661,1145678,1145687,1145920,1145922,1145934,1145937,1145940,1145941,1145942,1146074,1146084,1146163,1146285,1146346,1146351,1146352,1146361,1146368,1146376,1146378,1146381,1146391,1146399,1146413,1146425,1146516,1146519,1146524,1146526,1146529,1146531,1146543,1146547,1146550,1146575,1146589,1146678,1146938,1148031,1148032,1148033,1148034,1148035,1148093,1148133,1148192,1148196,1148198,1148202,1148303,1148363,1148379,1148394,1148527,1148574,1148616,1148617,1148619,1148698,1148859,1148868,1149053,1149083,1149104,1149105,1149106,1149197,1149214,1149224,1149325,1149376,1149413,1149418,1149424,1149522,1149527,1149539,1149552,1149591,1149602,1149612,1149626,1149652,1149713,1149940,1149959,1149963,1149976,1150025,1150033,1150112,1150562,1150727,1150860,1150861,1150933 CVE References: CVE-2017-18551,CVE-2018-20976,CVE-2018-21008,CVE-2019-10207,CVE-2019-14814,CVE-2019-14815,CVE-2019-14816,CVE-2019-14835,CVE-2019-15030,CVE-2019-15031,CVE-2019-15090,CVE-2019-15098,CVE-2019-15099,CVE-2019-15117,CVE-2019-15118,CVE-2019-15211,CVE-2019-15212,CVE-2019-15214,CVE-2019-15215,CVE-2019-15216,CVE-2019-15217,CVE-2019-15218,CVE-2019-15219,CVE-2019-15220,CVE-2019-15221,CVE-2019-15222,CVE-2019-15239,CVE-2019-15290,CVE-2019-15292,CVE-2019-15538,CVE-2019-15666,CVE-2019-15902,CVE-2019-15917,CVE-2019-15919,CVE-2019-15920,CVE-2019-15921,CVE-2019-15924,CVE-2019-15926,CVE-2019-15927,CVE-2019-9456 Sources used: SUSE Linux Enterprise Workstation Extension 12-SP4 (src): kernel-default-4.12.14-95.32.1 SUSE Linux Enterprise Software Development Kit 12-SP4 (src): kernel-docs-4.12.14-95.32.1, kernel-obs-build-4.12.14-95.32.1 SUSE Linux Enterprise Server 12-SP4 (src): kernel-default-4.12.14-95.32.1, kernel-source-4.12.14-95.32.1, kernel-syms-4.12.14-95.32.1 SUSE Linux Enterprise Live Patching 12-SP4 (src): kgraft-patch-SLE12-SP4_Update_8-1-6.3.1 SUSE Linux Enterprise High Availability 12-SP4 (src): kernel-default-4.12.14-95.32.1 SUSE Linux Enterprise Desktop 12-SP4 (src): kernel-default-4.12.14-95.32.1, kernel-source-4.12.14-95.32.1, kernel-syms-4.12.14-95.32.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-2019:2414-1: An update that solves 39 vulnerabilities and has 180 fixes is now available. Category: security (important) Bug References: 1047238,1050911,1051510,1054914,1055117,1056686,1060662,1061840,1061843,1064597,1064701,1065600,1065729,1066369,1071009,1071306,1078248,1082555,1085030,1085536,1085539,1086103,1087092,1090734,1091171,1093205,1102097,1104902,1106061,1106284,1106434,1108382,1112894,1112899,1112902,1112903,1112905,1112906,1112907,1113722,1114279,1114542,1118689,1119086,1120876,1120902,1120937,1123105,1123959,1124370,1129424,1129519,1129664,1131107,1131281,1131565,1133021,1134291,1134881,1134882,1135219,1135642,1135897,1136261,1137811,1137884,1138539,1139020,1139021,1139101,1139500,1140012,1140426,1140487,1141450,1141543,1141554,1142019,1142076,1142109,1142117,1142118,1142119,1142496,1142541,1142635,1142685,1142701,1142857,1143300,1143466,1143765,1143841,1143843,1144123,1144333,1144474,1144518,1144718,1144813,1144880,1144886,1144912,1144920,1144979,1145010,1145051,1145059,1145189,1145235,1145300,1145302,1145388,1145389,1145390,1145391,1145392,1145393,1145394,1145395,1145396,1145397,1145408,1145409,1145661,1145678,1145687,1145920,1145922,1145934,1145937,1145940,1145941,1145942,1146074,1146084,1146163,1146285,1146346,1146351,1146352,1146361,1146376,1146378,1146381,1146391,1146399,1146413,1146425,1146512,1146514,1146516,1146519,1146524,1146526,1146529,1146531,1146543,1146547,1146550,1146575,1146589,1146678,1146938,1148031,1148032,1148033,1148034,1148035,1148093,1148133,1148192,1148196,1148198,1148202,1148303,1148363,1148379,1148394,1148527,1148574,1148616,1148617,1148619,1148859,1148868,1149053,1149083,1149104,1149105,1149106,1149197,1149214,1149224,1149325,1149376,1149413,1149418,1149424,1149522,1149527,1149539,1149552,1149591,1149602,1149612,1149626,1149652,1149713,1149940,1149976,1150025,1150033,1150112,1150562,1150727,1150860,1150861,1150933 CVE References: CVE-2017-18551,CVE-2018-20976,CVE-2018-21008,CVE-2019-10207,CVE-2019-14814,CVE-2019-14815,CVE-2019-14816,CVE-2019-14835,CVE-2019-15030,CVE-2019-15031,CVE-2019-15090,CVE-2019-15098,CVE-2019-15117,CVE-2019-15118,CVE-2019-15211,CVE-2019-15212,CVE-2019-15214,CVE-2019-15215,CVE-2019-15216,CVE-2019-15217,CVE-2019-15218,CVE-2019-15219,CVE-2019-15220,CVE-2019-15221,CVE-2019-15222,CVE-2019-15239,CVE-2019-15290,CVE-2019-15292,CVE-2019-15538,CVE-2019-15666,CVE-2019-15902,CVE-2019-15917,CVE-2019-15919,CVE-2019-15920,CVE-2019-15921,CVE-2019-15924,CVE-2019-15926,CVE-2019-15927,CVE-2019-9456 Sources used: SUSE Linux Enterprise Workstation Extension 15 (src): kernel-default-4.12.14-150.35.1 SUSE Linux Enterprise Module for Open Buildservice Development Tools 15 (src): kernel-default-4.12.14-150.35.1, kernel-docs-4.12.14-150.35.1, kernel-obs-qa-4.12.14-150.35.1 SUSE Linux Enterprise Module for Live Patching 15 (src): kernel-default-4.12.14-150.35.1, kernel-livepatch-SLE15_Update_14-1-1.3.1 SUSE Linux Enterprise Module for Legacy Software 15 (src): kernel-default-4.12.14-150.35.1 SUSE Linux Enterprise Module for Development Tools 15 (src): kernel-docs-4.12.14-150.35.1, kernel-obs-build-4.12.14-150.35.1, kernel-source-4.12.14-150.35.1, kernel-syms-4.12.14-150.35.1, kernel-vanilla-4.12.14-150.35.1 SUSE Linux Enterprise Module for Basesystem 15 (src): kernel-default-4.12.14-150.35.1, kernel-source-4.12.14-150.35.1, kernel-zfcpdump-4.12.14-150.35.1 SUSE Linux Enterprise High Availability 15 (src): kernel-default-4.12.14-150.35.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-2019:2424-1: An update that solves 40 vulnerabilities and has 222 fixes is now available. Category: security (important) Bug References: 1047238,1050911,1051510,1054914,1055117,1056686,1060662,1061840,1061843,1064597,1064701,1065600,1065729,1066369,1071009,1071306,1078248,1082555,1082635,1085030,1085536,1085539,1086103,1087092,1090734,1091171,1093205,1102097,1103990,1104353,1104427,1104745,1104902,1106061,1106284,1106434,1108382,1109837,1111666,1112178,1112374,1112894,1112899,1112902,1112903,1112905,1112906,1112907,1113722,1113994,1114279,1114542,1118689,1119086,1119113,1120046,1120876,1120902,1123105,1123959,1124370,1129424,1129519,1129664,1131107,1131281,1131489,1131565,1133021,1134291,1134476,1134881,1134882,1135219,1135642,1135897,1135990,1136039,1136261,1136346,1136349,1136352,1136496,1136498,1136502,1136682,1137322,1137323,1137884,1138099,1138100,1138539,1139020,1139021,1139101,1139500,1140012,1140426,1140487,1141340,1141450,1141543,1141554,1142019,1142076,1142109,1142117,1142118,1142119,1142496,1142541,1142635,1142685,1142701,1142857,1143300,1143331,1143466,1143706,1143738,1143765,1143841,1143843,1143962,1144123,1144333,1144375,1144474,1144518,1144582,1144718,1144813,1144880,1144886,1144912,1144920,1144979,1145010,1145018,1145051,1145059,1145189,1145235,1145256,1145300,1145302,1145357,1145388,1145389,1145390,1145391,1145392,1145393,1145394,1145395,1145396,1145397,1145408,1145409,1145446,1145661,1145678,1145687,1145920,1145922,1145934,1145937,1145940,1145941,1145942,1145946,1146074,1146084,1146141,1146163,1146215,1146285,1146346,1146351,1146352,1146361,1146368,1146376,1146378,1146381,1146391,1146399,1146413,1146425,1146516,1146519,1146524,1146526,1146529,1146531,1146543,1146547,1146550,1146575,1146589,1146678,1146938,1148031,1148032,1148033,1148034,1148035,1148093,1148133,1148192,1148196,1148198,1148202,1148219,1148297,1148303,1148308,1148363,1148379,1148394,1148527,1148570,1148574,1148616,1148617,1148619,1148698,1148859,1148868,1149053,1149083,1149104,1149105,1149106,1149197,1149214,1149224,1149325,1149376,1149413,1149418,1149424,1149522,1149527,1149539,1149552,1149591,1149602,1149612,1149626,1149652,1149713,1149940,1149976,1150025,1150033,1150112,1150562,1150727,1150860,1150861,1150933 CVE References: CVE-2017-18551,CVE-2018-20976,CVE-2018-21008,CVE-2019-10207,CVE-2019-14814,CVE-2019-14815,CVE-2019-14816,CVE-2019-14835,CVE-2019-15030,CVE-2019-15031,CVE-2019-15090,CVE-2019-15098,CVE-2019-15099,CVE-2019-15117,CVE-2019-15118,CVE-2019-15211,CVE-2019-15212,CVE-2019-15214,CVE-2019-15215,CVE-2019-15216,CVE-2019-15217,CVE-2019-15218,CVE-2019-15219,CVE-2019-15220,CVE-2019-15221,CVE-2019-15222,CVE-2019-15239,CVE-2019-15290,CVE-2019-15292,CVE-2019-15538,CVE-2019-15666,CVE-2019-15902,CVE-2019-15917,CVE-2019-15919,CVE-2019-15920,CVE-2019-15921,CVE-2019-15924,CVE-2019-15926,CVE-2019-15927,CVE-2019-9456 Sources used: SUSE Linux Enterprise Workstation Extension 15-SP1 (src): kernel-default-4.12.14-197.18.1 SUSE Linux Enterprise Module for Open Buildservice Development Tools 15-SP1 (src): dtb-aarch64-4.12.14-197.18.1, kernel-debug-4.12.14-197.18.1, kernel-default-4.12.14-197.18.1, kernel-docs-4.12.14-197.18.1, kernel-kvmsmall-4.12.14-197.18.1, kernel-obs-qa-4.12.14-197.18.1, kernel-source-4.12.14-197.18.1, kernel-vanilla-4.12.14-197.18.1, kernel-zfcpdump-4.12.14-197.18.1 SUSE Linux Enterprise Module for Legacy Software 15-SP1 (src): kernel-default-4.12.14-197.18.1 SUSE Linux Enterprise Module for Development Tools 15-SP1 (src): kernel-docs-4.12.14-197.18.1, kernel-obs-build-4.12.14-197.18.1, kernel-source-4.12.14-197.18.1, kernel-syms-4.12.14-197.18.1 SUSE Linux Enterprise Module for Basesystem 15-SP1 (src): kernel-default-4.12.14-197.18.1, kernel-source-4.12.14-197.18.1, kernel-zfcpdump-4.12.14-197.18.1 SUSE Linux Enterprise High Availability 15-SP1 (src): kernel-default-4.12.14-197.18.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.
openSUSE-SU-2019:2173-1: An update that solves 38 vulnerabilities and has 159 fixes is now available. Category: security (important) Bug References: 1047238,1050911,1051510,1054914,1056686,1060662,1061840,1061843,1064597,1064701,1065600,1065729,1066369,1071009,1071306,1078248,1082555,1085030,1085536,1085539,1087092,1090734,1091171,1093205,1102097,1104902,1106284,1106434,1108382,1112894,1112899,1112902,1112903,1112905,1112906,1112907,1113722,1114279,1114542,1118689,1119086,1120876,1120902,1120937,1123105,1124370,1129424,1129519,1129664,1131107,1131565,1134291,1134881,1134882,1135219,1135642,1136261,1137884,1138539,1139020,1139021,1140012,1140487,1141543,1141554,1142019,1142076,1142109,1142541,1142635,1143300,1143765,1143841,1143843,1144123,1144333,1144718,1144813,1144880,1144886,1144912,1144920,1144979,1145010,1145051,1145059,1145189,1145235,1145300,1145302,1145388,1145389,1145390,1145391,1145392,1145393,1145394,1145395,1145396,1145397,1145408,1145409,1145661,1145678,1145687,1145920,1145922,1145934,1145937,1145940,1145941,1145942,1146074,1146084,1146163,1146285,1146346,1146351,1146352,1146361,1146376,1146378,1146381,1146391,1146399,1146413,1146425,1146512,1146514,1146516,1146519,1146524,1146526,1146529,1146531,1146543,1146547,1146550,1146575,1146589,1146678,1146938,1148031,1148032,1148033,1148034,1148035,1148093,1148133,1148192,1148196,1148198,1148202,1148303,1148363,1148379,1148394,1148527,1148574,1148616,1148617,1148619,1148859,1148868,1149053,1149083,1149104,1149105,1149106,1149197,1149214,1149224,1149325,1149376,1149413,1149418,1149424,1149522,1149527,1149539,1149552,1149591,1149602,1149612,1149626,1149652,1149713,1149940,1149976,1150025,1150033,1150112,1150562,1150727,1150860,1150861,1150933 CVE References: CVE-2017-18551,CVE-2018-20976,CVE-2018-21008,CVE-2019-14814,CVE-2019-14815,CVE-2019-14816,CVE-2019-14835,CVE-2019-15030,CVE-2019-15031,CVE-2019-15090,CVE-2019-15098,CVE-2019-15117,CVE-2019-15118,CVE-2019-15211,CVE-2019-15212,CVE-2019-15214,CVE-2019-15215,CVE-2019-15216,CVE-2019-15217,CVE-2019-15218,CVE-2019-15219,CVE-2019-15220,CVE-2019-15221,CVE-2019-15222,CVE-2019-15239,CVE-2019-15290,CVE-2019-15292,CVE-2019-15538,CVE-2019-15666,CVE-2019-15902,CVE-2019-15917,CVE-2019-15919,CVE-2019-15920,CVE-2019-15921,CVE-2019-15924,CVE-2019-15926,CVE-2019-15927,CVE-2019-9456 Sources used: openSUSE Leap 15.0 (src): kernel-debug-4.12.14-lp150.12.73.1, kernel-default-4.12.14-lp150.12.73.1, kernel-docs-4.12.14-lp150.12.73.1, kernel-kvmsmall-4.12.14-lp150.12.73.1, kernel-obs-build-4.12.14-lp150.12.73.1, kernel-obs-qa-4.12.14-lp150.12.73.1, kernel-source-4.12.14-lp150.12.73.1, kernel-syms-4.12.14-lp150.12.73.1, kernel-vanilla-4.12.14-lp150.12.73.1
openSUSE-SU-2019:2181-1: An update that solves 39 vulnerabilities and has 203 fixes is now available. Category: security (important) Bug References: 1047238,1050911,1051510,1054914,1056686,1060662,1061840,1061843,1064597,1064701,1065600,1065729,1066369,1071009,1071306,1078248,1082555,1082635,1085030,1085536,1085539,1087092,1090734,1091171,1093205,1102097,1103990,1104353,1104427,1104745,1104902,1106284,1106434,1108382,1109837,1111666,1112178,1112374,1112894,1112899,1112902,1112903,1112905,1112906,1112907,1113722,1113994,1114279,1114542,1118689,1119086,1119113,1120046,1120876,1120902,1123105,1124370,1129424,1129519,1129664,1131107,1131489,1131565,1134291,1134476,1134881,1134882,1135219,1135642,1135990,1136039,1136261,1136346,1136349,1136496,1136498,1136682,1137322,1137323,1137884,1138099,1138100,1138539,1139020,1139021,1140012,1140487,1141340,1141543,1141554,1142019,1142076,1142109,1142496,1142541,1142635,1142685,1143300,1143331,1143706,1143765,1143841,1143843,1143962,1144123,1144333,1144375,1144582,1144718,1144813,1144880,1144886,1144912,1144920,1144979,1145010,1145018,1145051,1145059,1145189,1145235,1145256,1145300,1145302,1145357,1145388,1145389,1145390,1145391,1145392,1145393,1145394,1145395,1145396,1145397,1145408,1145409,1145446,1145661,1145678,1145687,1145920,1145922,1145934,1145937,1145940,1145941,1145942,1145946,1146074,1146084,1146141,1146163,1146215,1146285,1146346,1146351,1146352,1146361,1146368,1146376,1146378,1146381,1146391,1146399,1146413,1146425,1146512,1146514,1146516,1146519,1146524,1146526,1146529,1146531,1146543,1146547,1146550,1146575,1146589,1146678,1146938,1148031,1148032,1148033,1148034,1148035,1148093,1148133,1148192,1148196,1148198,1148202,1148219,1148297,1148303,1148308,1148363,1148379,1148394,1148527,1148570,1148574,1148616,1148617,1148619,1148698,1148859,1148868,1149053,1149083,1149104,1149105,1149106,1149197,1149214,1149224,1149325,1149376,1149413,1149418,1149424,1149522,1149527,1149539,1149552,1149591,1149602,1149612,1149626,1149652,1149713,1149940,1149976,1150025,1150033,1150112,1150562,1150727,1150860,1150861,1150933 CVE References: CVE-2017-18551,CVE-2018-20976,CVE-2018-21008,CVE-2019-14814,CVE-2019-14815,CVE-2019-14816,CVE-2019-14835,CVE-2019-15030,CVE-2019-15031,CVE-2019-15090,CVE-2019-15098,CVE-2019-15099,CVE-2019-15117,CVE-2019-15118,CVE-2019-15211,CVE-2019-15212,CVE-2019-15214,CVE-2019-15215,CVE-2019-15216,CVE-2019-15217,CVE-2019-15218,CVE-2019-15219,CVE-2019-15220,CVE-2019-15221,CVE-2019-15222,CVE-2019-15239,CVE-2019-15290,CVE-2019-15292,CVE-2019-15538,CVE-2019-15666,CVE-2019-15902,CVE-2019-15917,CVE-2019-15919,CVE-2019-15920,CVE-2019-15921,CVE-2019-15924,CVE-2019-15926,CVE-2019-15927,CVE-2019-9456 Sources used: openSUSE Leap 15.1 (src): kernel-debug-4.12.14-lp151.28.16.1, kernel-default-4.12.14-lp151.28.16.1, kernel-docs-4.12.14-lp151.28.16.1, kernel-kvmsmall-4.12.14-lp151.28.16.1, kernel-obs-build-4.12.14-lp151.28.16.1, kernel-obs-qa-4.12.14-lp151.28.16.1, kernel-source-4.12.14-lp151.28.16.1, kernel-syms-4.12.14-lp151.28.16.1, kernel-vanilla-4.12.14-lp151.28.16.1
SUSE-SU-2019:2651-1: An update that solves 42 vulnerabilities and has 210 fixes is now available. Category: security (important) Bug References: 1047238,1050911,1051510,1054914,1055117,1056686,1060662,1061840,1061843,1064597,1064701,1065600,1065729,1066369,1071009,1071306,1071995,1078248,1082555,1085030,1085536,1085539,1087092,1090734,1091171,1093205,1102097,1104902,1104967,1106061,1106284,1106434,1108382,1109158,1112894,1112899,1112902,1112903,1112905,1112906,1112907,1113722,1114279,1114542,1118689,1119086,1120876,1120902,1120937,1123034,1123105,1124370,1127988,1129424,1129519,1129664,1131107,1131304,1131565,1134291,1134881,1134882,1135219,1135642,1135897,1136261,1137069,1137865,1137884,1137959,1138539,1139020,1139021,1139101,1139500,1140012,1140155,1140426,1140487,1141013,1141450,1141543,1141554,1142019,1142076,1142109,1142117,1142118,1142119,1142496,1142541,1142635,1142685,1142701,1143300,1143466,1143765,1143841,1143843,1144123,1144333,1144474,1144518,1144718,1144813,1144880,1144886,1144912,1144920,1144979,1145010,1145051,1145059,1145134,1145189,1145235,1145300,1145302,1145388,1145389,1145390,1145391,1145392,1145393,1145394,1145395,1145396,1145397,1145408,1145409,1145661,1145678,1145687,1145920,1145922,1145934,1145937,1145940,1145941,1145942,1146042,1146074,1146084,1146163,1146285,1146346,1146351,1146352,1146361,1146376,1146378,1146381,1146391,1146399,1146413,1146425,1146512,1146514,1146516,1146519,1146524,1146526,1146529,1146531,1146540,1146543,1146547,1146550,1146575,1146589,1146664,1146678,1146938,1148031,1148032,1148033,1148034,1148035,1148093,1148133,1148192,1148196,1148198,1148202,1148303,1148363,1148379,1148394,1148527,1148574,1148616,1148617,1148619,1148712,1148859,1148868,1149053,1149083,1149104,1149105,1149106,1149197,1149214,1149224,1149313,1149325,1149376,1149413,1149418,1149424,1149446,1149522,1149527,1149539,1149552,1149555,1149591,1149602,1149612,1149626,1149651,1149652,1149713,1149940,1149976,1150025,1150033,1150112,1150381,1150423,1150562,1150727,1150860,1150861,1150933,1151350,1151610,1151667,1151680,1151891,1151955,1152024,1152025,1152026,1152161,1152325,1152457,1152460,1152466,1152972,1152974,1152975 CVE References: CVE-2017-18551,CVE-2017-18595,CVE-2018-20976,CVE-2018-21008,CVE-2019-14814,CVE-2019-14815,CVE-2019-14816,CVE-2019-14821,CVE-2019-14835,CVE-2019-15030,CVE-2019-15031,CVE-2019-15090,CVE-2019-15098,CVE-2019-15117,CVE-2019-15118,CVE-2019-15211,CVE-2019-15212,CVE-2019-15214,CVE-2019-15215,CVE-2019-15216,CVE-2019-15217,CVE-2019-15218,CVE-2019-15219,CVE-2019-15220,CVE-2019-15221,CVE-2019-15222,CVE-2019-15239,CVE-2019-15290,CVE-2019-15291,CVE-2019-15292,CVE-2019-15538,CVE-2019-15666,CVE-2019-15902,CVE-2019-15917,CVE-2019-15919,CVE-2019-15920,CVE-2019-15921,CVE-2019-15924,CVE-2019-15926,CVE-2019-15927,CVE-2019-9456,CVE-2019-9506 Sources used: SUSE Linux Enterprise Module for Public Cloud 15 (src): kernel-azure-4.12.14-5.41.1, kernel-source-azure-4.12.14-5.41.1, kernel-syms-azure-4.12.14-5.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.
SUSE-SU-2019:2658-1: An update that solves 45 vulnerabilities and has 270 fixes is now available. Category: security (important) Bug References: 1047238,1050911,1051510,1054914,1055117,1056686,1060662,1061840,1061843,1064597,1064701,1065600,1065729,1066369,1071009,1071306,1071995,1078248,1082555,1082635,1085030,1085536,1085539,1086103,1087092,1090734,1091171,1093205,1102097,1103990,1104353,1104427,1104745,1104902,1104967,1106061,1106284,1106434,1108382,1109158,1109837,1111666,1112178,1112374,1112894,1112899,1112902,1112903,1112905,1112906,1112907,1113722,1113994,1114279,1114542,1118689,1119086,1119113,1120046,1120876,1120902,1123034,1123105,1123959,1124370,1127988,1129424,1129519,1129664,1131107,1131281,1131304,1131489,1131565,1132686,1133021,1134291,1134476,1134881,1134882,1135219,1135642,1135897,1135990,1136039,1136261,1136346,1136349,1136352,1136496,1136498,1136502,1136682,1137069,1137322,1137323,1137586,1137865,1137884,1137959,1137982,1138099,1138100,1138539,1139020,1139021,1139101,1139500,1140012,1140155,1140426,1140487,1141013,1141340,1141450,1141543,1141554,1142019,1142076,1142109,1142117,1142118,1142119,1142496,1142541,1142635,1142685,1142701,1142857,1143300,1143331,1143466,1143706,1143738,1143765,1143841,1143843,1143962,1144123,1144333,1144375,1144474,1144518,1144582,1144718,1144813,1144880,1144886,1144912,1144920,1144979,1145010,1145018,1145051,1145059,1145134,1145189,1145235,1145256,1145300,1145302,1145357,1145388,1145389,1145390,1145391,1145392,1145393,1145394,1145395,1145396,1145397,1145408,1145409,1145446,1145661,1145678,1145687,1145920,1145922,1145934,1145937,1145940,1145941,1145942,1145946,1146042,1146074,1146084,1146141,1146163,1146215,1146285,1146346,1146351,1146352,1146361,1146368,1146376,1146378,1146381,1146391,1146399,1146413,1146425,1146512,1146514,1146516,1146519,1146524,1146526,1146529,1146531,1146540,1146543,1146547,1146550,1146575,1146589,1146664,1146678,1146938,1148031,1148032,1148033,1148034,1148035,1148093,1148133,1148192,1148196,1148198,1148202,1148219,1148297,1148303,1148308,1148363,1148379,1148394,1148527,1148570,1148574,1148616,1148617,1148619,1148698,1148712,1148859,1148868,1149053,1149083,1149104,1149105,1149106,1149197,1149214,1149224,1149313,1149325,1149376,1149413,1149418,1149424,1149446,1149522,1149527,1149539,1149552,1149555,1149591,1149602,1149612,1149626,1149651,1149652,1149713,1149940,1149976,1150025,1150033,1150112,1150305,1150381,1150423,1150562,1150727,1150846,1150860,1150861,1150933,1151067,1151192,1151350,1151610,1151661,1151662,1151667,1151680,1151891,1151955,1152024,1152025,1152026,1152161,1152187,1152243,1152325,1152457,1152460,1152466,1152525,1152972,1152974,1152975 CVE References: CVE-2017-18551,CVE-2017-18595,CVE-2018-20976,CVE-2018-21008,CVE-2019-10207,CVE-2019-11477,CVE-2019-14814,CVE-2019-14815,CVE-2019-14816,CVE-2019-14821,CVE-2019-14835,CVE-2019-15030,CVE-2019-15031,CVE-2019-15090,CVE-2019-15098,CVE-2019-15099,CVE-2019-15117,CVE-2019-15118,CVE-2019-15211,CVE-2019-15212,CVE-2019-15214,CVE-2019-15215,CVE-2019-15216,CVE-2019-15217,CVE-2019-15218,CVE-2019-15219,CVE-2019-15220,CVE-2019-15221,CVE-2019-15222,CVE-2019-15239,CVE-2019-15290,CVE-2019-15291,CVE-2019-15292,CVE-2019-15538,CVE-2019-15666,CVE-2019-15902,CVE-2019-15917,CVE-2019-15919,CVE-2019-15920,CVE-2019-15921,CVE-2019-15924,CVE-2019-15926,CVE-2019-15927,CVE-2019-9456,CVE-2019-9506 Sources used: SUSE Linux Enterprise Module for Public Cloud 15-SP1 (src): kernel-azure-4.12.14-8.16.1, kernel-source-azure-4.12.14-8.16.1, kernel-syms-azure-4.12.14-8.16.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-2019:2738-1: An update that solves 40 vulnerabilities and has 225 fixes is now available. Category: security (important) Bug References: 1047238,1050911,1051510,1054914,1055117,1056686,1060662,1061840,1061843,1064597,1064701,1065600,1065729,1066369,1071009,1071306,1078248,1082555,1082635,1085030,1085536,1085539,1086103,1087092,1090734,1091171,1093205,1102097,1103990,1104353,1104427,1104745,1104902,1106061,1106284,1106434,1108382,1109837,1111666,1112178,1112374,1112894,1112899,1112902,1112903,1112905,1112906,1112907,1113722,1113994,1114279,1114542,1118689,1119086,1119113,1120046,1120876,1120902,1123105,1123959,1124370,1129424,1129519,1129664,1131107,1131281,1131489,1131565,1132426,1133021,1134291,1134476,1134881,1134882,1135219,1135642,1135897,1135990,1136039,1136261,1136346,1136349,1136352,1136496,1136498,1136502,1136682,1137322,1137323,1137884,1138099,1138100,1138539,1139020,1139021,1139101,1139500,1140012,1140426,1140487,1141340,1141450,1141543,1141554,1142019,1142076,1142109,1142117,1142118,1142119,1142496,1142541,1142635,1142685,1142701,1142857,1143300,1143331,1143466,1143706,1143738,1143765,1143841,1143843,1143962,1144123,1144333,1144375,1144474,1144518,1144582,1144718,1144813,1144880,1144886,1144912,1144920,1144979,1145010,1145018,1145051,1145059,1145189,1145235,1145256,1145300,1145302,1145357,1145388,1145389,1145390,1145391,1145392,1145393,1145394,1145395,1145396,1145397,1145408,1145409,1145446,1145661,1145678,1145687,1145920,1145922,1145934,1145937,1145940,1145941,1145942,1145946,1146074,1146084,1146141,1146163,1146215,1146285,1146346,1146351,1146352,1146361,1146368,1146376,1146378,1146381,1146391,1146399,1146413,1146425,1146512,1146514,1146516,1146519,1146524,1146526,1146529,1146531,1146543,1146547,1146550,1146575,1146589,1146678,1146938,1148031,1148032,1148033,1148034,1148035,1148093,1148133,1148192,1148196,1148198,1148202,1148219,1148297,1148303,1148308,1148363,1148379,1148394,1148527,1148570,1148574,1148616,1148617,1148619,1148698,1148859,1148868,1149053,1149083,1149104,1149105,1149106,1149197,1149214,1149224,1149325,1149376,1149413,1149418,1149424,1149522,1149527,1149539,1149552,1149591,1149602,1149612,1149626,1149652,1149713,1149940,1149976,1150025,1150033,1150112,1150562,1150727,1150860,1150861,1150933 CVE References: CVE-2017-18551,CVE-2018-20976,CVE-2018-21008,CVE-2019-10207,CVE-2019-14814,CVE-2019-14815,CVE-2019-14816,CVE-2019-14835,CVE-2019-15030,CVE-2019-15031,CVE-2019-15090,CVE-2019-15098,CVE-2019-15099,CVE-2019-15117,CVE-2019-15118,CVE-2019-15211,CVE-2019-15212,CVE-2019-15214,CVE-2019-15215,CVE-2019-15216,CVE-2019-15217,CVE-2019-15218,CVE-2019-15219,CVE-2019-15220,CVE-2019-15221,CVE-2019-15222,CVE-2019-15239,CVE-2019-15290,CVE-2019-15292,CVE-2019-15538,CVE-2019-15666,CVE-2019-15902,CVE-2019-15917,CVE-2019-15919,CVE-2019-15920,CVE-2019-15921,CVE-2019-15924,CVE-2019-15926,CVE-2019-15927,CVE-2019-9456 Sources used: SUSE Linux Enterprise Module for Realtime 15-SP1 (src): kernel-rt-4.12.14-14.11.1, kernel-rt_debug-4.12.14-14.11.1, kernel-source-rt-4.12.14-14.11.1, kernel-syms-rt-4.12.14-14.11.1 SUSE Linux Enterprise Module for Open Buildservice Development Tools 15-SP1 (src): kernel-rt-4.12.14-14.11.1, kernel-rt_debug-4.12.14-14.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-2019:2756-1: An update that solves 44 vulnerabilities and has 368 fixes is now available. Category: security (important) Bug References: 1012382,1047238,1050911,1051510,1053043,1054914,1055117,1056686,1060662,1061840,1061843,1064597,1064701,1065600,1065729,1066369,1071009,1071306,1071995,1078248,1082555,1083647,1083710,1085030,1085536,1085539,1086103,1087092,1088047,1090734,1091171,1093205,1094555,1098633,1102097,1102247,1104902,1104967,1106061,1106284,1106383,1106434,1106751,1108382,1109137,1109158,1111666,1112178,1112894,1112899,1112902,1112903,1112905,1112906,1112907,1113722,1114279,1114542,1115688,1117158,1118139,1118689,1119086,1119222,1119532,1120423,1120566,1120876,1120902,1120937,1123034,1123080,1123105,1123959,1124167,1124370,1124503,1127034,1127155,1127315,1127988,1128432,1128902,1128910,1129424,1129519,1129664,1129770,1130972,1131107,1131281,1131304,1131565,1132154,1132390,1132686,1133021,1133401,1134097,1134291,1134303,1134390,1134671,1134881,1134882,1135219,1135296,1135335,1135556,1135642,1135661,1135897,1136157,1136261,1136811,1136896,1136935,1136990,1137069,1137162,1137221,1137366,1137372,1137429,1137444,1137458,1137534,1137535,1137584,1137586,1137609,1137625,1137728,1137739,1137752,1137811,1137827,1137865,1137884,1137959,1137995,1137996,1137998,1137999,1138000,1138002,1138003,1138005,1138006,1138007,1138008,1138009,1138010,1138011,1138012,1138013,1138014,1138015,1138016,1138017,1138018,1138019,1138374,1138375,1138539,1138589,1138719,1139020,1139021,1139101,1139500,1139771,1139782,1139865,1140012,1140133,1140139,1140155,1140322,1140328,1140405,1140424,1140426,1140428,1140487,1140637,1140652,1140658,1140715,1140719,1140726,1140727,1140728,1140814,1140887,1140888,1140889,1140891,1140893,1140903,1140945,1140948,1140954,1140955,1140956,1140957,1140958,1140959,1140960,1140961,1140962,1140964,1140971,1140972,1140992,1141013,1141401,1141402,1141450,1141452,1141453,1141454,1141478,1141543,1141554,1142019,1142076,1142109,1142112,1142117,1142118,1142119,1142129,1142220,1142221,1142350,1142351,1142354,1142359,1142450,1142496,1142541,1142635,1142685,1142701,1142857,1142868,1143003,1143105,1143185,1143300,1143466,1143507,1143765,1143841,1143843,1144123,1144333,1144474,1144518,1144718,1144813,1144880,1144886,1144912,1144920,1144979,1145010,1145024,1145051,1145059,1145189,1145235,1145300,1145302,1145388,1145389,1145390,1145391,1145392,1145393,1145394,1145395,1145396,1145397,1145408,1145409,1145661,1145678,1145687,1145920,1145922,1145934,1145937,1145940,1145941,1145942,1146042,1146074,1146084,1146163,1146285,1146346,1146351,1146352,1146361,1146376,1146378,1146381,1146391,1146399,1146413,1146425,1146512,1146514,1146516,1146519,1146524,1146526,1146529,1146531,1146540,1146543,1146547,1146550,1146575,1146589,1146664,1146678,1146938,1148031,1148032,1148033,1148034,1148035,1148093,1148133,1148192,1148196,1148198,1148202,1148303,1148363,1148379,1148394,1148527,1148574,1148616,1148617,1148619,1148698,1148712,1148859,1148868,1149053,1149083,1149104,1149105,1149106,1149197,1149214,1149224,1149313,1149325,1149376,1149413,1149418,1149424,1149446,1149522,1149527,1149539,1149552,1149555,1149591,1149602,1149612,1149626,1149651,1149652,1149713,1149940,1149959,1149963,1149976,1150025,1150033,1150112,1150381,1150423,1150562,1150727,1150860,1150861,1150933,1151350,1151610,1151667,1151671,1151891,1151955,1152024,1152025,1152026,1152161,1152325,1152457,1152460,1152466,1152972,1152974,1152975 CVE References: CVE-2017-18551,CVE-2017-18595,CVE-2018-20976,CVE-2018-21008,CVE-2019-10207,CVE-2019-11479,CVE-2019-14814,CVE-2019-14815,CVE-2019-14816,CVE-2019-14821,CVE-2019-14835,CVE-2019-15030,CVE-2019-15031,CVE-2019-15090,CVE-2019-15098,CVE-2019-15117,CVE-2019-15118,CVE-2019-15211,CVE-2019-15212,CVE-2019-15214,CVE-2019-15215,CVE-2019-15216,CVE-2019-15217,CVE-2019-15218,CVE-2019-15219,CVE-2019-15220,CVE-2019-15221,CVE-2019-15222,CVE-2019-15239,CVE-2019-15290,CVE-2019-15291,CVE-2019-15292,CVE-2019-15538,CVE-2019-15666,CVE-2019-15902,CVE-2019-15917,CVE-2019-15919,CVE-2019-15920,CVE-2019-15921,CVE-2019-15924,CVE-2019-15926,CVE-2019-15927,CVE-2019-9456,CVE-2019-9506 Sources used: SUSE Linux Enterprise Real Time Extension 12-SP4 (src): kernel-rt-4.12.14-8.6.1, kernel-rt_debug-4.12.14-8.6.1, kernel-source-rt-4.12.14-8.6.1, kernel-syms-rt-4.12.14-8.6.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.