From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Andy Whitcroft <apw@shadowen.org>
Subject: Re: [BUG] linux-next: Tree for May 19/20/21 - BUG at arch/x86/kernel/io_apic_64.c:353!
Date: Thu, 22 May 2008 10:15:36 +1000 [thread overview]
Message-ID: <20080522101536.c449e082.sfr@canb.auug.org.au> (raw)
In-Reply-To: <48345B5E.1090506@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
Hi Kamalesh,
On Wed, 21 May 2008 22:56:54 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
>
> This kernel panic while booting up is reproducible with the next-20080519,
> next-20080520 and next-20080521 kernels.
Thanks for the reports.
Can you include the config when you send these, please. If it a standard
config then just say "defconfig" (or whatever) otherwise please attach
the config you used.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-22 0:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 7:41 linux-next: Tree for May 19 Stephen Rothwell
2008-05-19 10:27 ` [BUG] linux-next: Tree for May 19 - BUG at arch/x86/kernel/io_apic_64.c:353! Kamalesh Babulal
2008-05-21 17:26 ` [BUG] linux-next: Tree for May 19/20/21 " Kamalesh Babulal
2008-05-22 0:15 ` Stephen Rothwell [this message]
2008-05-22 10:22 ` Kamalesh Babulal
2008-05-19 17:08 ` [BUILD_FAILURE] linux-next: Tree for May 19 - build fails on cryptd_alloc_hash () Kamalesh Babulal
2008-05-19 17:26 ` Randy Dunlap
2008-05-20 6:40 ` Herbert Xu
2008-05-19 18:42 ` linux-next: Tree for May 19 Thomas Meyer
2008-05-20 4:19 ` Stephen Rothwell
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=20080522101536.c449e082.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=apw@shadowen.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
/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).