linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pasi Savolainen <psavo@iki.fi>
To: linux-kernel@vger.kernel.org
Cc: acpi-devel@lists.sourceforge.net
Subject: Re: 2.4.22-rc1 + ACPI patch: amd76x_pm do not work any longer
Date: Wed, 6 Aug 2003 18:26:10 +0000 (UTC)	[thread overview]
Message-ID: <bgrh82$3sp$1@main.gmane.org> (raw)
In-Reply-To: 200308061849.01416.d.nuetzel@wearabrain.de

* Dieter Nützel <d.nuetzel@wearabrain.de>:
> Am Mittwoch, 6. August 2003 12:08 schrieb Adrian Bunk:
>> On Wed, Aug 06, 2003 at 06:21:06AM +0200, Dieter Nützel wrote:
>> > Hello,
>>
>> Hi Dieter,
>>
>> > I had it running very well on my dual Athlon MP 1900+ for several months
>> > before. Latest Kernel was 2.4.22-pre5+ACPI patch.
>> >
>> > Any changes?
>> > I changed lm_sensors from 2.7.0 (?) to 2.8.0
> 
> This one is the culprit.
> Reverting to 2.7.0 cure my problems.

It's most probably because somebody (temp. monitoring) is already using
the south bridge, so just plain grabbing of it doesn't work. I faced
this with port to 2.6 and it's handled thus:


+       /* Find southbridge */
+       pdev_sb = NULL;
+       while((pdev_sb = pci_find_device(PCI_ANY_ID, PCI_ANY_ID, pdev_sb)) != NULL) {
+               if(pci_match_device(amd_sb_tbl, pdev_sb) != NULL)
+                       goto found_sb;
+       }
+       printk(KERN_ERR "amd76x_pm: Could not find southbridge\n");
+       return -ENODEV;


It could work in 2.4 too.


-- 
   Psi -- <http://www.iki.fi/pasi.savolainen>
Vivake -- Virtuaalinen valokuvauskerho <http://members.lycos.co.uk/vivake/>


      reply	other threads:[~2003-08-06 18:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06  4:21 2.4.22-rc1 + ACPI patch: amd76x_pm do not work any longer Dieter Nützel
2003-08-06 10:08 ` Adrian Bunk
2003-08-06 16:49   ` Dieter Nützel
2003-08-06 18:26     ` Pasi Savolainen [this message]

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='bgrh82$3sp$1@main.gmane.org' \
    --to=psavo@iki.fi \
    --cc=acpi-devel@lists.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;
as well as URLs for NNTP newsgroup(s).