From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Miche Baker-Harvey <miche@google.com>
Cc: Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com
Subject: Re: Regression: patch " hvc_console: display printk messages on console." causing infinite loop with 3.2-rc0 + Xen.
Date: Thu, 27 Oct 2011 11:08:26 -0400 [thread overview]
Message-ID: <20111027150826.GC1157@phenom.dumpdata.com> (raw)
In-Reply-To: <CAB8Rdaq2r4Uc-WZK-k=wiEW8DKdixn+9dB7E4_XDL7k8jCMwSw@mail.gmail.com>
On Thu, Oct 27, 2011 at 07:45:07AM -0700, Miche Baker-Harvey wrote:
> Bummer. Sorry about that.
>
> Konrad, could you give me a hand figuring out what's up with this - I'm not
> running Zen here. (If there's a test suite I could have run, mea culpa, and
> please point me in the right direction.)
I kind of run the nightly build/test rinse & repeat cycle using this:
git://xenbits.xen.org/xentesttools/bootstrap.git
But it might be just easier for you to install Fedora Core 16, do
'yum install xen', reboot, make sure you can boot Xen, and then build
a 3.2 kernel with your patch + debug stuff.
>
> The "console [hvc0] enabled" message is coming from register_console() in
> printk.c, and it doesn't have any loops.
> It's called from hvc_console_init(), hvc_instantiate(), and hvc_alloc(),
> none of which have loops. The call in hvc_alloc() is the one I added, so
> either I've inadvertently made one of the other two repeat (I'm guestting
> hvc_instantiate() is the one you're using), or you're infinitely calling
> hvc_alloc(). There's a calls to hvc_alloc() in hvc_xen.c::xen_hvc_init(),
> and in init_port_console() in virtio_console.c, but again, no loops.
> Similarly for hvc_instantiate().
>
> So, could I trouble you to put a breakpoint in register_console() and send
> me the stack?
A dump_stack() should suffice I presume? Yeah let me do that.
next prev parent reply other threads:[~2011-10-27 15:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 5:30 Regression: patch " hvc_console: display printk messages on console." causing infinite loop with 3.2-rc0 + Xen Konrad Rzeszutek Wilk
2011-10-27 5:34 ` Konrad Rzeszutek Wilk
2011-10-27 5:48 ` Greg KH
[not found] ` <CAB8Rdaq2r4Uc-WZK-k=wiEW8DKdixn+9dB7E4_XDL7k8jCMwSw@mail.gmail.com>
2011-10-27 14:50 ` Fwd: " Miche Baker-Harvey
2011-10-27 15:08 ` Konrad Rzeszutek Wilk [this message]
2011-10-27 15:31 ` Konrad Rzeszutek Wilk
2011-10-27 17:22 ` Miche Baker-Harvey
2011-10-27 17:35 ` Konrad Rzeszutek Wilk
2011-10-27 18:39 ` [PATCH] VirtioConsole support Miche Baker-Harvey
2011-10-27 21:15 ` Konrad Rzeszutek Wilk
2011-10-31 9:55 ` Amit Shah
2011-10-27 21:43 ` Miche Baker-Harvey
2011-10-27 21:55 ` Konrad Rzeszutek Wilk
2011-10-28 16:27 ` Greg KH
2011-10-28 2:55 ` Joe Perches
2011-10-28 18:19 ` Stephen Boyd
2011-11-02 22:02 ` Rusty Russell
2011-11-03 12:38 ` Christian Borntraeger
2011-11-03 14:15 ` Konrad Rzeszutek Wilk
2011-11-02 1:13 ` Regression: patch " hvc_console: display printk messages on console." causing infinite loop with 3.2-rc0 + Xen Stephen Rothwell
2011-11-03 1:30 ` Greg KH
2011-11-07 6:19 ` Stephen Rothwell
2011-11-07 20:24 ` Greg KH
2011-10-31 7:48 ` Rusty Russell
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=20111027150826.GC1157@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=miche@google.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).