From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: d.okias@gmail.com, bugzilla-daemon@bugzilla.kernel.org, x86@kernel.org
Subject: Re: [Bug 15076] System panic under load with clockevents_program_event
Date: Mon, 25 Jan 2010 09:46:03 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1001250831110.2906@localhost.localdomain> (raw)
In-Reply-To: <201001221017.o0MAHQmu015858@demeter.kernel.org>
Switched to email. Please reply to all instead of using the bugzilla
interface.
> --- Comment #4 from okias <d.okias@gmail.com> 2010-01-22 10:17:25 ---
> and it's regression. Now I work on 2.6.32.3 and no problem.
That's a really weird one. The system is 50 min up and running and out
of the blue it crashes in clockevents_program_event(). This function
has been called a couple of thousand times before that point.
The only way to crash there is when *dev is pointing into nirwana. dev
comes from
int tick_program_event(ktime_t expires, int force)
{
struct clock_event_device *dev = __get_cpu_var(tick_cpu_device).evtdev;
according to the callchain. At this point nothing fiddles with
tick_cpu_device.evtdev, so I suspect some really nasty memory
corruption going on.
okias, can you please disable highmem support and verify whether the
problem persists ?
Thanks,
tglx
next parent reply other threads:[~2010-01-25 8:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15076-6666@http.bugzilla.kernel.org/>
[not found] ` <201001221017.o0MAHQmu015858@demeter.kernel.org>
2010-01-25 8:46 ` Thomas Gleixner [this message]
2010-01-25 11:33 ` [Bug 15076] System panic under load with clockevents_program_event okias
2010-01-26 14:07 ` okias
2010-01-28 23:55 ` okias
2010-04-08 22:54 2.6.34-rc3-git8: Reported regressions 2.6.32 -> 2.6.33 Rafael J. Wysocki
2010-04-08 23:04 ` [Bug #15076] System panic under load with clockevents_program_event Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2010-03-21 20:27 2.6.34-rc2: Reported regressions 2.6.32 -> 2.6.33 Rafael J. Wysocki
2010-03-21 20:30 ` [Bug #15076] System panic under load with clockevents_program_event Rafael J. Wysocki
2010-02-21 21:25 2.6.33-rc8-git6: Reported regressions from 2.6.32 Rafael J. Wysocki
2010-02-21 21:30 ` [Bug #15076] System panic under load with clockevents_program_event Rafael J. Wysocki
2010-02-14 23:31 2.6.33-rc8: Reported regressions from 2.6.32 Rafael J. Wysocki
2010-02-14 23:38 ` [Bug #15076] System panic under load with clockevents_program_event Rafael J. Wysocki
2010-02-07 22:16 2.6.33-rc7: Reported regressions from 2.6.32 Rafael J. Wysocki
2010-02-07 22:28 ` [Bug #15076] System panic under load with clockevents_program_event Rafael J. Wysocki
2010-02-01 0:18 2.6.33-rc6: Reported regressions from 2.6.32 Rafael J. Wysocki
2010-02-01 0:22 ` [Bug #15076] System panic under load with clockevents_program_event Rafael J. Wysocki
2010-02-01 7:15 ` okias
2010-02-02 20:44 ` Rafael J. Wysocki
2010-01-24 21:54 2.6.33-rc5: Reported regressions from 2.6.32 Rafael J. Wysocki
2010-01-24 22:04 ` [Bug #15076] System panic under load with clockevents_program_event Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.00.1001250831110.2906@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=d.okias@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox