Bug 15073
Summary: | BUG at kernel/time/clockevents.c:262 prevents computer from completely shutting down | ||
---|---|---|---|
Product: | Timers | Reporter: | Ozan Caglayan (ozan) |
Component: | Other | Assignee: | john stultz (john.stultz) |
Status: | CLOSED DUPLICATE | ||
Severity: | normal | CC: | rjw, simon.j.munton, tglx |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.31.11 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 14885 | ||
Attachments: |
Screenshot of the stacktrace
Screenshot of 2.6.32.3 stacktrace |
Description
Ozan Caglayan
2010-01-16 19:21:37 UTC
Created attachment 24600 [details]
Screenshot of the stacktrace
// Assign to Thomas Gleixner Now I have 3 bug reports and 1 live system on which the bug appears. The 3 bug reporter have all Pentium 4 processors with different clock speeds. I'm attaching a screenshot which will show the stacktrace. Note that the commit was also introduced to 2.6.32.y with 2.6.32.3: http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.32.3 Thanks. The UI faked me, it seems to allow to change the assignee but once I submit it borks, sorry. I am also getting this problem with kernel version 2.6.32.3. It doesn't always happen on poweroff, and every time I've enabled the serial console to try and capture the trace, the problem hasn't occurred. I'll add a screenshot of the trace. Created attachment 24602 [details]
Screenshot of 2.6.32.3 stacktrace
Screenshot of problem on 2.6.32.3 kernel
Yes this is the same stacktrace. By the way reverting the commit I've mentioned above fixed the problem on 4 different systems all with Pentium 4 processors. |