linux-next: qemu boot failures with today's linux-next

linux-next: qemu boot failures with today's linux-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 2578 bytes --]

Hi all,

Today's linux-next tree does not boot in qemu (with kvm or without).
Here is the (non-kvm) boot log (the kvm one is basically the same):

------------------------------------------------------
SLOF^[[0m^[[?25l **********************************************************************
^[[1mQEMU Starting
^[[0m Build Date = Sep 24 2017 12:23:07
 FW Version = buildd@ release 20170724
 Press "s" to enter Open Firmware.

^[[0m^[[?25hC0000\rC0100\rC0120\rC0140\rC0200\rC0240\rC0260\rC02E0\rC0300\rC0320\rC0340\rC0360\rC0370\rC0380\rC0371\rC0372\rC0373\rC0374\rC03F0\rC0400\rC0480\rC04C0\rC04D0\rC0500\rPopulating /vdevice methods
Populating /vdevice/vty@71000000
Populating /vdevice/nvram@71000001
Populating /vdevice/l-lan@71000002
Populating /vdevice/v-scsi@71000003
       SCSI: Looking for devices
          8200000000000000 CD-ROM   : "QEMU     QEMU CD-ROM      2.5+"
C05A0\rPopulating /pci@800000020000000
C0600\rC06C0\rC0700\rC0800\rC0880\rNo NVRAM common partition, re-initializing...
C0890\rC08A0\rC08A8\rC08B0\rScanning USB 
C08C0\rC08D0\rUsing default console: /vdevice/vty@71000000
C08E0\rC08E8\rDetected RAM kernel at 400000 (122a850 bytes) 
C08FF\r     
  Welcome to Open Firmware

  Copyright (c) 2004, 2017 IBM Corporation All rights reserved.
  This program and the accompanying materials are made available
  under the terms of the BSD License available at
  http://www.opensource.org/licenses/bsd-license.php

Booting from memory...
OF stdout device is: /vdevice/vty@71000000
Preparing to boot Linux version 4.19.0-rc7 (sfr@ash) (gcc version 8.2.0 (Debian 8.2.0-4)) #2 SMP Mon Oct 15 18:53:28 AEDT 2018
Detected machine type: 0000000000000101
command line: 
Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... done
memory layout at init:
  memory_limit : 0000000000000000 (16 MB aligned)
  alloc_bottom : 0000000001640000
  alloc_top    : 0000000030000000
  alloc_top_hi : 0000000080000000
  rmo_top      : 0000000030000000
  ram_top      : 0000000080000000
instantiating rtas at 0x000000002fff0000... done
prom_hold_cpus: skipped
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x0000000001850000 -> 0x0000000001850a02
Device tree struct  0x0000000001860000 -> 0x0000000001870000
Quiescing Open Firmware ...
Booting Linux via __start() @ 0x0000000000400000 ...
------------------------------------------------------

I have no idea what may have caused this.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: qemu boot failures with today's linux-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 343 bytes --]

Hi all,

On Mon, 15 Oct 2018 19:18:59 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next tree does not boot in qemu (with kvm or without).
> Here is the (non-kvm) boot log (the kvm one is basically the same):

I should have said that the kernel build is pseries_le_defconfig.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: qemu boot failures with today's linux-next

[Michael Ellerman]

Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> Today's linux-next tree does not boot in qemu (with kvm or without).
> Here is the (non-kvm) boot log (the kvm one is basically the same):
>
> ------------------------------------------------------
...
>   Welcome to Open Firmware
>
>   Copyright (c) 2004, 2017 IBM Corporation All rights reserved.
>   This program and the accompanying materials are made available
>   under the terms of the BSD License available at
>   http://www.opensource.org/licenses/bsd-license.php
>
> Booting from memory...
> OF stdout device is: /vdevice/vty@71000000
> Preparing to boot Linux version 4.19.0-rc7 (sfr@ash) (gcc version 8.2.0 (Debian 8.2.0-4)) #2 SMP Mon Oct 15 18:53:28 AEDT 2018
                                  ^^^^^^^^^^
                                  I assume that's wrong, this is actually linux-next you're booting?


> Detected machine type: 0000000000000101
> command line: 
> Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
> Calling ibm,client-architecture-support... done
> memory layout at init:
>   memory_limit : 0000000000000000 (16 MB aligned)
>   alloc_bottom : 0000000001640000
>   alloc_top    : 0000000030000000
>   alloc_top_hi : 0000000080000000
>   rmo_top      : 0000000030000000
>   ram_top      : 0000000080000000
> instantiating rtas at 0x000000002fff0000... done
> prom_hold_cpus: skipped
> copying OF device tree...
> Building dt strings...
> Building dt structure...
> Device tree strings 0x0000000001850000 -> 0x0000000001850a02
> Device tree struct  0x0000000001860000 -> 0x0000000001870000
> Quiescing Open Firmware ...
> Booting Linux via __start() @ 0x0000000000400000 ...
> ------------------------------------------------------
>
> I have no idea what may have caused this.

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.

cheers

Re: linux-next: qemu boot failures with today's linux-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

Hi Michael,

On Mon, 15 Oct 2018 23:45:10 +1100 Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> > Preparing to boot Linux version 4.19.0-rc7 (sfr@ash) (gcc version 8.2.0 (Debian 8.2.0-4)) #2 SMP Mon Oct 15 18:53:28 AEDT 2018  
>                                   ^^^^^^^^^^
>                                   I assume that's wrong, this is actually linux-next you're booting?

Yes, it was just before -rc8 came out and I suppress the extra version
information to save rebuilding things that depend on the version.

> > 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

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: qemu boot failures with today's linux-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

Hi Michael,

On Mon, 15 Oct 2018 23:45:10 +1100 Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> > Preparing to boot Linux version 4.19.0-rc7 (sfr@ash) (gcc version 8.2.0 (Debian 8.2.0-4)) #2 SMP Mon Oct 15 18:53:28 AEDT 2018  
>                                   ^^^^^^^^^^
>                                   I assume that's wrong, this is actually linux-next you're booting?

Yes, it was just before -rc8 came out and I suppress the extra version
information to save rebuilding things that depend on the version.

> > 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

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: qemu boot failures with today's linux-next

[Michael Ellerman]

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

Re: linux-next: qemu boot failures with today's linux-next

[Michael Ellerman]

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