← Back to team overview

kernel-packages team mailing list archive

[Bug 1259727] Re: Crashes under load


I can't test the mainline kernel builds, because they are only built for
i386 and amd64, but not for armhf.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Crashes under load

Status in “linux” package in Ubuntu:

Bug description:
  The Wandboard Quad crashes under load. This can be triggered by
  running "apt-get upgrade" or a scripts that converts a git repository
  to bzr, for example. It does not crash every time, but often enough to
  reproduce the crash. Attached the output of dmesg after the crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-7-generic 3.12.0-7.15
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic armv7l
   total 0
   crw-rw---- 1 root audio 116,  1 Jan  1  1970 seq
   crw-rw---- 1 root audio 116, 33 Jan  1  1970 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.12.0-7-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Dec 10 23:38:45 2013
  HibernationDevice: RESUME=UUID=174445a8-0f41-440c-a1c4-9d6e6657b834
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: ro quiet splash root=UUID=5b2e9784-4869-4303-a512-a7f29dde7cf1
   linux-restricted-modules-3.12.0-7-generic N/A
   linux-backports-modules-3.12.0-7-generic  N/A
   linux-firmware                            1.117
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to: