odd timer bug, similar to VIA 686a symptoms

odd timer bug, similar to VIA 686a symptoms

Post by Alan Co » Thu, 30 May 2002 20:50:11




>> May 28 11:19:54 gull kernel: timer.c: VIA bug check triggered. Value read 65500 [0xffdc], re-read 65485 [0xffcd]
> May 28 11:19:55 gull kernel: timer.c: VIA bug check triggered. Value read 65500 [0xffdc], re-read 65486 [0xffce]
> May 28 11:19:56 gull kernel: timer.c: VIA bug check triggered. Value read 65500 [0xffdc], re-read 65486 [0xffce]
> May 28 11:19:57 gull kernel: timer.c: VIA bug check triggered. Value read 65499 [0xffdb], re-read 65484 [0xffcc]
> May 28 11:19:58 gull kernel: timer.c: VIA bug check triggered. Value read 65497 [0xffd9], re-read 65483 [0xffcb]

> Anyone got any good theories what's going on here, given that this is a
> ~1995 vintage laptop with a Pentium-120 (which I'm assured doesn't have a
> VIA 686a ;-)?

Neptune chipsets at least had latching bugs on timer reads. What chipset
is the laptop ?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

odd timer bug, similar to VIA 686a symptoms

Post by Vojtech Pavli » Thu, 30 May 2002 21:10:16




> >> May 28 11:19:54 gull kernel: timer.c: VIA bug check triggered. Value read 65500 [0xffdc], re-read 65485 [0xffcd]
> > May 28 11:19:55 gull kernel: timer.c: VIA bug check triggered. Value read 65500 [0xffdc], re-read 65486 [0xffce]
> > May 28 11:19:56 gull kernel: timer.c: VIA bug check triggered. Value read 65500 [0xffdc], re-read 65486 [0xffce]
> > May 28 11:19:57 gull kernel: timer.c: VIA bug check triggered. Value read 65499 [0xffdb], re-read 65484 [0xffcc]
> > May 28 11:19:58 gull kernel: timer.c: VIA bug check triggered. Value read 65497 [0xffd9], re-read 65483 [0xffcb]

> > Anyone got any good theories what's going on here, given that this is a
> > ~1995 vintage laptop with a Pentium-120 (which I'm assured doesn't have a
> > VIA 686a ;-)?

> Neptune chipsets at least had latching bugs on timer reads. What chipset
> is the laptop ?

This is unlikely to be the latching bug - note the values are near to
65535 - that means the timer is reprogrammed to count from 0xffff down
instead from LATCH. That is because of the suspend I presume. What's
weird is that the VIA fix doesn't program it to the correct value, or
perhaps is that missing from the patch?

--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

odd timer bug, similar to VIA 686a symptoms

Post by Neale Bank » Thu, 30 May 2002 21:40:07




> >> May 28 11:19:54 gull kernel: timer.c: VIA bug check triggered. Value read 65500 [0xffdc], re-read 65485 [0xffcd]
> > May 28 11:19:55 gull kernel: timer.c: VIA bug check triggered. Value read 65500 [0xffdc], re-read 65486 [0xffce]
> > May 28 11:19:56 gull kernel: timer.c: VIA bug check triggered. Value read 65500 [0xffdc], re-read 65486 [0xffce]
> > May 28 11:19:57 gull kernel: timer.c: VIA bug check triggered. Value read 65499 [0xffdb], re-read 65484 [0xffcc]
> > May 28 11:19:58 gull kernel: timer.c: VIA bug check triggered. Value read 65497 [0xffd9], re-read 65483 [0xffcb]

> > Anyone got any good theories what's going on here, given that this is a
> > ~1995 vintage laptop with a Pentium-120 (which I'm assured doesn't have a
> > VIA 686a ;-)?

> Neptune chipsets at least had latching bugs on timer reads. What chipset
> is the laptop ?

Does it help in that it's got a CMD640?  If not, what am I looking for?

Thanks,
Neale.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

odd timer bug, similar to VIA 686a symptoms

Post by Alan Co » Thu, 30 May 2002 21:50:08



> Does it help in that it's got a CMD640?  If not, what am I looking for?

Thats the IDE controller. Look at lspci and the bridges and see what
they are. Those are generally the core chipset of the PC

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

odd timer bug, similar to VIA 686a symptoms

Post by Neale Bank » Thu, 30 May 2002 22:10:08




> > Does it help in that it's got a CMD640?  If not, what am I looking for?

> Thats the IDE controller. Look at lspci and the bridges and see what
> they are. Those are generally the core chipset of the PC

Straight from the metaphorical horses's virtual mouth:

gull:~# lspci
00:00.0 Host bridge: Acer Laboratories Inc. [ALi] M1451 (rev ad)
00:02.0 Non-VGA unclassified device: Acer Laboratories Inc. [ALi] M1449 (rev b2)
00:06.0 VGA compatible controller: Chips and Technologies F65545
00:07.0 IDE interface: CMD Technology Inc PCI0640 (rev 02)

Is the "[ALi] M1451" and "[ALi] M1449" are what we are looking for here?

Thanks,
Neale.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

odd timer bug, similar to VIA 686a symptoms

Post by Alan Co » Thu, 30 May 2002 23:00:14



> Straight from the metaphorical horses's virtual mouth:

> gull:~# lspci
> 00:00.0 Host bridge: Acer Laboratories Inc. [ALi] M1451 (rev ad)
> 00:02.0 Non-VGA unclassified device: Acer Laboratories Inc. [ALi] M1449 (rev b2)
> 00:06.0 VGA compatible controller: Chips and Technologies F65545
> 00:07.0 IDE interface: CMD Technology Inc PCI0640 (rev 02)

> Is the "[ALi] M1451" and "[ALi] M1449" are what we are looking for here?

Yes - thanks.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. Ethernet slowdown? Odd symptoms!

I've been running this setup for over a year: RedHat 6.0, 486DX100, 32MB.
It's my firewall for my ADSL connection, so it's multi-homed: one 3C509 for
the ADSL connection, one NE2000 clone for the LAN connection. The 3C509 uses
'pump' to obtain an IP address from my ADSL provider's DHCP server.

Over the last couple of months, I'm getting traffic slowdowns. Usually, when
I ping the provider's POP server by IP address, it says response time is
36ms (plus or minus 2). During a slowdown, response time shows as 1036ms,
2036...up to 6036ms. It is interesting that the last two digits are always
consistent. One or more ping packets will disappear, but they don't take six
seconds; the speed seems more or less consistent.

To fix this, I run '/etc/sysconfig/network-scripts/ifdown' and '..../ifup'
to restart the Ethernet device, and get another IP address. Then, I flush
and re-apply my 'ipchains' rules. That works for a while.

Any ideas? I'd re-install from scratch if I thought it would help. I'd
install RedHat 7.2, if I knew it would work on a 486-class machine; can
anyone confirm or deny that?

I look forward to hearing from you!

2. Question: Problems loading shmsys module....

3. Odd symptoms: Intermittant Connectivity

4. Problem with Xwindows

5. Help: VIA 686A sound chip!!

6. 'select' on sockets ...

7. ALSA sound for Via 686a again !

8. Remote printing under SOLARIS 2.7

9. modprobe for via 686a soundcard fails

10. ALSA Via 686A build problem, patch

11. via 686a audio driver rate locked at 48Khz

12. VIA VT8363 & 686A

13. [highly-experimental] via-mwq (Was: Re: VIA acknowledges North Bridge bug...)