On Fri, Jan 23, 2004 at 12:15:03PM -0800, john stultz wrote: > > > 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? > > Not in a way that I yet understand. Do you see similar problems with > folks using clock=pit? Yes, I do. However in several cases using clock=pit cured the problem. In other cases the problem was cured by killing a battery applet in X. -- Vojtech Pavlik SuSE Labs, SuSE CR - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
References:
- 2.6.2-rc1-mm2Andrew Morton
- keyboard and USB problems (Re: 2.6.2-rc1-mm2)Rudo Thomas
- Re: keyboard and USB problems (Re: 2.6.2-rc1-mm2)Vojtech Pavlik
- Re: keyboard and USB problems (Re: 2.6.2-rc1-mm2)john stultz
- Re: keyboard and USB problems (Re: 2.6.2-rc1-mm2)Vojtech Pavlik
- Re: keyboard and USB problems (Re: 2.6.2-rc1-mm2)john stultz
- Prev by Date: install_latest_kernel for linux-2.6.x
- Next by Date: Re: DMI updates from 2.4
- Previous by thread: Re: keyboard and USB problems (Re: 2.6.2-rc1-mm2)
- Next by thread: [PATCH] use-tsc-for-delay_pmtmr.patch
- Indexes:[Main][Thread]