[Bug 1597267] Re: ThinkPad X260 connecting external DisplayPort hangs system

[Tero Marttila]

Current xenial linux-image-4.4.0-62-generic remains broken, with dmesg
WARNs on CRTC clocks and then system hangs when switching user sessions
(which invokes some gnome-session xrandr setup). Lost the exact dmesg on
the system hang.

Current mainline 4.8.x (4.8.17-040817-generic) continues to behave
nicely, although there's occasionally some delays when docking/undocking
before the xrandr configuration updates.

The 4.8 kernel is also included in the 16.04.02 HWE release, and a quick
test with linux-image-4.8.0-36-generic seems to also behave reasonably
well. I would tentatively consider this issue fixed in 16.04.02,
although I still need to test with xserver-xorg-hwe-16.04.

Will also test with the newest mainline 4.10 release when I have the
chance.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597267

Title:
  ThinkPad X260 connecting external DisplayPort hangs system

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1597267] Re: ThinkPad X260 connecting external DisplayPort hangs system

[Tero Marttila]

I've had good enough experiences with mainline 4.8.15 at this point that
I would consider this bug fixed in linux 4.8.x; it's still not perfect
(have to typically play around with xrandr and maybe undock/dock), but
external 4k DP monitor via a ThinkPad dock works fairly reliably now.

OTOH I was unable to get any DP video output at all with mainline Linux
4.9...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597267

Title:
  ThinkPad X260 connecting external DisplayPort hangs system

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1597267] Re: ThinkPad X260 connecting external DisplayPort hangs system

[Tero Marttila]

I've been running the 4.8.x mainline release kernels recently, and had
some success with 4k DP connected to the dock. It doesn't always work,
but a reboot fixes it, until it breaks again.

I'd appreciate advice for debugging this, it's pretty reproducible, but
typically when it happens I don't exactly have the time to start
debugging it, and just reboot.

With recent 4.8.10 kernels the symptom is usually that xrandr does
indeed detect and configure the display, but the monitor does not get
any signal and remains black. This is accompanied with the following
dmesg:

marras 23 11:43:46 tehobari kernel: Linux version 4.8.10-040810-generic 
(kernel@tangerine) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) 
#20161121053
marras 24 10:23:00 tehobari kernel: [drm:intel_dp_link_training_clock_recovery 
[i915]] *ERROR* too many voltage retries, give up
marras 24 10:23:00 tehobari kernel: [drm:intel_wait_ddi_buf_idle [i915]] 
*ERROR* Timeout waiting for DDI BUF C idle bit
marras 24 10:23:00 tehobari kernel: [drm] RC6 on
marras 24 10:23:00 tehobari kernel: [drm:intel_dp_link_training_clock_recovery 
[i915]] *ERROR* failed to get link status
marras 24 10:23:00 tehobari kernel: thinkpad_acpi: EC reports that Thermal 
Table has changed
marras 24 10:23:00 tehobari kernel: [drm:intel_wait_ddi_buf_idle [i915]] 
*ERROR* Timeout waiting for DDI BUF C idle bit
marras 24 10:23:00 tehobari kernel: [drm:intel_dp_link_training_clock_recovery 
[i915]] *ERROR* too many voltage retries, give up
marras 24 10:23:00 tehobari kernel: [drm:intel_wait_ddi_buf_idle [i915]] 
*ERROR* Timeout waiting for DDI BUF C idle bit
marras 24 10:23:00 tehobari kernel: [drm:intel_dp_link_training_clock_recovery 
[i915]] *ERROR* too many voltage retries, give up
marras 24 10:23:00 tehobari kernel: [drm:intel_wait_ddi_buf_idle [i915]] 
*ERROR* Timeout waiting for DDI BUF C idle bit
marras 24 10:23:00 tehobari kernel: [drm:intel_dp_link_training_clock_recovery 
[i915]] *ERROR* too many voltage retries, give up
marras 24 10:23:00 tehobari kernel: [drm:intel_wait_ddi_buf_idle [i915]] 
*ERROR* Timeout waiting for DDI BUF C idle bit
marras 24 10:23:00 tehobari kernel: [drm:intel_dp_link_training_clock_recovery 
[i915]] *ERROR* too many voltage retries, give up
marras 24 10:23:00 tehobari kernel: [drm:intel_wait_ddi_buf_idle [i915]] 
*ERROR* Timeout waiting for DDI BUF C idle bit
marras 24 10:23:00 tehobari kernel: [drm:intel_dp_link_training_clock_recovery 
[i915]] *ERROR* too many voltage retries, give up
marras 24 10:23:00 tehobari kernel: [drm:intel_dp_start_link_train [i915]] 
*ERROR* failed to train DP, aborting
marras 24 10:23:00 tehobari kernel: [drm:intel_dp_set_idle_link_train [i915]] 
*ERROR* Timed out waiting for DP idle patterns

Once this happens, AFAIK nothing short of a reboot will restore 4k DP
output on the dock. When I tried to fall back to the integrated miniDP
output, I was able to get a 1080p image, but no 4k image.

I upgraded to 4.8.11 having the following changelog entry: "drm/i915:
Refresh that status of MST capable connectors in ->detect()". Now I'm no
longer seeing the dmesg entries, but I still have occasional issues with
the DP output not working reliabily... not had a chance to figure those
out yet.

Here's some random bits of kernel dmesgs for 4.8.6, thrown in for good
measure:

marras 08 18:37:04 tehobari kernel: Linux version 4.8.6-040806-generic 
(kernel@tangerine) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) 
#201610310831 SMP Mon Oct 31 12:33:48 UTC 2016
marras 08 18:37:04 tehobari kernel: [drm] Finished loading 
i915/skl_dmc_ver1_26.bin (v1.26)
marras 08 18:37:04 tehobari kernel: [drm] Finished loading 
i915/skl_dmc_ver1_26.bin (v1.26)
marras 09 17:49:12 tehobari kernel: [ cut here ]
marras 09 17:49:12 tehobari kernel: WARNING: CPU: 1 PID: 10699 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:14305 
skl_max_scale.part.120+0x75/0x80 [i915]
marras 09 17:49:12 tehobari kernel: WARN_ON_ONCE(!crtc_clock || cdclk < 
crtc_clock)
marras 09 18:10:29 tehobari kernel: [drm:intel_dp_link_training_clock_recovery 
[i915]] *ERROR* failed to enable link training
marras 09 18:10:30 tehobari kernel: [drm:intel_dp_start_link_train [i915]] 
*ERROR* failed to start channel equalization
marras 09 19:18:58 tehobari kernel: [drm:intel_display_resume [i915]] *ERROR* 
Restoring old state failed with -22
marras 09 19:18:58 tehobari kernel: [drm] RC6 on
marras 09 20:08:28 tehobari kernel: [ cut here ]
marras 09 20:08:28 tehobari kernel: WARNING: CPU: 3 PID: 10699 at 
/home/kernel/COD/linux/drivers/gpu/drm/drm_modeset_lock.c:343 
drm_modeset_lock+0xd1/0xe0 [dr
m]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597267

Title:
  ThinkPad X260 connecting external DisplayPort hangs system

To manage notifications about this bug go to:

[Bug 1597267] Re: ThinkPad X260 connecting external DisplayPort hangs system

[Tero Marttila]

I've been having more luck with the newer 4.7 and 4.8 kernels, and using
a 4k monitor on the integrated DP connector mostly works okay at 60Hz.

Haven't really noticed any difference in stability with the
xorg.conf.d/20-intel.conf settings in https://github.com/linuxenko
/ubuntu-skylake-i915-video-fix. I also tried with `Option "DRI"
"false"`.

Currently running 4.8.0-040800rc5-generic together with yakkety linux-
firmware 1.160:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version   Architecture
  Description
+++-=-=-=-
ii  linux-firmware1.160 all 
  Firmware for Linux kernel drivers
ii  linux-image-4.8.0-040800rc5-gener 4.8.0-040800rc5.20160 amd64   
  Linux kernel image for version 4.8.0 on 64 bit x86 SMP

Still getting warnings in dmesg when connecting a DP monitor:

[ ...] Linux version 4.8.0-040800rc5-generic (kernel@tangerine) (gcc 
version 6.2.0 20160830 (Ubuntu 6.2.0-2ubuntu11) ) #201609041832 SMP Sun Sep 4 
22:34:01 UTC 2016

[  330.453739] [ cut here ]
[  330.453793] WARNING: CPU: 0 PID: 5134 at 
/home/kernel/COD/linux/drivers/gpu/drm/drm_irq.c:1215 
drm_wait_one_vblank+0x16b/0x1b0 [drm]
[  330.453796] vblank not available on crtc 0, ret=-22
[  330.453798] Modules linked in: uas usb_storage hid_lenovo usbhid hid ctr ccm 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm fuse 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc bnep 
snd_hda_codec_hdmi ext4 jbd2 arc4 snd_hda_codec_realtek snd_hda_codec_generic 
iwlmvm mac80211 fscrypto intel_rapl mbcache x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass intel_cstate intel_rapl_perf 
joydev serio_raw iwlwifi cfg80211 rtsx_pci_ms memstick option usb_wwan 
usbserial btusb btrtl cdc_ether btbcm usbnet btintel mii bluetooth sg crc16 
snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core 
snd_soc_sst_match
[  330.453921]  snd_soc_core snd_compress snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm thinkpad_acpi nvram rfkill battery 
ac snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer 
snd evdev tpm_tis tpm_tis_core tpm soundcore mei_me mei shpchp 
intel_pch_thermal parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq 
algif_skcipher af_alg dm_crypt dm_mod sd_mod rtsx_pci_sdmmc mmc_core 
crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i915 psmouse xhci_pci 
rtsx_pci xhci_hcd mfd_core ahci i2c_algo_bit usbcore libahci drm_kms_helper 
e1000e syscopyarea libata usb_common sysfillrect sysimgblt fb_sys_fops ptp 
pps_core drm scsi_mod thermal wmi video fjes button
[  330.454049] CPU: 0 PID: 5134 Comm: Xorg Tainted: GW  OE   
4.8.0-040800rc5-generic #201609041832
[  330.454052] Hardware name: LENOVO 20F6007RGE/20F6007RGE, BIOS R02ET48W (1.21 
) 06/01/2016
[  330.454057]  0286 0d9272e2 b2541064 
9487a2e239c8
[  330.454068]   b227f6ee 9487c7f3 
9487a2e23a20
[  330.454076]  9487c85a1600 9487c7f303d8 9487c7f3 

[  330.454085] Call Trace:
[  330.454099]  [] ? dump_stack+0x5c/0x78
[  330.454108]  [] ? __warn+0xbe/0xe0
[  330.454117]  [] ? warn_slowpath_fmt+0x5f/0x80
[  330.454155]  [] ? drm_vblank_get+0x76/0xc0 [drm]
[  330.454192]  [] ? drm_wait_one_vblank+0x16b/0x1b0 [drm]
[  330.454286]  [] ? chv_write32+0x3c0/0x3c0 [i915]
[  330.454344]  [] ? skl_wm_flush_pipe+0xcd/0x100 [i915]
[  330.454400]  [] ? skl_update_wm+0x42b/0x6c0 [i915]
[  330.454493]  [] ? haswell_crtc_enable+0x798/0x860 [i915]
[  330.454584]  [] ? intel_atomic_commit_tail+0x84f/0x10a0 
[i915]
[  330.454671]  [] ? intel_prepare_plane_fb+0x100/0x2b0 [i915]
[  330.454698]  [] ? 
drm_atomic_helper_setup_commit+0x252/0x320 [drm_kms_helper]
[  330.454784]  [] ? intel_atomic_commit+0x442/0x560 [i915]
[  330.454843]  [] ? 
drm_atomic_set_crtc_for_connector+0x92/0xf0 [drm]
[  330.454870]  [] ? drm_atomic_helper_set_config+0x79/0xb0 
[drm_kms_helper]
[  330.454919]  [] ? drm_mode_set_config_internal+0x61/0x110 
[drm]
[  330.454969]  [] ? drm_mode_setcrtc+0x42b/0x560 [drm]
[  330.455004]  [] ? drm_ioctl+0x2ab/0x460 [drm]
[  330.455051]  [] ? drm_mode_setplane+0x1c0/0x1c0 [drm]
[  330.455059]  [] ? do_vfs_ioctl+0x9f/0x640
[  330.455069]  [] ? recalc_sigpending+0x17/0x50
[  330.455078]  [] ? __set_task_blocked+0x3d/0x90
[  

[Bug 1567417] Re: WARN_ON(!wm_changed) skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]

[Tero Marttila]

You can try the mainline 4.8-rc builds here:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc4/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567417

Title:
  WARN_ON(!wm_changed) skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609823] Re: Outdated README.Debian for cross-compilation on Ubuntu xenial

[Tero Marttila]

Workaround is to use go build:

