September 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1203751] New: missing signing time in pesign-obs-integration
by bugzilla_noreply＠suse.com 27 Sep '22

27 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203751 Bug ID: 1203751 Summary: missing signing time in pesign-obs-integration 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The linux kernel is verifying the module signing time if available against the signer certificate: �� if (test_bit(sinfo_has_signing_time, &sinfo->aa_set)) { �� if (sinfo->signing_time < sinfo->signer->valid_from || �� sinfo->signing_time > sinfo->signer->valid_to) { �� pr_warn("Message signed outside of X.509 validity window\n"); �� return -EKEYREJECTED; �� } �� } according to MLS our signed modules do not actually have the signing time set, which means this validation is skipped. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1203678] IRQ 40 Disabled due to error
by bugzilla_noreply＠suse.com 26 Sep '22

26 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203678 http://bugzilla.opensuse.org/show_bug.cgi?id=1203678#c6 John Shand <jshand2013(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #6 from John Shand <jshand2013(a)gmail.com> --- (In reply to Takashi Iwai from comment #5) > OK, then could you verify that the previous kernel doesn't show the problem > with the same operation, while it's reproducible with the latest kernel? > Once after confirmation, please take hwinfo output (and dmesg output) from > both working and non-working kernels. i have rebooted several times since this error occured. i am now wondering if it was a one-time-only error. i will flag this as resolved for me. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203678] IRQ 40 Disabled due to error
by bugzilla_noreply＠suse.com 26 Sep '22

26 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203678 https://bugzilla.suse.com/show_bug.cgi?id=1203678#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- OK, then could you verify that the previous kernel doesn't show the problem with the same operation, while it's reproducible with the latest kernel? Once after confirmation, please take hwinfo output (and dmesg output) from both working and non-working kernels. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203176] System constantly freezes
by bugzilla_noreply＠suse.com 26 Sep '22

26 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203176 https://bugzilla.suse.com/show_bug.cgi?id=1203176#c9 --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- My first suspect would be the nouveau driver. It's not trustworthy, unfortunately. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203490] Kernel panic stops 5.3.18-150300.59.90-default and above
by bugzilla_noreply＠suse.com 26 Sep '22

26 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203490 https://bugzilla.suse.com/show_bug.cgi?id=1203490#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |hare(a)suse.com --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Hmm, it's quite hard to judge without any logs. In anyway, tossed this to storage team, as NVMe is the first suspect. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202825] Haswell Laptop Completely Freezes After Waking up from Suspend
by bugzilla_noreply＠suse.com 26 Sep '22

26 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202825 https://bugzilla.suse.com/show_bug.cgi?id=1202825#c12 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ege.oz(a)tutanota.c | |om) | --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- Thanks, so it appears to be a regression since 5.16.x. The next is to figure out what change broke the behavior -- that's a tough task, as there have been over 15000 changes between 5.15 and 5.16 :-< Maybe it's about ACPI, and it's only 59, so manageable... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203747] New: Kernel hard lockup during boot
by bugzilla_noreply＠suse.com 26 Sep '22

