public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Tonino <ttonino@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch] amd athlon cooling on kt266/266a chipset
Date: Fri, 25 Jan 2002 09:54:35 +0100	[thread overview]
Message-ID: <3C511D4B.5060205@users.sf.net> (raw)

Daniel wrote:

 > hmmm ... maybe it is realy hardware depending ... with my
 > relativly new motherboard and fast cpu/system componends
 > it is no problem at all ...
 > looking video, hearing music , ... no problems ...

I've played with lvcool on my box: Abit KT7A (KT133A), Athlon 1.1 GHz.

When I use my BT848 tv card to watch tv, there usually are some signs 
that the PCI transfer rate is not high enough - some bits of image do 
not get refreshed, but nothing major when lvcool is off.

But when running lvcool, the whole thing would look like a special 
effects show: not even half the image would be refreshed every frame.

The BT848 writes directly over the PCI to AGP bridge to the video card 
RAM so the CPU is completely idle. Thus it seems likely that the bus 
performance is affected. ISTR that the actual 'disconnect' effect is 
caused by a read from a south bridge register. I assume that read takes 
a while, and this keeps the bus busy. This may not be a prblem in 
itself, unless the PCU has the highest priority in the system, or has 
the possibility to 'just do another cycle'.

However, with lvcool the CPU temperature dropped remarkably - from 20 
degrees above case to 2 degrees above case.

But after updating the BIOS to version 3R, lvcool only results in a hard 
crash. So now I found out how PCI latencies work, I have no change to 
test. I can imagine that playing with the host bridge latencies will 
solve this, just as it can improve on the video playing without lvcool.

That said, the 3R bios version does not support ACPI based disconnect at 
all. But why lvcool wedges the system so well? Maybe some ACPI activity? 
But then, my kernel was the same before and after the BIOS update.


Thomas


             reply	other threads:[~2002-01-25  9:40 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25  8:54 Thomas Tonino [this message]
     [not found] <Pine.LNX.4.33.0201241223260.28872-100000@coffee.psychology.mcmaster.ca>
2002-01-24 18:25 ` [patch] amd athlon cooling on kt266/266a chipset Hans-Peter Jansen
2002-01-24 21:33   ` Daniel Nofftz
  -- strict thread matches above, loose matches on Subject: below --
2002-01-24 15:58 Dieter Nützel
     [not found] <200201232321.AAA02845@rzmail.uni-trier.de>
2002-01-24 10:32 ` Daniel Nofftz
     [not found] <200201232023.VAA07669@rzmail.uni-trier.de>
2002-01-23 20:55 ` Daniel Nofftz
     [not found] <000701c1a42c$8c6f8680$0201a8c0@HOMER>
2002-01-23 19:21 ` Daniel Nofftz
2002-01-23 20:36   ` Hans-Peter Jansen
2002-01-23 20:38     ` Daniel Nofftz
2002-01-23 20:50       ` Joel Jaeggli
2002-01-24  2:33   ` Dieter Nützel
     [not found]   ` <E16TZhr-00049f-00@mxng04.kundenserver.de>
2002-01-24 12:59     ` Hans-Peter Jansen
2002-01-24 14:23       ` Ed Sweetman
2002-01-25 12:23         ` Matthew Sackman
2002-01-24 14:39   ` Martin Eriksson
2002-01-24 21:06     ` Daniel Nofftz
2002-01-24 23:18       ` Dieter Nützel
2002-01-24 23:27       ` Dieter Nützel
2002-01-25 14:17         ` Liakakis Kostas
2002-01-25 15:31           ` Ed Sweetman
2002-01-25 16:10             ` Liakakis Kostas
2002-01-25 17:19               ` Dave Jones
     [not found] <200201222243.XAA14711@rzmail.uni-trier.de>
2002-01-23  7:42 ` Daniel Nofftz
2002-01-22 22:01 Dieter Nützel
2002-01-22 22:21 ` Daniel Nofftz
2002-01-22 22:42   ` Dieter Nützel
2002-01-24  5:14     ` Timothy Covell
2002-01-23  7:27       ` Daniel Nofftz
2002-01-23 11:55         ` Vojtech Pavlik
2002-01-23 13:19           ` Daniel Nofftz
2002-01-23 15:47             ` Ed Sweetman
2002-01-23 19:18               ` Daniel Nofftz
2002-01-24 18:14         ` Timothy Covell
2002-01-23 19:24           ` Daniel Nofftz
2002-01-23 20:22             ` Dieter Nützel
2002-01-24  9:55             ` Pavel Machek
2002-01-24 21:50               ` Daniel Nofftz
2002-01-23 20:18       ` Dieter Nützel
     [not found]   ` <200201232018.g0NKI9Q06525@dydimus.dreamhost.com>
     [not found]     ` <200201232248.g0NMmqL01292@home.ashavan.org.>
2002-01-23 23:20       ` Dieter Nützel
2002-01-22 17:15 Daniel Nofftz
2002-01-22 18:51 ` Lee Packham
2002-01-22 19:03   ` Daniel Nofftz
2002-01-23 20:16 ` Hans-Peter Jansen
2002-01-23 20:29   ` Ed Sweetman
2002-01-23 20:54     ` Hans-Peter Jansen
2002-01-23 21:04       ` Daniel Nofftz
2002-01-23 22:25       ` Hans-Peter Jansen
2002-01-24  9:54         ` Daniel Nofftz
2002-01-24  9:47     ` Daniel Nofftz
2002-01-24 12:35       ` Hans-Peter Jansen
2002-01-24 20:54         ` Daniel Nofftz
2002-01-24 21:16           ` Disconnect
2002-01-24 21:55             ` Daniel Nofftz
2002-01-24 22:16           ` Hans-Peter Jansen
2002-01-30  8:58             ` Daniel Nofftz
2002-01-23 20:49   ` Daniel Nofftz
2002-01-23 21:16     ` Hans-Peter Jansen
2002-01-24  9:49       ` Daniel Nofftz
2002-01-24 12:40         ` Rasmus Bøg Hansen
2002-01-24 20:57           ` Daniel Nofftz
2002-01-24 21:14             ` Rasmus Bøg Hansen
2002-01-24 21:52               ` Daniel Nofftz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C511D4B.5060205@users.sf.net \
    --to=ttonino@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox