From: okias <d.okias@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
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 12:33:09 +0100 [thread overview]
Message-ID: <c2673ca61001250333p33305d3fma638d73c0d448e17@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1001250831110.2906@localhost.localdomain>
Okey, I try without highmem soon.
2010/1/25, Thomas Gleixner <tglx@linutronix.de>:
> 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
>
--
Jabber/XMPP: okias@isgeek.info
SIP VoIP: sip:17474537254@proxy01.sipphone.com
next prev parent reply other threads:[~2010-01-25 11:33 UTC|newest]
Thread overview: 19+ 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 ` [Bug 15076] System panic under load with clockevents_program_event Thomas Gleixner
2010-01-25 11:33 ` okias [this message]
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
2010-04-08 23:04 ` 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-03-21 20:30 ` 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-07 22:28 ` 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 0:22 ` Rafael J. Wysocki
2010-02-01 7:15 ` okias
2010-02-01 7:15 ` okias
[not found] ` <c2673ca61001312315s3e50611fm81171ddca6d19477-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-02 20:44 ` Rafael J. Wysocki
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=c2673ca61001250333p33305d3fma638d73c0d448e17@mail.gmail.com \
--to=d.okias@gmail.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.