public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Merz <linux@merz-ka.de>
To: Brian Gerst <brgerst@gmail.com>
Cc: Matthias Merz <linux@merz-ka.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: Regression in linux 2.6.37: failure on remount / (ext4) rw
Date: Tue, 18 Jan 2011 14:47:21 +0100	[thread overview]
Message-ID: <20110118134721.GA20840@merz.inka.de> (raw)
In-Reply-To: <AANLkTimyKXfJ1x8tgwrr1hYnNLrPfgE1NTe4z7L6tUDm@mail.gmail.com>

Hello together,

Am Mo, 17.01.2011 07:32 schrieb Brian Gerst
> On Fri, Jan 14, 2011 at 9:04 AM, Matthias Merz <linux@merz-ka.de> wrote:
> > git bisect now told me "22d4cd4c4dce6d7b7d9a7e396aa4f87fe7a649b1 is the
> > first bad commit", which is titled: "x86-32: Allocate irq stacks
> > seperate from percpu area".
> > I reverted this change (and following 47f19a0814 due to #defines) and
> > waited over the night until this morning. That revert really seems to
> > fix my problem. So maybe in my special case something goes wrong with
> > the new method?
> 
> Does this patch fix the problem?
> 
> Subject: [PATCH] x86: Clear irqstack thread_info
> 
> Make sure that the thread_info part of the irqstack is initialized
> to zeroes.
> 
> Signed-off-by: Brian Gerst <brgerst@gmail.com>


Yes, I tried booting three times with that patch enabled, the last time
this morning after power-down over night; all seems fine so far.
Thank you very much for the prompt fix!


Yours
Matthias Merz

-- 
"I hope to die before I *have* to use Microsoft Word."
     - Donald E. Knuth, 2001-10-02 in Tübingen.

  reply	other threads:[~2011-01-18 13:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110110223154.GA9739@merz.inka.de>
2011-01-11  7:50 ` Regression in linux 2.6.37: failure to boot, caused by commit 37d57443d5 (mm/slub.c) Pekka Enberg
2011-01-11 13:09   ` Regression in linux 2.6.37: failure on remount / (ext4) rw (was: Re: Regression in linux 2.6.37: failure to boot, caused by commit 37d57443d5 (mm/slub.c)) Matthias Merz
2011-01-12  7:03     ` Pekka Enberg
2011-01-14 14:04       ` Regression in linux 2.6.37: failure on remount / (ext4) rw Matthias Merz
2011-01-17 12:32         ` Brian Gerst
2011-01-18 13:47           ` Matthias Merz [this message]
2011-01-18 13:49           ` Pekka Enberg
2011-01-18 19:03           ` [tip:x86/urgent] x86: Clear irqstack thread_info tip-bot for Brian Gerst
2011-01-18 21:45             ` Pekka Enberg
2011-01-18 22:09               ` Ingo Molnar

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=20110118134721.GA20840@merz.inka.de \
    --to=linux@merz-ka.de \
    --cc=brgerst@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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