On Tue, 17 Apr 2001, Andrew Morton wrote:
:viking wrote:
:>
:> Incidentally, Andrew, thanks for that patch.
:
:My brain is fading. Which patch was that?
Gee! 8-) and you suggested it to me! It was the patch against 2.4.3-pre6
which corrected the system clock slowing down, due to the
On Tue, 17 Apr 2001, Andrew Morton wrote:
:viking wrote:
:
: Incidentally, Andrew, thanks for that patch.
:
:My brain is fading. Which patch was that?
Gee! 8-) and you suggested it to me! It was the patch against 2.4.3-pre6
which corrected the system clock slowing down, due to the interrupts
James Simmons wrote:
> >Thanks, that solved my problem. Have added it to the patch...
> >THe patch & 2.4.3 kernel seem to be working well, except that I can't get
> >PowerOff to kick in - it stops dead there, where it used to power down.
>
> Is this the case when the patch is removed as well.
James Simmons wrote:
Thanks, that solved my problem. Have added it to the patch...
THe patch 2.4.3 kernel seem to be working well, except that I can't get
PowerOff to kick in - it stops dead there, where it used to power down.
Is this the case when the patch is removed as well. When does
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
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 your
>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
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@ `\_| |
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@ `\_| |
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
> 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
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 time
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
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
First off, CC: back to me, as my machine can't handle an estimated 200
messages a day for me to sign up to the list 8-( - Anyway..
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
First off, CC: back to me, as my machine can't handle an estimated 200
messages a day for me to sign up to the list 8-( - Anyway..
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
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-acrecent.
There's also a patch against
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-acrecent.
18 matches
Mail list logo
