Re: More about 2.4.3 timer problems

2001-04-04 Thread Eric Gillespie
On Wed, 4 Apr 2001, James Simmons wrote: : :>Err, tried the patch you recommended me to apply to the 2.4.3 source code :>(not the 2.4.3-pre6), but everything else started complaining it couldn't :>see printk() any more. Any advice? Thanks... : :Can you tell us your hardware configuration and yo

Re: More about 2.4.3 timer problems

2001-04-04 Thread James Simmons
>Err, tried the patch you recommended me to apply to the 2.4.3 source code >(not the 2.4.3-pre6), but everything else started complaining it couldn't >see printk() any more. Any advice? Thanks... Can you tell us your hardware configuration and your kernel configuration. What do you mean it cou

Re: More about 2.4.3 timer problems

2001-04-04 Thread Eric Gillespie
Err, tried the patch you recommended me to apply to the 2.4.3 source code (not the 2.4.3-pre6), but everything else started complaining it couldn't see printk() any more. Any advice? Thanks... -- /| _,.:*^*:., |\ Cheers from the Viking family, | |_/' viking@ `\_| |

Re: More about 2.4.3 timer problems

2001-04-03 Thread Alan Cox
> I updated my kernel to 2.4.3 when the patch was released. As I said earlier, I > noticed my timer losing a few seconds over the space of a couple of > hours. Well, I have since found out that the amount of time lost is > proportional to the load on the machine: the heavier the load, the more ti

Re: More about 2.4.3 timer problems

2001-04-02 Thread viking
Andrew Morton wrote: > Eric Gillespie wrote: > > > >... > > VESA fb mode 1280x1024x16, clock lost 1m 35s in time > > ... > > Same command, normal (non-fb mode) lost no time off clock. > > Is due to the 2.4.3 console drivers. They block interrupts during > console output. There's a fix in 2.4.2-

Re: More about 2.4.3 timer problems

2001-04-02 Thread Andrew Morton
Eric Gillespie wrote: > >... > VESA fb mode 1280x1024x16, clock lost 1m 35s in time > ... > Same command, normal (non-fb mode) lost no time off clock. Is due to the 2.4.3 console drivers. They block interrupts during console output. There's a fix in 2.4.2-ac. There's also a patch against 2.4.