public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [stable] Regression in 2.6.32.2: segfault on halt
Date: Sun, 20 Dec 2009 12:55:50 +0100	[thread overview]
Message-ID: <4B2E10C6.7050304@googlemail.com> (raw)
In-Reply-To: <20091220054847.GF32739@1wt.eu>

[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]

Willy Tarreau wrote:
> On Sat, Dec 19, 2009 at 04:10:49PM +0100, Holger Hoffstaette wrote:
>> After updating to 2.6.32.2 last night (using same config from .32.1) I
>> noticed that "halt" now trips during shutdown and won't power the
>> machine down any longer. This happens reproducibly on two completely
>> different machines, so it looks like a generic problem and regression,
>> since it did not happen in .32.1. Note that "reboot" works as expected -
>> only "halt" crashes.
> 
> I have it working fine here. So your config helps to reproduce the issue.
> Care to post it ?

Attached, if it matters. However I managed to find some time with a spare
machine and always wanted to try bisect, so that's what I did - apparently
successfully:

root>git bisect bad
37ed2d7007a65874850f3e357c095806c3756330 is the first bad commit
commit 37ed2d7007a65874850f3e357c095806c3756330
Author: Mike Galbraith <efault@gmx.de>
Date:   Wed Nov 4 17:53:50 2009 +0100

    sched: Rate-limit newidle

    commit 1b9508f6831e10d53256825de8904caa22d1ca2c upstream.

    Rate limit newidle to migration_cost. It's a win for all
    stages of sysbench oltp tests.

    Signed-off-by: Mike Galbraith <efault@gmx.de>
    Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
    LKML-Reference: <new-submission>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

aka:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;a=commit;h=37ed2d7007a65874850f3e357c095806c3756330

My understanding is that this was supposed to be a performance fix for the
CPU scheduler. Maybe it collides with CPU shutdown on halt?

Holger

[-- Attachment #2: kernel-config-x86-2.6.32.2 --]
[-- Type: message/delivery-status, Size: 61263 bytes --]

  reply	other threads:[~2009-12-20 12:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-19 15:10 [stable] Regression in 2.6.32.2: segfault on halt Holger Hoffstaette
2009-12-20  5:48 ` Willy Tarreau
2009-12-20 11:55   ` Holger Hoffstätte [this message]
2009-12-20 13:06     ` Willy Tarreau
2009-12-20 13:27       ` Holger Hoffstätte
2009-12-20 14:30         ` Mike Galbraith
2009-12-20 15:24           ` Holger Hoffstätte
     [not found]           ` <4B2E4056.50708@googlemail.com>
     [not found]             ` <1261339759.9188.4.camel@marge.simson.net>
     [not found]               ` <4B2EA5F8.4030907@googlemail.com>
     [not found]                 ` <1261372511.6048.3.camel@marge.simson.net>
     [not found]                   ` <4B2F3DD3.5090506@googlemail.com>
     [not found]                     ` <1261387782.25983.5.camel@marge.simson.net>
2009-12-21  9:35                       ` Mike Galbraith
2009-12-20 14:05       ` Mike Galbraith
2009-12-20 14:19         ` Willy Tarreau

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=4B2E10C6.7050304@googlemail.com \
    --to=holger.hoffstaette@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=w@1wt.eu \
    /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