From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@suse.cz>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Ingo Molnar <mingo@elte.hu>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>
Subject: Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325
Date: Thu, 26 Jun 2008 10:37:19 +0200 [thread overview]
Message-ID: <200806261037.20108.rjw@sisk.pl> (raw)
In-Reply-To: <20080624091516.GA5642@ucw.cz>
On Tuesday, 24 of June 2008, Pavel Machek wrote:
> Hi!
>
> > > What does ACPI claim the trip points are set to in this case? On the
> > > 6125, if IRQ 2 is enabled in the APIC then the DSDT sets all the thermal
> > > trip points to 16 degrees C. I suspect this means that enabling IRQ 2 is
> > > the wrong thing to do on this chipset.
> >
> > Ah, indeed, thanks for the hint. This is the output of
> >
> > $ cat /proc/acpi/thermal_zone/TZ*/trip_points
> >
> > in the failing case:
> >
> > critical (S5): 105 C
> > passive: 16 C: tc1=1 tc2=2 tsp=100 devices=C000 C001
> > active[0]: 16 C: devices=C34F
> > active[1]: 16 C: devices=C350
> > active[2]: 16 C: devices=C351
> > active[3]: 16 C: devices=C352
> > critical (S5): 100 C
> > passive: 16 C: tc1=1 tc2=2 tsp=300 devices=C000 C001
> > critical (S5): 100 C
> > passive: 16 C: tc1=1 tc2=2 tsp=300 devices=C000 C001
>
> Can we call the ACPI BIOS to be terminally broken at this point?
It is broken, but the configuration worked before the patch. Consequently,
the patch introduces a regression.
Thanks,
Rafael
next prev parent reply other threads:[~2008-06-26 8:37 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 13:22 linux-next: Tree for June 13 Stephen Rothwell
2008-06-13 17:13 ` linux-next: Tree for June 13 (XEN) Randy Dunlap
2008-06-13 22:16 ` Jeremy Fitzhardinge
2008-06-14 20:31 ` Jens Axboe
2008-06-14 23:13 ` Randy Dunlap
2008-06-15 6:11 ` Jeremy Fitzhardinge
2008-06-16 19:30 ` Jens Axboe
2008-06-16 20:40 ` Jeremy Fitzhardinge
2008-06-13 22:58 ` linux-next: Tree for June 13 (x86_64: panic) Randy Dunlap
2008-06-14 8:16 ` Stephen Rothwell
2008-06-14 23:15 ` Randy Dunlap
2008-06-15 16:33 ` linux-next: Tree for June 13 (soft lockup) Randy Dunlap
2008-06-15 18:31 ` linux-next: Tree for June 13 Rafael J. Wysocki
[not found] ` <200806160314.49489.rjw@sisk.pl>
2008-06-16 2:45 ` linux-next: Tree for June 13: IO APIC breakage on HP nx6325 Maciej W. Rozycki
2008-06-16 13:39 ` Rafael J. Wysocki
2008-06-16 15:39 ` Maciej W. Rozycki
2008-06-16 22:38 ` Rafael J. Wysocki
2008-06-16 23:05 ` Rafael J. Wysocki
2008-06-17 7:12 ` Thomas Gleixner
2008-06-17 20:44 ` Rafael J. Wysocki
2008-06-17 22:19 ` Rafael J. Wysocki
2008-06-17 22:25 ` Rafael J. Wysocki
2008-06-18 8:02 ` Thomas Gleixner
2008-06-18 12:41 ` Thomas Gleixner
2008-06-18 14:37 ` Rafael J. Wysocki
2008-06-18 14:40 ` Rafael J. Wysocki
2008-06-18 15:29 ` Thomas Gleixner
2008-06-21 22:47 ` Rafael J. Wysocki
2008-06-18 13:15 ` Ingo Molnar
2008-06-18 13:14 ` Ingo Molnar
2008-06-17 20:59 ` Rafael J. Wysocki
2008-06-17 21:19 ` Maciej W. Rozycki
2008-06-17 21:38 ` Rafael J. Wysocki
2008-06-17 22:53 ` Rafael J. Wysocki
2008-06-18 4:02 ` Maciej W. Rozycki
2008-06-18 19:06 ` Cyrill Gorcunov
2008-06-18 22:36 ` Maciej W. Rozycki
2008-06-20 18:59 ` Cyrill Gorcunov
2008-06-20 20:44 ` Maciej W. Rozycki
2008-06-18 22:11 ` Rafael J. Wysocki
2008-06-18 23:39 ` Maciej W. Rozycki
2008-06-19 0:25 ` Rafael J. Wysocki
2008-06-20 0:35 ` Maciej W. Rozycki
2008-06-20 11:53 ` Rafael J. Wysocki
2008-06-20 11:57 ` Matthew Garrett
2008-06-20 12:22 ` Rafael J. Wysocki
2008-06-20 12:27 ` Matthew Garrett
2008-06-21 1:09 ` Maciej W. Rozycki
2008-06-21 1:40 ` Matthew Garrett
2008-06-21 2:41 ` Maciej W. Rozycki
2008-06-21 12:38 ` Matthew Garrett
2008-06-26 19:52 ` Rafael J. Wysocki
2008-06-27 0:06 ` Maciej W. Rozycki
2008-06-29 14:00 ` Rafael J. Wysocki
2008-06-29 19:05 ` Maciej W. Rozycki
2008-06-29 19:23 ` Rafael J. Wysocki
2008-06-29 19:56 ` Maciej W. Rozycki
2008-06-29 20:02 ` Ingo Molnar
2008-06-29 20:14 ` Maciej W. Rozycki
2008-06-29 23:06 ` Rafael J. Wysocki
2008-06-30 0:45 ` Andi Kleen
2008-06-30 0:47 ` Matthew Garrett
2008-06-30 1:39 ` Maciej W. Rozycki
2008-06-30 9:24 ` Andi Kleen
2008-07-02 1:19 ` Maciej W. Rozycki
2008-06-30 10:41 ` Rafael J. Wysocki
2008-07-02 1:48 ` Maciej W. Rozycki
2008-07-02 9:35 ` Andi Kleen
2008-06-29 22:59 ` Rafael J. Wysocki
2008-06-29 22:56 ` Rafael J. Wysocki
2008-06-30 1:00 ` Maciej W. Rozycki
2008-06-30 9:06 ` Matthew Garrett
2008-06-30 15:29 ` Maciej W. Rozycki
2008-06-30 15:35 ` Matthew Garrett
2008-06-29 19:23 ` Matthew Garrett
2008-06-29 19:31 ` Rafael J. Wysocki
2008-06-29 20:03 ` Maciej W. Rozycki
2008-06-29 20:07 ` Matthew Garrett
2008-06-29 20:16 ` Maciej W. Rozycki
2008-06-24 9:15 ` Pavel Machek
2008-06-26 8:37 ` Rafael J. Wysocki [this message]
2008-06-27 1:53 ` Maciej W. Rozycki
2008-07-08 12:48 ` Pavel Machek
2008-06-21 1:49 ` Maciej W. Rozycki
2008-06-19 9:35 ` Ingo Molnar
2008-06-19 18:17 ` Maciej W. Rozycki
2008-06-20 10:44 ` Ingo Molnar
2008-06-20 13:11 ` Thomas Gleixner
2008-06-20 20:56 ` Maciej W. Rozycki
2008-06-17 0:08 ` Len Brown
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=200806261037.20108.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=pavel@suse.cz \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).