Bug 207009
Summary: | WARNING: CPU: 10 PID: 0 at do_debug+0x192/0x220 | ||
---|---|---|---|
Product: | ACPI | Reporter: | ilkka.prusi |
Component: | Other | Assignee: | Zhang Rui (rui.zhang) |
Status: | CLOSED WILL_NOT_FIX | ||
Severity: | normal | CC: | rui.zhang |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 5.5.13, 5.6.0-rc7+ | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | panic during booting |
Description
ilkka.prusi
2020-03-28 19:31:52 UTC
Potentially related bug #198833 Also kernel panic during booting 5.6.0-rc7+ Created attachment 288119 [details]
panic during booting
Image of panic
Kernel 5.5.11 seems to work better without same issues than newer kernels. 5.5.12 (and later) has changes in locking which might explain these issues. (In reply to ilkka.prusi from comment #4) > Kernel 5.5.11 seems to work better without same issues than newer kernels. > so 5.5.11 always work well. right? > 5.5.12 (and later) has changes in locking which might explain these issues. Give that you've already narrow down the problem to 5.5.11 - 5.5.12. please run git-bisect to find out the offending commit. (In reply to Zhang Rui from comment #5) > (In reply to ilkka.prusi from comment #4) > > Kernel 5.5.11 seems to work better without same issues than newer kernels. > > > so 5.5.11 always work well. right? > > > 5.5.12 (and later) has changes in locking which might explain these issues. > > Give that you've already narrow down the problem to 5.5.11 - 5.5.12. > please run git-bisect to find out the offending commit. Sorry I did not respond sooner, notification was lost somewhere.. "better" does not mean "no issues" - just that this particular splat was not there before: that does not really mean anything as any one of the crashes where log could not be recovered might have been the same issue. So I don't really have a known "good" configuration. Today 5.8.0-rc7 again showed similar splat but at least I could get picture of it (dmesg -w). I'll have to parse those pictures next.. Hopefully I'll get another system for comparison to rule out any hardware issues. Looks like problem only appears when there are two identical DIMMs (of a set) on the computer but not just one of them. My guess is that RAM is incompatible in some way. Current -stable is also stable on the computer when only one of the DIMMs is installed. I did try with different components (different motherboard, power supply, different display card etc.) and those did change the issue. But it seems to be entirely hardware problem. I think this bug can be closed. |