Bug 13305
| Summary: | cpu_add_remove_lock circular dependency at hibernate | ||
|---|---|---|---|
| Product: | Power Management | Reporter: | Johannes Berg (johannes) |
| Component: | Hibernation/Suspend | Assignee: | power-management_other |
| Status: | REJECTED INSUFFICIENT_DATA | ||
| Severity: | normal | CC: | rjw, rui.zhang |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.30-rc5-wl-23297-gbf2c6a3-dirty | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 7216 | ||
| Attachments: | lockdep report | ||
ISTR seeing that already, can't recall where exactly. What's the last known good kernel? Not sure really, I'm almost certain .29 was good but even though I surely tested every rc I don't know much more than that right now. I've also reported this before in various ways but nobody ever listened. I'm sure there's not much deadlock potential, but it's annoying to have to reboot to get lockdep into a working state again. does the problem still exists in the latest kernel, say 2.6.31? please re-open it if the problem still exists in 2.6.32. |
Created attachment 21352 [details] lockdep report lockdep report attached happens at resume too but in the old kernel so the report afterwards come from hibernate