From: Adrian Bunk <bunk-cg1h10c7RbKzQB+pC5nmwQ@public.gmane.org>
To: "Dieter Nützel" <d.nuetzel-VZcQ4qwp+CzQLMG2gba6HQ@public.gmane.org>
Cc: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>,
Linux Kernel List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
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 12:08:15 +0200 [thread overview]
Message-ID: <20030806100815.GH16091@fs.tum.de> (raw)
In-Reply-To: <200308060621.06216.d.nuetzel-VZcQ4qwp+CzQLMG2gba6HQ@public.gmane.org>
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
>
> System:
> dual Athlon MP 1900+
> MSI K7D Master-L
>
> 2.4.22-rc1
> acpi-20030730-2.4.22-pre8.diff
> preempt-kernel-rml-2.4.21-1.patch
>...
does an unpatched 2.4.22-rc1 work?
If yes, please check which of the two patches causes the problem.
> Thanks.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-08-06 10:08 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
[not found] ` <200308060621.06216.d.nuetzel-VZcQ4qwp+CzQLMG2gba6HQ@public.gmane.org>
2003-08-06 10:08 ` Adrian Bunk [this message]
[not found] ` <20030806100815.GH16091-cg1h10c7RbKzQB+pC5nmwQ@public.gmane.org>
2003-08-06 16:49 ` Dieter Nützel
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=20030806100815.GH16091@fs.tum.de \
--to=bunk-cg1h10c7rbkzqb+pc5nmwq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org \
--cc=d.nuetzel-VZcQ4qwp+CzQLMG2gba6HQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox