Re: 2.6.1 "clock preempt"?

From: timothy parkinson
Date: Fri Jan 23 2004 - 14:03:48 EST



On Thu, Jan 22, 2004 at 01:21:45PM -0800, john stultz wrote:
> On Thu, 2004-01-22 at 12:00, timothy parkinson wrote:
> > su -c "/usr/sbin/hdparm /dev/hda"
> > Password:
> >
> > /dev/hda:
> > multcount = 16 (on)
> > IO_support = 1 (32-bit)
> > unmaskirq = 0 (off)
> > using_dma = 0 (off)
> > keepsettings = 0 (off)
> > readonly = 0 (off)
> > readahead = 256 (on)
> > geometry = 65535/16/63, sectors = 156301488, start = 0
> >
> > but...
> >
> > su -c "/usr/sbin/hdparm -d1 /dev/hda"
> > Password:
> >
> > /dev/hda:
> > setting using_dma to 1 (on)
> > HDIO_SET_DMA failed: Operation not permitted
> > using_dma = 0 (off)
> >
> > it's an 80gig western digital from about 2-3 years ago.
>
> Its likely you need to enable support in the kernel for your IDE
> controller, or your DMA on your controller isn't supported.
>
> thanks
> -john
>
>

so, apparently the problem was that i just needed to enable dma... which meant
that i needed to set "CONFIG_BLK_DEV_VIA82CXXX=y" in my .config.

been running all night/morning with load - no "losing ticks" message or slowing
clock yet. thanks for pointing me in the right direction.

think we could improve that error message? i'd never have guessed that it was
hard disk related if you hadn't told me...

timothy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/