26 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203747 Bug ID: 1203747 Summary: Kernel hard lockup during boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: msvec(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 861725 --> https://bugzilla.suse.com/attachment.cgi?id=861725&action=edit oops screenshot The most recent 15.4 kernel locks up hard on Dell Latitude 7430. OK: kernel-default-5.14.21-150400.22.1.x86_64 OK: kernel-default-5.14.21-150400.24.11.1.x86_64 locks during boot: kernel-default-5.14.21-150400.24.21.2.x86_64 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1202341] Raspi 4 (4GB): boots to blank screen with kernel 5.14.21-150400.24.11-default
by bugzilla_noreply＠suse.com 26 Sep '22

26 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202341 https://bugzilla.suse.com/show_bug.cgi?id=1202341#c10 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tzimmermann(a)suse.com Assignee|ivan.ivanov(a)suse.com |kernel-bugs(a)opensuse.org --- Comment #10 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- I have back ported some of the missing upstream VC4 and DRM patches, which where looking related. Unfortunately issue still persist. I am afraid I can't help much more. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203748] Laptop very slow in battery mode (Lenovo Thinkpad T470)
by bugzilla_noreply＠suse.com 26 Sep '22

26 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203748 http://bugzilla.opensuse.org/show_bug.cgi?id=1203748#c1 --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- For example when watching video https://www.youtube.com/watch?v=hZ2joF8_1QY in 1440p60 when switching from power (running absolutely fluently) to battery mode this is switching to 60 sec/frame (!) or even worse! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203713] New: kernel 5.14.21-150400.24.21-default leads to sporadic cpu stucks
by bugzilla_noreply＠suse.com 25 Sep '22

25 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203713 Bug ID: 1203713 Summary: kernel 5.14.21-150400.24.21-default leads to sporadic cpu stucks Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ralf.koelmel(a)kit.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 861709 --> http://bugzilla.opensuse.org/attachment.cgi?id=861709&action=edit example of the console traces since update from kernel 5.14.21-150400.24.18-default to 5.14.21-150400.24.21-default i'm observing on different systems (Dualprocessorsystem with AMD Opteron(tm) Processor 6172,Dualprocessorsystem AMD EPYC 7742 64-Core Processor, VMs) sporadic kernel stucks during runtime. On the console there are traces in the manner [155369.287478][ C30] watchdog: BUG: soft lockup - CPU#30 stuck for 24614s! [kworker/u134:0:49915] Login on console is possible, but a command can't be executed without blocking. The network is dead. No critical messages before or at the date when this state is occuring. No message is written into system log after reaching this state. The systems are mainly compute systems, but according to monitoring they were in idle mode. For now i've reverted all systems to the previous kernel which doesn't show this problem. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1203718] New: USB/UAS device resets happening with external SATA III 6G HDD enclosure
by bugzilla_noreply＠suse.com 25 Sep '22

25 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203718 Bug ID: 1203718 Summary: USB/UAS device resets happening with external SATA III 6G HDD enclosure Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: eecdc3.opensuse(a)coders-haven.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Dear openSUSE community, I am unfortunately experiencing frequent USB/UAS device resets with my new FANTEC DB-ALU31, which according to its product name (ASM235) is using an ASM235CM chipset from ASMedia. The relevant output from `lsusb -vt` is as follows: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 10000M ID 0bda:0423 Realtek Semiconductor Corp. |__ Port 3: Dev 3, If 0, Class=Mass Storage, Driver=uas, 10000M ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge The device is detected and can be mounted without issues but during regular use it may slow down or freeze programs that try to access it with output in /var/log/messages looking like: 2022-09-24T10:16:25.112084+02:00 kernel: [ 6192.198327][T26507] sd 0:0:0:0: [sda] tag#14 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD OUT 2022-09-24T10:16:25.112102+02:00 kernel: [ 6192.198336][T26507] sd 0:0:0:0: [sda] tag#14 CDB: Write(16) 8a 00 00 00 00 02 46 07 2f 5f 00 00 00 18 00 00 2022-09-24T10:16:25.112104+02:00 kernel: [ 6192.198492][T26507] sd 0:0:0:0: [sda] tag#13 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD OUT 2022-09-24T10:16:25.112106+02:00 kernel: [ 6192.198498][T26507] sd 0:0:0:0: [sda] tag#13 CDB: Write(16) 8a 00 00 00 00 02 46 07 2f 37 00 00 00 28 00 00 2022-09-24T10:16:25.112108+02:00 kernel: [ 6192.198644][T26507] sd 0:0:0:0: [sda] tag#12 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD OUT 2022-09-24T10:16:25.112109+02:00 kernel: [ 6192.198650][T26507] sd 0:0:0:0: [sda] tag#12 CDB: Write(16) 8a 00 00 00 00 02 46 07 2f 17 00 00 00 20 00 00 2022-09-24T10:16:25.112111+02:00 kernel: [ 6192.198800][T26507] sd 0:0:0:0: [sda] tag#11 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD OUT 2022-09-24T10:16:25.112126+02:00 kernel: [ 6192.198806][T26507] sd 0:0:0:0: [sda] tag#11 CDB: Write(16) 8a 00 00 00 00 02 46 07 2e f7 00 00 00 20 00 00 2022-09-24T10:16:25.112127+02:00 kernel: [ 6192.198943][T26507] sd 0:0:0:0: [sda] tag#10 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD OUT 2022-09-24T10:16:25.112128+02:00 kernel: [ 6192.198949][T26507] sd 0:0:0:0: [sda] tag#10 CDB: Write(16) 8a 00 00 00 00 02 46 07 2e e7 00 00 00 10 00 00 2022-09-24T10:16:25.112129+02:00 kernel: [ 6192.199094][T26507] sd 0:0:0:0: [sda] tag#9 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT 2022-09-24T10:16:25.112130+02:00 kernel: [ 6192.199101][T26507] sd 0:0:0:0: [sda] tag#9 CDB: Write(16) 8a 00 00 00 00 02 46 07 2e c7 00 00 00 20 00 00 2022-09-24T10:16:25.112130+02:00 kernel: [ 6192.199278][T26507] sd 0:0:0:0: [sda] tag#8 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT 2022-09-24T10:16:25.112131+02:00 kernel: [ 6192.199285][T26507] sd 0:0:0:0: [sda] tag#8 CDB: Write(16) 8a 00 00 00 00 02 46 07 2e bf 00 00 00 08 00 00 2022-09-24T10:16:25.112133+02:00 kernel: [ 6192.199393][T26507] sd 0:0:0:0: [sda] tag#7 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN 2022-09-24T10:16:25.112134+02:00 kernel: [ 6192.199397][T26507] sd 0:0:0:0: [sda] tag#7 CDB: Read(16) 88 00 00 00 00 02 06 96 c9 d8 00 00 00 07 00 00 2022-09-24T10:16:25.112135+02:00 kernel: [ 6192.200510][T26507] sd 0:0:0:0: [sda] tag#6 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 2022-09-24T10:16:25.112136+02:00 kernel: [ 6192.200513][T26507] sd 0:0:0:0: [sda] tag#6 CDB: Read(16) 88 00 00 00 00 02 06 96 c5 df 00 00 03 f9 00 00 2022-09-24T10:16:25.116046+02:00 kernel: [ 6192.204015][T26507] sd 0:0:0:0: [sda] tag#5 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD IN 2022-09-24T10:16:25.116063+02:00 kernel: [ 6192.204022][T26507] sd 0:0:0:0: [sda] tag#5 CDB: Read(16) 88 00 00 00 00 02 06 96 cd d8 00 00 00 07 00 00 2022-09-24T10:16:25.120123+02:00 kernel: [ 6192.207464][T26507] sd 0:0:0:0: [sda] tag#4 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN 2022-09-24T10:16:25.120131+02:00 kernel: [ 6192.207472][T26507] sd 0:0:0:0: [sda] tag#4 CDB: Read(16) 88 00 00 00 00 02 06 96 c9 df 00 00 03 f9 00 00 2022-09-24T10:16:25.148038+02:00 kernel: [ 6192.234339][T25745] scsi host0: uas_eh_device_reset_handler start 2022-09-24T10:16:25.228043+02:00 kernel: [ 6192.314872][T25745] usb 4-1.3: reset SuperSpeed Plus Gen 2x1 USB device number 3 using xhci_hcd 2022-09-24T10:16:25.248055+02:00 kernel: [ 6192.337003][T25745] scsi host0: uas_eh_device_reset_handler success After I added a quirk to /etc/modprobe.d/ via 'options usb-storage quirks=174c:55aa:u' to ignore UASP support, the occurrance rate of the resets seems to have reduced but they still occur: 2022-09-24T10:52:44.552258+02:00 kernel: [ 545.639051][ T3616] usb 4-1.3: reset SuperSpeed Plus Gen 2x1 USB device number 3 using xhci_hcd 2022-09-24T10:52:44.572116+02:00 kernel: [ 545.660702][ C1] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s 2022-09-24T10:52:44.572139+02:00 kernel: [ 545.660715][ C1] sd 0:0:0:0: [sda] tag#0 CDB: Read(16) 88 00 00 00 00 01 f4 f4 1a 37 00 00 07 f9 00 00 2022-09-24T10:52:44.572143+02:00 kernel: [ 545.660719][ C1] blk_update_request: I/O error, dev sda, sector 8404605495 op 0x0:(READ) flags 0x84700 phys_seg 29 prio class 0 I am using an up-to-date installation of openSUSE Leap 15.4 running Linux 5.14.21-150400.24.21-default and any help debugging this further will be appreciated. (The fact that the device string shown by `lsusb` makes no mention of the updated chipset leads me to believe that support for this chipset has not hit the kernel yet, but I am not familiar with the USB kernel driver nor with debugging it.) Note that I have already checked the S.M.A.R.T. attributes and there does not appear to be a problem with the device itself. I can also use the device without problems with Windows 10 21H2, even after extended use. Thanks in advance for your assistance! -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1203176] System constantly freezes
by bugzilla_noreply＠suse.com 24 Sep '22

24 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203176 https://bugzilla.suse.com/show_bug.cgi?id=1203176#c8 --- Comment #8 from macias - <bluedzins(a)wp.pl> --- Created attachment 861711 --> https://bugzilla.suse.com/attachment.cgi?id=861711&action=edit dmesg -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203176] System constantly freezes
by bugzilla_noreply＠suse.com 24 Sep '22

24 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203176 https://bugzilla.suse.com/show_bug.cgi?id=1203176#c7 macias - <bluedzins(a)wp.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(bluedzins(a)wp.pl) | --- Comment #7 from macias - <bluedzins(a)wp.pl> --- Created attachment 861710 --> https://bugzilla.suse.com/attachment.cgi?id=861710&action=edit hwinfo $ cat /proc/version Linux version 5.14.21-150400.24.18-default (geeko@buildhost) (gcc (SUSE Linux) 7.5.0, GNU ld (GNU Binutils; SUSE Linux Enterprise 15) 2.37.20211103-150100.7.37) #1 SMP PREEMPT_DYNAMIC Thu Aug 4 14:17:48 UTC 2022 (e9f7bfc) > The latest Leap 15.4 update kernel (*-150400.24.21.2) has a bug on some systems > with intel_iommu. You can try the older version (*-150400.24.18.1) instead. It looks like I am running the older version already. I will attach dmesg output in a second. Other than that I don't know what to tell about this computer. Is CPU info useful? model name : Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203678] IRQ 40 Disabled due to error
by bugzilla_noreply＠suse.com 23 Sep '22

23 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203678 http://bugzilla.opensuse.org/show_bug.cgi?id=1203678#c4 --- Comment #4 from John Shand <jshand2013(a)gmail.com> --- (In reply to Takashi Iwai from comment #3) > Is it a regression, i.e. did the problem appear with the earlier kernels? this issue to my knowledge didn't happen on previous kernels. it could be btrfs doing its usual cleanup and quota rescans. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203691] [Build 20220922] openQA test fails in cve-2018-13405
by bugzilla_noreply＠suse.com 23 Sep '22

23 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203691 https://bugzilla.suse.com/show_bug.cgi?id=1203691#c3 --- Comment #3 from Anthony Iliopoulos <ailiopoulos(a)suse.com> --- (In reply to Anthony Iliopoulos from comment #2) > (In reply to Martin Doucha from comment #1) > > The failure is in a new subtest which was added yesterday. The kernel is > > missing a patch. According to KOTD results, all SLE versions up to SLE-15SP3 > > are affected. SLE-15SP4 appears to be fixed already. The bug is present only > > in the XFS filesystem. > > SLE-12SP4: https://openqa.suse.de/tests/9586412#step/cve-2018-13405/8 > > SLE-15SP3: https://openqa.suse.de/tests/9589714#step/cve-2018-13405/8 > > SLE-15SP4 (not affected): > > https://openqa.suse.de/tests/9589657#step/cve-2018-13405/8 > > Why is this being detected on the tumbleweed (upstream) kernel, though? Ah I see why, 1639a49ccdce and 426b4ca2d6a5 were merged in v6.0-rc1, and apparently have not been backported to stable. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203691] [Build 20220922] openQA test fails in cve-2018-13405
by bugzilla_noreply＠suse.com 23 Sep '22

23 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203691 https://bugzilla.suse.com/show_bug.cgi?id=1203691#c2 Anthony Iliopoulos <ailiopoulos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ailiopoulos(a)suse.com --- Comment #2 from Anthony Iliopoulos <ailiopoulos(a)suse.com> --- (In reply to Martin Doucha from comment #1) > The failure is in a new subtest which was added yesterday. The kernel is > missing a patch. According to KOTD results, all SLE versions up to SLE-15SP3 > are affected. SLE-15SP4 appears to be fixed already. The bug is present only > in the XFS filesystem. > SLE-12SP4: https://openqa.suse.de/tests/9586412#step/cve-2018-13405/8 > SLE-15SP3: https://openqa.suse.de/tests/9589714#step/cve-2018-13405/8 > SLE-15SP4 (not affected): > https://openqa.suse.de/tests/9589657#step/cve-2018-13405/8 Why is this being detected on the tumbleweed (upstream) kernel, though? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203691] [Build 20220922] openQA test fails in cve-2018-13405
by bugzilla_noreply＠suse.com 23 Sep '22

23 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203691 https://bugzilla.suse.com/show_bug.cgi?id=1203691#c1 Martin Doucha <martin.doucha(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.doucha(a)suse.com --- Comment #1 from Martin Doucha <martin.doucha(a)suse.com> --- The failure is in a new subtest which was added yesterday. The kernel is missing a patch. According to KOTD results, all SLE versions up to SLE-15SP3 are affected. SLE-15SP4 appears to be fixed already. The bug is present only in the XFS filesystem. SLE-12SP4: https://openqa.suse.de/tests/9586412#step/cve-2018-13405/8 SLE-15SP3: https://openqa.suse.de/tests/9589714#step/cve-2018-13405/8 SLE-15SP4 (not affected): https://openqa.suse.de/tests/9589657#step/cve-2018-13405/8 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203691] New: [Build 20220922] openQA test fails in cve-2018-13405
by bugzilla_noreply＠suse.com 23 Sep '22

23 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203691 Bug ID: 1203691 Summary: [Build 20220922] openQA test fails in cve-2018-13405 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2725391/modules/cve- 2018-13405/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation HINT: You _MAY_ be missing kernel fixes: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… HINT: You _MAY_ be vulnerable to CVE(s): https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-13405 What's a bit confusing here is that we did not have a new kernel in this snapshot openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-cve@uefi_virtio-2G fails in [cve-2018-13405](https://openqa.opensuse.org/tests/2725391/modules/cve-2018-… ## Test suite description ## Reproducible Fails since (at least) Build [20220922](https://openqa.opensuse.org/tests/2724510) ## Expected result Last good: [20220921](https://openqa.opensuse.org/tests/2717006) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203678] IRQ 40 Disabled due to error
by bugzilla_noreply＠suse.com 23 Sep '22

23 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203678 http://bugzilla.opensuse.org/show_bug.cgi?id=1203678#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jshand2013(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(jshand2013@gmail. | |com) --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Is it a regression, i.e. did the problem appear with the earlier kernels? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203678] IRQ 40 Disabled due to error
by bugzilla_noreply＠suse.com 23 Sep '22

23 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203678 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |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 1203539] Boot hangs with update to kernel 5.14.21-15040.24.21-default
by bugzilla_noreply＠suse.com 23 Sep '22

