All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pasi Savolainen <psavo-X3B1VOXEql0@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
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-VZcQ4qwp+CzQLMG2gba6HQ@public.gmane.org>:
> 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/>

WARNING: multiple messages have this Message-ID (diff)
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: 9+ 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  4:21 ` Dieter Nützel
     [not found] ` <200308060621.06216.d.nuetzel-VZcQ4qwp+CzQLMG2gba6HQ@public.gmane.org>
2003-08-06 10:08   ` Adrian Bunk
2003-08-06 10:08     ` Adrian Bunk
     [not found]     ` <20030806100815.GH16091-cg1h10c7RbKzQB+pC5nmwQ@public.gmane.org>
2003-08-06 16:49       ` Dieter Nützel
2005-05-19  6:24         ` Dieter Nützel
2003-08-06 16:49         ` Dieter Nützel
2003-08-06 18:26         ` Pasi Savolainen [this message]
2003-08-06 18:26           ` Pasi Savolainen

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-x3b1voxeql0@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.