From: Vojtech Pavlik <vojtech@suse.cz>
To: john stultz <johnstul@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: keyboard and USB problems (Re: 2.6.2-rc1-mm2)
Date: Fri, 23 Jan 2004 20:54:39 +0100 [thread overview]
Message-ID: <20040123195439.GA7878@ucw.cz> (raw)
In-Reply-To: <1074886056.12447.36.camel@localhost>
On Fri, Jan 23, 2004 at 11:27:41AM -0800, john stultz wrote:
> On Fri, 2004-01-23 at 08:19, Vojtech Pavlik wrote:
> > On Fri, Jan 23, 2004 at 05:01:52PM +0100, Rudo Thomas wrote:
> > > BogoMIPS is figured out to be 8.19 (this was already reported by another user),
> >
> > ... this the root cause of the following problems.
> >
> > > and i8042.c complaints with this:
> > > i8042.c: Can't write CTR while closing AUX.
> >
> > ... bogomips is used in udelay() and that's used for waiting. If
> > bogomips is measured lower than real, the wait takes shorter and the
> > hardware doesn't do what it should in that short time.
>
> Well, loops_per_jiffy is actually being measured correctly as we're
> using the acpi pm timesource to time udelay(). However there is a loss
> of resolution using the slower time source, so udelay(1) might take
> longer then 1 us.
Longer udelay shouldn't cause trouble. Shorter one definitely would.
> If that is going to cause problems, then we'll need to pull out the
> use-pmtmr-for-delay_pmtmr patch. I guess our only option is then to use
> the TSC for delay_pmtrm() (as a loop based delay fails in other cases).
> I'll write that up and send it your way, Andrew.
I've seen the PM timer breaking the mouse operation rather badly in the
past, the lost-sync check was triggering for many people when the PM
timer was used. This implies time inacurracy in the range of 0.5
seconds. Could that happen somehow?
--
Vojtech Pavlik
SuSE Labs, SuSE CR
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-01-23 19:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 9:37 2.6.2-rc1-mm2 Andrew Morton
2004-01-23 13:30 ` 2.6.2-rc1-mm2 Thomas Schlichter
2004-01-23 17:59 ` 2.6.2-rc1-mm2 john stultz
2004-01-23 15:12 ` 2.6.2-rc1-mm2 Ed Tomlinson
2004-01-23 18:43 ` 2.6.2-rc1-mm2 Andrew Morton
2004-01-24 0:46 ` 2.6.2-rc1-mm2 Ed Tomlinson
2004-01-23 16:01 ` keyboard and USB problems (Re: 2.6.2-rc1-mm2) Rudo Thomas
2004-01-23 16:19 ` Vojtech Pavlik
2004-01-23 18:46 ` Andrew Morton
2004-01-23 22:16 ` More timer/bogomip damage (was " Valdis.Kletnieks
2004-01-23 19:27 ` john stultz
2004-01-23 19:54 ` Vojtech Pavlik [this message]
2004-01-23 20:15 ` john stultz
2004-01-23 21:10 ` Vojtech Pavlik
2004-01-24 0:26 ` [PATCH] use-tsc-for-delay_pmtmr.patch john stultz
2004-01-23 17:08 ` 2.6.2-rc1-mm2 (compile stats) John Cherry
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=20040123195439.GA7878@ucw.cz \
--to=vojtech@suse.cz \
--cc=akpm@osdl.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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