GOPATH=~/go GOOS=linux GOARCH=arm GOARM=5 go build -o
bin/linux_arm/foo -v .

But this recompiles the entire stdlib each time.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609823

Title:
  Outdated README.Debian for cross-compilation on Ubuntu xenial

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609823] [NEW] Outdated README.Debian for cross-compilation on Ubuntu xenial

[Tero Marttila]

Public bug reported:

On Ubuntu trusty, I used to cross-compile Golang programs for ARM
devices, IIRC by installing the golang-go-linux-arm package. However,
these packages no longer exist in xenial, even though it is referred to
in the /usr/share/doc/golang-1.6-go/README.Debian file:

  If you get an error message like this:

~/gocode/src/helloworld $ GOARCH=386 go build
go build runtime: linux/386 must be bootstrapped using make.bash

  …you are missing the appropriate golang-go-$GOOS-$GOARCH debian package,
  i.e. golang-go-linux-386 in this case.

Not sure how to get the missing stdlib linux_arm pkgs. Trying to cross-
compile for e.g. GOOS=arm on amd64 results in:

$ GOPATH=~/go GOOS=linux GOARCH=arm GOARM=5 go install -v 
github.com/qmsk/e2/cmd/tally
go install runtime/internal/sys: mkdir /usr/lib/go-1.6/pkg/linux_arm: 
permission denied

$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

$ apt-cache policy golang-go
golang-go:
  Installed: 2:1.6-1ubuntu4
  Candidate: 2:1.6-1ubuntu4
  Version table:
 *** 2:1.6-1ubuntu4 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609823

Title:
  Outdated README.Debian for cross-compilation on Ubuntu xenial

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1597267] Re: ThinkPad X260 connecting external DisplayPort hangs system

[Tero Marttila]

I found a couple existing bugs in the freedesktop.org tracker that might
be related, all marked as fixed in recent nightlies:

https://bugs.freedesktop.org/show_bug.cgi?id=96714
https://bugs.freedesktop.org/show_bug.cgi?id=95498
https://bugs.freedesktop.org/show_bug.cgi?id=94822
https://bugs.freedesktop.org/show_bug.cgi?id=89055

There's also some indications this may be related to 4k monitors as
well; my original crash with the ThinkPad Dock and Ubuntu's 4.4.0 kernel
was a FullHD monitor, later tests with 4.6 and 4.7 were all with a 4k DP
1.2 monitor. I'll have to test again with the dock and a non-4k monitor
once I get my hands on it.

** Bug watch added: freedesktop.org Bugzilla #96714
   https://bugs.freedesktop.org/show_bug.cgi?id=96714

** Bug watch added: freedesktop.org Bugzilla #95498
   https://bugs.freedesktop.org/show_bug.cgi?id=95498

** Bug watch added: freedesktop.org Bugzilla #94822
   https://bugs.freedesktop.org/show_bug.cgi?id=94822

** Bug watch added: freedesktop.org Bugzilla #89055
   https://bugs.freedesktop.org/show_bug.cgi?id=89055

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597267

Title:
  ThinkPad X260 connecting external DisplayPort hangs system

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1597267] Re: ThinkPad X260 connecting external DisplayPort hangs system

[Tero Marttila]

I can confirm that linux-image 4.7.0-994-generic_4.7.0-994.201607052202
from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-
nightly/2016-07-06/ behaves much better.

DP hotplug/unplug behaves correctly across text console, VT switch to
lightdm and login into Unity. There's still some WARNs in dmesg
(attached) when connecting the external DP monitor, but nothing crashes,
and my 4k desktop appears to function correctly:

   [drm:skl_set_cdclk [i915]] *ERROR* failed to inform PCU about cdclk
change

WARNING: CPU: 1 PID: 929 at 
/home/kernel/COD/linux/drivers/gpu/drm/drm_irq.c:1218 
drm_wait_one_vblank+0x16f/0x1b0 [drm]
vblank not available on crtc 0, ret=-22

[drm:gen8_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun

Confirmed to still crash with http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.7-rc6-yakkety/

** Attachment added: "Linux version 4.7.0-994-generic (kernel@tangerine) (gcc 
version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1) ) #201607052202 SMP Wed Jul 6 
02:04:37 UTC 2016"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597267/+attachment/4696230/+files/ubuntu1604-linux47drm994-dp.dmesg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597267

Title:
  ThinkPad X260 connecting external DisplayPort hangs system

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1597267] Re: ThinkPad X260 connecting external DisplayPort hangs system

[Tero Marttila]

And no upgrades or prior working versions, this is a fresh Ubuntu 16.04
install on a newly purchased X260 laptop.

** Description changed:

  Running Ubuntu 16.04 on a Lenovo ThinkPad X260 with Intel Skylake HD
  Graphics 520, connecting an external monitor to the DisplayPort
  connector causes the system to quickly hang. The system stops responding
  to network pings, cannot switch consoles, and needs a hard reboot.
  
  The external monitor does work when using a text console, and does not
  always hang in the LightDM login screen, but starting up a desktop
  session will always hang.
  
  This originally happened using a ThinkPad dock, and I tested it further
  using an external DP monitor. This happens on 4.4.0-28-generic as well
  as mainline 4.6.3-040603-generic and 4.7.0-040700rc5-generic; they all
  hang in a similar fashion.
  
- I have attached a journalctl log from running 4.4.0-28-generic and
- connecting the DP monitor while in a text console, before switching to
- the graphical console and logging in. The system hangs after a series
+ I have attached a journalctl log from running 4.7.0-040700rc5-generic
+ and connecting the DP monitor while in a text console, before switching
+ to the graphical console and logging in. The system hangs after a series
  of:
  
  kernel: WARNING: CPU: 3 PID: 2319 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_pm.c:3647 
skl_update_other_pipe_wm+0x15d/0x170 [i915]
- 2016-06-29T12:54:52+0300 tehobari kernel: WARNING: CPU: 3 PID: 4418 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:13957 
skl_max_scale.part.108+0x69/0x70 [i915]
+ kernel: WARNING: CPU: 3 PID: 4418 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:13957 
skl_max_scale.part.108+0x69/0x70 [i915]
  kernel: [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
  
  The first warnings come immediately when connecting, and others when
  switching consoles and logging in.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  terom  1903 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 29 13:03:18 2016
  InstallationDate: Installed on 2016-06-26 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20F6007RGE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=6636a3bb-262e-4ab2-ae81-d9388e3f7684 ro rootflags=subvol=@ quiet 
splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R02ET48W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F6007RGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR02ET48W(1.21):bd06/01/2016:svnLENOVO:pn20F6007RGE:pvrThinkPadX260:rvnLENOVO:rn20F6007RGE:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20F6007RGE
  dmi.product.version: ThinkPad X260
  dmi.sys.vendor: LENOVO

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597267

Title:
  ThinkPad X260 connecting external DisplayPort hangs system

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1597267] Re: ThinkPad X260 connecting external DisplayPort hangs system

[Tero Marttila]

As per the description, I have tested this with 4.4.0-28-generic as well
as mainline 4.6.3-040603-generic and 4.7.0-040700rc5-generic; they all
hang in a similar fashion.

In fact, the journal output I attached was from the 4.7 kernel, I
renamed the attachment accordingly:  ubuntu16-04_linux4.7.0-040700rc5
-generic_dp-hang.log

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

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597267

Title:
  ThinkPad X260 connecting external DisplayPort hangs system

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1597267] Re: ThinkPad X260 connecting external DisplayPort hangs system

[Tero Marttila]

Note that compared to #1559308 , connecting the same monitor via the
HDMI port on the laptop running 4.4.0-28-generic does seem to work fine:

There's still some stuff in dmesg when using HDMI as well:

snd_hda_codec_hdmi hdaudioC0D2: HDMI: ELD buf size is 0, force 128
snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD data byte 0
[ cut here ]
WARNING: CPU: 1 PID: 1080 at 
/build/linux-BvkamA/linux-4.4.0/ubuntu/i915/intel_pm.c:3586 
skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]()
WARN_ON(!wm_changed)
Modules linked in:
 ctr ccm rfcomm bnep arc4 snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core 
intel_rapl x86_pkg_temp_thermal snd_soc_sst_ipc intel_powerclamp coretemp 
snd_soc_sst_dsp snd_hda_codec_hdmi snd_soc_core kvm_intel snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_codec_realtek kvm dw_dmac_core snd_hda_codec_generic 
input_leds snd_hda_intel irqbypass iwlmvm uvcvideo snd_hda_codec 
videobuf2_vmalloc videobuf2_memops mac80211 snd_hda_core videobuf2_v4l2 
videobuf2_core v4l2_common snd_hwdep joydev serio_raw snd_pcm videodev btusb 
media btrtl thinkpad_acpi cdc_ether btbcm option iwlwifi nvram usbnet usb_wwan 
usbserial btintel mii rtsx_pci_ms snd_seq_midi bluetooth memstick 
snd_seq_midi_event cfg80211 snd_rawmidi mei_me mei snd_seq shpchp 
snd_seq_device snd_timer snd soundcore mac_hid parport_pc ppdev lp
 parport autofs4 btrfs xor raid6_pq drbg ansi_cprng algif_skcipher af_alg 
dm_crypt rtsx_pci_sdmmc i915_bpo crct10dif_pclmul crc32_pclmul aesni_intel 
intel_ips i2c_algo_bit aes_x86_64 drm_kms_helper lrw gf128mul glue_helper 
ablk_helper syscopyarea cryptd sysfillrect sysimgblt fb_sys_fops e1000e ahci 
drm psmouse ptp rtsx_pci pps_core libahci wmi video fjes
CPU: 1 PID: 1080 Comm: Xorg Not tainted 4.4.0-28-generic #47-Ubuntu
Hardware name: LENOVO 20F6007RGE/20F6007RGE, BIOS R02ET48W (1.21 ) 06/01/2016
 0286 9c6cf672 88040dfa39a8 813eb1a3
 88040dfa39f0 c0373c98 88040dfa39e0 81081102
 88040fc7c000 880409629d9c 88040fc7b000 880409020b78
Call Trace:
 [] dump_stack+0x63/0x90
 [] warn_slowpath_common+0x82/0xc0
 [] warn_slowpath_fmt+0x5c/0x80
 [] skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]
 [] skl_update_wm+0x186/0x5f0 [i915_bpo]
 [] ? intel_display_power_put+0xd0/0x130 [i915_bpo]
 [] intel_update_watermarks+0x1e/0x30 [i915_bpo]
 [] intel_atomic_commit+0x485/0xdc0 [i915_bpo]
 [] ? drm_atomic_check_only+0x18e/0x590 [drm]
 [] drm_atomic_commit+0x37/0x60 [drm]
 [] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]
 [] ? drm_modeset_lock_all_ctx+0x9a/0xb0 [drm]
 [] drm_mode_set_config_internal+0x62/0x100 [drm]
 [] drm_mode_setcrtc+0x3d2/0x4f0 [drm]
 [] drm_ioctl+0x152/0x540 [drm]
 [] ? drm_mode_setplane+0x1b0/0x1b0 [drm]
 [] do_vfs_ioctl+0x29f/0x490
 [] ? __sys_recvmsg+0x80/0x90
 [] SyS_ioctl+0x79/0x90
 [] entry_SYSCALL_64_fastpath+0x16/0x71
---[ end trace a13f8ffdea74aa69 ]---

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597267

Title:
  ThinkPad X260 connecting external DisplayPort hangs system

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1597267] [NEW] ThinkPad X260 connecting external DisplayPort hangs system

[Tero Marttila]

Public bug reported:

Running Ubuntu 16.04 on a Lenovo ThinkPad X260 with Intel Skylake HD
Graphics 520, connecting an external monitor to the DisplayPort
connector causes the system to quickly hang. The system stops responding
to network pings, cannot switch consoles, and needs a hard reboot.

The external monitor does work when using a text console, and does not
always hang in the LightDM login screen, but starting up a desktop
session will always hang.

This originally happened using a ThinkPad dock, and I tested it further
using an external DP monitor. This happens on 4.4.0-28-generic as well
as mainline 4.6.3-040603-generic and 4.7.0-040700rc5-generic; they all
hang in a similar fashion.

I have attached a journalctl log from running 4.4.0-28-generic and
connecting the DP monitor while in a text console, before switching to
the graphical console and logging in. The system hangs after a series
of:

