From: Andrew Morton <akpm@linux-foundation.org>
To: "Vegard Nossum" <vegard.nossum@gmail.com>
Cc: kamalesh@linux.vnet.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.26-rc5-mm2 - kernel BUG at arch/x86/kernel/setup.c:388!
Date: Wed, 11 Jun 2008 12:43:03 -0700 [thread overview]
Message-ID: <20080611124303.017b853e.akpm@linux-foundation.org> (raw)
In-Reply-To: <19f34abd0806111112w5a6ed080jc098612806398828@mail.gmail.com>
On Wed, 11 Jun 2008 20:12:04 +0200
"Vegard Nossum" <vegard.nossum@gmail.com> wrote:
> On 6/9/08, Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
> > Hi Andrew,
> >
> > The 2.6.26-rc5-mm2 kernel panic's, while booting up on the x86_64
> > box with the attached .config file.
>
> (Please apologize for the strange way of replying to this message. It
> seems that LKML gave up delivering to my address, so I'm currently
> reading off lkml.org.)
>
> This should already be fixed, but Andrew refused to apply the patch
> before releasing the -mm1 (and -mm2 apparently).
a) nobody ever sent it to me and b) I was told about it too late to be
able to go work out what tree it was in, cherrypick it then merge it.
> I'm attaching the
> patch, can you see if it helps?
hallelujah, thanks. I already fished it out of linux-next.
I'm still hanging onto the 2.6.26-rc5-mm1 origin.patch and
linux-next.patch because I'm desperately trying to get things vaguely
stabilised so some VM testing can happen.
next prev parent reply other threads:[~2008-06-11 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 18:12 [BUG] 2.6.26-rc5-mm2 - kernel BUG at arch/x86/kernel/setup.c:388! Vegard Nossum
2008-06-11 19:43 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-10 5:31 2.6.26-rc5-mm2 Andrew Morton
2008-06-11 17:56 ` [BUG] 2.6.26-rc5-mm2 - kernel BUG at arch/x86/kernel/setup.c:388! Kamalesh Babulal
2008-06-11 18:28 ` Dave Hansen
2008-06-11 18:37 ` Vegard Nossum
2008-06-12 6:55 ` Kamalesh Babulal
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=20080611124303.017b853e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.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