Project

General

Profile

Actions
Copy link

action #48419

closed

action #47219: [functional][u][easy] test fails in keymap_or_locale - rogue workqueue lockup

[functional][u] Hunt for the rogue workqueue

Added by szarate about 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
SLindoMansilla
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 23
Start date:
2019-02-26
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Now that we are able to get the lockup: https://openqa.opensuse.org/tests/862930#step/mate_terminal/7 I guess it's time to actively look to the cause of the problem or at least figure out if there's already a bugzilla ticket for this.

Suggestions

  • Search bugzilla for this kind of problems, if there's no bug, report one.
  • Read the logs and try to find useful kernel messages

Related issues 2 (0 open — 2 closed)

Has duplicate openQA Tests - action #48689: [functional][y] test fails in yast2_snapper - "rogue workqueue lockup bsc#1126782 - Serial error: BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 32s!"Rejectedokurz2019-03-05

Actions
Blocks openQA Tests - action #44156: [opensuse][functional][u][sporadic][ppc64le] test fails in yast2_lan because rcu message in user-consoleRejectedzluo2018-11-21

Actions
Actions
Copy link
 #1

Updated by jorauch about 5 years ago

We have:
https://bugzilla.suse.com/show_bug.cgi?id=1126782
and in this referenced:
https://bugzilla.suse.com/show_bug.cgi?id=1126215

I am still against putting the bsc in the message as I see this as collection of known patterns that can appear

Actions
Copy link
 #2

Updated by okurz about 5 years ago

sure, just avoid the word "bug" in any message and make it obvious what the people that see the message need to do.

Actions
Copy link
 #3

Updated by szarate about 5 years ago

sure, just avoid the word "bug" in any message and make it obvious what the people that see the message need to do.

Let's call it a feature?. A bug it's a bug.

I am still against putting the bsc in the message as I see this as collection of known patterns that can appear

@jrauch, can you elaborate? I would use: https://bugzilla.suse.com/show_bug.cgi?id=1126782 however, maybe you are refering to the fact that this could happen many more times and be different problems?

Actions
Copy link
 #5

Updated by okurz about 5 years ago

  • Related to action #44156: [opensuse][functional][u][sporadic][ppc64le] test fails in yast2_lan because rcu message in user-console added
Actions
Copy link
 #6

Updated by okurz about 5 years ago

  • Related to deleted (action #44156: [opensuse][functional][u][sporadic][ppc64le] test fails in yast2_lan because rcu message in user-console)
Actions
Copy link
 #7

Updated by okurz about 5 years ago

  • Blocks action #44156: [opensuse][functional][u][sporadic][ppc64le] test fails in yast2_lan because rcu message in user-console added
Actions
Copy link
 #8

Updated by okurz about 5 years ago

  • Has duplicate action #48689: [functional][y] test fails in yast2_snapper - "rogue workqueue lockup bsc#1126782 - Serial error: BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 32s!" added
Actions
Copy link
 #9

Updated by SLindoMansilla about 5 years ago

  • Status changed from Workable to In Progress
  • Assignee set to SLindoMansilla

Refining

Actions
Copy link
 #10

Updated by SLindoMansilla about 5 years ago

  • Status changed from In Progress to Resolved

The workqueue lockup detection is already in place. The investigation should happen in the bug ticket: https://bugzilla.suse.com/show_bug.cgi?id=1126782

Actions
Copy link

Also available in: Atom PDF