From: Ingo Molnar <mingo@elte.hu>
To: Stefano Brivio <stefano.brivio@polimi.it>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, Michael Buesch <mb@bu3sch.de>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Len Brown <lenb@kernel.org>, Dave Jones <davej@redhat.com>
Subject: Re: [BUG] jiffies counter leaps in 2.6.24-rc3
Date: Thu, 29 Nov 2007 11:35:11 +0100 [thread overview]
Message-ID: <20071129103511.GD10577@elte.hu> (raw)
In-Reply-To: <20071129095034.24b3fc59@morte>
* Stefano Brivio <stefano.brivio@polimi.it> wrote:
> Ok, I found out how to reliably reproduce this bug. The root session issue
> was a bit weird, but I noticed I usually switch to root only when I need to
> change the CPU frequency. And here's what happens:
>
> # cpuspeedy min
> [after some time...]
> Nov 29 09:42:31 morte [ 4408.722597] b43-phy0 ERROR: PHY transmission error
>
> # cpuspeedy max
> Nov 29 09:42:41 morte [ 1177.238599] wmaster0: STA 00:14:c1:35:8d:eb Average rate: 540 (2160/4)
>
> It looks like jiffies get scaled exactly by a 3.75 factor, which is
> <max_frequency>/<min_frequency> here. I use acpi-cpufreq and this is my
> (only) CPU:
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 13
> model name : Intel(R) Pentium(R) M processor 1.50GHz
> stepping : 6
> cpu MHz : 1500.000
> cache size : 2048 KB
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 2
> wp : yes
> flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe bts est tm2
> bogomips : 2993.49
> clflush size : 64
>
> Any hint?
ah, the cpufreq/acpi/acpi-cpufreq angle is indeed a big clue. I've
Cc:-ed various interested parties.
Ingo
next prev parent reply other threads:[~2007-11-29 10:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 16:51 Stefano Brivio
2007-11-24 17:56 ` Frans Pop
2007-11-24 18:09 ` Stefano Brivio
2007-11-24 18:48 ` Rafael J. Wysocki
2007-11-24 18:46 ` Stefano Brivio
2007-11-24 19:31 ` Rafael J. Wysocki
2007-11-26 18:00 ` Stefano Brivio
2007-11-29 7:20 ` Stefano Brivio
2007-11-29 10:33 ` Ingo Molnar
2007-11-29 8:50 ` Stefano Brivio
2007-11-29 10:35 ` Ingo Molnar [this message]
2007-11-29 17:45 ` Dave Jones
2007-11-29 17:57 ` Stefano Brivio
2007-11-29 18:24 ` Dave Jones
2007-11-29 19:25 ` Stefano Brivio
2007-11-29 19:36 ` Ingo Molnar
2007-11-29 20:12 ` Stefano Brivio
2007-11-29 20:04 ` Dave Jones
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=20071129103511.GD10577@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=rjw@sisk.pl \
--cc=stefano.brivio@polimi.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome