Re: "clock timer configuration lost" on Serverworks chipset

you saying the code should be doing the equivalent of "(count > LATCH)", or is 2.2.19 correct and the whines I'm seeing mean there really is a problem with the Serverworks chipset? Thanks, jcastle Alan Cox wrote: >Jim Castleberry)wrote: >> How well has the problem been nailed

Re: clock timer configuration lost on Serverworks chipset

be doing the equivalent of (count LATCH), or is 2.2.19 correct and the whines I'm seeing mean there really is a problem with the Serverworks chipset? Thanks, jcastle Alan Cox wrote: Jim Castleberry)wrote: How well has the problem been nailed down? Could it be that it just showed up first

"clock timer configuration lost" on Serverworks chipset

I'm getting messages saying "clock timer configuration lost - probably a VIA686a" from 2.2.19 running on a board using the Serverworks HE chipset. Reading the list archives it sounds like this problem has previously been attributed to a possible bug in the VIA chipset. According to RedHat's

clock timer configuration lost on Serverworks chipset

I'm getting messages saying clock timer configuration lost - probably a VIA686a from 2.2.19 running on a board using the Serverworks HE chipset. Reading the list archives it sounds like this problem has previously been attributed to a possible bug in the VIA chipset. According to RedHat's