|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)|
|Severity:||normal||CC:||rjw, simon.j.munton, tglx|
|Bug Depends on:|
Screenshot of the stacktrace
Screenshot of 220.127.116.11 stacktrace
Description Ozan Caglayan 2010-01-16 19:21:37 UTC
Hi, One of our users reports that he can't properly shutdown the system and he gets a trace on VT. The system is partly shutted down: The power led is off for example. [4406.986777] kernel BUG at kernel/time/clockevents.c:262! [4406.986777] invalid opcode: 0000 [#1] SMP [4406.986777] last sysfs file: /sysfs/module/ip_tables/initstate He only reported the first 3 lines, I'll try to make him write down the whole message ASAP. I suspect the following commit which has been pushed to 18.104.22.168 which modifies kernel/time/clockevents.c:262. From bb6eddf7676e1c1f3e637aa93c5224488d99036f Mon Sep 17 00:00:00 2001 From: Thomas Gleixner <email@example.com> Date: Thu, 10 Dec 2009 15:35:10 +0100 Subject: [PATCH] clockevents: Prevent clockevent_devices list corruption on cpu hotplug CC'ing the author.
Comment 1 Ozan Caglayan 2010-01-17 09:00:51 UTC
Created attachment 24600 [details] Screenshot of the stacktrace
Comment 2 Ozan Caglayan 2010-01-17 09:01:20 UTC
// 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 22.214.171.124: http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-126.96.36.199 Thanks.
Comment 3 Ozan Caglayan 2010-01-17 09:02:15 UTC
The UI faked me, it seems to allow to change the assignee but once I submit it borks, sorry.
Comment 4 Simon Munton 2010-01-17 10:23:58 UTC
I am also getting this problem with kernel version 188.8.131.52. 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.
Comment 5 Simon Munton 2010-01-17 10:30:32 UTC
Created attachment 24602 [details] Screenshot of 184.108.40.206 stacktrace Screenshot of problem on 220.127.116.11 kernel
Comment 6 Ozan Caglayan 2010-01-17 15:17:41 UTC
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.