RE: Ide=nodma is "loosing too many ticks"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Roberto, 

 
> Dear Mark,
> 
> I was able to work on my DMA using the article: 
> http://www.linuxdevcenter.com/pub/a/linux/2000/06/29/hdparm.html

Thanks for the link I'll check it out...


> What do you meean with the incorrect syncronization onf an SMP system 
> and how could I fix this?
> Could you please suggest some changes?

No clue, that was part of the error message I got - I did not write that :)

I still am not sure if this is really a driver problem... It seems to me like my standard Dell box (about 2-3 years old) is really
nothing special, so the drivers should be pretty main-stream... But maybe I'm wrong...

I am also still not sure if this is really a problem or not...

MARK


> 
> Roberto
> 
> Roberto
> 
> Mark wrote:
> 
> >I got the following problem after my FC3 install:
> >
> >Losing too many ticks!
> >TSC cannot be used as a timesource.
> >Possible reasons for this are:
> >  You're running with Speedstep,
> >  You don't have DMA enabled for your hard disk (see hdparm),
> >  Incorrect TSC synchronization on an SMP system (see 
> dmesg). Falling 
> >back to a sane timesource now.
> >
> >
> >I have ide=nodma in the boot parameters, since I was not able to 
> >complete the install with that parameter. If I try to take this 
> >parameter out of the grub.conf, I get the below and the machine does 
> >not boot:
> >
> >hdc: cdrom_pc_intr: The drive appears confused (ireason 0x02)
> >ide-cd: cmd 0x1e timed out
> >hdc: lost interupt
> >
> >I also tried "ide0=dma ide1=nodma" with the same problem (CDROMs are 
> >hdc and hdd on ide1) Then I tried "ide=nodma ide0=dma". It 
> boots, but I 
> >dont know if it fixes the original problem...
> >
> >
> >Should I leave "ide=nodma" in and live with the first 
> warning? Is this 
> >just a warning that can be ignored or is there something that could 
> >actually go wrong if I use this as a production server?
> >
> >I am surprised about this whole "ide=nodma" thing anyway. It 
> seems that 
> >the only way to get Fedora installed on any of my machines is to use 
> >"ide=nodma"as boot params. Sometimes I even seem to need 
> "allowcddma". 
> >My machines are by no means special, just standard IDE 
> controllers with 
> >a bunch of IDE HDs and IDE cdrom... What is the best 
> practise for this 
> >case?
> >
> >
> >Thanks,
> >
> >MARK
> >
> >
> >  
> >
> 
> -- 
> Roberto R. Heredia, Ph.D
> Associate Professor of Psychology
> Department of Behavioral, Applied Sciences & Criminal Justice    
> Texas A&M International University                             
> 5201 University Boulevard                                            
> Laredo, Texas  78041-1900
> 
> Cognitive Science Laboratory: BH 224
> Phone: (956)326-2637
> Facsimile: (956)326-2474
> mailto:rheredia@xxxxxxxxx
> http://www.tamiu.edu/~rheredia <http://www.tamiu.edu/%7Erheredia>
> 


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux