Project

General

Profile

Actions
Copy link

action #117466

open

[qe-core] leap 15.5 memtest fails to boot

Added by lkocman over 1 year ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-09-30
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

Hello

It seems that in all scenarios leap 15.5 memtest fails to boot

openQA test in scenario opensuse-15.5-NET-x86_64-memtest@64bit fails in
memtest

Test suite description

Reproducible

Fails since (at least) Build 296.1 (current job)

Expected result

Last good: 293.1 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by maritawerner over 1 year ago

  • Subject changed from leap 15.5 memtest fails to boot to [qe-core] leap 15.5 memtest fails to boot
Actions
Copy link
 #2

Updated by mlin7442 over 1 year ago

This is an sporadic issue.

Actions
Copy link
 #3

Updated by openqa_review over 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: memtest
https://openqa.opensuse.org/tests/2852303#step/memtest/1

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

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #4

Updated by szarate over 1 year ago

Looks to me like a bug, now the fun part would be to debug qemu to find out where does it hides, Max have you seen this?

[2022-09-30T06:27:26.840367+02:00] [debug] QEMU: QEMU emulator version 6.2.0 (SUSE Linux Enterprise 15)
...
[2022-09-30T06:29:02.469932+02:00] [debug] QEMU: KVM internal error. Suberror: 1
[2022-09-30T06:29:02.469999+02:00] [debug] QEMU: emulation failure
[2022-09-30T06:29:02.470034+02:00] [debug] QEMU: EAX=00008bd4 EBX=0000a845 ECX=00000000 EDX=00000080
[2022-09-30T06:29:02.470066+02:00] [debug] QEMU: ESI=00001800 EDI=00008400 EBP=00008bd4 ESP=00153ffc
[2022-09-30T06:29:02.470096+02:00] [debug] QEMU: EIP=ff06f651 EFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
[2022-09-30T06:29:02.470125+02:00] [debug] QEMU: ES =0028 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
[2022-09-30T06:29:02.470155+02:00] [debug] QEMU: CS =0020 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
[2022-09-30T06:29:02.470184+02:00] [debug] QEMU: SS =0028 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
[2022-09-30T06:29:02.470213+02:00] [debug] QEMU: DS =0028 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
[2022-09-30T06:29:02.470242+02:00] [debug] QEMU: FS =0000 00000000 00000000 00000000
[2022-09-30T06:29:02.470269+02:00] [debug] QEMU: GS =0000 00000000 00000000 00000000
[2022-09-30T06:29:02.470296+02:00] [debug] QEMU: LDT=0000 00000000 00000000 00000000
[2022-09-30T06:29:02.470325+02:00] [debug] QEMU: TR =0008 00000580 00000067 00008b00 DPL=0 TSS32-busy
[2022-09-30T06:29:02.470353+02:00] [debug] QEMU: GDT=     0000abb0 0000002f
[2022-09-30T06:29:02.470381+02:00] [debug] QEMU: IDT=     000030b8 000007ff
[2022-09-30T06:29:02.470411+02:00] [debug] QEMU: CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
[2022-09-30T06:29:02.470442+02:00] [debug] QEMU: DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
[2022-09-30T06:29:02.470470+02:00] [debug] QEMU: DR6=00000000ffff0ff0 DR7=0000000000000400
[2022-09-30T06:29:02.470497+02:00] [debug] QEMU: EFER=0000000000000000
[2022-09-30T06:29:02.470538+02:00] [debug] QEMU: Code=?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? <??> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
[2022-09-30T06:29:02.470673+02:00] [debug] QEMU:  ??
Actions
Copy link
 #5

Updated by mlin7442 over 1 year ago

szarate wrote:

Looks to me like a bug, now the fun part would be to debug qemu to find out where does it hides, Max have you seen this?

[2022-09-30T06:27:26.840367+02:00] [debug] QEMU: QEMU emulator version 6.2.0 (SUSE Linux Enterprise 15)
...
[2022-09-30T06:29:02.469932+02:00] [debug] QEMU: KVM internal error. Suberror: 1
[2022-09-30T06:29:02.469999+02:00] [debug] QEMU: emulation failure
[2022-09-30T06:29:02.470034+02:00] [debug] QEMU: EAX=00008bd4 EBX=0000a845 ECX=00000000 EDX=00000080
[2022-09-30T06:29:02.470066+02:00] [debug] QEMU: ESI=00001800 EDI=00008400 EBP=00008bd4 ESP=00153ffc
[2022-09-30T06:29:02.470096+02:00] [debug] QEMU: EIP=ff06f651 EFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
[2022-09-30T06:29:02.470125+02:00] [debug] QEMU: ES =0028 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
[2022-09-30T06:29:02.470155+02:00] [debug] QEMU: CS =0020 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
[2022-09-30T06:29:02.470184+02:00] [debug] QEMU: SS =0028 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
[2022-09-30T06:29:02.470213+02:00] [debug] QEMU: DS =0028 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
[2022-09-30T06:29:02.470242+02:00] [debug] QEMU: FS =0000 00000000 00000000 00000000
[2022-09-30T06:29:02.470269+02:00] [debug] QEMU: GS =0000 00000000 00000000 00000000
[2022-09-30T06:29:02.470296+02:00] [debug] QEMU: LDT=0000 00000000 00000000 00000000
[2022-09-30T06:29:02.470325+02:00] [debug] QEMU: TR =0008 00000580 00000067 00008b00 DPL=0 TSS32-busy
[2022-09-30T06:29:02.470353+02:00] [debug] QEMU: GDT=     0000abb0 0000002f
[2022-09-30T06:29:02.470381+02:00] [debug] QEMU: IDT=     000030b8 000007ff
[2022-09-30T06:29:02.470411+02:00] [debug] QEMU: CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
[2022-09-30T06:29:02.470442+02:00] [debug] QEMU: DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
[2022-09-30T06:29:02.470470+02:00] [debug] QEMU: DR6=00000000ffff0ff0 DR7=0000000000000400
[2022-09-30T06:29:02.470497+02:00] [debug] QEMU: EFER=0000000000000000
[2022-09-30T06:29:02.470538+02:00] [debug] QEMU: Code=?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? <??> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
[2022-09-30T06:29:02.470673+02:00] [debug] QEMU:  ??

hmm... not on my radar, this fail is really sporadically, see DVD: https://openqa.opensuse.org/tests/2866102#next_previous and netiso: https://openqa.opensuse.org/tests/2864514#next_previous

Actions
Copy link
 #6

Updated by openqa_review over 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: memtest
https://openqa.opensuse.org/tests/2902759#step/memtest/1

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

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #7

Updated by slo-gin about 1 month ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions
Copy link

Also available in: Atom PDF