[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B52D822.1010700@pardus.org.tr>
Date: Sun, 17 Jan 2010 11:28:02 +0200
From: Ozan Çağlayan <ozan@...dus.org.tr>
To: Thomas Gleixner <tglx@...utronix.de>
CC: Xiaotian Feng <dfeng@...hat.com>, damm@...l.co.jp,
hsweeten@...ionengravers.com, akpm@...ux-foundation.org,
venkatesh.pallipadi@...el.com, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/4] clockevents: fix clockevent_devices list corruption
after cpu hotplug
Thomas Gleixner wrote:
>
> I'm not happy about that churn. Why don't we simply scan the
> clockevent_devices list for leftovers of the dead CPU ?
>
> Untested patch below solves the same problem.
Hi, I have 3 bug reports about a clockevent failure while halting the system (2.6.31.11 kernel).
It exactly pinpoints to the line 262 which got changed with this patch merged to 2.6.31.10 (and also 2.6.32.3):
[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
All 3 systems have Pentium 4 processors with different clock speeds.
Here's a screenshot of the full stacktrace:
http://bugs.pardus.org.tr/attachment.cgi?id=4820
and the relevant bugzilla report:
http://bugzilla.kernel.org/show_bug.cgi?id=15073
Thanks,
Ozan Caglayan
Pardus Linux -- http://www.pardus.org.tr/eng
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists