← Back to team overview

kernel-packages team mailing list archive

[Bug 1502946] Re: kernel crash on m400 arm64 server cartridge

 

@Tim: Please do - the dtb interface for numa is still in discussion, so
I think we can expect the OS/fw interface to change anyway.

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

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, then the initramfs not finding any network devices and thus failing to mount the iscsi root.

  The trace looks like this:
  [    0.000000] ------------[ cut here ]------------
  [    0.000000] WARNING: CPU: 0 PID: 0 at /build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [    0.000000] Modules linked in:
  [    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic #16-Ubuntu
  [    0.000000] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [    0.000000] Call trace:
  [    0.000000] [<ffffffc00008a6e8>] dump_backtrace+0x0/0x150
  [    0.000000] [<ffffffc00008a858>] show_stack+0x20/0x30
  [    0.000000] [<ffffffc00086cc7c>] dump_stack+0x7c/0x98
  [    0.000000] [<ffffffc0000bd900>] warn_slowpath_common+0xa0/0xe0
  [    0.000000] [<ffffffc0000bda70>] warn_slowpath_null+0x38/0x50
  [    0.000000] [<ffffffc000c05b40>] numa_init+0x8c/0x398
  [    0.000000] [<ffffffc000c05e7c>] arm64_numa_init+0x30/0x40
  [    0.000000] [<ffffffc000c04b24>] bootmem_init+0x60/0x104
  [    0.000000] [<ffffffc000c052a0>] paging_init+0x198/0x224
  [    0.000000] [<ffffffc000c01e98>] setup_arch+0x274/0x5f8
  [    0.000000] [<ffffffc000bfe6d0>] start_kernel+0xdc/0x3f4
  [    0.000000] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lo        no wireless extensions.
   
   eth1      no wireless extensions.
   
   eth0      no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware                             1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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


References