[Kernel-packages] [Bug 1793976] [NEW] kvm kernel missing nbd module

[Brian Candler]

Public bug reported:

The "nbd" module is missing from linux-modules-XXX-kvm in bionic

root@ubuntu:~# /sbin/modprobe nbd max_part=16
modprobe: FATAL: Module nbd not found in directory /lib/modules/4.15.0-1021-kvm
root@ubuntu:~# uname -a
Linux ubuntu 4.15.0-1021-kvm #21-Ubuntu SMP Tue Aug 28 09:57:01 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

root@ubuntu:~# dpkg-query -l | grep linux-modules
ii  linux-modules-4.15.0-1019-kvm 4.15.0-1019.19
 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
ii  linux-modules-4.15.0-1021-kvm 4.15.0-1021.21
 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
ii  linux-modules-4.15.0-34-generic   4.15.0-34.37  
 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
ii  linux-modules-extra-4.15.0-34-generic 4.15.0-34.37  
 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP

nbd exists for the generic kernel, but not kvm.

root@ubuntu:~# find /lib/modules -name '*nbd*'
/lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko
root@ubuntu:~# dpkg-query -S 
/lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko
linux-modules-4.15.0-34-generic: 
/lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko

In fact, there are many more modules in the generic kernel:

root@ubuntu:~# dpkg-query -L linux-modules-4.15.0-1021-kvm | wc -l
514
root@ubuntu:~# dpkg-query -L linux-modules-4.15.0-34-generic | wc -l
1285

I checked if there is a linux-modules-extra for kvm and this kernel
version, but there is not - only for azure.

root@ubuntu:~# apt-cache search linux-modules-extra-4.15.0-1021
linux-modules-extra-4.15.0-1021-azure - Linux kernel extra modules for version 
4.15.0 on 64 bit x86 SMP
root@ubuntu:~#

There is a "linux-image-extra-virtual" package, but it's empty:

root@ubuntu:~# dpkg-query -L linux-image-extra-virtual
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/linux-image-extra-virtual
/usr/share/doc/linux-image-extra-virtual/copyright
/usr/share/doc/linux-image-extra-virtual/changelog.gz

As a workaround, I expect I can use the generic kernel - but this won't
be optimised for kvm.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-modules-4.15.0-1021-kvm 4.15.0-1021.21
ProcVersionSignature: Ubuntu 4.15.0-1021.21-kvm 4.15.18
Uname: Linux 4.15.0-1021-kvm x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
Date: Sun Sep 23 19:43:56 2018
Dependencies:
 
