From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: LM Sensors <sensors@stimpy.netroedge.com>
Cc: Len Brown <len.brown@intel.com>,
David Shaohua <shaohua.li@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.28 breaks lm_sensors
Date: Sun, 21 Nov 2004 19:01:11 -0200 [thread overview]
Message-ID: <20041121210111.GC23689@logos.cnet> (raw)
In-Reply-To: <20041120114141.3e0f5f47.khali@linux-fr.org>
Hi,
On Sat, Nov 20, 2004 at 11:41:41AM +0100, Jean Delvare wrote:
> Hi Marcelo, hi all,
>
> We have been having reports that recent changes in the ACPI subsystem of
> the Linux 2.4 kernel are breaking lm_sensors on a fairly large number of
> systems. In particular, 2.4.28 is affected.
> http://www2.lm-sensors.nu/~lm78/readticket.cgi?ticket=1761
> http://www2.lm-sensors.nu/~lm78/readticket.cgi?ticket=1819
> http://www2.lm-sensors.nu/~lm78/readticket.cgi?ticket=1820
>
> I did not report earlier because I thought the problem would be fixed by
> the ACPI folks before 2.4.28 would be released. Unfortunately it wasn't.
Ouch :(
> The problem is already known, was reported for 2.6 kernels 4 months ago
> and fixed there by David Shaohua. See this kernel bug report for the
> detail of symptoms and the solution:
> http://bugzilla.kernel.org/show_bug.cgi?id=3049
>
> Applying the proposed patch to a 2.4.28 kernel make lm_sensors work
> again on affected systems, while not causing trouble to unaffected ones
> as far as I can tell.
>
> Len, David, any reason not to apply the same fix to the 2.4 tree?
It looks like this should come through the acpi BK tree. Len, David?
prev parent reply other threads:[~2004-11-22 1:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 10:41 Linux 2.4.28 breaks lm_sensors Jean Delvare
2004-11-21 21:01 ` Marcelo Tosatti [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=20041121210111.GC23689@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.com \
--cc=shaohua.li@intel.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