Project

General

Profile

Actions

action #81366

closed

[s390x] kernel parameter "transparent_hugepage=never" in openQA for s390x

Added by AdaLovelace over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Enhancement to existing tests
Target version:
-
Start date:
2020-12-26
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

RĂ¼diger has removed the kernel parameter transparent_hugepage=never from OBS to test the bugfix https://bugzilla.opensuse.org/show_bug.cgi?id=1163684 and to verify it in openQA.
The Linux kernel is buildable, but we have got this new error message with a kernel panic:

    '[    0.210957] ima: No TPM chip found, activating TPM-bypass!                   ',
      '[    0.210960] ima: Allocated hash algorithm: sha256                            ',
      '[    0.210966] ima: No architecture policies found                              ',
      '[    0.210972] evm: Initialising EVM extended attributes:                       ',
      '[    0.210973] evm: security.selinux                                            ',
      '[    0.210974] evm: security.apparmor                                           ',
      '[    0.210975] evm: security.ima                                                ',
      '[    0.210976] evm: security.capability                                         ',
      '[    0.210977] evm: HMAC attrs: 0x1                                             ',
      '[    0.211243] VFS: Cannot open root device "(null)" or unknown-block(1,0): erro',
      'r -6                                                                            ',
      '[    0.211245] Please append a correct "root=" boot option; here are the availab',
      'le partitions:                                                                  ',
      '[    0.211246] Kernel panic - not syncing: VFS: Unable to mount root fs on unkno',
      'wn-block(1,0)                                                                   ',

Can we add this kernel parameter to openQA as a workaround? Or should we use another one now?

Actions #1

Updated by AdaLovelace about 3 years ago

  • Status changed from New to Closed

Obsolete now

Actions

Also available in: Atom PDF