From: Mike Galbraith <efault@gmx.de>
To: Carsten Emde <C.Emde@osadl.org>
Cc: Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Len Brown <lenb@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Asit Mallick <asit.k.mallick@intel.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Linux 2.6.33.8
Date: Fri, 01 Apr 2011 06:35:55 +0200 [thread overview]
Message-ID: <1301632555.4766.5.camel@marge.simson.net> (raw)
In-Reply-To: <4D94C666.3060206@osadl.org>
On Thu, 2011-03-31 at 20:22 +0200, Carsten Emde wrote:
> Greg,
>
> > I'm announcing the release of the 2.6.33.8 kernel.
> >
> > This is primarily for the use of those people who are stuck using the
> > .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
> > is welcome to use this one as well.
> Thanks a lot for your work. It's highly appreciated.
>
> While preparing 2.6.33.8/9 plus PREEMPT_RT patches for quality
> assurance in our farm, I found that the "halt" command no longer
> powers down the pretest machine (i7/Gulftown); this misbehavior occurs
> with and without the PREEMPT_RT patches.
>
> 2.6.33.7:
> # halt
> sd 0:0:0:0: [sda] Synchronizing SCSI cache
> sd 0:0:0:0: [sda] Stopping disk
> sd 2:0:0:0: [sdb] Synchronizing SCSI cache
> sd 2:0:0:0: [sdb] Stopping disk
> The machine is powered down.
>
> 2.6.33.8:
> sd 0:0:0:0: [sda] Synchronizing SCSI cache
> sd 0:0:0:0: [sda] Stopping disk
> sd 2:0:0:0: [sdb] Synchronizing SCSI cache
> sd 2:0:0:0: [sdb] Stopping disk
> ACPI: Preparing to enter system sleep state S5
> Disabling non-boot CPUs ...
> The machine is NOT powered down. Can be powered down only by pulling
> the power plug or holding the on/off button for 5 seconds.
(FWIW, my x3550 M3 (E5620) and Q6600 power down fine with 2.6.33.9-rt30)
> Bisecting from 2.6.33.7 to 2.6.33.8 revealed:
> 74a6e0fd8fc216cfa5edcde4bd356a8972cbc74c is the first bad commit
> commit 74a6e0fd8fc216cfa5edcde4bd356a8972cbc74c
> Author: H. Peter Anvin <hpa@linux.intel.com>
> Date: Fri Dec 10 23:57:04 2010 -0500
>
> x86, hotplug: Use mwait to offline a processor, fix the legacy case
>
> upstream ea53069231f9317062910d6e772cca4ce93de8c8
> x86, hotplug: Use mwait to offline a processor, fix the legacy case
The question would appear to be does mainline beyond this point exhibit
the same symptom?
-Mike
next prev parent reply other threads:[~2011-04-01 4:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 20:41 Linux 2.6.33.8 Greg KH
2011-03-21 20:41 ` Greg KH
2011-03-31 18:22 ` Carsten Emde
2011-04-01 4:35 ` Mike Galbraith [this message]
2011-04-02 9:14 ` Carsten Emde
2011-04-02 10:24 ` Alexander Holler
2011-04-02 11:27 ` Carsten Emde
2011-04-04 9:20 ` Alexander Holler
2011-04-02 21:08 ` Carsten Emde
2011-04-02 22:23 ` Thomas Gleixner
2011-04-02 7:33 ` Intel i7/X 980 freezes with CONFIG_INTEL_IDLE and frequency scaling Carsten Emde
2011-04-04 14:19 ` Carsten Emde
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=1301632555.4766.5.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=C.Emde@osadl.org \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@linux.intel.com \
--cc=asit.k.mallick@intel.com \
--cc=gregkh@suse.de \
--cc=hpa@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@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