From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: qemu boot failures with today's linux-next
Date: Tue, 16 Oct 2018 20:36:59 +1100 [thread overview]
Message-ID: <87pnwakzb8.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20181016105240.70369b98@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
>> > Booting Linux via __start() @ 0x0000000000400000 ...
>>
>> If you git Ctrl-a-c you should get the qemu prompt. Then you can run
>> 'info registers' to print the regs and maybe see where it's stuck.
>>
>> And/or build with EARLY_DEBUG_LPAR to get early console output.
>
> That gave one more line:
>
> [ 0.000000] printk: bootconsole [udbg0] enabled
Yeah I tried it too, it must have crashed *really* early :)
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: qemu boot failures with today's linux-next
Date: Tue, 16 Oct 2018 20:36:59 +1100 [thread overview]
Message-ID: <87pnwakzb8.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20181016105240.70369b98@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
>> > Booting Linux via __start() @ 0x0000000000400000 ...
>>
>> If you git Ctrl-a-c you should get the qemu prompt. Then you can run
>> 'info registers' to print the regs and maybe see where it's stuck.
>>
>> And/or build with EARLY_DEBUG_LPAR to get early console output.
>
> That gave one more line:
>
> [ 0.000000] printk: bootconsole [udbg0] enabled
Yeah I tried it too, it must have crashed *really* early :)
cheers
next prev parent reply other threads:[~2018-10-16 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 8:18 linux-next: qemu boot failures with today's linux-next Stephen Rothwell
2018-10-15 8:20 ` Stephen Rothwell
2018-10-15 12:45 ` Michael Ellerman
2018-10-15 23:52 ` Stephen Rothwell
2018-10-15 23:52 ` Stephen Rothwell
2018-10-16 9:36 ` Michael Ellerman [this message]
2018-10-16 9:36 ` Michael Ellerman
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=87pnwakzb8.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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.