InstallationDate: Installed on 2018-06-15 (100 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
ProcEnviron:
 LANG=en_GB.UTF-8
 TERM=xterm-256color
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-kvm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic uec-images

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

Title:
  kvm kernel missing nbd module

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  The "nbd" module is missing from linux-modules-XXX-kvm in bionic

  root@ubuntu:~# /sbin/modprobe nbd max_part=16
  modprobe: FATAL: Module nbd not found in directory 
/lib/modules/4.15.0-1021-kvm
  root@ubuntu:~# uname -a
  Linux ubuntu 4.15.0-1021-kvm #21-Ubuntu SMP Tue Aug 28 09:57:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  root@ubuntu:~# dpkg-query -l | grep linux-modules
  ii  linux-modules-4.15.0-1019-kvm 4.15.0-1019.19  
   amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-4.15.0-1021-kvm 4.15.0-1021.21  
   amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-4.15.0-34-generic   4.15.0-34.37
   amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-extra-4.15.0-34-generic 4.15.0-34.37
   amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP

  nbd exists for the generic kernel, but not kvm.

  root@ubuntu:~# find /lib/modules -name '*nbd*'
  /lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko
  root@ubuntu:~# dpkg-query -S 
/lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko
  linux-modules-4.15.0-34-generic: 
/lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko

  In fact, there are many more modules in the generic kernel:

  root@ubuntu:~# dpkg-query -L linux-modules-4.15.0-1021-kvm | wc -l
  514
  root@ubuntu:~# dpkg-query -L linux-modules-4.15.0-34-generic | wc -l
  1285

  I checked if there is a linux-modules-extra for kvm and this kernel
  version, but there is not - o

[Kernel-packages] [Bug 1793976] Re: kvm kernel missing nbd module

[Brian Candler]

Excellent, thank you.  FYI, the actual application I'm using which
requires nbd is snf-image-creator.

I agree it makes sense to remove most modules relating to physical
hardware from the kvm kernel, but loopback and networking modules are
useful.

I did a quick diff. "rbd" might be another one to add; also veth and
vxlan.

(Aside: I was surprised to find many virtio modules missing, but since
they still work, I imagine they have been compiled directly in)

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

Title:
  kvm kernel missing nbd module

Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-kvm source package in Xenial:
  In Progress
Status in linux-kvm source package in Bionic:
  In Progress

Bug description:
  The "nbd" module is missing from linux-modules-XXX-kvm in bionic

  root@ubuntu:~# /sbin/modprobe nbd max_part=16
  modprobe: FATAL: Module nbd not found in directory 
/lib/modules/4.15.0-1021-kvm
  root@ubuntu:~# uname -a
  Linux ubuntu 4.15.0-1021-kvm #21-Ubuntu SMP Tue Aug 28 09:57:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  root@ubuntu:~# dpkg-query -l | grep linux-modules
  ii  linux-modules-4.15.0-1019-kvm 4.15.0-1019.19  
   amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-4.15.0-1021-kvm 4.15.0-1021.21  
   amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-4.15.0-34-generic   4.15.0-34.37
   amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-extra-4.15.0-34-generic 4.15.0-34.37
   amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP

  nbd exists for the generic kernel, but not kvm.

  root@ubuntu:~# find /lib/modules -name '*nbd*'
  /lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko
  root@ubuntu:~# dpkg-query -S 
/lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko
  linux-modules-4.15.0-34-generic: 
/lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko

  In fact, there are many more modules in the generic kernel:

  root@ubuntu:~# dpkg-query -L linux-modules-4.15.0-1021-kvm | wc -l
  514
  root@ubuntu:~# dpkg-query -L linux-modules-4.15.0-34-generic | wc -l
  1285

  I checked if there is a linux-modules-extra for kvm and this kernel
  version, but there is not - only for azure.

  root@ubuntu:~# apt-cache search linux-modules-extra-4.15.0-1021
  linux-modules-extra-4.15.0-1021-azure - Linux kernel extra modules for 
version 4.15.0 on 64 bit x86 SMP
  root@ubuntu:~#

  There is a "linux-image-extra-virtual" package, but it's empty:

  root@ubuntu:~# dpkg-query -L linux-image-extra-virtual
  /.
  /usr
  /usr/share
  /usr/share/doc
  /usr/share/doc/linux-image-extra-virtual
  /usr/share/doc/linux-image-extra-virtual/copyright
  /usr/share/doc/linux-image-extra-virtual/changelog.gz

  As a workaround, I expect I can use the generic kernel - but this
  won't be optimised for kvm.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-modules-4.15.0-1021-kvm 4.15.0-1021.21
  ProcVersionSignature: Ubuntu 4.15.0-1021.21-kvm 4.15.18
  Uname: Linux 4.15.0-1021-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Sun Sep 23 19:43:56 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-06-15 (100 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANG=en_GB.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

[Brian Candler]

Seeing this on bare metal (Dell R740xd) with Ubuntu 18.04 and linux-
image-generic-hwe-18.04 (5.3.0-62-generic)

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

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  SRU Justification

  Impact: The KVP daemon fails to start on first boot due to being
  started before the hv_kvp device appears.

  Fix: Update the hv-kvp-daemon service file to start the daemon after
  device node appears.

  Regression Potential: The changes are only to the hv-kvp-daemon
  service file and adding a udev rule, so the worst case regression
  would be that the service does not start. In testing the service did
  start as expected.

  Test Case: See comment #15.

  ---

  
  Launching a recent daily image of disco on azure results in a VM in which the 
hv-kvp-daemon.service fails to start:

  $ systemctl status -o cat hv-kvp-daemon.service
  ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
     Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor 
pr
     Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 
11min a
   Main PID: 219 (code=exited, status=1/FAILURE)

  Started Hyper-V KVP Protocol Daemon.
  KVP starting; pid is:219
  open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory
  hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE
  hv-kvp-daemon.service: Failed with result 'exit-code'.

  The instance was created with:
  $ az vm create --resource-group [redacted] --image 
Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name 
disco-0313

  As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the 
hv-kvp-daemon.service starts, but it is available a few seconds later. Manually 
starting the daemon once I can ssh in works.
  ---
  ProblemType: Bug
  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: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure 
root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1011-azure N/A
   linux-backports-modules-4.18.0-1011-azure  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco uec-images
  Uname: Linux 4.18.0-1011-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1290832] [NEW] No console display on D2xxx/N2xxx integrated graphics with raring enablement stack

[Brian Candler]

Public bug reported:

Installed Ubuntu 12.04.4 Server 64-bit on Intel D2700MUD motherboard
(Atom D2700), 4GB RAM

Installation process went fine. But after rebooting, after the grub
screen the display was completely blank. This is using a VGA connection
to an external monitor (the board also has a DVI output which I have not
tried).

The machine was however running fine, e.g. I was able to ssh to it after
I had worked out what IP address it had picked up.

Attempts to resolve the problem:

* Add "nomodeset" to kernel command line (both with ctrl-e and in 
/etc/defaults/grub). No change.
* Uncomment GRUB_GFXMODE=640x480 in /etc/defaults/grub. This made the GRUB menu 
text appear larger, but still completely blank after that point.
* Upgrade BIOS to latest version 0076 (it was on 0067). No change.

The only way I have been able to get the console to work is to remove
the enablement stack and go to 3.2.0-60 kernel

# apt-get remove --purge linux-generic-lts-raring 
linux-headers-generic-lts-raring linux-image-generic-lts-raring
# apt-get install linux-generic linux-headers-generic linux-image 
linux-image-generic linux-libc-dev linux-tools
# dpkg-query -l | grep -i '3\.8\.0'   # then remove these packages too

Note: this is not an X11 issue - this is a server install and I don't
have X11 at all.

Additional info: when booting the 3.8.0 kernel I got a bunch of messages
in dmesg about drm and EDID. These do not appear at all when booting
with the 3.2.0 kernel

...
[3.109992] udevd[331]: starting version 175
[3.149552] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[2.324900] lp: driver loaded but no devices found
[2.504295] parport_pc 00:07: reported by Plug and Play ACPI
[2.504361] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[2.545514] [drm] Initialized drm 1.1.0 20060810
[2.563748] gma500 :00:02.0: setting latency timer to 64
[2.564027] gma500 :00:02.0: irq 45 for MSI/MSI-X
[2.564146] gma500 :00:02.0: GPU: power management timed out.
[2.582176] ACPI Warning: _BQC returned an invalid level (20121018/video-534)
[2.582479] acpi device:1f: registered as cooling_device4
[2.582937] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[2.583079] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
[2.583980] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[2.583988] [drm] No driver support for vblank timestamp query.
[2.610172] lp0: using parport0 (interrupt-driven).
[2.698484] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, 
remainder is 130
[2.698505] Raw EDID:
[2.698515]  00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[2.698524]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.698533]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.698543]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.698552]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.698561]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.698571]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.698580]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.733915] type=1400 audit(1394539018.224:2): apparmor="STATUS" 
operation="profile_load" name="/sbin/dhclient" pid=496 comm="apparmor_parser"
[2.735325] type=1400 audit(1394539018.224:3): apparmor="STATUS" 
operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" 
pid=496 comm="apparmor_parser"
[2.736218] type=1400 audit(1394539018.228:4): apparmor="STATUS" 
operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" 
pid=496 comm="apparmor_parser"
[2.741475] microcode: CPU0 sig=0x30661, pf=0x4, revision=0x10d
[2.802983] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, 
remainder is 130
[2.803006] Raw EDID:
[2.803017]  00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[2.803028]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.803039]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.803050]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.803061]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.803071]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.803081]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.803091]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.907667] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, 
remainder is 130
[2.907689] Raw EDID:
[2.907699]  00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[2.907710]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.907720]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.907731]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.907742]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[2.907754] 

[Kernel-packages] [Bug 1290832] Re: No console display on D2xxx/N2xxx integrated graphics with raring enablement stack

[Brian Candler]

Forgot to add: in the things I tried, I also did a full "apt-get update;
apt-get dist-upgrade", so I was on the latest 3.8.0 kernel version.

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

Title:
  No console display on D2xxx/N2xxx integrated graphics with raring
  enablement stack

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Installed Ubuntu 12.04.4 Server 64-bit on Intel D2700MUD motherboard
  (Atom D2700), 4GB RAM

  Installation process went fine. But after rebooting, after the grub
  screen the display was completely blank. This is using a VGA
  connection to an external monitor (the board also has a DVI output
  which I have not tried).

  The machine was however running fine, e.g. I was able to ssh to it
  after I had worked out what IP address it had picked up.

  Attempts to resolve the problem:

  * Add "nomodeset" to kernel command line (both with ctrl-e and in 
/etc/defaults/grub). No change.
  * Uncomment GRUB_GFXMODE=640x480 in /etc/defaults/grub. This made the GRUB 
menu text appear larger, but still completely blank after that point.
  * Upgrade BIOS to latest version 0076 (it was on 0067). No change.

  The only way I have been able to get the console to work is to remove
  the enablement stack and go to 3.2.0-60 kernel

  # apt-get remove --purge linux-generic-lts-raring 
linux-headers-generic-lts-raring linux-image-generic-lts-raring
  # apt-get install linux-generic linux-headers-generic linux-image 
linux-image-generic linux-libc-dev linux-tools
  # dpkg-query -l | grep -i '3\.8\.0'   # then remove these packages too

  Note: this is not an X11 issue - this is a server install and I don't
  have X11 at all.

  Additional info: when booting the 3.8.0 kernel I got a bunch of
  messages in dmesg about drm and EDID. These do not appear at all when
  booting with the 3.2.0 kernel

  ...
  [3.109992] udevd[331]: starting version 175
  [3.149552] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
  [2.324900] lp: driver loaded but no devices found
  [2.504295] parport_pc 00:07: reported by Plug and Play ACPI
  [2.504361] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
  [2.545514] [drm] Initialized drm 1.1.0 20060810
  [2.563748] gma500 :00:02.0: setting latency timer to 64
  [2.564027] gma500 :00:02.0: irq 45 for MSI/MSI-X
  [2.564146] gma500 :00:02.0: GPU: power management timed out.
  [2.582176] ACPI Warning: _BQC returned an invalid level 
(20121018/video-534)
  [2.582479] acpi device:1f: registered as cooling_device4
  [2.582937] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
  [2.583079] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
  [2.583980] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
  [2.583988] [drm] No driver support for vblank timestamp query.
  [2.610172] lp0: using parport0 (interrupt-driven).
  [2.698484] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, 
remainder is 130
  [2.698505] Raw EDID:
  [2.698515]00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
  [2.698524]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.698533]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.698543]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.698552]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.698561]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.698571]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.698580]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.733915] type=1400 audit(1394539018.224:2): apparmor="STATUS" 
operation="profile_load" name="/sbin/dhclient" pid=496 comm="apparmor_parser"
  [2.735325] type=1400 audit(1394539018.224:3): apparmor="STATUS" 
operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" 
pid=496 comm="apparmor_parser"
  [2.736218] type=1400 audit(1394539018.228:4): apparmor="STATUS" 
operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" 
pid=496 comm="apparmor_parser"
  [2.741475] microcode: CPU0 sig=0x30661, pf=0x4, revision=0x10d
  [2.802983] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, 
remainder is 130
  [2.803006] Raw EDID:
  [2.803017]00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
  [2.803028]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.803039]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.803050]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.803061]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.803071]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.803081]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.803091]

[Kernel-packages] [Bug 1290832] Re: No console display on D2xxx/N2xxx integrated graphics with raring enablement stack

[Brian Candler]

Intermediate update: the machine boots with the linux-
image-3.14.0-031400rc6-generic kernel, it still reports EDID errors,
dmesg info below.

Unfortunately the machine is now in data centre so I can't tell if it is
generating a VGA output or not! I'll update this when I'm next able to
get a console on it.

[3.527667] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[3.580869] lp: driver loaded but no devices found
[3.825323] ACPI Warning: SystemIO range 
0x0428-0x042f conflicts with OpRegion 
0x0400-0x047f (\PMIO) (20131218/utaddress-258)
[3.825342] ACPI Warning: SystemIO range 
0x0428-0x042f conflicts with OpRegion 
0x0400-0x042f (\SWC1) (20131218/utaddress-258)
[3.825353] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[3.825362] ACPI Warning: SystemIO range 
0x0530-0x053f conflicts with OpRegion 
0x0500-0x053b (\GPIO) (20131218/utaddress-258)
[3.825373] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[3.825378] ACPI Warning: SystemIO range 
0x0500-0x052f conflicts with OpRegion 
0x0500-0x053b (\GPIO) (20131218/utaddress-258)
[3.825388] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[3.825392] lpc_ich: Resource conflict(s) found affecting gpio_ich
[3.826838] [drm] Initialized drm 1.1.0 20060810
[3.920586] gma500 :00:02.0: irq 45 for MSI/MSI-X
[3.920701] gma500 :00:02.0: GPU: power management timed out.
[3.968488] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[3.969317] acpi device:20: registered as cooling_device4
[3.969536] input: Video Bus as 
/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input5
[3.970924] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[3.970933] [drm] No driver support for vblank timestamp query.
[4.052259] parport_pc 00:07: reported by Plug and Play ACPI
[4.052323] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[4.130397] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, 
remainder is 130
[4.142687] Raw EDID:
[4.148460]  00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[4.152372] lp0: using parport0 (interrupt-driven).
[4.154698]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.160400]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.166027]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.171892]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.177001]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.181877]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.186623]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.300402] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, 
remainder is 130
[4.310033] Raw EDID:
[4.314839]  00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[4.319336]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.323997]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.328527]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.332981]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.336954]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.340420]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.343977]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.451258] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, 
remainder is 130
[4.458050] Raw EDID:
[4.461533]  00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[4.465042]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.468142]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.470927]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.473796]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.476268]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.478469]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.480623]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.592130] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, 
remainder is 130
[4.596592] Raw EDID:
[4.599084]  00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[4.601695]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.604434]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.607408]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.610058]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.612705]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[4.614886]  ff ff ff ff ff ff ff ff 

[Kernel-packages] [Bug 1290832] Re: No console display on D2xxx/N2xxx integrated graphics with raring enablement stack

[Brian Candler]

I got access the the boxes in the data centre (there are two).

The one which was on 3.13 kernel: VGA output was fine
The one which was on 3.2 kernel: VGA output was fine
However when I upgraded the 3.2 to 3.8, the VGA output was still fine :-(

This was using a different VGA monitor than I had tried before. It's
possible that the 3.8 kernel had enabled a video mode which the original
monitor didn't like. That was AOC I2269V, also labelled model no
215LM00040. That monitor *should* be pretty modern, it has a "Windows 8
Compatible" sticker.

Anyway, sorry for the noise. This can be closed as I was unable to
reproduce it with a different monitor.

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

Title:
  No console display on D2xxx/N2xxx integrated graphics with raring
  enablement stack

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Installed Ubuntu 12.04.4 Server 64-bit on Intel D2700MUD motherboard
  (Atom D2700), 4GB RAM

  Installation process went fine. But after rebooting, after the grub
  screen the display was completely blank. This is using a VGA
  connection to an external monitor (the board also has a DVI output
  which I have not tried).

  The machine was however running fine, e.g. I was able to ssh to it
  after I had worked out what IP address it had picked up.

  Attempts to resolve the problem:

  * Add "nomodeset" to kernel command line (both with ctrl-e and in 
/etc/defaults/grub). No change.
  * Uncomment GRUB_GFXMODE=640x480 in /etc/defaults/grub. This made the GRUB 
menu text appear larger, but still completely blank after that point.
  * Upgrade BIOS to latest version 0076 (it was on 0067). No change.

  The only way I have been able to get the console to work is to remove
  the enablement stack and go to 3.2.0-60 kernel

  # apt-get remove --purge linux-generic-lts-raring 
linux-headers-generic-lts-raring linux-image-generic-lts-raring
  # apt-get install linux-generic linux-headers-generic linux-image 
linux-image-generic linux-libc-dev linux-tools
  # dpkg-query -l | grep -i '3\.8\.0'   # then remove these packages too

  Note: this is not an X11 issue - this is a server install and I don't
  have X11 at all.

  Additional info: when booting the 3.8.0 kernel I got a bunch of
  messages in dmesg about drm and EDID. These do not appear at all when
  booting with the 3.2.0 kernel

  ...
  [3.109992] udevd[331]: starting version 175
  [3.149552] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
  [2.324900] lp: driver loaded but no devices found
  [2.504295] parport_pc 00:07: reported by Plug and Play ACPI
  [2.504361] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
  [2.545514] [drm] Initialized drm 1.1.0 20060810
  [2.563748] gma500 :00:02.0: setting latency timer to 64
  [2.564027] gma500 :00:02.0: irq 45 for MSI/MSI-X
  [2.564146] gma500 :00:02.0: GPU: power management timed out.
  [2.582176] ACPI Warning: _BQC returned an invalid level 
(20121018/video-534)
  [2.582479] acpi device:1f: registered as cooling_device4
  [2.582937] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
  [2.583079] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
  [2.583980] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
  [2.583988] [drm] No driver support for vblank timestamp query.
  [2.610172] lp0: using parport0 (interrupt-driven).
  [2.698484] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, 
remainder is 130
  [2.698505] Raw EDID:
  [2.698515]00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
  [2.698524]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.698533]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.698543]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.698552]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.698561]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.698571]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.698580]ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [2.733915] type=1400 audit(1394539018.224:2): apparmor="STATUS" 
operation="profile_load" name="/sbin/dhclient" pid=496 comm="apparmor_parser"
  [2.735325] type=1400 audit(1394539018.224:3): apparmor="STATUS" 
operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" 
pid=496 comm="apparmor_parser"
  [2.736218] type=1400 audit(1394539018.228:4): apparmor="STATUS" 
operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" 
pid=496 comm="apparmor_parser"
  [2.741475] microcode: CPU0 sig=0x30661, pf=0x4, revision=0x10d
  [2.802983] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, 
remainder is 130
  [2.803006] Raw EDID:
  [2.803017

[Kernel-packages] [Bug 96578] Re: The sysctl net.ipv6.conf.all.autoconf does not apply to "all"

[Brian Candler]

I have observed this as a more general problem with any sysctl setting
for "all" interfaces.

For example, try:

sysctl -a | grep '^net\.ipv4\.conf.*send_redirects'
sysctl -w net.ipv4.conf.all.send_redirects=0
sysctl -a | grep '^net\.ipv4\.conf.*send_redirects'
sysctl -w net.ipv4.conf.all.send_redirects=1
sysctl -a | grep '^net\.ipv4\.conf.*send_redirects'

It seems that setting conf.all does not have any effect on the
individual conf. settings. This begs the question of what
setting conf.all is supposed to do.

There is also conf.default which appears to be the value inherited when
a new interface is created. To test:

sysctl -w net.ipv4.conf.all.send_redirects=1
sysctl -w net.ipv4.conf.default.send_redirects=0
brctl addbr br100
sysctl net.ipv4.conf.br100.send_redirects   # it's 0

sysctl -w net.ipv4.conf.all.send_redirects=1
sysctl net.ipv4.conf.br100.send_redirects   # it's still 0

sysctl -w net.ipv4.conf.all.send_redirects=0
sysctl -w net.ipv4.conf.default.send_redirects=1
brctl addbr br101
sysctl net.ipv4.conf.br101.send_redirects   # it's 1
sysctl net.ipv4.conf.br100.send_redirects   # it's still 0

This is sensible. Hence I can see how "default" is useful, but not
"all".

Above tests done with Ubuntu 12.04.4 running kernel 3.8.0-36-generic

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

Title:
  The sysctl net.ipv6.conf.all.autoconf does not apply to "all"

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux-source-2.6.20” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: linux-source-2.6.20

  Just specifying:

  net.ipv6.conf.default.autoconf=0
  net.ipv6.conf.all.autoconf=0

  in sysctl.conf does not actually disable autoconf.

  Explicitly setting

  net.ipv6.conf.eth0.autoconf=0

  on the other hand does work (if I've added "ipv6" to /etc/modules, but
  that's another issue).

  Our workaround for this is to list enough ethN to cover "all likely" network 
interfaces, but that's not exactly a neat solution.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   Cannot stat file /proc/4797/fd/11: No such file or directory
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maswan 2400 F pulseaudio
   /dev/snd/pcmC0D0p:   maswan 2400 F...m pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf302 irq 21'
 Mixer name : 'Analog Devices AD1884'
 Components : 'HDA:11d41884,103c2819,00100100'
 Controls  : 30
 Simple ctrls  : 18
  DistroRelease: Ubuntu 10.04
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   ppp0  no wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc7800 Convertible Minitower
  NonfreeKernelModules: openafs
  Package: linux (not installed)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-33-generic 
root=/dev/mapper/rootvg-rootlv ro quiet splash
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-33.71-generic 2.6.32.41+drm33.18
  Regression: No
  RelatedPackageVersions: linux-firmware 1.34.7
  Reproducible: Yes
  RfKill:
   
  Tags: lucid kconfig needs-upstream-testing
  Uname: Linux 2.6.32-33-generic x86_64
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev 
video voice
  dmi.bios.date: 02/26/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F1 v01.28
  dmi.board.asset.tag: CZC84703HB
  dmi.board.name: 0AACh
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC84703HB
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F1v01.28:bd02/26/2009:svnHewlett-Packard:pnHPCompaqdc7800ConvertibleMinitower:pvr:rvnHewlett-Packard:rn0AACh:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq dc7800 Convertible Minitower
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 96578] Re: The sysctl net.ipv6.conf.all.autoconf does not apply to "all"

[Brian Candler]

The answer for IPv4 was figured out here:
http://unix.stackexchange.com/questions/90443/sysctl-proc-sys-net-ipv46-conf-whats-the-difference-between-all-defau

The behaviour is non-obvious. For some settings the interface and 'all'
settings are ANDed together; for others they are OR'd, for others the
MAX is taken.

send_redirects is an OR, which means you can enable sending of redirects
on all interfaces (conf.all.send_redirects=1) but you cannot disable
sending them on all interfaces. In that case you have to set
conf.all.send_redirects=0 *and* set each individual interface.

So in /etc/sysctl.conf you have to list all the interfaces which the
host has (or may have) at startup time, if you want to disable sending
of redirects on those interfaces. A tri-state setting for conf.all would
be much more useful, but that's not what we have.

Now back to the original report, which was about
net.ipv6.conf.all.autoconf=0. What is the intended behaviour from the
kernel authors?

include/linux/inetdevice.h appears to have IPv4 settings only. For IPv6:

grep -R devconf_all net/ipv6

Unfortunately it's not obvious to me how "all" + interface-specific
parameters  interact for IPv6. There are some places where the two are
explicitly combined: e.g.

[net/ipv6/ndisc.c]
 (net->ipv6.devconf_all->proxy_ndp || idev->cnf.proxy_ndp) 
&&

I don't see anything similar for autoconf. However there is:

[net/ipv6/af_inet6.c]
MODULE_PARM_DESC(autoconf, "Enable IPv6 address autoconfiguration on all 
interfaces");

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

Title:
  The sysctl net.ipv6.conf.all.autoconf does not apply to "all"

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux-source-2.6.20” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: linux-source-2.6.20

  Just specifying:

  net.ipv6.conf.default.autoconf=0
  net.ipv6.conf.all.autoconf=0

  in sysctl.conf does not actually disable autoconf.

  Explicitly setting

  net.ipv6.conf.eth0.autoconf=0

  on the other hand does work (if I've added "ipv6" to /etc/modules, but
  that's another issue).

  Our workaround for this is to list enough ethN to cover "all likely" network 
interfaces, but that's not exactly a neat solution.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   Cannot stat file /proc/4797/fd/11: No such file or directory
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maswan 2400 F pulseaudio
   /dev/snd/pcmC0D0p:   maswan 2400 F...m pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf302 irq 21'
 Mixer name : 'Analog Devices AD1884'
 Components : 'HDA:11d41884,103c2819,00100100'
 Controls  : 30
 Simple ctrls  : 18
  DistroRelease: Ubuntu 10.04
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   ppp0  no wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc7800 Convertible Minitower
  NonfreeKernelModules: openafs
  Package: linux (not installed)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-33-generic 
root=/dev/mapper/rootvg-rootlv ro quiet splash
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-33.71-generic 2.6.32.41+drm33.18
  Regression: No
  RelatedPackageVersions: linux-firmware 1.34.7
  Reproducible: Yes
  RfKill:
   
  Tags: lucid kconfig needs-upstream-testing
  Uname: Linux 2.6.32-33-generic x86_64
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev 
video voice
  dmi.bios.date: 02/26/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F1 v01.28
  dmi.board.asset.tag: CZC84703HB
  dmi.board.name: 0AACh
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC84703HB
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F1v01.28:bd02/26/2009:svnHewlett-Packard:pnHPCompaqdc7800ConvertibleMinitower:pvr:rvnHewlett-Packard:rn0AACh:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq dc7800 Convertible Minitower
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1348688] Re: kernel does not support limiting swap usage (memory.memsw.limit_in_bytes missing)

[Brian Candler]

After updating to that kernel (under 14.04), the problem is not fixed.

$ uname -a
Linux kit1 3.19.0-031900rc4-generic #201501112135 SMP Sun Jan 11 21:36:48 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

* The LXC instance still does not start if the 131072 setting is included.

$ virsh -c lxc: start gold-lxc-20140717
error: Failed to start domain gold-lxc-20140717
error: internal error: guest failed to start: Unable to write to 
'/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.memsw.limit_in_bytes':
 No such file or directory

$ ls /sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/
cgroup.clone_children   memory.kmem.tcp.failcnt 
memory.oom_control
cgroup.event_controlmemory.kmem.tcp.limit_in_bytes  
memory.pressure_level
cgroup.procsmemory.kmem.tcp.max_usage_in_bytes  
memory.soft_limit_in_bytes
memory.failcnt  memory.kmem.tcp.usage_in_bytes  memory.stat
memory.force_empty  memory.kmem.usage_in_bytes  
memory.swappiness
memory.kmem.failcnt memory.limit_in_bytes   
memory.usage_in_bytes
memory.kmem.limit_in_bytes  memory.max_usage_in_bytes   
memory.use_hierarchy
memory.kmem.max_usage_in_bytes  memory.move_charge_at_immigrate 
notify_on_release
memory.kmem.slabinfomemory.numa_stattasks

(Note it does not include memory.memsw.limit_in_bytes)

* After reverting to kernel 3.13.0-43 and doing the same lxc start which
fails in the same way:

$ ls /sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/
cgroup.clone_children   memory.kmem.tcp.failcnt 
memory.oom_control
cgroup.event_controlmemory.kmem.tcp.limit_in_bytes  
memory.pressure_level
cgroup.procsmemory.kmem.tcp.max_usage_in_bytes  
memory.soft_limit_in_bytes
memory.failcnt  memory.kmem.tcp.usage_in_bytes  memory.stat
memory.force_empty  memory.kmem.usage_in_bytes  
memory.swappiness
memory.kmem.failcnt memory.limit_in_bytes   
memory.usage_in_bytes
memory.kmem.limit_in_bytes  memory.max_usage_in_bytes   
memory.use_hierarchy
memory.kmem.max_usage_in_bytes  memory.move_charge_at_immigrate 
notify_on_release
memory.kmem.slabinfomemory.numa_stattasks

Looks identical to me.

** Tags added: kernel-bug-exists-upstream

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

Title:
  kernel does not support limiting swap usage
  (memory.memsw.limit_in_bytes missing)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (Sorry I'm not sure exactly what package to report this against -
  kernel perhaps? libvirt is what I was using to replicate the problem)

  Host platform: ubuntu 14.04 amd64, Mac Mini, 16GB RAM.

  Short version: create an LXC domain with memtune > swap_hard_limit set
  in the XML:

  
gold-lxc-20140717
b2a02d49-bb1e-4aec-81d1-58910892780e
327680
327680

  131072

...

  (full version at end of this report)

  Now try to start it:

  $ virsh -c lxc: start gold-lxc-20140717error: Failed to start domain 
gold-lxc-20140717
  error: internal error: guest failed to start: Unable to write to 
'/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.memsw.limit_in_bytes':
 No such file or directory

  The reason this matters is because otherwise the LXC memory limit
  applies only to real RAM used. If the guest exceeds this it can still
  use as much swap space as it likes, and is therefore effectively
  unlimited (and can happily DoS the swap disk).

  Long version:

  I created an ubuntu 14.04 i386 VM image using python-vmbuilder,
  loopback-mounted it with qemu-nbd, and rsync'd it to create a root
  filesystem for an LXC guest.

  Then defined a guest using libvirt XML and started it using "virsh -c
  lxc: start " (as per XML at end but without the 
  section). It starts successfully, networking is fine, I can get a
  console etc.

  Now, the libvirt XML description says the guest's memory limit is
  320MB:

327680
327680

  and indeed the cgroups setting has been set:

  $ cat 
/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.limit_in_bytes
  335544320

  However inside the guest I can happily allocate as much memory as I
  like, up to just under 4GB, which is the limit for a 32-bit guest.

  Here's the test program I ran in the guest (usemem.c):

  #include 
  #include 
  #include 

  int main(void)
  {
  char *p;
  int i,j;
  int ok=0, fail=0;
  for (i=0; i<4096; i++) {
  p = malloc(1024*1024);
  if (p) {
  ok++;
  for (j=0; j<1024*1024; j++)
  p[j] = rand();
  }
  else
  fail++;
  }
  fprin

[Kernel-packages] [Bug 1348688] Re: kernel does not support limiting swap usage (memory.memsw.limit_in_bytes missing)

[Brian Candler]

First you need to convince me that this is a kernel bug.

How come libvirt's LXC driver is trying to use a /sys API that doesn't
even exist in the very latest mainline kernel?

I would guess that either libvirt assumes the kernel is built with some
option that the Ubuntu kernel hasn't been built with; or it assumes some
patch has been applied; or it's trying to use some old API which no
longer exists.

None of those cases would count as a kernel bug.

OTOH, I don't see anything at
http://libvirt.org/sources/virshcmdref/html-single/#sect-memtune
which implies any special options are required.

There are requirements for namespaces to be compiled in at
https://libvirt.org/drvlxc.html

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

Title:
  kernel does not support limiting swap usage
  (memory.memsw.limit_in_bytes missing)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  (Sorry I'm not sure exactly what package to report this against -
  kernel perhaps? libvirt is what I was using to replicate the problem)

  Host platform: ubuntu 14.04 amd64, Mac Mini, 16GB RAM.

  Short version: create an LXC domain with memtune > swap_hard_limit set
  in the XML:

  
gold-lxc-20140717
b2a02d49-bb1e-4aec-81d1-58910892780e
327680
327680

  131072

...

  (full version at end of this report)

  Now try to start it:

  $ virsh -c lxc: start gold-lxc-20140717error: Failed to start domain 
gold-lxc-20140717
  error: internal error: guest failed to start: Unable to write to 
'/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.memsw.limit_in_bytes':
 No such file or directory

  The reason this matters is because otherwise the LXC memory limit
  applies only to real RAM used. If the guest exceeds this it can still
  use as much swap space as it likes, and is therefore effectively
  unlimited (and can happily DoS the swap disk).

  Long version:

  I created an ubuntu 14.04 i386 VM image using python-vmbuilder,
  loopback-mounted it with qemu-nbd, and rsync'd it to create a root
  filesystem for an LXC guest.

  Then defined a guest using libvirt XML and started it using "virsh -c
  lxc: start " (as per XML at end but without the 
  section). It starts successfully, networking is fine, I can get a
  console etc.

  Now, the libvirt XML description says the guest's memory limit is
  320MB:

327680
327680

  and indeed the cgroups setting has been set:

  $ cat 
/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.limit_in_bytes
  335544320

  However inside the guest I can happily allocate as much memory as I
  like, up to just under 4GB, which is the limit for a 32-bit guest.

  Here's the test program I ran in the guest (usemem.c):

  #include 
  #include 
  #include 

  int main(void)
  {
  char *p;
  int i,j;
  int ok=0, fail=0;
  for (i=0; i<4096; i++) {
  p = malloc(1024*1024);
  if (p) {
  ok++;
  for (j=0; j<1024*1024; j++)
  p[j] = rand();
  }
  else
  fail++;
  }
  fprintf(stderr, "Done: %d ok, %d fail\n", ok, fail);
  sleep(600);
  return fail ? 1 : 0;
  }

  Result from running:

  Done: 4076 ok, 20 fail

  View from the host:

  nsrc@kit1:~/workshop-kit$ ps auxwww | grep usemem | grep -v grep
  nsrc 10506 96.1  1.3 4192152 224776 ?  S+   14:41   0:55 ./usemem

  $ cat 
/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.limit_in_bytes
  335544320
  $ cat 
/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.max_usage_in_bytes
  335544320
  $ cat 
/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.usage_in_bytes
  292331520

  You can see there's definitely 4GB in use by this process, and yet the
  cgroup thinks less than 280MB is in use, which is below the 320MB
  limit.

  However if you look at swap usage in the host while the memory suck
  program is running:

  $ free
   total   used   free sharedbuffers cached
  Mem:  163383003066952   13271348   1684 1355121489268
  -/+ buffers/cache:1442172   14896128
  Swap: 166789083971248   12707660

  and after it has terminated:

  $ free
   total   used   free sharedbuffers cached
  Mem:  163383002774440   13563860   1684 1355441489188
  -/+ buffers/cache:1149708   15188592
  Swap: 16678908   5484   16673424

  i.e. the LXC guest used nearly 4GB of swap, and then gave it up when
  it terminated.

  Additional info:

  cgroup view from inside the guest:

  $ cat /proc/self/cgroup
  11:name=systemd:/
  10:hugetlb:/
  9:perf_event:/machine/gold-lxc-20140717.libvirt-lxc
  8:blkio:/machine/gold-lxc-20140717.libvirt-lxc
  7:freezer:/machine/gold-lxc-20140717.libvirt-lxc
  6:devices:/mach

[Kernel-packages] [Bug 1606345] [NEW] bcmwl crashes kernel when monitor mode enabled

[Brian Candler]

Public bug reported:

Ubuntu 14.04 with linux-generic-lts-xenial kernel (4.4.0), running on
Macmini6,2

Installed package bcmwl-kernel-source, which gives me this module for my
wlan0:

# lsmod | grep wl
wl   6365184  0
cfg80211  557056  1 wl

Machine immediately and reliably crashes when I do the following:

# echo 1 > /proc/brcm_monitor0

At that time, console displays the following (hand-transcribed from
slightly fuzzy photo):

[  313.202989] xhci_hcd :00:14.0: HC died; cleaning up
[  313.203118] asix 3-4:1.0 eth1: Failed to enable software MII access
[  313.203148] asix 3-4:1.0 eth1: Failed to enable software MII access
[  313.203174] asix 3-4:1.0 eth1: Failed to enable software MII access
[  313.203200] asix 3-4:1.0 eth1: Failed to enable software MII access
[  313.908406] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0
[  328.127778] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 22s! 
[charts.d.plugin:12702]
[  356.129362] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 22s! 
[charts.d.plugin:12702]
[  361.369660] INFO: rcu_sched detected stalls on CPUs/tasks:
[  361.369691] N0-..: (1 GPs behind) idle=8fd/140/0 
softirq=18394/18394 fqs=14978
[  361.369717] N(detected by 3, t=15002 jiffies, g=10311, c=10310, q=74589)
[  384.130946] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 22s! 
[charts.d.plugin:12702]

Note: "charts.d.plugin" I believe refers to the 'netdata' application
which I also have running. However as it's just a userland process I
don't think it should be able to kill the kernel like this.

Workaround: I was installing this to try to get monitor mode working.
However I will revert to b43 driver (which unfortunately does not appear
to do promiscuous monitor mode)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2
ProcVersionSignature: Ubuntu 4.4.0-28.47~14.04.1-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Mon Jul 25 18:14:03 2016
InstallationDate: Installed on 2014-07-16 (740 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
SourcePackage: bcmwl
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: bcmwl (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  bcmwl crashes kernel when monitor mode enabled

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Ubuntu 14.04 with linux-generic-lts-xenial kernel (4.4.0), running on
  Macmini6,2

  Installed package bcmwl-kernel-source, which gives me this module for
  my wlan0:

  # lsmod | grep wl
  wl   6365184  0
  cfg80211  557056  1 wl

  Machine immediately and reliably crashes when I do the following:

  # echo 1 > /proc/brcm_monitor0

  At that time, console displays the following (hand-transcribed from
  slightly fuzzy photo):

  [  313.202989] xhci_hcd :00:14.0: HC died; cleaning up
  [  313.203118] asix 3-4:1.0 eth1: Failed to enable software MII access
  [  313.203148] asix 3-4:1.0 eth1: Failed to enable software MII access
  [  313.203174] asix 3-4:1.0 eth1: Failed to enable software MII access
  [  313.203200] asix 3-4:1.0 eth1: Failed to enable software MII access
  [  313.908406] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0
  [  328.127778] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 22s! 
[charts.d.plugin:12702]
  [  356.129362] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 22s! 
[charts.d.plugin:12702]
  [  361.369660] INFO: rcu_sched detected stalls on CPUs/tasks:
  [  361.369691] N0-..: (1 GPs behind) idle=8fd/140/0 
softirq=18394/18394 fqs=14978
  [  361.369717] N(detected by 3, t=15002 jiffies, g=10311, c=10310, q=74589)
  [  384.130946] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 22s! 
[charts.d.plugin:12702]

  Note: "charts.d.plugin" I believe refers to the 'netdata' application
  which I also have running. However as it's just a userland process I
  don't think it should be able to kill the kernel like this.

  Workaround: I was installing this to try to get monitor mode working.
  However I will revert to b43 driver (which unfortunately does not
  appear to do promiscuous monitor mode)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-28.47~14.04.1-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Jul 25 18:14:03 2016
  InstallationDate: Installed o

[Kernel-packages] [Bug 1609475] Re: recovery mode completely broken by systemd

[Brian Candler]

I will happily file a separate bug for NUC5CPYH not booting properly
with 16.04.1, and I will test it with a mainline kernel.

However this bug is to report that "recovery mode" is completely broken
in this situation, which makes it especially hard to debug the problem.

If I cannot open a console for more than two minutes, because systemd
continues launching programs and then takes over the console, this is
broken behaviour.

The workaround is to boot from USB and do the repair from there
(although this is unfortunately a more long-winded process, prompting
you for many of the installation questions)

If there is no intention to fix recovery mode, then I think it should be
removed.

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the
  hope that providing a *specific* way that it sucks might help get it
  fixed. (I have had a number of other cases of system recovery being
  frustrated by systemd, but this time I thought I would at least
  document the specifics)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1609475] Re: recovery mode completely broken by systemd

[Brian Candler]

The specific problem with NUC seems to have been my fault: I didn't
realise it was installing in UEFI mode, so did not create an ESP (EFI
System Partition).

It was strange that it managed to even start booting the kernel at all;
I can only guess that the hardware was not correctly initialized.

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the
  hope that providing a *specific* way that it sucks might help get it
  fixed. (I have had a number of other cases of system recovery being
  frustrated by systemd, but this time I thought I would at least
  document the specifics)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1609475] Re: recovery mode completely broken by systemd

[Brian Candler]

Separate issue #1609715 raised about installer continuing with UEFI
installation even if there is no ESP.

This specific hardware is now working fine.

I would still like recovery mode to be more predictable in the event of
startup problems: after all, the whole point of recovery mode is for
when there are problems during bootup which need investigation/fixing.

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the
  hope that providing a *specific* way that it sucks might help get it
  fixed. (I have had a number of other cases of system recovery being
  frustrated by systemd, but this time I thought I would at least
  document the specifics)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1609475] Card0.Codecs.codec.0.txt

[Brian Candler]

apport information

** Attachment added: "Card0.Codecs.codec.0.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735769/+files/Card0.Codecs.codec.0.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Relea

[Kernel-packages] [Bug 1609475] ProcCpuinfo.txt

[Brian Candler]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735775/+files/ProcCpuinfo.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(2016071

[Kernel-packages] [Bug 1609475] UdevDb.txt

[Brian Candler]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1609475/+attachment/4735778/+files/UdevDb.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConf

[Kernel-packages] [Bug 1609475] ProcInterrupts.txt

[Brian Candler]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735776/+files/ProcInterrupts.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(2

[Kernel-packages] [Bug 1609475] Card0.Codecs.codec.2.txt

[Brian Candler]

apport information

** Attachment added: "Card0.Codecs.codec.2.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735770/+files/Card0.Codecs.codec.2.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Relea

[Kernel-packages] [Bug 1609475] ProcModules.txt

[Brian Candler]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735777/+files/ProcModules.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(2016071

[Kernel-packages] [Bug 1609475] PciMultimedia.txt

[Brian Candler]

apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735774/+files/PciMultimedia.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(201

[Kernel-packages] [Bug 1609475] CurrentDmesg.txt

[Brian Candler]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735771/+files/CurrentDmesg.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160

[Kernel-packages] [Bug 1609475] WifiSyslog.txt

[Brian Candler]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735779/+files/WifiSyslog.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)

[Kernel-packages] [Bug 1609475] Lspci.txt

[Brian Candler]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1609475/+attachment/4735773/+files/Lspci.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig

[Kernel-packages] [Bug 1609475] Re: recovery mode completely broken by systemd

[Brian Candler]

apport information

** Tags added: apport-collected

** Description changed:

  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).
  
  There is a problem running on this machine, but the problem report here
  is specifically about how systemd makes this impossible to debug.
  
  Symptoms:
  
  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"
  
  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"
  
  It appears to boot fine. From the Recovery Menu I select "root: Drop to
  root shell prompt", then "Press Enter for maintenance". All is good so
  far: I get a prompt.
  
  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:
  
  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.
  
  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of the
  lines has the ctrl-D for maintenance message.
  
  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts me
  back to the frozen recovery menu.
  
  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that the
  shell and the recovery menu are both fighting over the keyboard. By
  pressing cursor down repeatedly, it appears about 50% of them cause the
  recovery menu to move.
  
  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps; and
  when I get a shell, I want that shell to be mine on the console with no
  interference - and not taken away again.
  
- Lots of people say "systemd sucks", but I am submitting this in the hope
- that providing a *specific* way that it sucks might help get it fixed.
- (I have had a number of other cases of system recovery being frustrated
- by systemd, but this time I thought I would at least document the
- specifics)
+ Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
+ --- 
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ Card0.Amixer.info: Error: [Errno 2] No such file or directory
+ Card0.Amixer.values: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
+ InstallationDate: Installed on 2016-08-04 (33 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ IwConfig: Error: [Err

[Kernel-packages] [Bug 1609475] CRDA.txt

[Brian Candler]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1609475/+attachment/4735768/+files/CRDA.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: 

[Kernel-packages] [Bug 1609475] JournalErrors.txt

[Brian Candler]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735772/+files/JournalErrors.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(201

[Kernel-packages] [Bug 1609475] Re: recovery mode completely broken by systemd

[Brian Candler]

Not sure about tag "bios-outdated-0055". The latest BIOS for this machine is 
0055: see
https://downloadcenter.intel.com/product/85254/Intel-NUC-Kit-NUC5CPYH

As for live CD: no, it can't be reproduced that way. The specific
sequence is:

* Boot from USB in UEFI mode
* Repartition the disk, but forget to include a UEFI boot partition
* Continue with installation
* Reboot, things go horribly wrong

Problems are:
(1a) The installer lets you do a UEFI-mode install without a UEFI boot partition
(1b) The installer doesn't maker it clear whether you are making a UEFI-mode 
install or a BIOS-mode install

(These have been raised as separate issues)

(2) The broken system boots but then goes mental; and systemd makes it
*much* harder to diagnose than without systemd.

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: c

[Kernel-packages] [Bug 1609475] Re: recovery mode completely broken by systemd

[Brian Candler]

Let me try one last time to separate the issues.

** The UEFI issue (a side issue)

The installer works in two completely different ways, depending on
whether the system booted via UEFI or BIOS. But it does not show whether
it is installing in UEFI or BIOS mode. Hence the user has little way,
short of guesswork, to know how to partition the system correctly.

Many systems can boot from a USB stick in either mode. If you don't tell
it, you get whatever the system chose. So:

(1) The installer *could* tell you which mode it's running in, but it
doesn't. If you don't realise you've booted via UEFI mode and that the
system is going to configure UEFI booting, and decide to partition
manually, then you don't realise that you need a UEFI boot partition.

(2) The system *could* warn you that you have a missing UEFI boot
partition when installing in UEFI mode, but it doesn't.

Those points have now been raised separately in issue #1609715.

However the only relevance here is it gives a way to reproduce the main
problem.

** Broken recovery mode (the main issue)

The point I tried to raise in this issue is the brokenness of recovery
mode when you have a system with some sort of corruption. The UEFI
missing-boot-partition problem is just one specific way to reproduce the
brokenness in recovery mode. Reproducible cases are good; they allow
things to be fixed. There are however many other different ways the
system could be broken and recovery mode would not work.

With an older version of Ubuntu, I could simply log in, poke around,
look at logs, find the problem and fix it.

With ubuntu 16.04, I have now experienced a situation where recovery
mode is broken. I described what happens at the top of this issue.
Basically you can start a recovery shell, and 50% of your keystrokes are
thrown away; and then a few minutes later the recovery shell quits and
recovery mode locks up. I suspect this is something to do with systemd
sitting in the background launching stuff when it thinks dependencies
have been met, and terminating stuff when it thinks it would be a good
idea to do so.

For recovery mode, I just want a shell. Let me do my job. Please spawn
me a shell connected to the console, reliably. That's it. No shells
vanishing and reappearing. No timeouts because filesystems haven't yet
been mounted or because networking is not up. That's the whole point of
recovery mode - to have sufficient access to be able to fix those
things.

For now, the best workaround seems to be to boot from an Ubuntu 14.04
USB, and then mount the system disk. But it makes me sad that 16.04 has
become less good in this respect than it was before. It seems to be a
regression in how easy it is to recover a broken system.

Of course, this only affects systems which require some sort of
maintenance - but it's a fact of life that systems *do* get into states
which require fixing.

That's it. If you have never had to use recovery mode, and hence don't
care about it, then you are lucky.

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  

[Kernel-packages] [Bug 1609475] Re: Recovery mode won't allow recovery after manually installing the OS incorrectly

[Brian Candler]

> The user would already have setup in the BIOS menu to either be in
UEFI or BIOS mode prior to installation. This would also be user error.

Really? What's wrong with:

- buy computer
- plug in USB stick
- boot it up

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

Title:
  Recovery mode won't allow recovery after manually installing the OS
  incorrectly

Status in linux package in Ubuntu:
  Opinion

Bug description:
  If one manually installs Ubuntu but doesn't install a boot partition,
  the recovery mode doesn't work.

  The expectation (perhaps naively) is that the recovery mode is
  bootable and allows one to fix the situation.

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=a91f753b-69af-4125-a03d-0dcb63d55d38 ro net.ifnames=0
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 05/03/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0054.2016.0503.1546
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-407
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0054.2016.0503.1546:bd05/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-407:cvn:ct3:cvr:

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1609475] Re: Recovery mode won't allow recovery after manually installing the OS incorrectly

[Brian Candler]

BTW, I reproduced the same problem in a different (and arguably more
realistic) scenario:

- install ubuntu 16.04
- configure networking with a bridge interface but a port member that doesn't 
exist when you next boot up (e.g. make br0 with a member which is a USB 
ethernet adapter, and then remove the USB adapter)
- reboot - you find it hangs for about 6 minutes
- so you decide to reboot again, and go into recovery mode to fix the 
networking config

Then you get the same as described before: you get a recovery shell
which works for a few minutes, but then systemd continues with the
bootup and blats over the recovery shell with a new session, making the
system unusable.

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

Title:
  Recovery mode won't allow recovery after manually installing the OS
  incorrectly

Status in linux package in Ubuntu:
  Opinion

Bug description:
  If one manually installs Ubuntu but doesn't install a boot partition,
  the recovery mode doesn't work.

  The expectation (perhaps naively) is that the recovery mode is
  bootable and allows one to fix the situation.

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=a91f753b-69af-4125-a03d-0dcb63d55d38 ro net.ifnames=0
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 05/03/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0054.2016.0503.1546
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-407
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0054.2016.0503.1546:bd05/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-407:cvn:ct3:cvr:

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1180649] Re: Setting up linux-signed-image-3.8.0-21-generic (3.8.0-21.32) ... warning: file-aligned section .text extends beyond end of file

[Brian Candler]

Same for 12.04.3 LTS. During dist-upgrade:

...
Setting up linux-headers-generic-lts-raring (3.8.0.32.32) ...
Setting up linux-signed-image-3.8.0-32-generic (3.8.0-32.47~precise1) ...
warning: file-aligned section .text extends beyond end of file
warning: checksum areas are greater than image size. Invalid section table?
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.8.0-32-generic
Found initrd image: /boot/initrd.img-3.8.0-32-generic
...

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

Title:
  Setting up linux-signed-image-3.8.0-21-generic (3.8.0-21.32) ...
  warning: file-aligned section .text extends beyond end of file

Status in “linux-signed” package in Ubuntu:
  Confirmed

Bug description:
  Error in dist-upgrade to 3.8.0-21 for x86_64 SMP:

  Setting up linux-signed-image-3.8.0-21-generic (3.8.0-21.32) ...
  warning: file-aligned section .text extends beyond end of file
  warning: checksum areas are greater than image size. Invalid section table?

  The dist-upgrade completed without further errors and system is
  running with new kernel without any further error.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2092182] [NEW] bridge help message wrong for -compressvlans

[Brian Candler]

Public bug reported:

The "bridge" command gives the following help message:

# bridge
Usage: bridge [ OPTIONS ] OBJECT { COMMAND | help }
   bridge [ -force ] -batch filename
where  OBJECT := { link | fdb | mdb | vlan | monitor }
   OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] |
-o[neline] | -t[imestamp] | -n[etns] name |
-c[ompressvlans] -color -p[retty] -j[son] }

