action #44156
closed[opensuse][functional][u][sporadic][ppc64le] test fails in yast2_lan because rcu message in user-console
Added by michel_mno over 5 years ago. Updated over 3 years ago.
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-NET-ppc64le-minimalx@ppc64le fails in
yast2_lan
because of rcu message in root-console (ppc64le)
extract of serial0.txt
rcu: INFO: rcu_sched self-detected stall on CPU
rcu: 0-...!: (1 ticks this GP) idle=8c2/0/0x1 softirq=42694/42694 fqs=0
rcu: (t=9536 jiffies g=22325 q=6)
rcu: rcu_sched kthread starved for 9536 jiffies! g22325 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=0
rcu: RCU grace-period kthread stack dump:
Reproducible¶
Seldomly
Expected result¶
Last good: 20181118 (or more recent)
Suggestions¶
- Investigate what the message means
- Look into preventing that message in tests or reference product issue with soft-fail and workaround (needle is already in place but references this "test issue" ticket instead)
Further details¶
Always latest result in this scenario: latest
Updated by michel_mno over 5 years ago
I created a bypass with workaround needle https://github.com/os-autoinst/os-autoinst-needles-opensuse/commit/70ff7d7de401065da9e0a9deafb127545d76fcfa (user-console-poo44156-20181121)
Updated by michel_mno over 5 years ago
- Subject changed from [opensuse][functional][u] test fails in yast2_lan because rcu message in root-console (ppc64le) to [opensuse][functional][u] test fails in yast2_lan because rcu message in user-console (ppc64le)
Updated by okurz over 5 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: lvm
https://openqa.opensuse.org/tests/826862
Updated by okurz over 5 years ago
- Priority changed from Normal to High
Used as label in currently failing tests -> setting prio to "High"
Updated by okurz about 5 years ago
- Subject changed from [opensuse][functional][u] test fails in yast2_lan because rcu message in user-console (ppc64le) to [opensuse][functional][u][sporadic][ppc64le] test fails in yast2_lan because rcu message in user-console
- Description updated (diff)
- Status changed from New to Workable
- Priority changed from High to Normal
With the workaround needle in place this should not be necessarily "High"-prio. Using https://openqa.opensuse.org/admin/needles we can find uses and matches of the needle. Last match was 29 days ago in https://openqa.opensuse.org/tests/830237#step/yast2_lan/1
Updated by okurz about 5 years ago
- Related to action #48419: [functional][u] Hunt for the rogue workqueue added
Updated by okurz about 5 years ago
- Related to deleted (action #48419: [functional][u] Hunt for the rogue workqueue)
Updated by okurz about 5 years ago
- Blocked by action #48419: [functional][u] Hunt for the rogue workqueue added
Updated by okurz about 5 years ago
- Status changed from Workable to Blocked
- Assignee set to okurz
- Target version changed from Milestone 24 to Milestone 25
Updated by okurz almost 5 years ago
- Assignee changed from okurz to mgriessmeier
Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.
Updated by mgriessmeier almost 5 years ago
- Status changed from Blocked to Workable
- Assignee deleted (
mgriessmeier) - Target version changed from Milestone 25 to Milestone 27
unblocked
Updated by zluo over 4 years ago
- Status changed from Workable to Rejected
- Assignee set to zluo
https://openqa.opensuse.org/tests/1004109#next_previous
no issue anymore.
Updated by michel_mno over 4 years ago
for me the related needles 'console-poo14156' are still used as per needle search in Webui:
Directory.......Filename................................Last use................Last match
opensuse........root-console-poo44156-20190821.json.....about 2 hours ago.......5 days ago
opensuse........user-console-poo44156-20181121.json.....about 2 hours ago.......5 days ago
https://openqa.opensuse.org/tests/1016703#step/curl_https/2
https://openqa.opensuse.org/tests/1016703#step/check_network/3
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: lvm
https://openqa.opensuse.org/tests/1036033
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: minimalx
https://openqa.opensuse.org/tests/1049615
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: lvm
https://openqa.opensuse.org/tests/1060459
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: lvm
https://openqa.opensuse.org/tests/1075691
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: lvm
https://openqa.opensuse.org/tests/1091298
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: minimalx
https://openqa.opensuse.org/tests/1116310
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: lvm
https://openqa.opensuse.org/tests/1130298
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: minimalx
https://openqa.opensuse.org/tests/1145397
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz about 4 years ago
- Status changed from Rejected to Workable
- Target version deleted (
Milestone 27)
apparently still an issue :)
Similar: https://openqa.opensuse.org/tests/1169499#step/consoletest_setup/27 for "workqueue lockup" which probably also be prevented with a simple needle covering the console message.
Updated by zluo about 4 years ago
- Blocked by action #60992: [qe-core][functional][sporadic] generic problem with select_console / workqueue lockup message added
Updated by zluo about 4 years ago
- Status changed from Workable to Blocked
- Assignee deleted (
zluo)
Updated by okurz almost 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.opensuse.org/tests/1297646
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by michel_mno almost 4 years ago
- Related to action #68218: [opensuse][ppc64le] test fails because "rcu_sched kthread starved" while VM snapshot added
Updated by michel_mno over 3 years ago
- Status changed from Blocked to In Progress
problem disappeared for same reason as action#68218
so should change state to resolved.
Updated by zluo over 3 years ago
- Assignee set to zluo
@ michel_mno in progress? nobody is working on it.
change it to invalid since this doesn't happen anymore.
Updated by zluo over 3 years ago
- Blocked by deleted (action #60992: [qe-core][functional][sporadic] generic problem with select_console / workqueue lockup message)