public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Lepple <clepple@ghz.cc>
To: Tony Lindgren <tony@atomide.com>, john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>, psavo@iki.fi
Subject: Re: [PATCH] amd76x_pm on 2.6.0-test9 cleanup
Date: Tue, 4 Nov 2003 14:44:56 -0500	[thread overview]
Message-ID: <200311041444.57464.clepple@ghz.cc> (raw)
In-Reply-To: <20031104191504.GB1042@atomide.com>

On Tuesday 04 November 2003 02:15 pm, Tony Lindgren wrote:
> I've heard of timing problems if it's compiled in, but supposedly they
> don't happen when loaded as module.

In some of the earlier testX versions of the kernel, I did not see any 
difference between compiling as a module, and compiling into the kernel. (It 
is currently a module on my system.)

I did, however, manage to keep ntpd happy by reducing HZ to 100. Even raising 
HZ to 200 is enough to throw off its PLL. The machine is idle for 90% of the 
day, though, so I don't know if the PLL is adapting to the fact that the 
system is idling, but the values for tick look reasonable.

> Then the 2.4 version does not load if i2c-amd756 is loaded, but this may
> have been already fixed by this patch, I have not verified it yet though.

Pasi's patch against test9 seems to work fine in this regard. I am running 
with i2c_amd756 and amd_k7_agp now, and neither one has trouble loading 
anymore (after a cold boot, anyway).

> I have problem where my S2460 goes into sleep for a while if compiled in,
> but this does not happen when loaded as module.

After a warm reboot on my S2460 motherboard, it seems as though the module 
occasionally needs to receive an interrupt from somewhere ACPI-related. Most 
of the time, this means that I have to press either the soft power button or 
the sleep button to get the system to continue booting (!).

I am using the default #defines (i.e. no C3, POS or NTH enabled).

Info on the northbridge:

$ lspci -vn -s 0:0
00:00.0 Class 0600: 1022:700c (rev 11)
...

and the southbridge:

$ lspci -vn -s 7:3
00:07.3 Class 0680: 1022:7413 (rev 01)
...

I looked through the chipset documentation again (specifically checking the 
errata for these revisions), and nothing jumped out at me. I won't be able to 
look at this in depth for another month or two, though.

-- 
Charles Lepple
ghz.cc!clepple


  reply	other threads:[~2003-11-04 19:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04  0:22 [PATCH] amd76x_pm on 2.6.0-test9 cleanup Tony Lindgren
2003-11-04 18:41 ` john stultz
2003-11-04 19:15   ` Tony Lindgren
2003-11-04 19:44     ` Charles Lepple [this message]
2003-11-04 20:05       ` Tony Lindgren
2003-11-04 20:52         ` Charles Lepple
2003-11-04 22:38         ` Charles Lepple
2003-11-04 23:11           ` Tony Lindgren
2003-11-04 23:46             ` Pasi Savolainen
2003-11-04 20:21     ` Pasi Savolainen
2003-11-04 20:55       ` Tony Lindgren
2003-11-04 20:57         ` john stultz
2003-11-04 21:14           ` Tony Lindgren
2003-11-14 11:56         ` Pasi Savolainen
2003-11-04 21:01       ` Charles Lepple
2003-11-04 21:17         ` Tony Lindgren
2003-11-05 19:42     ` Felix Maibaum

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=200311041444.57464.clepple@ghz.cc \
    --to=clepple@ghz.cc \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psavo@iki.fi \
    --cc=tony@atomide.com \
    /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