The implication is that "-c" is a shortcut for "-compressvlans".

However this is not true. "-c" or "-co" act the same as "-color". But
you can give "-com" as a shorthand for "-compressvlans".

Suggested change to help text:

-com[pressvlans] | -c[olor] | -p[retty] | -j[son] }

iproute2 version: 5.15.0-1ubuntu2
Ubuntu version: 22.04.5

Aside: it's not clear to me how to report bugs directly upstream for
iproute2, which is why I'm reporting it here.

** Affects: iproute2 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  bridge help message wrong for -compressvlans

Status in iproute2 package in Ubuntu:
  New

Bug description:
  The "bridge" command gives the following help message:

  # bridge
  Usage: bridge [ OPTIONS ] OBJECT { COMMAND | help }
 bridge [ -force ] -batch filename
  where  OBJECT := { link | fdb | mdb | vlan | monitor }
 OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] |
  -o[neline] | -t[imestamp] | -n[etns] name |
  -c[ompressvlans] -color -p[retty] -j[son] }

  The implication is that "-c" is a shortcut for "-compressvlans".

  However this is not true. "-c" or "-co" act the same as "-color". But
  you can give "-com" as a shorthand for "-compressvlans".

  Suggested change to help text:

  -com[pressvlans] | -c[olor] | -p[retty] | -j[son]
  }

  iproute2 version: 5.15.0-1ubuntu2
  Ubuntu version: 22.04.5

  Aside: it's not clear to me how to report bugs directly upstream for
  iproute2, which is why I'm reporting it here.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp