On Fri, 2004-01-23 at 12:38, timothy parkinson wrote: > no problem, i'll take it from here. > > * Running with SpeedStep (this is a cpu thing i assume?) could cause this. > * Not having DMA enabled on your hard disk(s) could cause this. See the hdparm > utility to enable it. > * Incorrect TSC synchronization on SMP systems could cause this. > * Anything else? Not that I can think of right off. Sounds good. Thanks! -john - 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:
- Re: 2.6.1 "clock preempt"?timothy parkinson
- Re: 2.6.1 "clock preempt"?john stultz
- Re: 2.6.1 "clock preempt"?timothy parkinson
- Re: 2.6.1 "clock preempt"?john stultz
- Re: 2.6.1 "clock preempt"?timothy parkinson
- Re: 2.6.1 "clock preempt"?john stultz
- Re: 2.6.1 "clock preempt"?timothy parkinson
- Re: 2.6.1 "clock preempt"?john stultz
- Re: 2.6.1 "clock preempt"?timothy parkinson
- Re: 2.6.1 "clock preempt"?john stultz
- Re: 2.6.1 "clock preempt"?timothy parkinson
- Prev by Date: Re: sched-idle and disk-priorities for 2.6.X
- Next by Date: Re: [OFFTOPIC] "smack the penguin"
- Previous by thread: Re: 2.6.1 "clock preempt"?
- Next by thread: Re: 2.6.1 "clock preempt"?
- Indexes:[Main][Thread]