From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] x86, reboot: skip reboot_fixups in early boot phase
Date: Fri, 25 Jan 2013 10:13:03 +0900 [thread overview]
Message-ID: <20130125011303.GA3401@lge.com> (raw)
In-Reply-To: <CAErSpo5_dgH1Au3QChVrhqBY_Fm54+Aw_ZiwGf2JSsgQaR1dug@mail.gmail.com>
Hello, Bjorn.
On Thu, Jan 24, 2013 at 10:45:13AM -0700, Bjorn Helgaas wrote:
> On Fri, Dec 28, 2012 at 6:50 AM, Joonsoo Kim <js1304@gmail.com> wrote:
> > During early boot phase, PCI bus subsystem is not yet initialized.
> > If panic is occured in early boot phase and panic_timeout is set,
> > code flow go into emergency_restart() and hit mach_reboot_fixups(), then
> > encounter another panic. When second panic, we can't hold a panic_lock, so
> > code flow go into panic_smp_self_stop() which prevent system to restart.
> >
> > For avoid second panic, skip reboot_fixups in early boot phase.
> > It makes panic_timeout works in early boot phase.
> >
> > Cc: Thomas Gleixner <tglx@linutronix.de>
> > Cc: Ingo Molnar <mingo@redhat.com>
> > Cc: "H. Peter Anvin" <hpa@zytor.com>
> > Signed-off-by: Joonsoo Kim <js1304@gmail.com>
> >
> > diff --git a/arch/x86/kernel/reboot_fixups_32.c b/arch/x86/kernel/reboot_fixups_32.c
> > index c8e41e9..b9b8ec9 100644
> > --- a/arch/x86/kernel/reboot_fixups_32.c
> > +++ b/arch/x86/kernel/reboot_fixups_32.c
> > @@ -89,6 +89,10 @@ void mach_reboot_fixups(void)
> > if (in_interrupt())
> > return;
> >
> > + /* During early boot phase, PCI is not yet initialized */
> > + if (system_state == SYSTEM_BOOTING)
> > + return;
> > +
> > for (i=0; i < ARRAY_SIZE(fixups_table); i++) {
> > cur = &(fixups_table[i]);
> > dev = pci_get_device(cur->vendor, cur->device, NULL);
>
> I guess you're saying that if we call pci_get_device() too early, it
> panics? Did you figure out why that happens?
>
> If we call pci_get_device() before PCI has been initialized, it would
> be good if it just returned NULL, indicating that we didn't find any
> matching device. I looked briefly, and I thought that's what would
> happen, but apparently I'm missing something.
In bus_find_device(), klist_iter_init_node() is called with
@bus->p->klist_device. Before initialization, bus->p is NULL,
so panic is occured.
> Bjorn
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2013-01-25 1:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 13:50 [PATCH] x86, reboot: skip reboot_fixups in early boot phase Joonsoo Kim
2013-01-24 17:45 ` Bjorn Helgaas
2013-01-25 1:13 ` Joonsoo Kim [this message]
2013-01-25 2:59 ` Bjorn Helgaas
2013-01-25 4:14 ` Greg Kroah-Hartman
2013-01-25 4:21 ` Bjorn Helgaas
2013-01-25 4:52 ` Greg Kroah-Hartman
2013-01-29 6:03 ` Joonsoo Kim
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=20130125011303.GA3401@lge.com \
--to=iamjoonsoo.kim@lge.com \
--cc=bhelgaas@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 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.