|
Bugzilla – Full Text Bug Listing |
| Summary: | soft lockup during test fstests with ext4 | ||
|---|---|---|---|
| Product: | [SUSE ALP - SUSE Adaptable Linux Platform] Granite | Reporter: | Yong Sun <yosun> |
| Component: | Kernel | Assignee: | Kernel Bugs <kernel-bugs> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | Normal | ||
| Priority: | P2 - High | CC: | fcrozat, jalausuch, jcheung, lan, rgoldwyn, tiwai, yosun |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Yong Sun
2023-07-28 09:31:24 UTC
Looking at the kernel log there's nothing pointing at ext4, or to any filesystem code. There's a softlockup that seems to be happening in the self-modifying code infrastructure (jump_label), in the network core code, more specifically in the netstamp_clear workqueue. I've tried to find something similar on lkml but no luck. Wrong search keywords, I guess. Goldwyn, can you suggest someone else to bring some knowledge on these areas? By the way, I see there are a lot of fstests that aren't being executed simply because the VM doesn't include some tools (for example, the 'chacl', from the 'acl' package). Where can I report these sort of things? (Or try to help fixing them?) Yes, I assigned it in a hurry. This does not look like a softlockup in ext4 and looks like something else is taking up processing resources. Re-assigning back to kernel-bugs. It needs retests with the later 6.4.x kernel, in anyway... Requesting retest of the scenario This test generic/101-200 in ext4 tested in ALP build5.6 didn't reproduce this issue. https://openqa.suse.de/tests/11835577 Consider this a random issue when running xfstests, and not a filesystem issue. I checked all tests in build5.6 and didn't see related fails. https://openqa.suse.de/tests/overview?distri=alp&version=1.0&build=5.6&groupid=519 Closing as WORKSFORME in latest version tested (build5.6) |