Messages in this thread | | | Date | Fri, 23 Jan 2004 14:36:35 -0500 | From | timothy parkinson <> | Subject | Re: 2.6.1 "clock preempt"? |
| |
On Fri, Jan 23, 2004 at 11:17:29AM -0800, john stultz wrote: > On Fri, 2004-01-23 at 11:02, timothy parkinson wrote: > > On Thu, Jan 22, 2004 at 01:21:45PM -0800, john stultz wrote: > > > Its likely you need to enable support in the kernel for your IDE > > > controller, or your DMA on your controller isn't supported. > > > > 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... > > Well, lost ticks can be caused by many things, but your point is valid, > the message could be a bit more elightening. > > thanks > -john > >
googling for this issue turns up quite a few questions about it - there's already one possible answer in the source, couldn't hurt to stick in a few more:
if (lost_count++ > 100) { printk(KERN_WARNING "Losing too many ticks!\n"); printk(KERN_WARNING "TSC cannot be used as a timesource.\n" "Are you running with SpeedStep?\n" + "Perhaps you should enable DMA using \"hdparm\"?\n" + "etc..........)\n"); printk(KERN_WARNING "Falling back to a sane timesource.\n"); clock_fallback(); }
not that you have to actually listen to me or anything... :-)
- 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/
| |