kernel-packages team mailing list archive

[Ryan Finnie <ryan.finnie@xxxxxxxxxxxxx>]

The only option on https://wiki.ubuntu.com/DebuggingKernelBoot of
relevance to booting an ARM kernel in QEMU is the "debug" flag, which
doesn't change anything.  The u-boot output is in the original report;
when booting through u-boot, it CPU spins after "Starting kernel ...".
When booting the kernel directly from qemu-system-arm, there is
literally no output.

I don't have access to 3.13.0-22, it was a d-r-u from saucy to trusty
this weekend.  I was referring to the difference between the saucy
kernel line (3.11) and the trusty kernel line (3.13).  I'm compiling an
armhf kernel from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.14-trusty/ to test vanilla, but this is going to take a
very long time.

** Summary changed:

- Cannot boot 3.13.0-23-generic on qemu-system-arm
+ Cannot boot trusty kernel on qemu-system-arm

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1303657

Title:
  Cannot boot trusty kernel on qemu-system-arm

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Upon d-r-u of a qemu ARM guest from saucy to trusty, the kernel no
  longer boots:

  ===
  U-Boot 2013.10 (Nov 23 2013 - 04:30:10)

  DRAM:  1 GiB
  WARNING: Caches not enabled
  Flash: 256 MiB
  MMC:   MMC: 0
  In:    serial
  Out:   serial
  Err:   serial
  Net:   smc911x-0
  Hit any key to stop autoboot:  0 
  reading boot.scr
  352 bytes read in 28 ms (11.7 KiB/s)
  ## Executing script at 60000000
  reading vmlinuz
  5474584 bytes read in 958 ms (5.4 MiB/s)
  reading initrd.img
  17883834 bytes read in 3013 ms (5.7 MiB/s)
  reading board.dtb
  11863 bytes read in 6 ms (1.9 MiB/s)
  Kernel image @ 0x60008000 [ 0x000000 - 0x538918 ]
  ## Flattened Device Tree blob at 62008000
     Booting using the fdt blob at 0x62008000
     Using Device Tree in place at 62008000, end 6200de56

  Starting kernel ...

  ===

  At this point, the host CPU just spins.  The previous kernel from
  saucy (3.11.0-19-generic) boots correctly into the trusty environment.

  The VM is being launched as so:

  export QEMU_AUDIO_DRV=none
  exec qemu-system-arm -display none -M vexpress-a9 -kernel /srv/arm-dev/u-boot -m 1024 \
      -serial stdio -net nic,model=lan9118,macaddr=52:54:00:68:90:14 \
      -net tap,ifname=arm-dev,script=no,downscript=no -sd /dev/mapper/host-arm_dev \
      -pflash /srv/arm-dev/pflash1.img -pflash /srv/arm-dev/pflash2.img -smp 1

  The flash images are unused; the scr points to the SD:

  fatload mmc 0:1 0x60008000 vmlinuz
  fatload mmc 0:1 0x61008000 initrd.img
  fatload mmc 0:1 0x62008000 board.dtb
  setenv bootargs console=ttyAMA0,38400 root=/dev/mmcblk0p2 nosmp
  setenv fdt_high 0xffffffff
  setenv initrd_high 0xffffffff
  bootz 0x60008000 0x61008000:0x1000000 0x62008000

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-23-generic 3.13.0-23.45
  ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic armv7l
  AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-19-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CurrentDmesg: [  113.007517] init: plymouth-upstart-bridge main process ended, respawning
  Date: Mon Apr  7 01:23:13 2014
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyAMA0,38400 root=/dev/mmcblk0p2 nosmp
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-19-generic N/A
   linux-backports-modules-3.11.0-19-generic  N/A
   linux-firmware                             1.127
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1303657/+subscriptions