kernel: WARNING: CPU: 3 PID: 2319 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_pm.c:3647 
skl_update_other_pipe_wm+0x15d/0x170 [i915]
2016-06-29T12:54:52+0300 tehobari kernel: WARNING: CPU: 3 PID: 4418 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:13957 
skl_max_scale.part.108+0x69/0x70 [i915]
kernel: [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun

The first warnings come immediately when connecting, and others when
switching consoles and logging in.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-28-generic 4.4.0-28.47
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  terom  1903 F pulseaudio
CurrentDesktop: Unity
Date: Wed Jun 29 13:03:18 2016
InstallationDate: Installed on 2016-06-26 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20F6007RGE
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=6636a3bb-262e-4ab2-ae81-d9388e3f7684 ro rootflags=subvol=@ quiet 
splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-28-generic N/A
 linux-backports-modules-4.4.0-28-generic  N/A
 linux-firmware1.157.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/01/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R02ET48W (1.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20F6007RGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR02ET48W(1.21):bd06/01/2016:svnLENOVO:pn20F6007RGE:pvrThinkPadX260:rvnLENOVO:rn20F6007RGE:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20F6007RGE
dmi.product.version: ThinkPad X260
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug xenial

** Attachment added: "ubuntu1604-linux44-dp1.log"
   
https://bugs.launchpad.net/bugs/1597267/+attachment/4692147/+files/ubuntu1604-linux44-dp1.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597267

Title:
  ThinkPad X260 connecting external DisplayPort hangs system

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1593301] [NEW] docker in security.privileged=true containers cannot start containers: write /sys/fs/cgroup/devices/docker/.../devices.allow: operation not permitted

[Tero Marttila]

Public bug reported:

Hi,

Running Ubuntu xenial with current 4.4.0-22-generic kernel and lxd
2.0.2-0ubuntu1~16.04.1, running Ubuntu's patched docker.io package
within an unprivileged container (`lxc launch -p default -p docker
ubuntu:xenial docker-test`) works, but fails once configuring the
container with `lxc config set docker-test security.privileged true`:

root@docker-test:~# docker run --rm -it debian:jessie bash
docker: Error response from daemon: Cannot start container 
07f5ddd392059c60aa12dd2f7292e54e01b153f2e203180f963989257fec9202: [10] System 
error: write 
/sys/fs/cgroup/devices/docker/07f5ddd392059c60aa12dd2f7292e54e01b153f2e203180f963989257fec9202/devices.allow:
 operation not permitted.

Upgrading to yakkety's docker.io=1.11.2-0ubuntu4 gives a slightly better
error:

docker: Error response from daemon: rpc error: code = 2 desc =
"oci runtime error: failed to write c 10:200 rwm to devices.allow: write
/sys/fs/cgroup/devices/docker/f05ecde20639572f27ac1ecf582b034d313b7d6573bddc2b57bd49ba1326e36d/devices.allow:
operation not permitted".

Where:

lrwxrwxrwx 1 root root 0 Jun 16 18:28 /sys/dev/char/10:200 ->
../../devices/virtual/misc/tun

It looks like containerd/runc per default wants to allow access to
/dev/net/tun for containers:

https://github.com/docker/docker/blob/master/vendor/src/github.com/opencontainers/runc/libcontainer/configs/device_defaults.go#L101

Adding the tuntap device to the docker profile (and restarting the
container):

lxc profile device add docker tuntap unix-char path=/dev/net/tun

allows the device within the devices cgroup hierarchy:

root@docker-test:~# cat /sys/fs/cgroup/devices/devices.list 
c *:* m
b *:* m
c 5:0 rwm
c 5:1 rwm
c 1:5 rwm
c 1:7 rwm
c 1:3 rwm
c 1:8 rwm
c 1:9 rwm
c 5:2 rwm
c 136:* rwm
c 10:229 rwm
c 10:200 rwm

and fixes docker run:

root@docker-test:~# docker run --rm -it debian:jessie bash
root@7ecba0a17fdd:/# 

---

On the lxd host:

$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04

$ apt-cache policy lxd
lxd:
  Installed: 2.0.2-0ubuntu1~16.04.1
  Candidate: 2.0.2-0ubuntu1~16.04.1
  Version table:
 *** 2.0.2-0ubuntu1~16.04.1 500
500 http://apt/ubuntu xenial-security/main amd64 Packages
500 http://apt/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 2.0.0-0ubuntu4 500
500 http://apt/ubuntu xenial/main amd64 Packages

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593301

Title:
  docker in security.privileged=true containers cannot start containers:
  write
  /sys/fs/cgroup/devices/docker/.../devices.allow: operation not
  permitted

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1580192] [NEW] systemd-nspawn --network-interface= disappears when container exits

[Tero Marttila]

Public bug reported:

On Ubuntu xenial,

$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
$ apt-cache policy systemd
systemd:
  Installed: 229-4ubuntu4
  Candidate: 229-4ubuntu4
  Version table:
 *** 229-4ubuntu4 500
500 http://apt/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

The systemd-nspawn manpage states that the existing --network-interface=
device should be returned to the host's namespace on exit:

   --network-interface=
   Assign the specified network interface to the container. This will 
remove the specified interface from the calling namespace
   and place it in the container. *When the container terminates, it is 
moved back to the host namespace*. Note that
   --network-interface= implies --private-network. This option may be 
used more than once to add multiple network interfaces to
   the container.

However, this does not appear to be the case for a VLAN interface
(created using systemd-networkd):

$ ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1:  mtu 1500 qdisc mq state UP 
mode DEFAULT group default qlen 1000
link/ether 00:26:b9:5a:45:03 brd ff:ff:ff:ff:ff:ff
3: eno2:  mtu 1500 qdisc noop state DOWN mode 
DEFAULT group default qlen 1000
link/ether 00:26:b9:5a:45:04 brd ff:ff:ff:ff:ff:ff
6: vlan-terom-dev@eno1:  mtu 1500 qdisc noop state 
DOWN mode DEFAULT group default qlen 1000
link/ether 66:c9:35:09:49:74 brd ff:ff:ff:ff:ff:ff
$ sudo systemd-nspawn -M obelix-terom-dev 
--network-interface=vlan-terom-dev bash
Spawning container obelix-terom-dev on 
/var/lib/machines/.#machine.obelix-terom-devfc1e2f39f5df67dd.
Press ^] three times within 1s to kill container.
mount(/var/lib/machines/obelix-terom-dev/sys/fs/selinux) failed, 
ignoring: No such file or directory
mount(/var/lib/machines/obelix-terom-dev/sys/fs/selinux) failed, 
ignoring: Invalid argument
/etc/localtime is not a symlink, not updating container timezone.
root@obelix-terom-dev:/# ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
6: vlan-terom-dev@if2:  mtu 1500 qdisc noop state 
DOWN mode DEFAULT group default qlen 1000
link/ether 66:c9:35:09:49:74 brd ff:ff:ff:ff:ff:ff link-netnsid 0
root@obelix-terom-dev:/# exit
Container obelix-terom-dev exited successfully.
$ ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1:  mtu 1500 qdisc mq state UP 
mode DEFAULT group default qlen 1000
link/ether 00:26:b9:5a:45:03 brd ff:ff:ff:ff:ff:ff
3: eno2:  mtu 1500 qdisc noop state DOWN mode 
DEFAULT group default qlen 1000
link/ether 00:26:b9:5a:45:04 brd ff:ff:ff:ff:ff:ff
$ sudo systemd-nspawn -M obelix-terom-dev 
--network-interface=vlan-terom-dev bash
Spawning container obelix-terom-dev on 
/var/lib/machines/obelix-terom-dev.
Press ^] three times within 1s to kill container.
Failed to resolve interface vlan-terom-dev: No such device
mount(/var/lib/machines/obelix-terom-dev/sys/fs/selinux) failed, 
ignoring: No such file or directory
mount(/var/lib/machines/obelix-terom-dev/sys/fs/selinux) failed, 
ignoring: Invalid argument
/etc/localtime is not a symlink, not updating container timezone.
$ 

Possibly related upstream mailing list thread, including workarounds:

https://lists.freedesktop.org/archives/systemd-
devel/2015-April/030934.html

Is this just a documentation bug in the man page?

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580192

Title:
  systemd-nspawn --network-interface= disappears when container exits

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1556451] [NEW] xenial lvm2-monitor.service fails with lvm raid1 volumes

[Tero Marttila]

Public bug reported:

After installing xenial using the daily ubuntu-server installer,
creating an LVM volume for the root filesystem, I lvconverted it into a
raid1 mirror for redundancy over the pair of SSDs installed (as separate
LVM PVs):

sudo lvconvert -m 1 --type raid1 bonk/bonk1 /dev/sdc1 /dev/sdd1

After a reboot, the lvm2-monitor.service fails. Relevant lines from
journalctl:

$ sudo journalctl | grep -iE '(lvm|dmeventd)'
Mar 12 19:32:48 bonk1 systemd[1]: Listening on LVM2 metadata daemon 
socket.
Mar 12 19:32:48 bonk1 systemd[1]: Listening on LVM2 poll daemon socket.
Mar 12 19:32:48 bonk1 systemd[1]: Starting Monitoring of LVM2 mirrors, 
snapshots etc. using dmeventd or progress polling...
Mar 12 19:32:49 bonk1 systemd[1]: Started LVM2 metadata daemon.
Mar 12 19:32:52 bonk1 dmeventd[1039]: dmeventd 
libdevmapper-event-lvm2raid.so dlopen failed: libdevmapper-event-lvm2raid.so: 
cannot open shared object file: No such file or directory.
Mar 12 19:32:52 bonk1 dmeventd[1039]: dmeventd 
libdevmapper-event-lvm2raid.so dlopen failed: libdevmapper-event-lvm2raid.so: 
cannot open shared object file: No such file or directory.
Mar 12 19:32:52 bonk1 dmeventd[1039]: dmeventd 
libdevmapper-event-lvm2raid.so dlopen failed: libdevmapper-event-lvm2raid.so: 
cannot open shared object file: No such file or directory.
Mar 12 19:32:59 bonk1 lvm[556]:   Monitoring bonk/bonk1 failed.
Mar 12 19:32:59 bonk1 lvm[556]:   4 logical volume(s) in volume group 
"bonk" monitored
Mar 12 19:32:59 bonk1 systemd[1]: lvm2-monitor.service: Main process 
exited, code=exited, status=5/NOTINSTALLED
Mar 12 19:32:59 bonk1 systemd[1]: Failed to start Monitoring of LVM2 
mirrors, snapshots etc. using dmeventd or progress polling.
Mar 12 19:32:59 bonk1 systemd[1]: lvm2-monitor.service: Unit entered 
failed state.
Mar 12 19:32:59 bonk1 systemd[1]: lvm2-monitor.service: Failed with 
result 'exit-code'.
Mar 12 19:33:00 bonk1 dmeventd[1039]: dmeventd 
libdevmapper-event-lvm2raid.so dlopen failed: libdevmapper-event-lvm2raid.so: 
cannot open shared object file: No 
such file or directory.
Mar 12 19:33:08 bonk1 systemd-udevd[662]: Process 'watershed sh -c 
'/sbin/lvm vgscan; /sbin/lvm vgchange -a y'' failed with exit code 5.
Mar 12 19:33:08 bonk1 dmeventd[1039]: dmeventd 
libdevmapper-event-lvm2raid.so dlopen failed: libdevmapper-event-lvm2raid.so: 
cannot open shared object file: No such file or directory.
Mar 12 19:33:16 bonk1 systemd-udevd[655]: Process 'watershed sh -c 
'/sbin/lvm vgscan; /sbin/lvm vgchange -a y'' failed with exit code 5.

The .so file is present and installed as part of dmeventd:

$ dpkg -S libdevmapper-event-lvm2raid.so
dmeventd: 
/lib/x86_64-linux-gnu/device-mapper/libdevmapper-event-lvm2raid.so

This may be related to Debian's lvm2 2.02.133-2 change:

* Drop event plugin directory move.  This moves the plugins back into
 the main library path. (closes: #807279)

See:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807279

--- 
$ apt-cache policy lvm2 dmeventd 
lvm2:
  Installed: 2.02.133-1ubuntu7
  Candidate: 2.02.133-1ubuntu7
  Version table:
 *** 2.02.133-1ubuntu7 500
500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
dmeventd:
  Installed: 2:1.02.110-1ubuntu7
  Candidate: 2:1.02.110-1ubuntu7
  Version table:
 *** 2:1.02.110-1ubuntu7 500
500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556451

Title:
  xenial lvm2-monitor.service fails with lvm raid1 volumes

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1492709] Re: New packages (e.g. kernels) not marked for autoremove iff update-manager set to "display" rather than "install automatically"

[Tero Marttila]

Crude, crude workaround on trusty:

aptitude markauto '?name(linux-image-.*-generic)'

This lets 'apt-get autoremove' clean out old kernels installed via
update-manager, while /etc/apt/apt.conf.d/01autoremove-kernels ensures
that some kernels are retained.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492709

Title:
  New packages (e.g. kernels) not marked for autoremove iff update-
  manager set to "display" rather than "install automatically"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1492709/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1495853] [NEW] puppet service enable broken on ubuntu vivid for services shipping sysvinit and systemd support

[Tero Marttila]

Public bug reported:

Running Puppet on Ubuntu 15.04 Vivid:

