September 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1190190] kmod: manpage of modprobe.d not correctly rendered
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190190 https://bugzilla.suse.com/show_bug.cgi?id=1190190#c7 --- Comment #7 from Michal Suchanek <msuchanek(a)suse.com> --- Thanks for the information. For me it does not suffice to change the path. Apparently I have both docbook4 and docbook5 and even with the docbook4 stylesheet path the man page is mangled. But if I sell OBS to use the docbook4 stylesheet it does not install docbook 5 and the manpage is rendered correctly when built in OBS. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190190] kmod: manpage of modprobe.d not correctly rendered
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190190 https://bugzilla.suse.com/show_bug.cgi?id=1190190#c6 --- Comment #6 from Thomas Schraitle <thomas.schraitle(a)suse.com> --- I've just tested my theory with the upstream DocBook source of xsltproc (see https://gitlab.gnome.org/GNOME/libxslt/-/blob/master/doc/xsltproc.xml) This source code refers DocBook v4.1.2 (quite old). I used this command line: /usr/bin/xsltproc \ -o xsltproc \ --nonet \ --stringparam man.output.quietly 1 \ --stringparam funcsynopsis.style "ansi" \ /usr/share/xml/docbook/stylesheet/nwalsh/current/manpages/docbook.xsl When I open the manpage, everything looks fine. Using the ns variant (nwalsh -> nwalsh5), I can see the effect that was described in comment#0. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190190] kmod: manpage of modprobe.d not correctly rendered
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190190 https://bugzilla.suse.com/show_bug.cgi?id=1190190#c5 --- Comment #5 from Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> --- (In reply to Pedro Monreal Gonzalez from comment #3) > (In reply to Michal Suchanek from comment #1) > > This is some tooling error. > > > > The man page comes correctly rendered in the upstream git, we alter the > > source, and then it comes mangled after it is regenerated from the XML > > > > Any idea what might have gone wrong with the xsltproc? > > > > /usr/bin/xsltproc \ > > -o modprobe.d.5 \ > > --nonet \ > > --stringparam man.output.quietly 1 \ > > --param funcsynopsis.style "'ansi'" \ > > /usr/share/xml/docbook/stylesheet/nwalsh5/current/manpages/docbook.xsl > > modprobe.d.xml > > Note: namesp. add : added namespace before processing modprobe.d > > Hi, @Michal. Looks like this recently accepted submissions is related: > https://build.opensuse.org/request/show/898998 > > I'm adding @Petr here in CC. Just for reference: * Upstream issue: https://gitlab.gnome.org/GNOME/libxslt/-/issues/31 * Upstream commit: https://gitlab.gnome.org/GNOME/libxslt/-/commit/f165525fe744e6fe3b377b480d6… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190190] kmod: manpage of modprobe.d not correctly rendered
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190190 https://bugzilla.suse.com/show_bug.cgi?id=1190190#c4 Thomas Schraitle <thomas.schraitle(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(thomas.schraitle@ | |suse.com) | --- Comment #4 from Thomas Schraitle <thomas.schraitle(a)suse.com> --- Just to to let you know a few details which could be important. 1. Different DocBook versions Nowadays, DocBook has two major versions: 4 or 5. Among other changes, the most prevalent difference is a namespace in version 5. This looks like this: <refentry xmlns="http://docbook.org/ns/docbook" ...> If you don't have this namespace it is DocBook 4 which usually looks like this: <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> <refentry ...> 2. Different DocBook stylesheets Furthermore, the DocBook project publishes also the DocBook stylesheets. These are XSLT stylesheets which can transform the XML input into the most common output formats (HTML, FO, or--in your case--manpage). The tricky part is that these stylesheets comes in a non-ns and ns variant (ns stands for namespace). Although the non-ns variant is made for DocBook 4 and the ns variant for DocBook 5, it normally doesn't matter. However, I discovered some strange effects when using the ns variant with DocBook 4 sources (or vice versa). To make a long story short: check which DocBook version you have and use the right stylesheet for the job. For example, in case you still use DocBook 4, you want to try the non-ns variant. Replace this path: /usr/share/xml/docbook/stylesheet/nwalsh5/current/manpages/docbook.xsl with this: /usr/share/xml/docbook/stylesheet/nwalsh/current/manpages/docbook.xsl (without the "5" in nwalsh) Hope that helps. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190190] kmod: manpage of modprobe.d not correctly rendered
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190190 https://bugzilla.suse.com/show_bug.cgi?id=1190190#c3 Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |petr.vorel(a)suse.com Flags|needinfo?(pmonrealgonzalez@ | |suse.com) | --- Comment #3 from Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> --- (In reply to Michal Suchanek from comment #1) > This is some tooling error. > > The man page comes correctly rendered in the upstream git, we alter the > source, and then it comes mangled after it is regenerated from the XML > > Any idea what might have gone wrong with the xsltproc? > > /usr/bin/xsltproc \ > -o modprobe.d.5 \ > --nonet \ > --stringparam man.output.quietly 1 \ > --param funcsynopsis.style "'ansi'" \ > /usr/share/xml/docbook/stylesheet/nwalsh5/current/manpages/docbook.xsl > modprobe.d.xml > Note: namesp. add : added namespace before processing modprobe.d Hi, @Michal. Looks like this recently accepted submissions is related: https://build.opensuse.org/request/show/898998 I'm adding @Petr here in CC. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190143] 5.13.13 does not detect firmware framebuffer resolution (regression against 5.13.6)
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190143 https://bugzilla.suse.com/show_bug.cgi?id=1190143#c8 Michael Chang <mchang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(arvidjaar(a)gmail.c | |om) --- Comment #8 from Michael Chang <mchang(a)suse.com> --- (In reply to Andrei Borzenkov from comment #5) > (In reply to Takashi Iwai from comment #4) > > ... and I guess it's about bug 1189782, which could be a regression by bug > > 1189879. > > This is about wrong grub configuration due to file location change; in my > case grub configuration remains the same (gfxmode is set statically in > /etc/default/grub by YaST). Hi Andrei, This still looks to me a problem introduced by bsc#1189782. If the gfxpayload is missing, the gfxmode used by grub won't be set for linux kernel thus expected VESA VGA mode is not enabled. Would you please check if regenerating grub.cfg with restored kernel config in prior location could help to fix problem or not ? > ln -srf /usr/lib/modules/5.13.13-1-default/config /boot/config-5.13.13-1-default > grub2-mkconfig -o /boot/grub2/grub.cfg Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190190] kmod: manpage of modprobe.d not correctly rendered
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190190 https://bugzilla.suse.com/show_bug.cgi?id=1190190#c2 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.schraitle(a)suse.com Flags| |needinfo?(thomas.schraitle@ | |suse.com) --- Comment #2 from Michal Suchanek <msuchanek(a)suse.com> --- We carry a patch to not download the template from the internet during build but use packaged template instead: --- kmod-27/man/Makefile.am~ 2018-01-31 18:10:59.569903733 +0100 +++ kmod-27/man/Makefile.am 2021-01-12 21:48:28.488571775 +0100 @@ -22,4 +22,4 @@ --nonet \ --stringparam man.output.quietly 1 \ --param funcsynopsis.style "'ansi'" \ - http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl $< + /usr/share/xml/docbook/stylesheet/nwalsh5/current/manpages/docbook.xsl $< Looks like there is non-trivial difference between these two files. Is the stylesheet we provide outdated or should the XML be adjusted? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190190] kmod: manpage of modprobe.d not correctly rendered
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190190 https://bugzilla.suse.com/show_bug.cgi?id=1190190#c1 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmonrealgonzalez(a)suse.com Flags| |needinfo?(pmonrealgonzalez@ | |suse.com) --- Comment #1 from Michal Suchanek <msuchanek(a)suse.com> --- This is some tooling error. The man page comes correctly rendered in the upstream git, we alter the source, and then it comes mangled after it is regenerated from the XML Any idea what might have gone wrong with the xsltproc? /usr/bin/xsltproc \ -o modprobe.d.5 \ --nonet \ --stringparam man.output.quietly 1 \ --param funcsynopsis.style "'ansi'" \ /usr/share/xml/docbook/stylesheet/nwalsh5/current/manpages/docbook.xsl modprobe.d.xml Note: namesp. add : added namespace before processing modprobe.d -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190188] New: AMD GPU reset causes sporadic system freezes with kernel 5.3.18-59.19
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190188 Bug ID: 1190188 Summary: AMD GPU reset causes sporadic system freezes with kernel 5.3.18-59.19 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: runger(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hardware: Company provided laptop Lenovo ThinkPad T14s, AMD Ryzen Pro 7. After updating kernel from 5.3.18-59.16 to .19 the following behavior is observerd: System boots, Gnomes starts, after a while (I have not seen a pattern) the whole system comes to a freeze. Hard reset is necessary to come out of that condition. 'dmesg' did not yield useful logs for me. Below are a collection of logs from /var/log/messages at the time of the freezes. ------ 2021-08-27T08:00:12.349977+02:00 localhost fwupd[2890]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) 2021-08-27T08:00:12.056977+02:00 localhost fwupd[2890]: 06:00:12:0056 FuEngine failed to add device usb:04:00:01:03:03: failed to read SPI chip ID: failed to read chip ID: endpoint stalled or request not supported 2021-08-27T08:00:10.696953+02:00 localhost gnome-shell[2242]: JS ERROR: TypeError: corner.set_style_pseudo_class is not a function#012updateElementPositions/connectCorner/corner._buttonStyleChangedSignalId<@/home/ralf/.local/share/gnome-shell/extensions/dash-to-panel@jderose9.github.com/panel.js:574:21#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:621:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:135:27#012SystemBackground/id<@resource:///org/gnome/shell/ui/background.js:526:17 021-08-27T07:44:33.816089+02:00 localhost kernel: [ 89.019320] xhci_hcd 0000:06:00.3: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 2021-08-27T07:44:46.862479+02:00 localhost kernel: [ 102.069523] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=518, emitted seq=521 2021-08-27T07:44:46.862482+02:00 localhost kernel: [ 102.069646] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 2013 thread gnome-shel:cs0 pid 2042 2021-08-27T07:44:46.862485+02:00 localhost kernel: [ 102.069652] amdgpu 0000:06:00.0: amdgpu: GPU reset begin! 2021-08-27T07:44:49.416068+02:00 localhost kernel: [ 104.622887] amdgpu 0000:06:00.0: amdgpu: failed send message: DisallowGfxOff (8) param: 0x00000000 response 0xffffffc2 2021-08-27T07:44:55.420076+02:00 localhost kernel: [ 110.623526] [drm:smu_v12_0_gfx_off_control [amdgpu]] *ERROR* disable gfxoff timeout and failed! 2021-08-27T07:44:55.420094+02:00 localhost kernel: [ 110.623532] amdgpu 0000:06:00.0: amdgpu: Failed to disable gfxoff! 2021-08-27T07:44:56.776102+02:00 localhost kernel: [ 111.979537] WARNING: CPU: 5 PID: 191 at ../drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn21/rn_clk_mgr_vbios_smu.c:104 rn_vbios_smu_send_msg_with_param+0xab/0x1e0 [amdgpu] 2021-08-27T07:44:59.372083+02:00 localhost kernel: [ 114.579105] amdgpu 0000:06:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state! 2021-08-27T07:44:59.372099+02:00 localhost kernel: [ 114.579109] amdgpu 0000:06:00.0: amdgpu: Failed to power gate SDMA! 2021-08-27T07:44:59.632106+02:00 localhost kernel: [ 114.839020] amdgpu 0000:06:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) 2021-08-27T07:45:02.188068+02:00 localhost kernel: [ 117.394329] amdgpu 0000:06:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state! 021-08-27T08:10:38.516112+02:00 localhost kernel: [ 636.719266] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20200925/psparse-531) 2021-08-27T08:10:38.516115+02:00 localhost kernel: [ 636.719274] ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20200925/psparse-531) 2021-08-27T08:10:38.516118+02:00 localhost kernel: [ 636.719279] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20200925/psparse-531) 021-08-27T07:56:51.724723+02:00 localhost kernel: [ 629.931089] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! 2021-08-27T07:56:56.856044+02:00 localhost kernel: [ 629.931264] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! 2021-08-27T07:56:56.856064+02:00 localhost kernel: [ 635.061135] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=70578, emitted seq=70580 2021-08-27T07:56:56.856070+02:00 localhost kernel: [ 635.061258] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 2374 thread Xwayland:cs0 pid 2375 2021-08-27T07:56:56.856073+02:00 localhost kernel: [ 635.061264] amdgpu 0000:06:00.0: amdgpu: GPU reset begin! 2021-08-27T07:56:57.160276+02:00 localhost kernel: [ 635.363002] [drm] free PSP TMR buffer 2021-08-27T07:56:57.192050+02:00 localhost kernel: [ 635.396068] amdgpu 0000:06:00.0: amdgpu: GPU reset succeeded, trying to resume 2021-08-27T07:56:57.192070+02:00 localhost kernel: [ 635.396258] [drm] PCIE GART of 1024M enabled (table at 0x000000F400900000). 2021-08-27T07:56:57.192075+02:00 localhost kernel: [ 635.396502] [drm] PSP is resuming... 2021-08-27T07:56:57.209813+02:00 localhost kernel: [ 635.416407] [drm] reserve 0x400000 from 0xf41f800000 for PSP TMR 2021-08-27T07:56:57.608048+02:00 localhost kernel: [ 635.811004] amdgpu 0000:06:00.0: amdgpu: SMU is resuming... 2021-08-27T07:56:57.608069+02:00 localhost kernel: [ 635.811834] amdgpu 0000:06:00.0: amdgpu: SMU is resumed successfully! 2021-08-27T07:56:57.852039+02:00 localhost kernel: [ 636.055472] [drm] kiq ring mec 2 pipe 1 q 0 2021-08-27T07:56:57.864034+02:00 localhost kernel: [ 636.069062] [drm] DMUB hardware initialized: version=0x01000000 2021-08-27T07:56:58.324045+02:00 localhost kernel: [ 636.194260] [drm] Failed to add display topology, DTM TA is not initialized. 2021-08-27T07:56:58.352064+02:00 localhost kernel: [ 636.527082] [drm] Failed to add display topology, DTM TA is not initialized. 2021-08-27T07:56:58.352089+02:00 localhost kernel: [ 636.556442] [drm] VCN decode and encode initialized successfully(under DPG Mode). 2021-08-27T07:56:58.352094+02:00 localhost kernel: [ 636.556590] [drm] JPEG decode initialized successfully. 2021-08-27T07:56:58.352097+02:00 localhost kernel: [ 636.556597] amdgpu 0000:06:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 2021-08-27T07:56:58.352100+02:00 localhost kernel: [ 636.556599] amdgpu 0000:06:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 2021-08-27T07:56:58.352104+02:00 localhost kernel: [ 636.556601] amdgpu 0000:06:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 2021-08-27T07:56:58.352107+02:00 localhost kernel: [ 636.556603] amdgpu 0000:06:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 2021-08-27T07:56:58.352109+02:00 localhost kernel: [ 636.556604] amdgpu 0000:06:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 2021-08-27T07:56:58.352112+02:00 localhost kernel: [ 636.556606] amdgpu 0000:06:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 2021-08-27T07:56:58.352115+02:00 localhost kernel: [ 636.556607] amdgpu 0000:06:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 2021-08-27T07:56:58.352117+02:00 localhost kernel: [ 636.556609] amdgpu 0000:06:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 2021-08-27T07:56:58.352120+02:00 localhost kernel: [ 636.556611] amdgpu 0000:06:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 2021-08-27T07:56:58.352123+02:00 localhost kernel: [ 636.556613] amdgpu 0000:06:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 2021-08-27T07:56:58.352125+02:00 localhost kernel: [ 636.556615] amdgpu 0000:06:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1 2021-08-27T07:56:58.352128+02:00 localhost kernel: [ 636.556616] amdgpu 0000:06:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1 2021-08-27T07:56:58.352131+02:00 localhost kernel: [ 636.556618] amdgpu 0000:06:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1 2021-08-27T07:56:58.352134+02:00 localhost kernel: [ 636.556619] amdgpu 0000:06:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1 2021-08-27T07:56:58.352137+02:00 localhost kernel: [ 636.556621] amdgpu 0000:06:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 2021-08-27T07:56:58.356074+02:00 localhost kernel: [ 636.562581] [drm] recover vram bo from shadow start 2021-08-27T07:56:58.356099+02:00 localhost kernel: [ 636.562584] [drm] recover vram bo from shadow done 2021-08-27T07:56:58.356102+02:00 localhost kernel: [ 636.562587] [drm] Skip scheduling IBs! 2021-08-27T07:56:58.356105+02:00 localhost kernel: [ 636.562648] amdgpu 0000:06:00.0: amdgpu: GPU reset(2) succeeded! 2021-08-27T07:56:58.356108+02:00 localhost kernel: [ 636.562683] [drm] Skip scheduling IBs! 2021-08-27T07:56:58.356129+02:00 localhost kernel: [ 636.562809] gmc_v9_0_process_interrupt: 10 callbacks suppressed 2021-08-27T07:56:58.356132+02:00 localhost kernel: [ 636.562818] amdgpu 0000:06:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:4 pasid:32771, for process Xwayland pid 2374 thread Xwayland:cs0 pid 2375) 2021-08-27T07:56:58.356136+02:00 localhost kernel: [ 636.562822] amdgpu 0000:06:00.0: amdgpu: in page starting at address 0x000080010082d000 from client 27 2021-08-27T07:56:58.356139+02:00 localhost kernel: [ 636.562824] amdgpu 0000:06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00440C11 2021-08-27T07:56:58.356142+02:00 localhost kernel: [ 636.562825] amdgpu 0000:06:00.0: amdgpu: Faulty UTCL2 client ID: 0x6 2021-08-27T07:56:58.356143+02:00 localhost kernel: [ 636.562827] amdgpu 0000:06:00.0: amdgpu: MORE_FAULTS: 0x1 2021-08-27T07:56:58.356146+02:00 localhost kernel: [ 636.562829] amdgpu 0000:06:00.0: amdgpu: WALKER_ERROR: 0x0 2021-08-27T07:56:58.356149+02:00 localhost kernel: [ 636.562831] amdgpu 0000:06:00.0: amdgpu: PERMISSION_FAULTS: 0x1 2021-08-27T07:56:58.356152+02:00 localhost kernel: [ 636.562835] amdgpu 0000:06:00.0: amdgpu: MAPPING_ERROR: 0x0 2021-08-27T07:56:58.356155+02:00 localhost kernel: [ 636.562839] amdgpu 0000:06:00.0: amdgpu: RW: 0x1 2021-08-27T07:56:58.357727+02:00 localhost kernel: [ 636.563630] amdgpu 0000:06:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:4 pasid:32771, for process Xwayland pid 2374 thread Xwayland:cs0 pid 2375) 2021-08-27T07:56:58.357740+02:00 localhost kernel: [ 636.563633] amdgpu 0000:06:00.0: amdgpu: in page starting at address 0x000080010082d000 from client 27 2021-08-27T07:57:18.136423+02:00 localhost kernel: [ 656.340199] BTRFS info (device nvme0n1p2): qgroup scan completed (inconsistency flag cleared) 2021-08-27T07:57:20.150733+02:00 localhost kernel: [ 658.357082] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=70588, emitted seq=70590 2021-08-27T07:57:20.150759+02:00 localhost kernel: [ 658.357269] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 2304 thread gnome-shel:cs0 pid 2336 2021-08-27T07:57:20.150763+02:00 localhost kernel: [ 658.357276] amdgpu 0000:06:00.0: amdgpu: GPU reset begin! ------- -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1190184] r8169 driver no longer negotiates 1Gb/s link
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190184 https://bugzilla.suse.com/show_bug.cgi?id=1190184#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anandrajan(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(anandrajan@gmail. | |com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you give hwinfo output and the output of dmesg from Leap 15.3? Also, could you try the latest upstream kernel from OBS Kernel:stable:Backport repo to see whether the problem persists? Note that this is an unofficial build, hence it won't boot with Secure Boot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190200] Severe graphics glitches in KDE applications when compositor is disabled
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190200 https://bugzilla.suse.com/show_bug.cgi?id=1190200#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Dup of bug 1190095? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190143] 5.13.13 does not detect firmware framebuffer resolution (regression against 5.13.6)
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190143 https://bugzilla.suse.com/show_bug.cgi?id=1190143#c7 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com, | |mchang(a)suse.com --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- OK, it means that VESA framebuffer isn't probed at all at early boot, and this is again something likely related with GRUB. Adding Michael and Jiri to Cc, who might have more insights about the recent changes on TW kernel/grub stuff. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190186] New: Cannot get to console with newer kernel and nvidia driver
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190186 Bug ID: 1190186 Summary: Cannot get to console with newer kernel and nvidia driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fred.blaise(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852296 --> http://bugzilla.opensuse.org/attachment.cgi?id=852296&action=edit dmesg Hi, Since 5.13.12-2-default, my boot sequence does not get to console anymore (I start my i3 desktop with startx). Same now 5.13.13-1-default. Everything worked fine with what I think was 5.13.8, which of course got delete today when I did a zypper dup... need to find that puppy again. Somewhere after I type my home partition encryption password, the screen freezes and never gets to the prompt. I can however ssh to the box. Everything looks normal then. My home partition is mounted. Just my console display seems stuck. Attached my dmesg and a picture of my frozen console. Removing the nvidia driver - thus using nouveau - it works ok. Just lacking vulkan api and graph performance. I know the nvidiadriver is a never ending debate, but here it is anyways. Wondering what changed in between 5.13.8 and .13. Maybe the delta is small enough that it triggers something in someone's mind. Thank you. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1190193] New: Sabre Lite i.MX6 image contains invalid modules in dracut configuration
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190193 Bug ID: 1190193 Summary: Sabre Lite i.MX6 image contains invalid modules in dracut configuration Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: victhor.foster(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852305 --> http://bugzilla.opensuse.org/attachment.cgi?id=852305&action=edit Proposed fix for configuration file The Sabre Lite prebuilt image for Tumblweed ARM contains references to non-existing modules in the file /etc/dracut.conf.d/sabrelite_modules.conf, such as "imx_ldb" and "imx_ipuv3_crtc". Replacing these entries with "imxdrm", "imx-ldb" and "dw_hdmi_imx" should provide equivalent functionality to what's intended. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189773] Keyboard / Mouse do not work when connected through MT VIKI Auto USB KVM Switch
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1189773 http://bugzilla.opensuse.org/show_bug.cgi?id=1189773#c17 --- Comment #17 from Thomas Vatter <thomas_vatter(a)web.de> --- (In reply to Takashi Iwai from comment #8) > Also, please check whether the recent upstream kernel works better or not. > Download kernel-default.rpm from > > http://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard/ > > and install it on your Leap 15.3 system, boot with it and test. > Note that this kernel is an unofficial build, and it won't boot with Secure > Boot. With the recent upstream kernel it's the same problem. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190007] openSUSE Kernel version is old, can't install on my laptop.
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190007 https://bugzilla.suse.com/show_bug.cgi?id=1190007#c15 --- Comment #15 from Chanryul Yoon <razorbacky(a)gmail.com> --- (In reply to Takashi Iwai from comment #11) > Thanks. Now can you boot with openSUSE Leap 15.3 rescue system or a live > image, run hwinfo and upload the output again for comparison? Updated. please check, thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190007] openSUSE Kernel version is old, can't install on my laptop.
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190007 https://bugzilla.suse.com/show_bug.cgi?id=1190007#c14 --- Comment #14 from Chanryul Yoon <razorbacky(a)gmail.com> --- Created attachment 852302 --> https://bugzilla.suse.com/attachment.cgi?id=852302&action=edit leap_rescure_hwinfo-dmesg -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190007] openSUSE Kernel version is old, can't install on my laptop.
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190007 https://bugzilla.suse.com/show_bug.cgi?id=1190007#c13 --- Comment #13 from Chanryul Yoon <razorbacky(a)gmail.com> --- Created attachment 852301 --> https://bugzilla.suse.com/attachment.cgi?id=852301&action=edit leap_rescure_hwinfo-short leap_rescure_hwinfo-short -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190007] openSUSE Kernel version is old, can't install on my laptop.
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190007 https://bugzilla.suse.com/show_bug.cgi?id=1190007#c12 --- Comment #12 from Chanryul Yoon <razorbacky(a)gmail.com> --- Created attachment 852300 --> https://bugzilla.suse.com/attachment.cgi?id=852300&action=edit leap_rescure_hwinfo leap_rescure_hwinfo -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190093] New: CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT in 5.14 causes reboot, kexec, suspend to panic
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190093 Bug ID: 1190093 Summary: CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT in 5.14 causes reboot, kexec, suspend to panic Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mkubecek(a)suse.com Found By: --- Blocker: --- On my Dell Latitude 7280, the new 5.14 option CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT causes all reboot, kexec, suspend to panic. Disabling that option makes it all work again. Provided it happens very late in the process, I don't know how to grab some logs. For the time being, I am going to turn the option off in master and stable. It remains to decide about 15-sp4. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1190184] r8169 driver no longer negotiates 1Gb/s link
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190184 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Network |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189773] Keyboard / Mouse do not work when connected through MT VIKI Auto USB KVM Switch
by bugzilla_noreply＠suse.com 03 Sep '21

03 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1189773 http://bugzilla.opensuse.org/show_bug.cgi?id=1189773#c16 --- Comment #16 from Thomas Vatter <thomas_vatter(a)web.de> --- (In reply to Takashi Iwai from comment #15) > If you switch back again from the graphics desktop to the text mode (e.g. > plug another or re-plug the keyboard directly to the USB d or re-plug the > same one to the USB port directly (without KVM), does it start working? > > The dmesg shows that the device have been recognized, at least. No, it doesn't. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190133] New: Bluetooth no longer working
by bugzilla_noreply＠suse.com 03 Sep '21

03 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190133 Bug ID: 1190133 Summary: Bluetooth no longer working Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: gantsevdenis(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Bluetooth is not launching/working anymore. When trying to restart, computer hangs. Current kernel: 5.13.13 [ 505.776532] ------------[ cut here ]------------ [ 505.776537] kernel BUG at mm/slub.c:316! [ 505.776556] invalid opcode: 0000 [#1] SMP PTI [ 505.776566] CPU: 2 PID: 6389 Comm: rfkill Not tainted 5.13.13-1-default #1 openSUSE Tumbleweed [ 505.776576] Hardware name: HP OMEN by HP Laptop/825B, BIOS F.23 10/13/2016 [ 505.776580] RIP: 0010:__slab_free+0x22d/0x420 [ 505.776593] Code: 00 44 8b 44 24 14 44 0f b6 54 24 26 48 8b 54 24 18 8b 74 24 20 48 89 44 24 08 44 0f b6 4c 24 27 48 8b 7c 24 28 e9 8d fe ff ff <0f> 0b 49 3b 54 24 28 0f 85 6b ff ff ff 49 89 5c 24 20 49 89 4c 24 [ 505.776600] RSP: 0018:ffffa26083bebcd0 EFLAGS: 00010246 [ 505.776609] RAX: ffff8c57c9757e70 RBX: ffff8c57c9757e00 RCX: ffff8c57c9757e00 [ 505.776615] RDX: 000000008010000b RSI: ffffd6ce4425d5c0 RDI: ffff8c57c0bcfe00 [ 505.776620] RBP: ffffa26083bebd78 R08: 0000000000000001 R09: ffffffffc1137b0b [ 505.776626] R10: ffff8c57dc8bea68 R11: 0000000000000a86 R12: ffffd6ce4425d5c0 [ 505.776631] R13: ffff8c57c9757e00 R14: ffff8c57c0bcfe00 R15: ffff8c57c9757e00 [ 505.776636] FS: 00007f930799b740(0000) GS:ffff8c5b2ed00000(0000) knlGS:0000000000000000 [ 505.776643] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 505.776649] CR2: 00007f534b40faf0 CR3: 000000014cd06005 CR4: 00000000003706e0 [ 505.776655] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 505.776660] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 505.776665] Call Trace: [ 505.776673] ? schedule_timeout+0x93/0x140 [ 505.776683] ? finish_wait+0x35/0x70 [ 505.776692] kmem_cache_free+0x423/0x450 [ 505.776703] ? btusb_shutdown_intel+0x5b/0x90 [btusb] [ 505.776717] btusb_shutdown_intel+0x5b/0x90 [btusb] [ 505.776730] hci_dev_do_close+0x487/0x5d0 [bluetooth] [ 505.776815] hci_rfkill_set_block+0x4c/0x90 [bluetooth] [ 505.776881] rfkill_set_block+0x92/0x160 [rfkill] [ 505.776895] rfkill_fop_write+0x138/0x1e0 [rfkill] [ 505.776908] vfs_write+0xbc/0x250 [ 505.776918] ksys_write+0xa7/0xe0 [ 505.776926] do_syscall_64+0x61/0x80 [ 505.776937] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 505.776946] RIP: 0033:0x7f9307a8f367 [ 505.776953] Code: 0d 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 505.776960] RSP: 002b:00007ffee8adaae8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 505.776969] RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f9307a8f367 [ 505.776974] RDX: 0000000000000009 RSI: 00007ffee8adaaff RDI: 0000000000000003 [ 505.776978] RBP: 000055766deb8054 R08: 000055766f501b50 R09: 00007f9307b61a60 [ 505.776983] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000003 [ 505.776987] R13: 0000000000000003 R14: 000055766deba8a0 R15: 00000000ffffffff [ 505.776996] Modules linked in: uinput rfcomm xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter bridge stp llc ccm nft_objref nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_tables ebtable_nat ebtable_broute af_packet ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security iscsi_ibft iscsi_boot_sysfs ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables bpfilter cmac algif_hash algif_skcipher af_alg bnep dmi_sysfs msr btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc bluetooth videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc ecdh_generic iwlmvm mac80211 intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp [ 505.777116] coretemp libarc4 kvm_intel iTCO_wdt intel_pmc_bxt ee1004 kvm mei_hdcp snd_ctl_led iwlwifi iTCO_vendor_support snd_hda_codec_realtek intel_rapl_msr snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi irqbypass r8169 cfg80211 snd_hda_intel realtek hp_wmi snd_intel_dspcfg platform_profile snd_intel_sdw_acpi i2c_i801 mdio_devres sparse_keymap efi_pstore wmi_bmof joydev libphy intel_lpss_pci snd_hda_codec i2c_smbus mei_me intel_lpss rfkill mei idma64 intel_pch_thermal snd_hda_core hp_accel snd_hwdep int3400_thermal processor_thermal_device lis3lv02d hp_wireless snd_pcm intel_pmc_core acpi_thermal_rel processor_thermal_rfim processor_thermal_mbox processor_thermal_rapl intel_rapl_common snd_timer thermal int340x_thermal_zone acpi_pad ac intel_soc_dts_iosf snd soundcore tiny_power_button nls_iso8859_1 nls_cp437 vfat fat fuse configfs hid_saitek hid_generic usbhid i915 nouveau crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_ttm_helper ttm mxm_wmi [ 505.777237] rtsx_pci_sdmmc xhci_pci xhci_pci_renesas i2c_algo_bit xhci_hcd drm_kms_helper mmc_core syscopyarea sysfillrect sysimgblt fb_sys_fops aesni_intel cec rc_core crypto_simd cryptd serio_raw rtsx_pci usbcore drm sr_mod cdrom battery wmi video button btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs [ 505.777302] ---[ end trace 718b559f5d5a6c69 ]--- [ 505.777308] RIP: 0010:__slab_free+0x22d/0x420 [ 505.777316] Code: 00 44 8b 44 24 14 44 0f b6 54 24 26 48 8b 54 24 18 8b 74 24 20 48 89 44 24 08 44 0f b6 4c 24 27 48 8b 7c 24 28 e9 8d fe ff ff <0f> 0b 49 3b 54 24 28 0f 85 6b ff ff ff 49 89 5c 24 20 49 89 4c 24 [ 505.777322] RSP: 0018:ffffa26083bebcd0 EFLAGS: 00010246 [ 505.777328] RAX: ffff8c57c9757e70 RBX: ffff8c57c9757e00 RCX: ffff8c57c9757e00 [ 505.777333] RDX: 000000008010000b RSI: ffffd6ce4425d5c0 RDI: ffff8c57c0bcfe00 [ 505.777338] RBP: ffffa26083bebd78 R08: 0000000000000001 R09: ffffffffc1137b0b [ 505.777342] R10: ffff8c57dc8bea68 R11: 0000000000000a86 R12: ffffd6ce4425d5c0 [ 505.777347] R13: ffff8c57c9757e00 R14: ffff8c57c0bcfe00 R15: ffff8c57c9757e00 [ 505.777351] FS: 00007f930799b740(0000) GS:ffff8c5b2ed00000(0000) knlGS:0000000000000000 [ 505.777358] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 505.777363] CR2: 00007f534b40faf0 CR3: 000000014cd06005 CR4: 00000000003706e0 [ 505.777369] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 505.777373] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 507.808363] Bluetooth: hci0: command 0x2005 tx timeout -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1190143] New: 5.13.13 does not detect firmware framebuffer resolution (regression against 5.13.6)
by bugzilla_noreply＠suse.com 03 Sep '21

03 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190143 Bug ID: 1190143 Summary: 5.13.13 does not detect firmware framebuffer resolution (regression against 5.13.6) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using QEMU 6.0.0 (compiled from sources) with PC BIOS and video -nodefaults \ -machine q35,accel=kvm \ -vga virtio -display gtk,gl=on,zoom-to-fit=off,show-cursor=on I set resolution 1280x960 in grub (set gfxmode=1280x960). Kernel 5.13.6 retains this resolution. Kernel 5.13.13 switches to tiny window with resolution 720x400 (I believe). No other changes in environment. Comparing dmesg output 5.13.6: Sep 01 20:27:08 tw kernel: [drm] pci: virtio-vga detected at 0000:00:01.0 Sep 01 20:27:08 tw kernel: checking generic (fe000000 4b0000) vs hw (fe000000 800000) Sep 01 20:27:08 tw kernel: fb0: switching to virtiodrmfb from VESA VGA Sep 01 20:27:08 tw kernel: Console: switching to colour dummy device 80x25 Sep 01 20:27:08 tw kernel: virtio-pci 0000:00:01.0: vgaarb: deactivate vga console Sep 01 20:27:08 tw kernel: [drm] features: +virgl +edid -resource_blob -host_visible Sep 01 20:27:08 tw kernel: [drm] number of scanouts: 1 Sep 01 20:27:08 tw kernel: [drm] number of cap sets: 2 Sep 01 20:27:08 tw kernel: [drm] cap set 0: id 1, max-version 1, max-size 308 Sep 01 20:27:08 tw kernel: [drm] cap set 1: id 2, max-version 2, max-size 696 Sep 01 20:27:08 tw kernel: [drm] Initialized virtio_gpu 0.1.0 0 for virtio0 on minor 0 Sep 01 20:27:08 tw kernel: Console: switching to colour frame buffer device 160x60 Sep 01 20:27:08 tw kernel: virtio_gpu virtio0: [drm] fb0: virtio_gpudrmfb frame buffer device 5.13.13: Sep 03 07:51:58 tw kernel: virtio-pci 0000:00:01.0: vgaarb: deactivate vga console Sep 03 07:51:58 tw systemd[1]: Reached target Initrd Root Device. Sep 03 07:51:58 tw kernel: Console: switching to colour dummy device 80x25 Sep 03 07:51:58 tw kernel: [drm] features: +virgl +edid -resource_blob -host_visible Sep 03 07:51:58 tw kernel: [drm] number of scanouts: 1 Sep 03 07:51:58 tw kernel: [drm] number of cap sets: 2 Sep 03 07:51:58 tw kernel: [drm] cap set 0: id 1, max-version 1, max-size 308 Sep 03 07:51:58 tw kernel: [drm] cap set 1: id 2, max-version 2, max-size 696 Sep 03 07:51:58 tw kernel: [drm] Initialized virtio_gpu 0.1.0 0 for virtio0 on minor 0 Sep 03 07:51:58 tw kernel: Console: switching to colour frame buffer device 90x25 Sep 03 07:51:58 tw kernel: virtio_gpu virtio0: [drm] fb0: virtio_gpudrmfb frame buffer device There is no "switching to virtiodrmfb from VESA VGA" line in 5.13.13. Full boot logs attached. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1189782] [Build 20210824] JeOS: gfxpayload missing in config
by bugzilla_noreply＠suse.com 03 Sep '21

03 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189782 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0