From: Chr <chunkeey@web.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org,
Andi Kleen <andi-suse@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7
Date: Tue, 1 Apr 2008 00:01:50 +0200 [thread overview]
Message-ID: <200804010001.51288.chunkeey@web.de> (raw)
In-Reply-To: <alpine.LFD.1.10.0803302315270.3219@apollo.tec.linutronix.de>
On Sunday 30 March 2008 23:36:40 Thomas Gleixner wrote:
> On Sun, 30 Mar 2008, Chr wrote:
>
> You mentioned that you have tons of other logs. Can you please
> upload those to some place? If you don't have a possiblity, please
> contact me private and I'll provide you one.
>
Ahhm it happend again (well, actually it's the fifth time today, but this time
I _hopefully_ found something)
I made a new log: (check out bugzilla)
http://bugzilla.kernel.org/show_bug.cgi?id=10369
(direct link)
http://bugzilla.kernel.org/attachment.cgi?id=15542
so, this log was made from a _working_ machine over the serial
console... I put some _real_ "date" marks here and there...
to explain a bit, how the time STALLS... (well, it seems like
it goes a bit backward and forward and backwards again... it loops?!
whatever..!??!?!!)
just take a look at the jiffies (grep for them... it takes "minutes"
until jiffies+1 comes)
Maybe there's a "signed" problem somewhere in the timekeeping
code? Or does 2.6.25-rcX have a general problem with NTP-daemons
like chrony?
Regards,
Chr.
next prev parent reply other threads:[~2008-03-31 22:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 19:09 The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7 Chr
2008-03-30 19:25 ` Rafael J. Wysocki
2008-03-30 19:59 ` Thomas Gleixner
2008-03-30 20:18 ` Chr
2008-03-30 20:37 ` Thomas Gleixner
2008-03-30 21:09 ` Chr
2008-03-30 21:36 ` Thomas Gleixner
2008-03-30 22:19 ` Chr
2008-03-31 12:56 ` Adrian Bunk
2008-03-31 13:23 ` Chr
2008-03-31 22:01 ` Chr [this message]
2008-03-31 23:14 ` Rafael J. Wysocki
2008-03-31 23:30 ` Chr
2008-04-01 21:16 ` Rafael J. Wysocki
2008-04-01 22:27 ` Chr
2008-04-02 12:45 ` Chr
2008-04-01 16:27 ` Thomas Gleixner
2008-04-01 18:57 ` Chr
2008-04-01 22:29 ` Chr
2008-04-02 7:08 ` Thomas Gleixner
2008-04-02 9:34 ` Chr
2008-03-31 7:10 ` Andi Kleen
2008-03-31 12:51 ` Chr
-- strict thread matches above, loose matches on Subject: below --
2008-04-03 22:49 2.6.25-rc8-git2: Reported regressions from 2.6.24 Rafael J. Wysocki
2008-04-03 23:22 ` The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7 Rafael J. Wysocki
2008-04-04 1:49 ` Chr
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=200804010001.51288.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=akpm@linux-foundation.org \
--cc=andi-suse@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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.