kernel-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Two boxes (lxd-armhf{1,2}) have been running for three days with cking's
kernel, 3 is running the standard xenial kernel. 1 and 3 don't respond
to ssh connections any more; 2 still does, but several processes are in
'D' state:

root        47  0.0  0.0      0     0 ?        D    May13   0:00 [fsnotify_mark]
root     12892  0.0  0.0      0     0 ?        D    May13   0:00 [kworker/1:0]
root     26785  0.0  0.0      0     0 ?        D    May13   0:00 [kworker/1:2]

 (uninterruptible kernel sleep), such as lxd or systemd (pid 1). Calling
"top" hangs as well (but "ps" works), and there are a ton of zombie
processes (including lxd, check-new-release, sshd, socat).

All three continue to have lots of dmesg like

203722.697873] rcu_sched kthread starved for 15002 jiffies! g50919 c50918 f0x0 s3 ->state=0x1
[209670.455074] INFO: rcu_sched detected stalls on CPUs/tasks:
[209670.456446]         3-...: (126 GPs behind) idle=a7e/0/0 softirq=30811/30811 fqs=1 
[209670.457910]         (detected by 2, t=15002 jiffies, g=50962, c=50961, q=8377)
[209670.459430] Call trace:

So I'd say that this kernel did not really help (but also did not make
things worse for sure).

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

Title:
  [arm64] locks up some time after booting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I
  want to use for armhf autopkgtesting in LXD). I started with wily as
  that has lxd available (it's not yet available in trusty nor the PPA
  for arm64).

  However, pretty much any LXD task that I do (I haven't tried much
  else) on this machine takes unbearably long. A simple "lxc profile set
  default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes.

  I see tons of

  [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0
  [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds.

  in dmesg (the attached apport info has the complete dmesg).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic aarch64
  AlsaDevices:
   total 0
   crw-rw---- 1 root audio 116,  1 Jan  7 09:18 seq
   crw-rw---- 1 root audio 116, 33 Jan  7 09:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: arm64
  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: N/A
  Date: Thu Jan  7 09:24:01 2016
  IwConfig:
   eth0      no wireless extensions.

   lo        no wireless extensions.

   lxcbr0    no wireless extensions.
  Lspci:
   00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008]
    Subsystem: Red Hat, Inc Device [1af4:1100]
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
  PciMultimedia:

  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=LABEL=cloudimg-rootfs earlyprintk
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware                            1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

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