$ lsb_release -d
Description:Ubuntu 15.04

$ apt-cache policy puppet-common
puppet-common:
Installed: 3.7.2-1ubuntu2

Using the bird package as an example:

$ dpkg -L bird | vgrep service unit files
/lib/systemd/system/bird.service
/lib/systemd/system/bird6.service
/etc/init.d/bird6
/etc/init.d/bird
/etc/init/bird.conf
/etc/init/bird6.conf

Puppet appears to choose the debian provider for the bird service, over
the systemd provider:

$ sudo puppet resource --debug --param provider --param enable service 
bird
Debug: Runtime environment: puppet_version=3.7.2, ruby_version=2.1.2, 
run_mode=user, default_encoding=UTF-8
...
Debug: /Service[bird]: Provider debian does not support features 
flaggable; not managing attribute flags
...
Debug: Service bird found in both debian and init; skipping the init 
version
...
Debug: /Service[bird.service]: Provider systemd does not support 
features flaggable; not managing attribute flags
...
Debug: Executing '/etc/init.d/bird status'
service { 'bird':
  ensure   => 'stopped',
  enable   => 'true',
  provider => 'debian',
}

This means that while `ensure => running/stopped` works:

$ sudo puppet resource --debug --param provider service bird 
ensure=stopped
Debug: Executing '/etc/init.d/bird status'
Debug: Executing '/etc/init.d/bird stop'
Notice: /Service[bird]/ensure: ensure changed 'running' to 'stopped'
Debug: Finishing transaction 3255100
Debug: Storing state
Debug: Stored state in 0.13 seconds
Debug: Executing '/etc/init.d/bird status'
service { 'bird':
  ensure   => 'stopped',
  provider => 'debian',
}

The service `enabled => true/false` state does not:

$ sudo puppet resource --debug --param provider service bird 
enable=false
Debug: Executing '/etc/init.d/bird status'
Debug: Executing '/usr/sbin/update-rc.d bird disable'
Notice: /Service[bird]/enable: enable changed 'true' to 'false'
Debug: Finishing transaction 23676980
Debug: Storing state
Debug: Stored state in 0.12 seconds
Debug: Executing '/etc/init.d/bird status'
service { 'bird':
  ensure   => 'stopped',
  enable   => 'false',
  provider => 'debian',
}
$ sudo puppet resource --debug --param provider service bird enable=true
Debug: Executing '/etc/init.d/bird status'
Debug: Executing '/usr/sbin/update-rc.d -f bird remove'
Debug: Executing '/usr/sbin/update-rc.d bird defaults'
Notice: /Service[bird]/enable: enable changed 'false' to 'true'
Debug: Finishing transaction 12984740
Debug: Storing state
Debug: Stored state in 0.14 seconds
Debug: Executing '/etc/init.d/bird status'
service { 'bird':
  ensure   => 'stopped',
  enable   => 'true',
  provider => 'debian',
}
$ ls /etc/rc?.d/*bird*
/etc/rc0.d/K01bird   /etc/rc1.d/K01bird6  /etc/rc3.d/K01bird6  
/etc/rc4.d/S02bird   /etc/rc6.d/K01bird
/etc/rc0.d/K01bird6  /etc/rc2.d/K01bird6  /etc/rc3.d/S02bird   
/etc/rc5.d/K01bird6  /etc/rc6.d/K01bird6
/etc/rc1.d/K01bird   /etc/rc2.d/S02bird   /etc/rc4.d/K01bird6  
/etc/rc5.d/S02bird
$ sudo systemctl is-enabled bird
disabled

I presume that systemd ignores any sysvinit configuration (/etc/rc?.d/*)
for services that have a native systemd unit, and is thus blind to any
state inspected/changed by puppet's debian service provider.

Workaround is to explcitly use the systemd provider for the service
shipping a native systemd service unit:

$ sudo puppet resource --debug --param provider --param enable service 
bird provider=systemd enable=true
Warning: Setting manifest is deprecated in puppet.conf. See 
http://links.puppetlabs.com/env-settings-deprecations
Debug: Executing '/bin/systemctl is-active bird'
Debug: Executing '/bin/systemctl is-enabled bird'
Debug: Executing '/bin/systemctl enable bird'
Notice: /Service[bird]/enable: enable changed 'false' to 'true'
Debug: Finishing transaction 14759420
Debug: Storing state
Debug: Stored state in 0.20 seconds
Debug: Executing '/bin/systemctl is-active bird'
Debug: Executing '/bin/systemctl is-enabled bird'
service { 'bird':
  ensure   => 'stopped',
  enable   => 'true',
  provider => 'systemd',
}
$ sudo systemctl is-enabled bird
enabled

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

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, 

[Bug 1495853] Re: puppet service enable broken on ubuntu vivid with debian provider

[Tero Marttila]

** Summary changed:

- puppet service enable broken on ubuntu vivid for services shipping sysvinit 
and systemd support
+ puppet service enable broken on ubuntu vivid with debian provider

** Description changed:

  Running Puppet on Ubuntu 15.04 Vivid:
  
-   $ lsb_release -d
-   Description:Ubuntu 15.04
+  $ lsb_release -d
+  Description: Ubuntu 15.04
  
-   $ apt-cache policy puppet-common
-   puppet-common:
-   Installed: 3.7.2-1ubuntu2
+  $ apt-cache policy puppet-common
+  puppet-common:
+   Installed: 3.7.2-1ubuntu2
  
- Using the bird package as an example:
+ Using the bird package as an example, which ships both sysvinit and
+ systemd service files:
  
-   $ dpkg -L bird | vgrep service unit files
-   /lib/systemd/system/bird.service
-   /lib/systemd/system/bird6.service
-   /etc/init.d/bird6
-   /etc/init.d/bird
-   /etc/init/bird.conf
-   /etc/init/bird6.conf
+  $ dpkg -L bird | vgrep service unit files
+  /lib/systemd/system/bird.service
+  /lib/systemd/system/bird6.service
+  /etc/init.d/bird6
+  /etc/init.d/bird
+  /etc/init/bird.conf
+  /etc/init/bird6.conf
  
  Puppet appears to choose the debian provider for the bird service, over
  the systemd provider:
  
-   $ sudo puppet resource --debug --param provider --param enable service 
bird
-   Debug: Runtime environment: puppet_version=3.7.2, ruby_version=2.1.2, 
run_mode=user, default_encoding=UTF-8
-   ...
-   Debug: /Service[bird]: Provider debian does not support features 
flaggable; not managing attribute flags
-   ...
-   Debug: Service bird found in both debian and init; skipping the init 
version
-   ...
-   Debug: /Service[bird.service]: Provider systemd does not support 
features flaggable; not managing attribute flags
-   ...
-   Debug: Executing '/etc/init.d/bird status'
-   service { 'bird':
- ensure   => 'stopped',
- enable   => 'true',
- provider => 'debian',
-   }
+  $ sudo puppet resource --debug --param provider --param enable service bird
+  Debug: Runtime environment: puppet_version=3.7.2, ruby_version=2.1.2, 
run_mode=user, default_encoding=UTF-8
+  ...
+  Debug: /Service[bird]: Provider debian does not support features flaggable; 
not managing attribute flags
+  ...
+  Debug: Service bird found in both debian and init; skipping the init version
+  ...
+  Debug: /Service[bird.service]: Provider systemd does not support features 
flaggable; not managing attribute flags
+  ...
+  Debug: Executing '/etc/init.d/bird status'
+  service { 'bird':
+    ensure   => 'stopped',
+    enable   => 'true',
+    provider => 'debian',
+  }
  
  This means that while `ensure => running/stopped` works:
  
-   $ sudo puppet resource --debug --param provider service bird 
ensure=stopped
-   Debug: Executing '/etc/init.d/bird status'
-   Debug: Executing '/etc/init.d/bird stop'
-   Notice: /Service[bird]/ensure: ensure changed 'running' to 'stopped'
-   Debug: Finishing transaction 3255100
-   Debug: Storing state
-   Debug: Stored state in 0.13 seconds
-   Debug: Executing '/etc/init.d/bird status'
-   service { 'bird':
- ensure   => 'stopped',
- provider => 'debian',
-   }
+  $ sudo puppet resource --debug --param provider service bird ensure=stopped
+  Debug: Executing '/etc/init.d/bird status'
+  Debug: Executing '/etc/init.d/bird stop'
+  Notice: /Service[bird]/ensure: ensure changed 'running' to 'stopped'
+  Debug: Finishing transaction 3255100
+  Debug: Storing state
+  Debug: Stored state in 0.13 seconds
+  Debug: Executing '/etc/init.d/bird status'
+  service { 'bird':
+    ensure   => 'stopped',
+    provider => 'debian',
+  }
  
  The service `enabled => true/false` state does not:
  
-   $ sudo puppet resource --debug --param provider service bird 
enable=false
-   Debug: Executing '/etc/init.d/bird status'
-   Debug: Executing '/usr/sbin/update-rc.d bird disable'
-   Notice: /Service[bird]/enable: enable changed 'true' to 'false'
-   Debug: Finishing transaction 23676980
-   Debug: Storing state
-   Debug: Stored state in 0.12 seconds
-   Debug: Executing '/etc/init.d/bird status'
-   service { 'bird':
- ensure   => 'stopped',
- enable   => 'false',
- provider => 'debian',
-   }
-   $ sudo puppet resource --debug --param provider service bird enable=true
-   Debug: Executing '/etc/init.d/bird status'
-   Debug: Executing '/usr/sbin/update-rc.d -f bird remove'
-   Debug: Executing '/usr/sbin/update-rc.d bird defaults'
-   Notice: /Service[bird]/enable: enable changed 'false' to 'true'
-   Debug: Finishing transaction 12984740
-   Debug: Storing state
-   Debug: Stored state in 0.14 seconds
-   Debug: Executing '/etc/init.d/bird status'
-   service { 'bird':
- ensure   => 'stopped',
- enable   => 'true',
- provider => 

[Bug 1495853] Re: puppet service enable broken on ubuntu vivid for services shipping sysvinit and systemd support

[Tero Marttila]

Note that the same scenario behaves correctly under Debian jessie, with
the patched debian service provider in version 3.7.2-3:

https://bugs.debian.org/775795

Similar example on a Debian jessie system:

$ sudo lsb_release -d
Description:Debian GNU/Linux 8.2 (jessie)
$ apt-cache policy puppet
puppet:
  Installed: 3.7.2-4
  Candidate: 3.7.2-4
  Version table:
 *** 3.7.2-4 0
500 http://apt/debian/ jessie/main amd64 Packages
100 /var/lib/dpkg/status
$ dpkg -L bird | vgrep ...
/etc/init/bird.conf
/etc/init/bird6.conf
/etc/init.d/bird
/etc/init.d/bird6
/lib/systemd/system/bird.service
/lib/systemd/system/bird6.service

$ sudo puppet resource --debug --param provider --param enable service 
bird
Debug: Executing '/usr/sbin/service bird status'
Debug: Executing '/bin/systemctl show -pSourcePath bird'
Debug: Executing '/bin/systemctl is-enabled bird'
service { 'bird':
  ensure   => 'running',
  enable   => 'true',
  provider => 'debian',
}
$ sudo puppet resource --debug --param provider --param enable service 
bird enable=false
Debug: Executing '/usr/sbin/service bird status'
Debug: Executing '/bin/systemctl show -pSourcePath bird'
Debug: Executing '/bin/systemctl is-enabled bird'
Debug: Executing '/bin/systemctl disable bird'
Notice: /Service[bird]/enable: enable changed 'true' to 'false'
Debug: Finishing transaction 16554200
Debug: Storing state
Debug: Stored state in 0.29 seconds
Debug: Executing '/usr/sbin/service bird status'
Debug: Executing '/bin/systemctl show -pSourcePath bird'
Debug: Executing '/bin/systemctl is-enabled bird'
service { 'bird':
  ensure   => 'running',
  enable   => 'false',
  provider => 'debian',
}
$ sudo puppet resource --debug --param provider --param enable service 
bird enable=true
Debug: Executing '/usr/sbin/service bird status'
Debug: Executing '/bin/systemctl show -pSourcePath bird'
Debug: Executing '/bin/systemctl is-enabled bird'
Debug: Executing '/bin/systemctl enable bird'
Notice: /Service[bird]/enable: enable changed 'false' to 'true'
Debug: Finishing transaction 18953360
Debug: Storing state
Debug: Stored state in 0.21 seconds
Debug: Executing '/usr/sbin/service bird status'
Debug: Executing '/bin/systemctl show -pSourcePath bird'
Debug: Executing '/bin/systemctl is-enabled bird'
service { 'bird':
  ensure   => 'running',
  enable   => 'true',
  provider => 'debian',
}


** Bug watch added: Debian Bug tracker #775795
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775795

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495853

Title:
  puppet service enable broken on ubuntu vivid with debian provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1495853] Re: puppet service enable broken on ubuntu vivid for services shipping sysvinit and systemd support

[Tero Marttila]

Note that the same scenario behaves correctly under Debian jessie, with
the patched debian service provider in version 3.7.2-3:

https://bugs.debian.org/775795

Similar example on a Debian jessie system:

$ sudo lsb_release -d
Description:Debian GNU/Linux 8.2 (jessie)
$ apt-cache policy puppet
puppet:
  Installed: 3.7.2-4
  Candidate: 3.7.2-4
  Version table:
 *** 3.7.2-4 0
500 http://apt/debian/ jessie/main amd64 Packages
100 /var/lib/dpkg/status
$ dpkg -L bird | vgrep ...
/etc/init/bird.conf
/etc/init/bird6.conf
/etc/init.d/bird
/etc/init.d/bird6
/lib/systemd/system/bird.service
/lib/systemd/system/bird6.service

$ sudo puppet resource --debug --param provider --param enable service 
bird
Debug: Executing '/usr/sbin/service bird status'
Debug: Executing '/bin/systemctl show -pSourcePath bird'
Debug: Executing '/bin/systemctl is-enabled bird'
service { 'bird':
  ensure   => 'running',
  enable   => 'true',
  provider => 'debian',
}
$ sudo puppet resource --debug --param provider --param enable service 
bird enable=false
Debug: Executing '/usr/sbin/service bird status'
Debug: Executing '/bin/systemctl show -pSourcePath bird'
Debug: Executing '/bin/systemctl is-enabled bird'
Debug: Executing '/bin/systemctl disable bird'
Notice: /Service[bird]/enable: enable changed 'true' to 'false'
Debug: Finishing transaction 16554200
Debug: Storing state
Debug: Stored state in 0.29 seconds
Debug: Executing '/usr/sbin/service bird status'
Debug: Executing '/bin/systemctl show -pSourcePath bird'
Debug: Executing '/bin/systemctl is-enabled bird'
service { 'bird':
  ensure   => 'running',
  enable   => 'false',
  provider => 'debian',
}
$ sudo puppet resource --debug --param provider --param enable service 
bird enable=true
Debug: Executing '/usr/sbin/service bird status'
Debug: Executing '/bin/systemctl show -pSourcePath bird'
Debug: Executing '/bin/systemctl is-enabled bird'
Debug: Executing '/bin/systemctl enable bird'
Notice: /Service[bird]/enable: enable changed 'false' to 'true'
Debug: Finishing transaction 18953360
Debug: Storing state
Debug: Stored state in 0.21 seconds
Debug: Executing '/usr/sbin/service bird status'
Debug: Executing '/bin/systemctl show -pSourcePath bird'
Debug: Executing '/bin/systemctl is-enabled bird'
service { 'bird':
  ensure   => 'running',
  enable   => 'true',
  provider => 'debian',
}


** Bug watch added: Debian Bug tracker #775795
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775795

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1495853

Title:
  puppet service enable broken on ubuntu vivid with debian provider

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1495853] [NEW] puppet service enable broken on ubuntu vivid for services shipping sysvinit and systemd support

[Tero Marttila]

Public bug reported:

Running Puppet on Ubuntu 15.04 Vivid:

$ lsb_release -d
Description:Ubuntu 15.04

$ apt-cache policy puppet-common
puppet-common:
Installed: 3.7.2-1ubuntu2

Using the bird package as an example:

$ dpkg -L bird | vgrep service unit files
/lib/systemd/system/bird.service
/lib/systemd/system/bird6.service
/etc/init.d/bird6
/etc/init.d/bird
/etc/init/bird.conf
/etc/init/bird6.conf

Puppet appears to choose the debian provider for the bird service, over
the systemd provider:

$ sudo puppet resource --debug --param provider --param enable service 
bird
Debug: Runtime environment: puppet_version=3.7.2, ruby_version=2.1.2, 
run_mode=user, default_encoding=UTF-8
...
Debug: /Service[bird]: Provider debian does not support features 
flaggable; not managing attribute flags
...
Debug: Service bird found in both debian and init; skipping the init 
version
...
Debug: /Service[bird.service]: Provider systemd does not support 
features flaggable; not managing attribute flags
...
Debug: Executing '/etc/init.d/bird status'
service { 'bird':
  ensure   => 'stopped',
  enable   => 'true',
  provider => 'debian',
}

This means that while `ensure => running/stopped` works:

$ sudo puppet resource --debug --param provider service bird 
ensure=stopped
Debug: Executing '/etc/init.d/bird status'
Debug: Executing '/etc/init.d/bird stop'
Notice: /Service[bird]/ensure: ensure changed 'running' to 'stopped'
Debug: Finishing transaction 3255100
Debug: Storing state
Debug: Stored state in 0.13 seconds
Debug: Executing '/etc/init.d/bird status'
service { 'bird':
  ensure   => 'stopped',
  provider => 'debian',
}

The service `enabled => true/false` state does not:

$ sudo puppet resource --debug --param provider service bird 
enable=false
Debug: Executing '/etc/init.d/bird status'
Debug: Executing '/usr/sbin/update-rc.d bird disable'
Notice: /Service[bird]/enable: enable changed 'true' to 'false'
Debug: Finishing transaction 23676980
Debug: Storing state
Debug: Stored state in 0.12 seconds
Debug: Executing '/etc/init.d/bird status'
service { 'bird':
  ensure   => 'stopped',
  enable   => 'false',
  provider => 'debian',
}
$ sudo puppet resource --debug --param provider service bird enable=true
Debug: Executing '/etc/init.d/bird status'
Debug: Executing '/usr/sbin/update-rc.d -f bird remove'
Debug: Executing '/usr/sbin/update-rc.d bird defaults'
Notice: /Service[bird]/enable: enable changed 'false' to 'true'
Debug: Finishing transaction 12984740
Debug: Storing state
Debug: Stored state in 0.14 seconds
Debug: Executing '/etc/init.d/bird status'
service { 'bird':
  ensure   => 'stopped',
  enable   => 'true',
  provider => 'debian',
}
$ ls /etc/rc?.d/*bird*
/etc/rc0.d/K01bird   /etc/rc1.d/K01bird6  /etc/rc3.d/K01bird6  
/etc/rc4.d/S02bird   /etc/rc6.d/K01bird
/etc/rc0.d/K01bird6  /etc/rc2.d/K01bird6  /etc/rc3.d/S02bird   
/etc/rc5.d/K01bird6  /etc/rc6.d/K01bird6
/etc/rc1.d/K01bird   /etc/rc2.d/S02bird   /etc/rc4.d/K01bird6  
/etc/rc5.d/S02bird
$ sudo systemctl is-enabled bird
disabled

I presume that systemd ignores any sysvinit configuration (/etc/rc?.d/*)
for services that have a native systemd unit, and is thus blind to any
state inspected/changed by puppet's debian service provider.

Workaround is to explcitly use the systemd provider for the service
shipping a native systemd service unit:

$ sudo puppet resource --debug --param provider --param enable service 
bird provider=systemd enable=true
Warning: Setting manifest is deprecated in puppet.conf. See 
http://links.puppetlabs.com/env-settings-deprecations
Debug: Executing '/bin/systemctl is-active bird'
Debug: Executing '/bin/systemctl is-enabled bird'
Debug: Executing '/bin/systemctl enable bird'
Notice: /Service[bird]/enable: enable changed 'false' to 'true'
Debug: Finishing transaction 14759420
Debug: Storing state
Debug: Stored state in 0.20 seconds
Debug: Executing '/bin/systemctl is-active bird'
Debug: Executing '/bin/systemctl is-enabled bird'
service { 'bird':
  ensure   => 'stopped',
  enable   => 'true',
  provider => 'systemd',
}
$ sudo systemctl is-enabled bird
enabled

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is 

[Bug 1495853] Re: puppet service enable broken on ubuntu vivid with debian provider

[Tero Marttila]

** Summary changed:

- puppet service enable broken on ubuntu vivid for services shipping sysvinit 
and systemd support
+ puppet service enable broken on ubuntu vivid with debian provider

** Description changed:

  Running Puppet on Ubuntu 15.04 Vivid:
  
-   $ lsb_release -d
-   Description:Ubuntu 15.04
+  $ lsb_release -d
+  Description: Ubuntu 15.04
  
-   $ apt-cache policy puppet-common
-   puppet-common:
-   Installed: 3.7.2-1ubuntu2
+  $ apt-cache policy puppet-common
+  puppet-common:
+   Installed: 3.7.2-1ubuntu2
  
- Using the bird package as an example:
+ Using the bird package as an example, which ships both sysvinit and
+ systemd service files:
  
-   $ dpkg -L bird | vgrep service unit files
-   /lib/systemd/system/bird.service
-   /lib/systemd/system/bird6.service
-   /etc/init.d/bird6
-   /etc/init.d/bird
-   /etc/init/bird.conf
-   /etc/init/bird6.conf
+  $ dpkg -L bird | vgrep service unit files
+  /lib/systemd/system/bird.service
+  /lib/systemd/system/bird6.service
+  /etc/init.d/bird6
+  /etc/init.d/bird
+  /etc/init/bird.conf
+  /etc/init/bird6.conf
  
  Puppet appears to choose the debian provider for the bird service, over
  the systemd provider:
  
-   $ sudo puppet resource --debug --param provider --param enable service 
bird
-   Debug: Runtime environment: puppet_version=3.7.2, ruby_version=2.1.2, 
run_mode=user, default_encoding=UTF-8
-   ...
-   Debug: /Service[bird]: Provider debian does not support features 
flaggable; not managing attribute flags
-   ...
-   Debug: Service bird found in both debian and init; skipping the init 
version
-   ...
-   Debug: /Service[bird.service]: Provider systemd does not support 
features flaggable; not managing attribute flags
-   ...
-   Debug: Executing '/etc/init.d/bird status'
-   service { 'bird':
- ensure   => 'stopped',
- enable   => 'true',
- provider => 'debian',
-   }
+  $ sudo puppet resource --debug --param provider --param enable service bird
+  Debug: Runtime environment: puppet_version=3.7.2, ruby_version=2.1.2, 
run_mode=user, default_encoding=UTF-8
+  ...
+  Debug: /Service[bird]: Provider debian does not support features flaggable; 
not managing attribute flags
+  ...
+  Debug: Service bird found in both debian and init; skipping the init version
+  ...
+  Debug: /Service[bird.service]: Provider systemd does not support features 
flaggable; not managing attribute flags
+  ...
+  Debug: Executing '/etc/init.d/bird status'
+  service { 'bird':
+    ensure   => 'stopped',
+    enable   => 'true',
+    provider => 'debian',
+  }
  
  This means that while `ensure => running/stopped` works:
  
-   $ sudo puppet resource --debug --param provider service bird 
ensure=stopped
-   Debug: Executing '/etc/init.d/bird status'
-   Debug: Executing '/etc/init.d/bird stop'
-   Notice: /Service[bird]/ensure: ensure changed 'running' to 'stopped'
-   Debug: Finishing transaction 3255100
-   Debug: Storing state
-   Debug: Stored state in 0.13 seconds
-   Debug: Executing '/etc/init.d/bird status'
-   service { 'bird':
- ensure   => 'stopped',
- provider => 'debian',
-   }
+  $ sudo puppet resource --debug --param provider service bird ensure=stopped
+  Debug: Executing '/etc/init.d/bird status'
+  Debug: Executing '/etc/init.d/bird stop'
+  Notice: /Service[bird]/ensure: ensure changed 'running' to 'stopped'
+  Debug: Finishing transaction 3255100
+  Debug: Storing state
+  Debug: Stored state in 0.13 seconds
+  Debug: Executing '/etc/init.d/bird status'
+  service { 'bird':
+    ensure   => 'stopped',
+    provider => 'debian',
+  }
  
  The service `enabled => true/false` state does not:
  
-   $ sudo puppet resource --debug --param provider service bird 
enable=false
-   Debug: Executing '/etc/init.d/bird status'
-   Debug: Executing '/usr/sbin/update-rc.d bird disable'
-   Notice: /Service[bird]/enable: enable changed 'true' to 'false'
-   Debug: Finishing transaction 23676980
-   Debug: Storing state
-   Debug: Stored state in 0.12 seconds
-   Debug: Executing '/etc/init.d/bird status'
-   service { 'bird':
- ensure   => 'stopped',
- enable   => 'false',
- provider => 'debian',
-   }
-   $ sudo puppet resource --debug --param provider service bird enable=true
-   Debug: Executing '/etc/init.d/bird status'
-   Debug: Executing '/usr/sbin/update-rc.d -f bird remove'
-   Debug: Executing '/usr/sbin/update-rc.d bird defaults'
-   Notice: /Service[bird]/enable: enable changed 'false' to 'true'
-   Debug: Finishing transaction 12984740
-   Debug: Storing state
-   Debug: Stored state in 0.14 seconds
-   Debug: Executing '/etc/init.d/bird status'
-   service { 'bird':
- ensure   => 'stopped',
- enable   => 'true',
- provider => 

[Bug 1349768] Re: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors

[Tero Marttila]

Yes, I can confirm that the trusty-proposed 3.13.0-38 kernel resolves
this issue. The dnsmasq-tftp transfer succeeds in my test environment
without any of the symptoms that were present with the trusty-
updates/security kernels between -30 and -37, nor do I notice any
regressions in my (IPv4) ipvs ruleset.

$ uname -a
Linux catcp2-test 3.13.0-38-generic #65-Ubuntu SMP Thu Oct 9 11:36:50 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

$ apt-cache policy linux-image-generic
linux-image-generic:
  Installed: 3.13.0.38.45
  Candidate: 3.13.0.38.45
  Version table:
 *** 3.13.0.38.45 0
 50 http://fi.archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
  ...


** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] Re: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors

[Tero Marttila]

ACK

3.13.0-35-generic #62~lp1349768v5v201408250842 appears to resolve the
issue completely on my actual test setup as well. No TFTP stalls,
dnsmasq EPERM errors or dmesg errors, and ftrace doesn't show any calls
to ipv6_find_hdr.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] Re: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors

[Tero Marttila]

NAK

Unfortunately no, the 3.13.0-35-generic #62~lp1349768v4v201408220857
from above continues to exhibit the same issues with my actual test
setup. Same thing with the ./lp1349768.sh testcase.

The 0041-ipvs-fix-ipv4-issues-in-ip_vs_out.patch in the lp1349768v4
build is a different patch, though?

The resulting ftrace that correlates with dnsmasq sendto() getting stuck
is still the same:

 dnsmasq-1447  [000]   1272.430975: ipv6_find_hdr 
-ip_vs_out_icmp_v6.isra.21
 dnsmasq-1447  [000]   1272.430983: stack trace
 = ip_vs_out.part.22
 = ip_vs_local_reply6
 = nf_iterate
 = nf_hook_slow
 = __ip_local_out
 = ip_local_out
 = ip_send_skb
 = udp_send_skb
 = udp_sendmsg
 = inet_sendmsg
 = sock_sendmsg
 = SYSC_sendto
 = SyS_sendto
 = tracesys

 Is there something I can use to confirm that the booted kernel image
actually has the correct nf_hook_ops.pf set? The fix seems pretty
obvious, so I was expecting it to work...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] Re: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors

[Tero Marttila]

NAK

Linux 3.13.0-35-generic #62~lp1349768v3v201408191448 still exhibits the
same symptoms (stalled dnsmasq-tftp transfer and IPv6 header not found
messages). Unloading the ip_vs module clears the issue.

I'll attempt to work out a minimal reproducer.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] Re: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors

[Tero Marttila]

Attached is a small script to setup dnsmasq-tftp and ipvs to reproduce
the dnsmasq-tftp stall. The strace at the end should start showing
sendto() = EPERM errors after running the curl tftp://.../ command given
as an example from a remote host.

The exact contents of the ipvs rules don't seem to matter.

The dnsmasq-tftp stall issue appears to happen with all the ubuntu-
installer/amd64/linux versions that I've tried, with the exact block
within the TFTP stream where it stalls changing betwen different
versions but remaining consistent between runs.

With the current netboot.tar.gz it appers to happen at block 600:

d4fc2ba26cad96f4360cb36f04c26b2f50dceee9413c206431148b87e4958909
/srv/tftp/ubuntu-installer/amd64/linux

With the original ubuntu-installer netboot.tar.gz version (from sometime
early June) I've been using it happens at block 311:

bdebc6c7bbd873bf5ad2480d90c2523da49cca8da5a0f4cb40adb7d1aeafb821
/srv/tftp/lp1349768/linux

Curiously, however, testing this setup on the 3.13.0-34-generic kernel
the dmesg error (IPv6 header not found) does NOT show up... may be
some other facters at play as well there?

** Attachment added: minimal testcase for LP#1349768 on Ubuntu 14.04
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349768/+attachment/4182427/+files/lp1349768.sh

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] Re: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors

[Tero Marttila]

ACK

I can confirm that this issue is no longer present with the Linux
3.13.0-33-generic #58~lp1349768v2v201407300928 kernel as installed from
above. Rebooting into the given kernel results in dnsmasq-tftp transfers
working fine, and no related dmesg errors occur.

Apologies for the delay. I was away, and had to reproduce this in a test
environment first.

Do tell me if you would still like a minimal reproducer to track down
the issue further, and I can work on getting something like that up.
AFAICT it would involve dnsmasq with enable-tftp/tftp-root and a
libvirt-qemu domain with boot dev='network' , requesting the ubuntu-
installer amd64 linux kernel over TFTP, with the ip_vs modules loaded
and a trivial ipvs ruleset applied on the server.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] Re: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors

[Tero Marttila]

The utopic kernel appears to be affected as well. Booting the same
Ubuntu 14.04 machine into the Linux 3.16.0-6-generic #11-Ubuntu kernel
installed from

   https://launchpad.net/ubuntu/+source/linux/3.16.0-6.11/+build/6217368

gives identical symptoms, i.e. dnsmasq-tftp stalls, dmesg reports IPv6
header not found, stracing dnsmasq shows sendto() giving EPERM, and
unloading ip_vs allows the stalled tftp transfer to continue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] Re: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors

[Tero Marttila]

NACK

The same faulty behaviour persists with linux-
image-3.13.0-33-generic=3.13.0-33.58~lp1349768v201407290941 (uname
3.13.0-33-generic #58~lp1349768v201407290941).

I do not notice any difference; identical symptoms. `rmmod ip_vs_rr
ip_vs` continues to immediately resolve the fault.

Note that my configuration also includes openvswitch. The tftp stall
continues to happen when flushing the ipvs ruleset, only unloading the
ip_vs module resolves it. However, only re-loading the ip_vs_rr module
does not trigger the stall, but loading the ipvs ruleset does. My IPVS
ruleset consists of only four TCP Masq forwards.

Using ktrace to try and get a rough stack trace, I was able to observe
the following sequences:

 dnsmasq-5012  [001]   2060.572946: ipv6_find_hdr 
-ip_vs_out.part.23
 dnsmasq-5012  [001]   2060.572955: stack trace
 = ip_vs_local_reply6
 = nf_iterate
 = nf_hook_slow
 = __ip_local_out
 = ip_local_out
 = ip_send_skb
 = udp_send_skb
 = udp_sendmsg
 = inet_sendmsg
 = sock_sendmsg
 = SYSC_sendto
 = SyS_sendto
 = tracesys
 dnsmasq-5012  [001]   2060.572956: ipv6_find_hdr 
-ip_vs_out_icmp_v6.isra.22
 dnsmasq-5012  [001]   2060.572963: stack trace
 = ip_vs_out.part.23
 = ip_vs_local_reply6
 = nf_iterate
 = nf_hook_slow
 = __ip_local_out
 = ip_local_out
 = ip_send_skb
 = udp_send_skb
 = udp_sendmsg
 = inet_sendmsg
 = sock_sendmsg
 = SYSC_sendto
 = SyS_sendto
 = tracesys

with the first sequence being repeated for every packet (?) and the
second, slightly different, sequence corresponding per the timestamp to
the dmesg:

[ 2060.572964] IPv6 header not found

This is with a my full iptables rulset loaded, but my OUTPUT DROP rules
counters do not indicate any matches. The ftrace output seems to be
identical with the iptables ruleset flushed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] Re: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors

[Tero Marttila]

Apologies, misfiled initially on biosdevname, I meant to file on the
linux-image package source.

** Description changed:

  I have an Ubuntu 14.04 host that I am using as both a keepalived/ipvs
  loadbalancer and dnsmasq server for pxebooting servers.
  
- After updating linux-image 3.13.0-30.55 - 3.13.0-32.57 I noticed that
+ After updating linux-image 3.13.0-29.53 - 3.13.0-32.57 I noticed that
  dnsmasq-tftp stopped working. pxeboot clients would hang on the Loading
  /linux TFTP transfer, with the transfer stalling roughly ~1000
  blocks into the transfer:
  
  10:30:51.011728 IP 10.1.1.2.43540  10.1.12.1.49165: UDP, length 1412
  10:30:51.011924 IP 10.1.12.1.49165  10.1.1.2.43540: UDP, length 4
  10:30:51.012012 IP 10.1.1.2.43540  10.1.12.1.49165: UDP, length 1412
  10:30:51.012183 IP 10.1.12.1.49165  10.1.1.2.43540: UDP, length 4
  
  stracing dnsmasq I noticed something very odd: sendto() on the
  socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) would suddenly start
  persistently returning EPERM in mid-transfer, even when dnsmasq
  continued to periodically retry:
  
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 1 (in [17], 
left {0, 249834})
  recvfrom(17, \0\4\3\352, 4096, 0, NULL, NULL) = 4
  lseek(16, 1410816, SEEK_SET) = 1410816
  read(16, 
\25\306\345f\2{\r\4)W\276\32\336q\252_\230q\213\341U\354\25\374k7\243\32\221X+\v...,
 1408) = 1408
  sendto(17, 
\0\3\3\353\25\306\345f\2{\r\4)W\276\32\336q\252_\230q\213\341U\354\25\374k7\243\32...,
 1412, 0, {sa_family=AF_INET, sin_port=htons(49165), 
sin_addr=inet_addr(10.1.11.3)}, 16) = 1412
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 1 (in [17], 
left {0, 249839})
  recvfrom(17, \0\4\3\353, 4096, 0, NULL, NULL) = 4
  lseek(16, 1412224, SEEK_SET) = 1412224
  read(16, *\360 
C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277\221\\\307\372...,
 1408) = 1408
  sendto(17, \0\3\3\354*\360 
C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277..., 
1412, 0, {sa_family=AF_INET, sin_port=htons(49165), 
sin_addr=inet_addr(10.1.11.3)}, 16) = -1 EPERM (Operation not permitted)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  lseek(16, 1412224, SEEK_SET) = 1412224
  read(16, *\360 
C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277\221\\\307\372...,
 1408) = 1408
  sendto(17, \0\3\3\354*\360 
C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277..., 
1412, 0, {sa_family=AF_INET, sin_port=htons(49165), 
sin_addr=inet_addr(10.1.11.3)}, 16) = -1 EPERM (Operation not permitted)
  
  This was with all iptables rules unloaded (so no OUTPUT -j DENY) and
  apparmor profiles torn down.
  
  I also noticed the following dmesgs appearing at roughly similar times
  to the tftp transfers getting stuck (although not coinciding exactly
  with the stall):
  
  [70325.516724] IPv6 header not found
  
  The error pointed to ipvs (which I am using on the same host as an IPv4 NAT 
loadbalancer):
  http://archive.linuxvirtualserver.org/html/lvs-devel/2012-08/msg00018.html
  http://comments.gmane.org/gmane.comp.linux.lvs.devel/3614
  
  I then tore down the ipvs rules (service keepalived stop) and unloaded
  the modules (rmmod ip_vs_rr ip_vs), and the issue resolved itself - the
  stalled dnsmasq-tftp transfer resumed!
  
  This seems to be reproducible, i.e. modprobing ip_vs and starting
  keepalived will cause dnsmasq-tftp to stall again, and
  stopping/unloading will resume.
  
  This seems to happen reproducibly on boot with -32 and -30. This does
  NOT seem to happen with 3.13.0-29 which I was using up until now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] [NEW] kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors

[Tero Marttila]

Public bug reported:

I have an Ubuntu 14.04 host that I am using as both a keepalived/ipvs
loadbalancer and dnsmasq server for pxebooting servers.

After updating linux-image 3.13.0-29.53 - 3.13.0-32.57 I noticed that
dnsmasq-tftp stopped working. pxeboot clients would hang on the Loading
/linux TFTP transfer, with the transfer stalling roughly ~1000
blocks into the transfer:

10:30:51.011728 IP 10.1.1.2.43540  10.1.12.1.49165: UDP, length 1412
10:30:51.011924 IP 10.1.12.1.49165  10.1.1.2.43540: UDP, length 4
10:30:51.012012 IP 10.1.1.2.43540  10.1.12.1.49165: UDP, length 1412
10:30:51.012183 IP 10.1.12.1.49165  10.1.1.2.43540: UDP, length 4

stracing dnsmasq I noticed something very odd: sendto() on the
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) would suddenly start
persistently returning EPERM in mid-transfer, even when dnsmasq
continued to periodically retry:

select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 1 (in [17], 
left {0, 249834})
recvfrom(17, \0\4\3\352, 4096, 0, NULL, NULL) = 4
lseek(16, 1410816, SEEK_SET) = 1410816
read(16, 
\25\306\345f\2{\r\4)W\276\32\336q\252_\230q\213\341U\354\25\374k7\243\32\221X+\v...,
 1408) = 1408
sendto(17, 
\0\3\3\353\25\306\345f\2{\r\4)W\276\32\336q\252_\230q\213\341U\354\25\374k7\243\32...,
 1412, 0, {sa_family=AF_INET, sin_port=htons(49165), 
sin_addr=inet_addr(10.1.11.3)}, 16) = 1412
select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 1 (in [17], 
left {0, 249839})
recvfrom(17, \0\4\3\353, 4096, 0, NULL, NULL) = 4
lseek(16, 1412224, SEEK_SET) = 1412224
read(16, *\360 
C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277\221\\\307\372...,
 1408) = 1408
sendto(17, \0\3\3\354*\360 
C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277..., 
1412, 0, {sa_family=AF_INET, sin_port=htons(49165), 
sin_addr=inet_addr(10.1.11.3)}, 16) = -1 EPERM (Operation not permitted)
select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
lseek(16, 1412224, SEEK_SET) = 1412224
read(16, *\360 
C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277\221\\\307\372...,
 1408) = 1408
sendto(17, \0\3\3\354*\360 
C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277..., 
1412, 0, {sa_family=AF_INET, sin_port=htons(49165), 
sin_addr=inet_addr(10.1.11.3)}, 16) = -1 EPERM (Operation not permitted)

This was with all iptables rules unloaded (so no OUTPUT -j DENY) and
apparmor profiles torn down.

I also noticed the following dmesgs appearing at roughly similar times
to the tftp transfers getting stuck (although not coinciding exactly
with the stall):

[70325.516724] IPv6 header not found

The error pointed to ipvs (which I am using on the same host as an IPv4 NAT 
loadbalancer):
http://archive.linuxvirtualserver.org/html/lvs-devel/2012-08/msg00018.html
http://comments.gmane.org/gmane.comp.linux.lvs.devel/3614

I then tore down the ipvs rules (service keepalived stop) and unloaded
the modules (rmmod ip_vs_rr ip_vs), and the issue resolved itself - the
stalled dnsmasq-tftp transfer resumed!

This seems to be reproducible, i.e. modprobing ip_vs and starting
keepalived will cause dnsmasq-tftp to stall again, and
stopping/unloading will resume.

This seems to happen reproducibly on boot with -32 and -30. This does
NOT seem to happen with 3.13.0-29 which I was using up until now.

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

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: biosdevname (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] Lspci.txt

[Tero Marttila]

apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/1349768/+attachment/4165028/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] CurrentDmesg.txt

[Tero Marttila]

apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/1349768/+attachment/4165025/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] Re: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors

[Tero Marttila]

apport information

** Tags added: apport-collected trusty

** Description changed:

  I have an Ubuntu 14.04 host that I am using as both a keepalived/ipvs
  loadbalancer and dnsmasq server for pxebooting servers.
  
  After updating linux-image 3.13.0-29.53 - 3.13.0-32.57 I noticed that
  dnsmasq-tftp stopped working. pxeboot clients would hang on the Loading
  /linux TFTP transfer, with the transfer stalling roughly ~1000
  blocks into the transfer:
  
  10:30:51.011728 IP 10.1.1.2.43540  10.1.12.1.49165: UDP, length 1412
  10:30:51.011924 IP 10.1.12.1.49165  10.1.1.2.43540: UDP, length 4
  10:30:51.012012 IP 10.1.1.2.43540  10.1.12.1.49165: UDP, length 1412
  10:30:51.012183 IP 10.1.12.1.49165  10.1.1.2.43540: UDP, length 4
  
  stracing dnsmasq I noticed something very odd: sendto() on the
  socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) would suddenly start
  persistently returning EPERM in mid-transfer, even when dnsmasq
  continued to periodically retry:
  
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 1 (in [17], 
left {0, 249834})
  recvfrom(17, \0\4\3\352, 4096, 0, NULL, NULL) = 4
  lseek(16, 1410816, SEEK_SET) = 1410816
  read(16, 
\25\306\345f\2{\r\4)W\276\32\336q\252_\230q\213\341U\354\25\374k7\243\32\221X+\v...,
 1408) = 1408
  sendto(17, 
\0\3\3\353\25\306\345f\2{\r\4)W\276\32\336q\252_\230q\213\341U\354\25\374k7\243\32...,
 1412, 0, {sa_family=AF_INET, sin_port=htons(49165), 
sin_addr=inet_addr(10.1.11.3)}, 16) = 1412
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 1 (in [17], 
left {0, 249839})
  recvfrom(17, \0\4\3\353, 4096, 0, NULL, NULL) = 4
  lseek(16, 1412224, SEEK_SET) = 1412224
  read(16, *\360 
C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277\221\\\307\372...,
 1408) = 1408
  sendto(17, \0\3\3\354*\360 
C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277..., 
1412, 0, {sa_family=AF_INET, sin_port=htons(49165), 
sin_addr=inet_addr(10.1.11.3)}, 16) = -1 EPERM (Operation not permitted)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout)
  lseek(16, 1412224, SEEK_SET) = 1412224
  read(16, *\360 
C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277\221\\\307\372...,
 1408) = 1408
  sendto(17, \0\3\3\354*\360 
C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277..., 
1412, 0, {sa_family=AF_INET, sin_port=htons(49165), 
sin_addr=inet_addr(10.1.11.3)}, 16) = -1 EPERM (Operation not permitted)
  
  This was with all iptables rules unloaded (so no OUTPUT -j DENY) and
  apparmor profiles torn down.
  
  I also noticed the following dmesgs appearing at roughly similar times
  to the tftp transfers getting stuck (although not coinciding exactly
  with the stall):
  
  [70325.516724] IPv6 header not found
  
  The error pointed to ipvs (which I am using on the same host as an IPv4 NAT 
loadbalancer):
  http://archive.linuxvirtualserver.org/html/lvs-devel/2012-08/msg00018.html
  http://comments.gmane.org/gmane.comp.linux.lvs.devel/3614
  
  I then tore down the ipvs rules (service keepalived stop) and unloaded
  the modules (rmmod ip_vs_rr ip_vs), and the issue resolved itself - the
  stalled dnsmasq-tftp transfer resumed!
  
  This seems to be reproducible, i.e. modprobing ip_vs and starting
  keepalived will cause dnsmasq-tftp to stall again, and
  stopping/unloading will resume.
  
- This seems to happen reproducibly on boot with -32 and -30. This does
- NOT seem to happen with 3.13.0-29 which I was using up until now.
+ This seems to happen reproducibly on boot with -32 and -30. This does NOT 
seem to happen with 3.13.0-29 which I was using up until now.
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Jul 29 13:43 seq
+  crw-rw 1 root audio 116, 33 Jul 29 13:43 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.14.1-0ubuntu3.2
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=/dev/mapper/catcp2-swap
+ InstallationDate: Installed on 2014-06-03 (56 days ago)
+ InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
+ MachineType: Dell Inc. PowerEdge R410
+ Package: 

[Bug 1349768] UdevDb.txt

[Tero Marttila]

apport information

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/1349768/+attachment/4165033/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] ProcCpuinfo.txt

[Tero Marttila]

apport information

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/1349768/+attachment/4165030/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] Dependencies.txt

[Tero Marttila]

apport information

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/1349768/+attachment/4165026/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] Re: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors

[Tero Marttila]

Reported apport-collect information against package linux-
image-3.13.0-32-generic, reproducing the dnsmasq-tftp issue with a
remote client pxebooting and stalling.

The CurrentDmesg contains the symptom message at 1214.740931

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] ProcModules.txt

[Tero Marttila]

apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1349768/+attachment/4165032/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] WifiSyslog.txt

[Tero Marttila]

apport information

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/1349768/+attachment/4165035/+files/WifiSyslog.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] ProcInterrupts.txt

[Tero Marttila]

apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1349768/+attachment/4165031/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] Lsusb.txt

[Tero Marttila]

apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1349768/+attachment/4165029/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] IwConfig.txt

[Tero Marttila]

apport information

** Attachment added: IwConfig.txt
   
https://bugs.launchpad.net/bugs/1349768/+attachment/4165027/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349768] UdevLog.txt

[Tero Marttila]

apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1349768/+attachment/4165034/+files/UdevLog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768

Title:
  kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
  sendto() EPERM errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1343245] Re: virt-aa-helper does not whitelist actual source dev='...' paths for domain disk type='volume'

[Tero Marttila]

A type=VIR_STORAGE_TYPE_VOLUME disk is not necessarily a
virStoragePoolDefPtr.type=VIR_STORAGE_POOL_LOGICAL, and may or may not
involve a /dev/... path; the logic for translating them into src paths
seems to be somewhere like qemuTranslateDiskSourcePool() via
virStorageVolGetPath(), and seems to also depend on the mode?

AFAICT the significant difference is between the persistent config and
the live running config for a domain; the later contains the actual
translated source dev='...' / paths directly. Ideally virt-aa-helper
would be based off of the translated config?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1343245

Title:
  virt-aa-helper does not whitelist actual source dev='...' paths for
  domain disk type='volume'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1343245] [NEW] virt-aa-helper does not whitelist actual source dev='...' paths for domain disk type='volume'

[Tero Marttila]

Public bug reported:

Release:14.04
Package:libvirt-bin
Version: 1.2.2-0ubuntu13.1.1

For a normal block-based LVM disk definition

disk type='block' device='disk'
  driver name='qemu' type='raw'/
  source dev='/dev/host-vg/guest.img'/
  target dev='vda' bus='virtio'/
/disk

virt-aa-helper will generate /dev/dm-X rw rules in the
/etc/apparmor.d/libvirt/libvirt-*.files

  /dev/dm-10 rw,

However, using a storage pool:

pool type='logical'
  namelvm/name
  source
namehost-vg/name
  /source
  target
path/dev/host-vg/path
  /target
/pool

to create the volume:

volume
nameguest.img/name
capacity/capacity
/volume

and attempting to use the equivalent:

disk type='volume' device='disk'
  driver name='qemu' type='raw'/
  source pool='lvm' volume='guest.img'/
  target dev='vda' bus='virtio'/
  address type='pci' domain='0x' bus='0x00' slot='0x04' 
function='0x0'/
/disk

Results in the following with `virsh start guest`

error: Failed to start domain guest
error: internal error: process exited while connecting to monitor: 
qemu-system-x86_64: -drive 
file=/dev/host-vg/guest.img,if=none,id=drive-virtio-disk0,format=raw: could not 
open disk image /dev/host-vg/guest.img: Could not open 
'/dev/host-vg/guest.img': Permission denied

And:

[164096.938448] type=1400 audit(1405596016.664:100): apparmor=DENIED 
operation=open profile=libvirt-fdd84027-cb8e-42d5-bca1-a662871d97bb 
name=/dev/dm-10 pid=26835 comm=qemu-system-x86 requested_mask=r 
denied_mask=r fsuid=109 ouid=109
[164096.938472] type=1400 audit(1405596016.664:101): apparmor=DENIED 
operation=open profile=libvirt-fdd84027-cb8e-42d5-bca1-a662871d97bb 
name=/dev/dm-10 pid=26835 comm=qemu-system-x86 requested_mask=r 
denied_mask=r fsuid=109 ouid=109
[164096.938515] type=1400 audit(1405596016.664:102): apparmor=DENIED 
operation=open profile=libvirt-fdd84027-cb8e-42d5-bca1-a662871d97bb 
name=/dev/dm-10 pid=26835 comm=qemu-system-x86 requested_mask=rw 
denied_mask=rw fsuid=109 ouid=109

The apparmor libvirt-*.files does not contain any /dev/dm-* rules.

I'm not familar enough with the virAppArmorSecurityDriver code to know if the 
load_profile() call to virDomainDefFormat() will give the persistent or live 
xml config, but when testing with virt-aa-helper manually, feeding it the 
inactive config (i.e. `virsh dumpxml` while the domain is stopped) will cause 
get_files() to call virDomainDiskDefForeachPath() with a virDomainDiskDefPtr of 
type=VIR_DOMAIN_DISK_TYPE_VOLUME and src=NULL, so it never iters over the disk. 
I suspect that virt-aa-helper should instead be fed the active config, i.e. one 
where the disk type='volume' has been fed through 
qemuTranslateDiskSourcePool() to resolve it into the actual disk 
type='block'source dev='...' //disk?

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

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1343245

Title:
  virt-aa-helper does not whitelist actual source dev='...' paths for
  domain disk type='volume'

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1343245] [NEW] virt-aa-helper does not whitelist actual source dev='...' paths for domain disk type='volume'

[Tero Marttila]

Public bug reported:

Release:14.04
Package:libvirt-bin
Version: 1.2.2-0ubuntu13.1.1

For a normal block-based LVM disk definition

disk type='block' device='disk'
  driver name='qemu' type='raw'/
  source dev='/dev/host-vg/guest.img'/
  target dev='vda' bus='virtio'/
/disk

virt-aa-helper will generate /dev/dm-X rw rules in the
/etc/apparmor.d/libvirt/libvirt-*.files

  /dev/dm-10 rw,

However, using a storage pool:

pool type='logical'
  namelvm/name
  source
namehost-vg/name
  /source
  target
path/dev/host-vg/path
  /target
/pool

to create the volume:

volume
nameguest.img/name
capacity/capacity
/volume

and attempting to use the equivalent:

disk type='volume' device='disk'
  driver name='qemu' type='raw'/
  source pool='lvm' volume='guest.img'/
  target dev='vda' bus='virtio'/
  address type='pci' domain='0x' bus='0x00' slot='0x04' 
function='0x0'/
/disk

Results in the following with `virsh start guest`

error: Failed to start domain guest
error: internal error: process exited while connecting to monitor: 
qemu-system-x86_64: -drive 
file=/dev/host-vg/guest.img,if=none,id=drive-virtio-disk0,format=raw: could not 
open disk image /dev/host-vg/guest.img: Could not open 
'/dev/host-vg/guest.img': Permission denied

And:

[164096.938448] type=1400 audit(1405596016.664:100): apparmor=DENIED 
operation=open profile=libvirt-fdd84027-cb8e-42d5-bca1-a662871d97bb 
name=/dev/dm-10 pid=26835 comm=qemu-system-x86 requested_mask=r 
denied_mask=r fsuid=109 ouid=109
[164096.938472] type=1400 audit(1405596016.664:101): apparmor=DENIED 
operation=open profile=libvirt-fdd84027-cb8e-42d5-bca1-a662871d97bb 
name=/dev/dm-10 pid=26835 comm=qemu-system-x86 requested_mask=r 
denied_mask=r fsuid=109 ouid=109
[164096.938515] type=1400 audit(1405596016.664:102): apparmor=DENIED 
operation=open profile=libvirt-fdd84027-cb8e-42d5-bca1-a662871d97bb 
name=/dev/dm-10 pid=26835 comm=qemu-system-x86 requested_mask=rw 
denied_mask=rw fsuid=109 ouid=109

The apparmor libvirt-*.files does not contain any /dev/dm-* rules.

I'm not familar enough with the virAppArmorSecurityDriver code to know if the 
load_profile() call to virDomainDefFormat() will give the persistent or live 
xml config, but when testing with virt-aa-helper manually, feeding it the 
inactive config (i.e. `virsh dumpxml` while the domain is stopped) will cause 
get_files() to call virDomainDiskDefForeachPath() with a virDomainDiskDefPtr of 
type=VIR_DOMAIN_DISK_TYPE_VOLUME and src=NULL, so it never iters over the disk. 
I suspect that virt-aa-helper should instead be fed the active config, i.e. one 
where the disk type='volume' has been fed through 
qemuTranslateDiskSourcePool() to resolve it into the actual disk 
type='block'source dev='...' //disk?

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1343245

Title:
  virt-aa-helper does not whitelist actual source dev='...' paths for
  domain disk type='volume'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1322568] Re: nova interface-attach fails

[Tero Marttila]

Any chance of getting this fix into trusty?

Fixing this up by hand via /etc/apparmor.d/libvirt/TEMPLATE is possible
for pre-existing domain profiles, but involves shutting down the domain
etc. Is there any better way?

  virsh shutdown foobar
  sudo /usr/lib/libvirt/virt-aa-helper --delete --uuid libvirt-$(virsh domuuid 
foobar)
  virsh dumpxml foobar | sudo /usr/lib/libvirt/virt-aa-helper --create --uuid 
libvirt-$(virsh domuuid foobar)
  virsh start foobar

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322568

Title:
  nova interface-attach fails

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1330252] Re: ubuntu 14.04 ltsp-server /etc/X11/Xsession.d/40-ltsp-server DESKTOP_SESSION breaks lubuntu-desktop login

[Tero Marttila]

Note that in Ubuntu 12.04 (where Lubuntu LTSP works) the lubuntu-
default-settings 0.27 package ships a different
/usr/share/xsessions/Lubuntu.desktop :

Exec=/usr/bin/startlubuntu

The /etc/X11/Xsession.d/... files seem to be the same.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1330252

Title:
  ubuntu 14.04 ltsp-server /etc/X11/Xsession.d/40-ltsp-server
  DESKTOP_SESSION breaks lubuntu-desktop login

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1330252] [NEW] ubuntu 14.04 ltsp-server /etc/X11/Xsession.d/40-ltsp-server DESKTOP_SESSION breaks lubuntu-desktop login

[Tero Marttila]

Public bug reported:

DistroRelease: Ubuntu 14.04
Package: ltsp-server 5.5.1-1ubuntu2


The following code in `/etc/X11/Xsession.d/40-ltsp-server` causes issues with 
dash `export ...` expansion as regards LP#139097 :

DESKTOP_SESSION=$(echo $1 | sed s/gnome-session --session=//g)

Given the following `/usr/share/xsessions/Lubuntu.desktop` :

Exec=/usr/bin/lxsession -s Lubuntu -e LXDE

Attempting to login to the Lubuntu desktop session results in the
following error in `~/.xsession-errors` :

/etc/X11/Xsession: 6: export: -s: bad variable name

Presumeably due to the `DESKTOP_SESSION` being set above breaking in
`/etc/X11/Xsession.d/70gconfd_path-on-session` :

export MANDATORY_PATH=${GCONF_PREFIX}/${DESKTOP_SESSION}.mandatory.path
export DEFAULTS_PATH=${GCONF_PREFIX}/${DESKTOP_SESSION}.default.path

Commenting out the culprit DESKTOP_SESSION=... assignment lets me login
to the Lubuntu desktop again.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1330252

Title:
  ubuntu 14.04 ltsp-server /etc/X11/Xsession.d/40-ltsp-server
  DESKTOP_SESSION breaks lubuntu-desktop login

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1281964] Re: Firmware iwlwifi-7260-7.ucode is missing

[Tero Marttila]

Do you have the updated linux-firmware 1.79.10 installed? Confirm with
`dpkg -L linux-firmware | grep iwlwifi-7260-7.ucode`?

$ dpkg -l linux-firmware
||/ Name   VersionDescription
+++-==-==-
ii  linux-firmware 1.79.10Firmware for Linux kernel drivers

$ dpkg -L linux-firmware | grep iwlwifi-7260-7.ucode
/lib/firmware/iwlwifi-7260-7.ucode

The workaroud in this bug report is going to be completely version-
specific, and will have to be repeated for every kernel upgrade until
you switch over to the firmware included in the newer linux-firmware.

FWIW it just rebooted into the updated 3.11.0-18-generic and my Intel
7260 works fine. I never applied the workaround in this bug report.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281964

Title:
  Firmware iwlwifi-7260-7.ucode is missing

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1285727] [NEW] linux-image-3.11.0-17-generic omits iwlwifi-7260-7.ucode firmware

[Tero Marttila]

Public bug reported:

The latest precise-updates linux-image seems to omit the required
iwlwifi-7260-7.ucode firwmware

03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)

$ dpkg -l linux-image-3.11*
ii  linux-image-3.11.0-14-generic  3.11.0-14.21~precise1
  Linux kernel image for version 3.11.0 on 64 bit x86 SMP
ii  linux-image-3.11.0-15-generic  3.11.0-15.25~precise1
  Linux kernel image for version 3.11.0 on 64 bit x86 SMP
ii  linux-image-3.11.0-17-generic  3.11.0-17.31~precise1
  Linux kernel image for version 3.11.0 on 64 bit x86 SMP

$ dpkg -S iwlwifi-7260
linux-image-3.11.0-15-generic: 
/lib/firmware/3.11.0-15-generic/iwlwifi-7260-7.ucode
linux-image-3.11.0-14-generic: 
/lib/firmware/3.11.0-14-generic/iwlwifi-7260-7.ucode

$ dmesg # failed iwlwifi on latest 3.11.0-17 (no iw phy present)
[0.00] Linux version 3.11.0-17-generic (buildd@toyol) (gcc version 
4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #31~precise1-Ubuntu SMP Tue Feb 4 
21:25:43 UTC 2014 (Ubuntu 3.11
.0-17.31~precise1-generic 3.11.10.3)
...
[   17.770121] iwlwifi :03:00.0: request for firmware file 
'iwlwifi-7260-7.ucode' failed.
[   17.770127] iwlwifi :03:00.0: no suitable firmware found!

$ dmesg # succesfful 3.11.0-15 boot (iw phy0 present)
[0.00] Linux version 3.11.0-15-generic (buildd@allspice) (gcc version 
4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #25~precise1-Ubuntu SMP Thu Jan 30 
17:39:31 UTC 2014 (Ubuntu 3.11.0-15.25~precise1-generic 3.11.10)
...
[   49.046204] iwlwifi :03:00.0: loaded firmware version 22.0.7.0 op_mode 
iwlmvm
[   49.120558] iwlwifi :03:00.0: Detected Intel(R) Dual Band Wireless AC 
7260, REV=0x144

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1285727

Title:
  linux-image-3.11.0-17-generic omits iwlwifi-7260-7.ucode firmware

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1285727] Re: linux-image-3.11.0-17-generic omits iwlwifi-7260-7.ucode firmware

[Tero Marttila]

*** This bug is a duplicate of bug 1281964 ***
https://bugs.launchpad.net/bugs/1281964

Workaroud: Boot with Shift held down, and select older 3.11.0-15 linux
version in grub.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1285727

Title:
  linux-image-3.11.0-17-generic omits iwlwifi-7260-7.ucode firmware

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1285727] Re: linux-image-3.11.0-17-generic omits iwlwifi-7260-7.ucode firmware

[Tero Marttila]

*** This bug is a duplicate of bug 1281964 ***
https://bugs.launchpad.net/bugs/1281964

Confirm that updating to linux-firmware 1.79.10 from precise-updates
resolves this, giving me a functional phy0 on 3.11.0-17-generic.

$ apt-cache policy linux-firmware
linux-firmware:
  Installed: 1.79.10
  Candidate: 1.79.10
  Version table:
 *** 1.79.10 0
500 http://fi.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 
Packages
100 /var/lib/dpkg/status
 1.79 0
500 http://fi.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
$ dmesg | grep iw
[   21.900148] iwlwifi :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[   21.900534] iwlwifi :03:00.0: irq 62 for MSI/MSI-X
[   22.597407] iwlwifi :03:00.0: loaded firmware version 22.1.7.0 op_mode 
iwlmvm
[   23.421577] iwlwifi :03:00.0: Detected Intel(R) Dual Band Wireless AC 
7260, REV=0x144
[   23.421915] iwlwifi :03:00.0: L1 Enabled; Disabling L0S
[   23.422293] iwlwifi :03:00.0: L1 Enabled; Disabling L0S
[   23.733900] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[   26.266427] iwlwifi :03:00.0: L1 Enabled; Disabling L0S
[   26.266872] iwlwifi :03:00.0: L1 Enabled; Disabling L0S

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1285727

Title:
  linux-image-3.11.0-17-generic omits iwlwifi-7260-7.ucode firmware

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 133606] Re: f-spot 0.3.5 crashes while exporting folder

[Tero Marttila]

I can confirm this happening with F-Spot 0.3.5-0ubuntu2 on Ubuntu 7.04
with libexif12 0.6.13-5ubuntu0.2 and libmono0 1.2.3.1-1ubuntu1. F-Spot
crashes to the desktop when exporting a vertically taken photo (as
opposed to horizontal) to a Folder (web gallery or files only) with the
Autorotate option on. No I/O errors in syslog/dmesg, and no image files
are created, but if exported as a web gallery, the HTML/style/script
files are.

** Changed in: f-spot (Ubuntu)
   Status: Invalid = Confirmed

-- 
f-spot 0.3.5 crashes while exporting folder
https://bugs.launchpad.net/bugs/133606
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 133606] Re: f-spot 0.3.5 crashes while exporting folder

[Tero Marttila]

I have researched this further, and it turns out that the bug is in libexif - 
the exiftran utility uses 1.7g of mem and segfaults when trying to process 
these photos (taken with an Olympus E-510 camera), and The GIMP cannot open 
them: 
 https://bugs.launchpad.net/ubuntu/+source/libexif/+bug/117189 
 
https://sourceforge.net/tracker/index.php?func=detailaid=1599114group_id=12272atid=112272

If I compile libexif 0.6.16 from source and run f-spot with that lib,
the exporting works fine. I suspect this is simply an issue with libexif
0.6.13 not being able to handle the Exif data in the JPEG files created
by this model of camera.

** Changed in: f-spot (Ubuntu)
   Status: Confirmed = Invalid

-- 
f-spot 0.3.5 crashes while exporting folder
https://bugs.launchpad.net/bugs/133606
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs