February 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1184804] move kernel out of /boot
by bugzilla_noreply＠suse.com 10 Feb '22

10 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1184804 https://bugzilla.suse.com/show_bug.cgi?id=1184804#c160 --- Comment #160 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2022:0366-1: An update that solves 27 vulnerabilities and has 23 fixes is now available. Category: security (critical) Bug References: 1071995,1124431,1167162,1169514,1172073,1179599,1184804,1185377,1186207,1186222,1187167,1189305,1189841,1190358,1190428,1191229,1191241,1191384,1191731,1192032,1192267,1192740,1192845,1192847,1192877,1192946,1193306,1193440,1193442,1193575,1193669,1193727,1193731,1193767,1193861,1193864,1193867,1193927,1194001,1194048,1194087,1194227,1194302,1194516,1194529,1194880,1194888,1194985,1195166,1195254 CVE References: CVE-2018-25020,CVE-2019-15126,CVE-2020-27820,CVE-2021-0920,CVE-2021-0935,CVE-2021-28711,CVE-2021-28712,CVE-2021-28713,CVE-2021-28714,CVE-2021-28715,CVE-2021-33098,CVE-2021-3564,CVE-2021-39648,CVE-2021-39657,CVE-2021-4002,CVE-2021-4083,CVE-2021-4135,CVE-2021-4149,CVE-2021-4197,CVE-2021-4202,CVE-2021-43975,CVE-2021-43976,CVE-2021-44733,CVE-2021-45095,CVE-2021-45486,CVE-2022-0322,CVE-2022-0330 JIRA References: Sources used: openSUSE Leap 15.4 (src): kernel-debug-4.12.14-197.105.1, kernel-default-4.12.14-197.105.1, kernel-kvmsmall-4.12.14-197.105.1, kernel-vanilla-4.12.14-197.105.1, kernel-zfcpdump-4.12.14-197.105.1 openSUSE Leap 15.3 (src): kernel-debug-4.12.14-197.105.1, kernel-default-4.12.14-197.105.1, kernel-kvmsmall-4.12.14-197.105.1, kernel-vanilla-4.12.14-197.105.1, kernel-zfcpdump-4.12.14-197.105.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195736] leap 15.3, latest kernels- lack exactly one cpu core (6core cpu)
by bugzilla_noreply＠suse.com 10 Feb '22

10 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195736 https://bugzilla.suse.com/show_bug.cgi?id=1195736#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- OK, then I close as already working. Feel free to reopen if you encounter the problem. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188896] "BUG: Bad rss-counter state mm:00000000e555b579 type:MM_FILEPAGES val:-256" during build of cross-epiphany-gcc11-bootstrap
by bugzilla_noreply＠suse.com 10 Feb '22

10 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1188896 https://bugzilla.suse.com/show_bug.cgi?id=1188896#c50 --- Comment #50 from Ruediger Oertel <ro(a)suse.com> --- the OBS workers have this (panic_on_taint=5) now temporarily in the guest kernel cmdline -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188729] kernel: socfpga_setup_ocram_self_refresh: Unable to find mmio-sram in dtb
by bugzilla_noreply＠suse.com 10 Feb '22

10 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1188729 https://bugzilla.suse.com/show_bug.cgi?id=1188729#c14 --- Comment #14 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos@aarch32-HD24G https://openqa.opensuse.org/tests/2180185 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195142] New: kernel 5.3.18-150300.59.43-default: radeon: RIP: 0010:rb_first_postorder+0xb/0x30
by bugzilla_noreply＠suse.com 09 Feb '22

