From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
lkml <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Mike Travis <travis@sgi.com>
Subject: Re: kernel BUG at arch/x86/kernel/io_apic_64.c:357!
Date: Wed, 30 Jul 2008 01:51:34 +0530 [thread overview]
Message-ID: <20080729202134.GC4484@linux.vnet.ibm.com> (raw)
In-Reply-To: <86802c440807291220t7813effcwb32ae6c18e3cddfe@mail.gmail.com>
On Tue, Jul 29, 2008 at 12:20:01PM -0700, Yinghai Lu wrote:
> On Tue, Jul 29, 2008 at 11:35 AM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> > On Tue, Jul 29, 2008 at 9:09 AM, Dhaval Giani <dhaval@linux.vnet.ibm.com> wrote:
> >> Hi Ingo, Thomas,
> >>
> >> Hit this on 2.6.27-rc1
> >>
> >> (The kernel bug is at line 356 (Its 357 as I applied a debug patch to
> >> print out the irq) (Full dmesg and .config attached)
> >
> > can you boot with "debug apic=verbose pci=routeirq"?
>
> please try attached patch
>
Thanks. The patch gets my system to boot.
--
regards,
Dhaval
prev parent reply other threads:[~2008-07-29 20:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 16:09 kernel BUG at arch/x86/kernel/io_apic_64.c:357! Dhaval Giani
2008-07-29 18:35 ` Yinghai Lu
2008-07-29 19:20 ` Yinghai Lu
2008-07-29 20:14 ` Eric W. Biederman
2008-07-29 20:37 ` Yinghai Lu
2008-07-29 22:17 ` Mike Travis
2008-07-29 22:21 ` Yinghai Lu
2008-07-29 23:12 ` Eric W. Biederman
2008-07-30 0:00 ` Alan Cox
2008-07-30 1:29 ` Eric W. Biederman
2008-07-29 23:12 ` Eric W. Biederman
2008-07-29 23:42 ` Jeremy Fitzhardinge
2008-07-30 0:01 ` Eric W. Biederman
2008-07-30 0:50 ` Jeremy Fitzhardinge
2008-07-30 1:36 ` Eric W. Biederman
2008-08-01 17:48 ` Jeremy Fitzhardinge
2008-07-29 20:21 ` Dhaval Giani [this message]
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=20080729202134.GC4484@linux.vnet.ibm.com \
--to=dhaval@linux.vnet.ibm.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=yhlu.kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.