From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Bongani Hlope <bonganilinux@mweb.co.za>,
linux-kernel@vger.kernel.org, john stultz <johnstul@us.ibm.com>
Subject: Re: limit-timer_pm-printk-storms.patch
Date: Wed, 21 Jan 2004 09:26:35 +0100 [thread overview]
Message-ID: <20040121082635.GA5980@dominikbrodowski.de> (raw)
In-Reply-To: <20040120115751.5e4441bc.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
On Tue, Jan 20, 2004 at 11:57:51AM -0800, Andrew Morton wrote:
> Bongani Hlope <bonganilinux@mweb.co.za> wrote:
> >
> > This patch has been inspired by the limit-IO-error-printk-storms patch. On my PII when I enable
> > CONFIG_X86_PM_TIMER this gets called a lot of times, I guess my VIA chipset is too broken to play with this.
> >
> > <example>
> > ...
> > Jan 19 04:21:46 bongani kernel: bad pmtmr read: (15567390, 15567423, 15567393)
> > Jan 19 04:21:46 bongani kernel: bad pmtmr read: (1746710, 1746719, 1746713)
> > Jan 19 04:21:47 bongani kernel: bad pmtmr read: (2239982, 2239999, 2239986)
>
> Does the PM timer actually do the right thing once these printk's are
> suppressed?
Just recognized my backup notebook, a Pentium III / Intel 440-BX-AGPset
does the same thing -- the pmtmr readings are always quite close to each
other, but not linear.
However, overall the PM timer _does_ the right thing all the time [it always
did the right thing on that system, as that's where the original patch was
created....]
Dominik
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-01-21 8:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040120212514.43e31237.bonganilinux@mweb.co.za>
2004-01-20 19:57 ` limit-timer_pm-printk-storms.patch Andrew Morton
2004-01-20 20:27 ` limit-timer_pm-printk-storms.patch Bongani Hlope
2004-01-20 21:05 ` limit-timer_pm-printk-storms.patch john stultz
2004-01-21 8:26 ` Dominik Brodowski [this message]
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=20040121082635.GA5980@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--cc=akpm@osdl.org \
--cc=bonganilinux@mweb.co.za \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.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
Powered by JetHome