09 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 Bug ID: 1195142 Summary: kernel 5.3.18-150300.59.43-default: radeon: RIP: 0010:rb_first_postorder+0xb/0x30 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: manfred99(a)gmx.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I upgraded my Leap15.3 box from 5.3.18-59.40-default to 5.3.18-59.43-default today. Monitor stayed black, but box was booting fine after some delay. Via ssh, I could access the logs. The only irregular messages I could find were from a crash of the radeon driver: 2022-01-26T12:14:39.732506+00:00 localhost kernel: [ 3.168424] radeon 0000:09:00.0: still active bo inside vm 2022-01-26T12:14:39.732508+00:00 localhost kernel: [ 3.168433] general protection fault: 0000 [#1] SMP NOPTI 2022-01-26T12:14:39.732509+00:00 localhost kernel: [ 3.168435] CPU: 10 PID: 357 Comm: systemd-udevd Not tainted 5.3.18-150300.59.43-default #1 SLE15-SP3 2022-01-26T12:14:39.732509+00:00 localhost kernel: [ 3.168437] Hardware name: Gigabyte Technology Co., Ltd. AX370-Gaming 5/AX370-Gaming 5, BIOS F42e 10/18/2019 2022-01-26T12:14:39.732509+00:00 localhost kernel: [ 3.168443] RIP: 0010:rb_first_postorder+0xb/0x30 2022-01-26T12:14:39.732510+00:00 localhost kernel: [ 3.168445] Code: d2 74 f5 48 89 d0 48 8b 52 10 48 85 d2 75 f4 48 8b 50 08 48 85 d2 75 eb f3 c3 0f 1f 44 00 00 48 8b 17 48 85 d2 74 17 48 89 d0 <48> 8b 52 10 48 85 d2 75 f4 48 8b 50 08 48 85 d2 75 eb f3 c3 31 c0 2022-01-26T12:14:39.732510+00:00 localhost kernel: [ 3.168448] RSP: 0018:ffffb579007c7910 EFLAGS: 00010286 2022-01-26T12:14:39.732512+00:00 localhost kernel: [ 3.168450] RAX: 8948530000441f0f RBX: ffff8c958756b800 RCX: 0000000000000007 2022-01-26T12:14:39.732512+00:00 localhost kernel: [ 3.168451] RDX: 8948530000441f0f RSI: 0000000000000092 RDI: ffff8c958756b820 2022-01-26T12:14:39.732513+00:00 localhost kernel: [ 3.168452] RBP: 0000000000000001 R08: 00000000000003a8 R09: 000000000000003d 2022-01-26T12:14:39.732513+00:00 localhost kernel: [ 3.168454] R10: 0000000000000263 R11: ffffb579007c7668 R12: ffff8c9c726a8000 2022-01-26T12:14:39.732513+00:00 localhost kernel: [ 3.168456] R13: ffff8c9c726a8000 R14: ffff8c958756b820 R15: ffff8c958756b800 2022-01-26T12:14:39.732514+00:00 localhost kernel: [ 3.168457] FS: 00007fcde7096980(0000) GS:ffff8c9c7e880000(0000) knlGS:0000000000000000 2022-01-26T12:14:39.732515+00:00 localhost kernel: [ 3.168459] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2022-01-26T12:14:39.732516+00:00 localhost kernel: [ 3.168460] CR2: 0000562eff0496b8 CR3: 00000007f5882000 CR4: 00000000003506e0 2022-01-26T12:14:39.732516+00:00 localhost kernel: [ 3.168462] Call Trace: 2022-01-26T12:14:39.732517+00:00 localhost kernel: [ 3.168486] radeon_vm_fini+0x2e/0x220 [radeon] 2022-01-26T12:14:39.732517+00:00 localhost kernel: [ 3.168505] radeon_driver_open_kms+0x56/0x1c0 [radeon] 2022-01-26T12:14:39.732517+00:00 localhost kernel: [ 3.168517] drm_file_alloc+0x1a1/0x240 [drm] 2022-01-26T12:14:39.732518+00:00 localhost kernel: [ 3.168528] drm_client_init+0xb1/0x140 [drm] 2022-01-26T12:14:39.732519+00:00 localhost kernel: [ 3.168537] drm_fb_helper_init+0x37/0x40 [drm_kms_helper] 2022-01-26T12:14:39.732520+00:00 localhost kernel: [ 3.168556] radeon_fbdev_init+0x8e/0x130 [radeon] 2022-01-26T12:14:39.732520+00:00 localhost kernel: [ 3.168575] radeon_modeset_init+0x46c/0x9e0 [radeon] 2022-01-26T12:14:39.732521+00:00 localhost kernel: [ 3.168591] radeon_driver_load_kms+0x8a/0x250 [radeon] 2022-01-26T12:14:39.732521+00:00 localhost kernel: [ 3.168601] drm_dev_register+0x150/0x1e0 [drm] 2022-01-26T12:14:39.732521+00:00 localhost kernel: [ 3.168618] radeon_pci_probe+0x130/0x1e0 [radeon] 2022-01-26T12:14:39.732523+00:00 localhost kernel: [ 3.168621] ? __pm_runtime_resume+0x54/0x80 2022-01-26T12:14:39.732524+00:00 localhost kernel: [ 3.168625] local_pci_probe+0x42/0x90 2022-01-26T12:14:39.732524+00:00 localhost kernel: [ 3.168628] ? pci_assign_irq+0x27/0x130 2022-01-26T12:14:39.732524+00:00 localhost kernel: [ 3.168630] pci_device_probe+0x10b/0x1c0 2022-01-26T12:14:39.732525+00:00 localhost kernel: [ 3.168633] really_probe+0xef/0x430 2022-01-26T12:14:39.732525+00:00 localhost kernel: [ 3.168635] driver_probe_device+0x110/0x120 2022-01-26T12:14:39.732527+00:00 localhost kernel: [ 3.168637] device_driver_attach+0x4f/0x60 2022-01-26T12:14:39.732527+00:00 localhost kernel: [ 3.168639] __driver_attach+0x51/0x130 2022-01-26T12:14:39.732528+00:00 localhost kernel: [ 3.168641] ? device_driver_attach+0x60/0x60 2022-01-26T12:14:39.732528+00:00 localhost kernel: [ 3.168643] bus_for_each_dev+0x76/0xc0 2022-01-26T12:14:39.732528+00:00 localhost kernel: [ 3.168645] bus_add_driver+0x144/0x220 2022-01-26T12:14:39.732529+00:00 localhost kernel: [ 3.168647] ? 0xffffffffc06f4000 2022-01-26T12:14:39.732529+00:00 localhost kernel: [ 3.168649] driver_register+0x5b/0xf0 2022-01-26T12:14:39.732531+00:00 localhost kernel: [ 3.168651] ? 0xffffffffc06f4000 2022-01-26T12:14:39.732531+00:00 localhost kernel: [ 3.168654] do_one_initcall+0x46/0x1f4 2022-01-26T12:14:39.732532+00:00 localhost kernel: [ 3.168656] ? kmem_cache_alloc_trace+0x18f/0x270 2022-01-26T12:14:39.732532+00:00 localhost kernel: [ 3.168659] ? do_init_module+0x22/0x22f 2022-01-26T12:14:39.732532+00:00 localhost kernel: [ 3.168662] ? __vunmap+0x1b5/0x210 2022-01-26T12:14:39.732533+00:00 localhost kernel: [ 3.168664] do_init_module+0x5b/0x22f 2022-01-26T12:14:39.732534+00:00 localhost kernel: [ 3.168666] load_module+0x1d81/0x2320 2022-01-26T12:14:39.732535+00:00 localhost kernel: [ 3.168669] ? __do_sys_init_module+0x160/0x190 2022-01-26T12:14:39.732535+00:00 localhost kernel: [ 3.168671] ? _cond_resched+0x15/0x40 2022-01-26T12:14:39.732535+00:00 localhost kernel: [ 3.168673] __do_sys_init_module+0x160/0x190 2022-01-26T12:14:39.732536+00:00 localhost kernel: [ 3.168676] do_syscall_64+0x5b/0x1e0 2022-01-26T12:14:39.732536+00:00 localhost kernel: [ 3.168678] entry_SYSCALL_64_after_hwframe+0x44/0xa9 2022-01-26T12:14:39.732536+00:00 localhost kernel: [ 3.168680] RIP: 0033:0x7fcde5e916da 2022-01-26T12:14:39.732539+00:00 localhost kernel: [ 3.168682] Code: 48 8b 0d b9 c7 2c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 86 c7 2c 00 f7 d8 64 89 01 48 2022-01-26T12:14:39.732540+00:00 localhost kernel: [ 3.168685] RSP: 002b:00007ffcf45aa2e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af 2022-01-26T12:14:39.732540+00:00 localhost kernel: [ 3.168687] RAX: ffffffffffffffda RBX: 0000562eff039820 RCX: 00007fcde5e916da 2022-01-26T12:14:39.732540+00:00 localhost kernel: [ 3.168689] RDX: 00007fcde67f179d RSI: 00000000002bcf00 RDI: 0000562eff4ade70 2022-01-26T12:14:39.732541+00:00 localhost kernel: [ 3.168690] RBP: 00007fcde67f179d R08: 0000000000000002 R09: 0000000000000000 2022-01-26T12:14:39.732541+00:00 localhost kernel: [ 3.168692] R10: 0000000000000003 R11: 0000000000000246 R12: 0000562eff4ade70 2022-01-26T12:14:39.732543+00:00 localhost kernel: [ 3.168693] R13: 0000562eff035f70 R14: 0000562eff00be10 R15: 0000562eff037af0 2022-01-26T12:14:39.732543+00:00 localhost kernel: [ 3.168695] Modules linked in: hid_generic usbhid sd_mod t10_pi radeon(+) i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core ttm xhci_pci xhci_hcd drm ahci libahci libata usbcore crc32c_intel wmi sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod msr 2022-01-26T12:14:39.732544+00:00 localhost kernel: [ 3.168705] Supported: Yes 2022-01-26T12:14:39.732544+00:00 localhost kernel: [ 3.168707] ---[ end trace b2aadc042ce7a558 ]--- 2022-01-26T12:14:39.732544+00:00 localhost kernel: [ 3.168709] RIP: 0010:rb_first_postorder+0xb/0x30 2022-01-26T12:14:39.732545+00:00 localhost kernel: [ 3.168711] Code: d2 74 f5 48 89 d0 48 8b 52 10 48 85 d2 75 f4 48 8b 50 08 48 85 d2 75 eb f3 c3 0f 1f 44 00 00 48 8b 17 48 85 d2 74 17 48 89 d0 <48> 8b 52 10 48 85 d2 75 f4 48 8b 50 08 48 85 d2 75 eb f3 c3 31 c0 2022-01-26T12:14:39.732547+00:00 localhost kernel: [ 3.168714] RSP: 0018:ffffb579007c7910 EFLAGS: 00010286 2022-01-26T12:14:39.732547+00:00 localhost kernel: [ 3.168716] RAX: 8948530000441f0f RBX: ffff8c958756b800 RCX: 0000000000000007 2022-01-26T12:14:39.732548+00:00 localhost kernel: [ 3.168717] RDX: 8948530000441f0f RSI: 0000000000000092 RDI: ffff8c958756b820 2022-01-26T12:14:39.732548+00:00 localhost kernel: [ 3.168719] RBP: 0000000000000001 R08: 00000000000003a8 R09: 000000000000003d 2022-01-26T12:14:39.732548+00:00 localhost kernel: [ 3.168720] R10: 0000000000000263 R11: ffffb579007c7668 R12: ffff8c9c726a8000 2022-01-26T12:14:39.732549+00:00 localhost kernel: [ 3.168722] R13: ffff8c9c726a8000 R14: ffff8c958756b820 R15: ffff8c958756b800 2022-01-26T12:14:39.732550+00:00 localhost kernel: [ 3.168724] FS: 00007fcde7096980(0000) GS:ffff8c9c7e880000(0000) knlGS:0000000000000000 2022-01-26T12:14:39.732551+00:00 localhost kernel: [ 3.168725] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2022-01-26T12:14:39.732551+00:00 localhost kernel: [ 3.168727] CR2: 0000562eff0496b8 CR3: 00000007f5882000 CR4: 00000000003506e0 This crash is new, introduced by the latest update, and repeatable. -- You are receiving this mail because: You are the assignee for the bug.

1 35

[Bug 1193640] [Rocket Lake UHD 730] absent nomodeset, 15.4 alpha installation hard locks at "Starting udev....".
by bugzilla_noreply＠suse.com 09 Feb '22

09 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193640 http://bugzilla.opensuse.org/show_bug.cgi?id=1193640#c25 --- Comment #25 from Felix Miata <mrmazda(a)earthlink.net> --- (In reply to Takashi Iwai from comment #21) > We have already kABI freeze, and only P1 bugs are accepted for the GM kernel. > The rest fixes (including this) are merged to the maintenance update kernel > that will be released right after GM release. It ought to be P1. People are going to migrate elsewhere when they try to install and get a lockup instead of a 15.4 installation started on their year+ old computers come May or June. It's not just my Asus B560M-A that's affected, but also Asus TUF GAMING Z590-PLUS WIFI[1], ASRock B560 Steel Legend and ASRock H570M-ITX/ac that we know of. Others reported this without including motherboard or PC model numbers. It looks like the whole B5xx series of products from Asus & ASRock are likely affected, and it could be half the FCLGA1200 series potentially. That'll be really lovely for openSUSE reputation if Fedora 36 and Ubuntu 22.04 get released in April with this fix in it but Leap a month or two later does not. This isn't just affecting use of the motherboard's own video ports. It also happens when a discrete GPU card is installed and attempt is made to use 2 displays. Which card I tested with I don't remember, but I doubt it matters. And for this reason, I'm betting the following thread was caused by this bug: <https://lists.opensuse.org/archives/list/support@lists.opensuse.org/thread/…> That user returned his Dell to the vendor because of his problem. Luckily he was a long time openSUSE user, so wasn't chased away by this. > > Is 15.3 going to get > > this fix backported? > Unlikely. The patches are not compatible with the older DRM code at all, > hence not trivial to backport. Which kernel repo should people enable to participate in 15.4 Alpha & Beta development? After all, I did report this specifically as a Leap (installation) bug, not TW. ;) > > It seems simpledrm is in it too. Is this correct? > It's not enabled as default. You still need to specify a special boot > option to boot with simpledrm (and the option is temporary, only for > (open)SUSE downstream). What option would that be? Not one in https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt I suppose. ;) [1] I spent quite a bit of time over more than a week trying to help someone with a TUF GAMING Z590-PLUS WIFI here: https://www.linuxquestions.org/questions/linux-desktop-74/dual-monitors-set… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195736] New: leap 15.3, latest kernels- lack exactly one cpu core (6core cpu)
by bugzilla_noreply＠suse.com 09 Feb '22

09 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195736 Bug ID: 1195736 Summary: leap 15.3, latest kernels- lack exactly one cpu core (6core cpu) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: abittner(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- My 6core CPU ( AMD Phenom(tm) II X6 1100T Processor )is apparently missing one of its cpu cores during kernel boot. The booting process only brings up a total of 5 cores. I think this came along around these latest newer kind (my gut feeling) of kernel-default releases that were suddenly named -150300. First I was thinking I was still affected by some of those amd/amd-gpu based troubles from the recent kernel releases, but fixed as of a few days, I also had to boot with nomodeset > https://bugzilla.opensuse.org/show_bug.cgi?id=1195142 but not any more after the fixed kernel. that earlier kernel with nomodeset needed for amd-based gpu also expressed these limited core numbers on this cpu. the most current kernel as of now also has the lacking core. currently I still have installed rpm: kernel-default-5.3.18-150300.59.43.1.x86_64 kernel-default-5.3.18-150300.59.46.1.x86_64 kernel-default-5.3.18-59.40.1.x86_64 running/booted: Linux linux 5.3.18-150300.59.46-default #1 SMP Tue Feb 1 16:19:33 UTC 2022 (fb6d1ec) x86_64 x86_64 x86_64 GNU/Linux cat /proc/cpuinfo | grep "processor" processor : 0 processor : 1 processor : 2 processor : 3 processor : 4 Kde application "KDE System Monitor", KSysGuard, also only shows 5 cores/cpus. same for top and other tools top - 15:46:43 up 16 min, 12 users, load average: 0.36, 0.84, 0.98 Tasks: 243 total, 2 running, 240 sleeping, 0 stopped, 1 zombie %Cpu0 : 3.4 us, 0.3 sy, 0.0 ni, 96.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu1 : 10.3 us, 2.6 sy, 0.0 ni, 86.8 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st %Cpu2 : 5.7 us, 4.7 sy, 0.0 ni, 89.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu3 : 11.8 us, 3.5 sy, 0.0 ni, 83.8 id, 0.6 wa, 0.0 hi, 0.3 si, 0.0 st %Cpu4 : 11.3 us, 4.0 sy, 0.0 ni, 84.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st sudo dmesg -e | grep CPU [sudo] password for root: [ +0.000003] smpboot: Allowing 6 CPUs, 1 hotplug CPUs [ +0.100440] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:6 nr_cpu_ids:6 nr_node_ids:1 [ +0.000144] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1 [ +0.000001] rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=6. [ +0.108315] process: Switch to broadcast mode on CPU0 [ +0.000007] smpboot: CPU0: AMD Phenom(tm) II X6 1100T Processor (family: 0x10, model: 0xa, stepping: 0x0) [ +0.000080] smp: Bringing up secondary CPUs ... [ +0.000001] .... node #0, CPUs: #1 [ -0.331118] process: Switch to broadcast mode on CPU1 [ -0.333662] process: Switch to broadcast mode on CPU2 [ -0.334194] process: Switch to broadcast mode on CPU3 [ -0.338196] process: Switch to broadcast mode on CPU4 [ +0.340744] smp: Brought up 1 node, 5 CPUs [ +0.000173] mtrr: your CPUs had inconsistent variable MTRR settings [ +0.000001] mtrr: probably your BIOS does not setup all CPUs. [ +0.000071] ledtrig-cpu: registered to indicate activity on CPUs [ +0.000025] microcode: CPU0: patch_level=0x010000dc [ +0.000010] microcode: CPU1: patch_level=0x010000dc [ +0.000009] microcode: CPU2: patch_level=0x010000dc [ +0.000004] microcode: CPU3: patch_level=0x010000dc [ +0.000007] microcode: CPU4: patch_level=0x010000dc hwinfo shows the same 5 activated cores. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1193640] [Rocket Lake UHD 730] absent nomodeset, 15.4 alpha installation hard locks at "Starting udev....".
by bugzilla_noreply＠suse.com 09 Feb '22

09 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193640 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sweiberg(a)suse.com | |) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195707] What with new CONFIG_FRAMEBUFFER_CONSOLE_LEGACY_ACCELERATION?
by bugzilla_noreply＠suse.com 09 Feb '22

09 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195707 https://bugzilla.suse.com/show_bug.cgi?id=1195707#c2 --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- I guess we don't care much for now, as we're targeting more on simpledrm enablement. So I'd say the current config is fine. We can enable them later only if anyone gives a strong argument that options must be inevitably enabled. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195707] What with new CONFIG_FRAMEBUFFER_CONSOLE_LEGACY_ACCELERATION?
by bugzilla_noreply＠suse.com 09 Feb '22

09 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195707 https://bugzilla.suse.com/show_bug.cgi?id=1195707#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson(a)suse.com, | |tiwai(a)suse.com, | |tzimmermann(a)suse.com Assignee|gfx-bugs(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- Honeslty, I don't know. I think Thomas, Patrik and Takashi are more competent here. -- You are receiving this mail because: You are the assignee for the bug.

1 0