Re: 2.6.1 "clock preempt"?
From: timothy parkinson (t_at_timothyparkinson.com)
Date: 01/31/04
- Previous message: Eric W. Biederman: "Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patch"
- In reply to: Bartlomiej Zolnierkiewicz: "Re: 2.6.1 "clock preempt"?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 30 Jan 2004 19:24:12 -0500 To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
On Sat, Jan 31, 2004 at 12:32:23AM +0100, Bartlomiej Zolnierkiewicz wrote:
> On Tuesday 27 of January 2004 22:30, markus reichelt wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > timothy parkinson <t@timothyparkinson.com> wrote:
> > > * 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?
> >
> > Yepp:
> >
> > Jan 27 20:12:12 tatooine kernel: Losing too many ticks!
> >
> > I had to set "CONFIG_IDE_TASK_IOCTL=y" in my .config in order to get
> > it working.
>
> How's that possible?
> This config option only exports HDIO_DRIVE_TASKFILE ioctl to user-space.
>
> --bart
>
without that, "hdparm -d1 /dev/hda" would claim that dma wasn't supported on my
harddrive.
i'm positive it's the only variable, i didn't change anything else!
timothy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Eric W. Biederman: "Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patch"
- In reply to: Bartlomiej Zolnierkiewicz: "Re: 2.6.1 "clock preempt"?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