23 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203539 http://bugzilla.opensuse.org/show_bug.cgi?id=1203539#c15 --- Comment #15 from John Carrick Smith <jcarricksmith(a)gmail.com> --- Should I have mentioned that the cooling fan on the computer runs unusually fast after a the hang in the boot process? Suggesting a tight loop stuck in a processor? This may be clear from the journals but they don't mean much to me. John -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203558] openSUSE support for Renesas RZ/G2M
by bugzilla_noreply＠suse.com 23 Sep '22

23 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c7 --- Comment #7 from Dirk Mueller <dmueller(a)suse.com> --- (In reply to Duy Hua from comment #6) > Excuse me, Did you know when we have an OS distro for a test? my changes for tumbleweed are still under review. its a matter of days, hopefully. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201845] mt7921e 0000:03:00.0: driver own failed
by bugzilla_noreply＠suse.com 23 Sep '22

23 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201845 http://bugzilla.opensuse.org/show_bug.cgi?id=1201845#c13 --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- Such a hang must be avoided, of course. Care to report it to the upstream? The best would be over linux-wireless ML. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201845] mt7921e 0000:03:00.0: driver own failed
by bugzilla_noreply＠suse.com 23 Sep '22

23 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201845 http://bugzilla.opensuse.org/show_bug.cgi?id=1201845#c12 --- Comment #12 from Atri Bhattacharya <badshah400(a)gmail.com> --- Created attachment 861675 --> http://bugzilla.opensuse.org/attachment.cgi?id=861675&action=edit journal output from failed session OK I see, the kernel does not 'oops' indeed; however, the driver failure apparently stops everything from working... even `halt` does not work and I had eventually do the Alt+SysRq+B sequence to reboot. That the latter worked is perhaps further proof that the kernel does not indeed crash, nevertheless for all intents and purposes the session is irrecoverably dead. Would be nice if when the wifi driver failed, I could still safely power the machine off. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203558] openSUSE support for Renesas RZ/G2M
by bugzilla_noreply＠suse.com 22 Sep '22

22 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c6 --- Comment #6 from Duy Hua <duy.hua-duc(a)banvien.com.vn> --- Excuse me, Did you know when we have an OS distro for a test? -- You are receiving this mail because: You are the assignee for the bug.

1 0