[Touch-packages] [Bug 1577575] Re: NFS share does not mount on boot using fstab

[Kelvin Middleton]

Have been plagued with this for a while now, noted that Debian tracked a
similar issue (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746358)
but the solution/scripting is different for ubuntu but could this be
ported?  Problem presents on every boot, I use the linux-bridge package
to create a bridge for a kvm/qemu guest networks.  NFS server is in my
local network one physical hop from the client.

/etc/fstab contains:
192.168.1.2: /nfs/mnt/blacknas  nfs defaults 0  0

Boot hangs for the 91 seconds trying to mount this, fails, completes the
boot to desktop.  Once on the desktop a 'sudo mount -a' the successfully
mounts the nfs share.  No issues on shutdown.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1577575

Title:
  NFS share does not mount on boot using fstab

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  What I expected to happen?

  I want an NFS share to be mounted on startup using

  
  192.168.178.66:/media/captainplanet/7EF8B26FF8B22575/ 
/media/captainplanet/banane/ nfs rw 0 0

  What happened instead?

  It does not mount on startup. Systemd waits 91sec instead and finally
  starts after failing.

  I can successfully mount the NFS share with

  sudo mount 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575
  /media/captainplanet/banane/

  When I try to shutdown Xubuntu it hangs forever. Unmounting the NFS
  share manually before shutdown fixes the second problem.

  
  Do you need more information?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May  2 23:10:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (10 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20DM003XUK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=eece9973-0430-4a60-9291-9a994782bf86 ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JFET44WW(1.21)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20DM003XUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJFET44WW(1.21):bd08/26/2015:svnLENOVO:pn20DM003XUK:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DM003XUK:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DM003XUK
  dmi.product.version: ThinkPad S3 Yoga 14
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1428121] Re: Intel HDMI Audio not working with IOMMU enabled

[Kelvin Middleton]

Glad to see this bug report isn't completely dead.

Can confirm too that the problem still exists with kernel
4.2.0-27-generic with the same motherboard as per the original bug
report.

The attached is a recent extract from dmesg outputs...I use vfio
passthrough for GFX on a Windows guest.  You can see from the timestamps
that I start the guest at 21:02:44 and at around 21:26:07 I get some
DMAR faults pertain to device at 00:02.0.  This device is the Intel
IGD...

lspci -s 00:02.0
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)

...not sure if this is related to the HDMI audio or not.

What I can say is that I have to boot the host with "intel_iommu=on".
If I change this to =on,igfx_off then my syslog fills with constant
complaints about DMAR for another device I use in passthrough which
works perfectly with =on, this device is a DVB-S2 device.  If I use
=igfx_off this stops IOMMU so I can not longer passthrough PCI devices
but presto the HDMI audio now works?!



** Attachment added: "dmesg-extract-intel_iommu-on"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1428121/+attachment/4573164/+files/dmesg-extract-intel_iommu-on

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1428121

Title:
  Intel HDMI Audio not working with IOMMU enabled

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an
  Nvidia GTX 650.

  Host uses Intel IGD for video and HDMI audio out.

  When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on'
  HDMI audio no longer functions although the device and modules seem to
  load and I cannot locate any error messages.  In this configuration
  IOMMU functions as expected and I can successfully pass the Nvidia
  card through to a KVM guest using VFIO.

  As per this
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug
  report and the linked bugzilla thread I attempted to use kernel flag
  'intel_iommu=on,igfx_off'.  This resolves the HDMI audio out but
  breaks IOMMU as in VGA pass through generates DMA errors.

  I'm running from a clean installation of 14.10 with no modifications
  to the kernel or kvm, qemu, libvirt or virt-manager.

  In either scenario above the analogue audio out continues to function,
  I haven't tested the optical out as I have no hardware to do so.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kelvin 3468 F pulseaudio
   /dev/snd/controlC3:  kelvin 3468 F pulseaudio
   /dev/snd/controlC0:  kelvin 3468 F pulseaudio
   /dev/snd/controlC1:  kelvin 3468 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar  4 12:53:17 2015
  HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931
  InstallationDate: Installed on 2015-02-26 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout 
intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1428121/+subscriptions

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

[Touch-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage

[Kelvin Middleton]

Have had the memory leak issues since moved to 15.04, not seen any
consistent/persistent CPU spikes though...

Services affected are consistently unity-panel-service and hud-service.

I run a virtual host and daily use Chrome and virt-viewer/virt-
manager/bash.  Don't use GIMP and don't have any other indicators
running beyond the Chrome popups for Hangouts and browser extensions
i.e. Sabnzbd.

The only problem I repeated encounter is the main title bar where my
user name, date/time and indicators are freezes, I notice this as the
time is obviously wrong.  I just kill the 2 offending services which
have grabbed most of the memory and everything reverts to normal.

** Attachment added: Screen short of memory leakage
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1199877/+attachment/4428754/+files/Screenshot%20from%202015-07-14%2014%3A05%3A37.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1199877

Title:
  unity-panel-service memory leak and 100% CPU usage

Status in Application Menu Indicator:
  Fix Released
Status in Application Menu Indicator 13.10 series:
  Fix Released
Status in The Ubuntu Power Consumption Project:
  Fix Released
Status in Unity:
  Invalid
Status in Ubuntu:
  Fix Released
Status in indicator-appmenu package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid
Status in The Saucy Salamander:
  Fix Released
Status in indicator-appmenu source package in Saucy:
  Fix Released

Bug description:
  Impact: high CPU/memory usage from unity-panel-service

  Test case:

  Open a large image in the GIMP and activate a lot of items from the
  global menu. Using shortcuts is enough and faster to reproduce this
  bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity-
  panel-service increases steadily and it uses a lot of CPU shortly
  after activating the menu items in a short time.

  Regression potential: check that the menus are stable/working as they
  should

  -
  Just going about my business on Ubuntu Raring amd64 on an x230 and I heard 
the fan kick into action.  top showed me that unity-panel-service was consuming 
all the free cycles on one of my CPUs.  I killed it before my machine 
overheated, so I didn't attach a debugger to see why it was totally pegging out 
a  CPU.

  I'm not sure if this adds any context, but I was using a LibreOffice
  spreadsheet and I could not insert a table because the menu had lost
  it's mind, and then I observed the overly loaded CPU a very short
  while after that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+subscriptions

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

[Touch-packages] [Bug 1430103] [NEW] package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured

[Kelvin Del Monte]

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

Public bug reported:

package language-pack-gnome-en-base 1:14.04+20150219 failed to
install/upgrade: package language-pack-gnome-en-base is already
installed and configured

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: language-pack-gnome-en-base 1:14.04+20150219
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.14.1-0ubuntu3.7
AptdaemonVersion: 1.1.1-1ubuntu5.1
Architecture: amd64
Date: Mon Mar  9 21:26:02 2015
DuplicateSignature: 
package:language-pack-gnome-en-base:1:14.04+20150219:package 
language-pack-gnome-en-base is already installed and configured
ErrorMessage: package language-pack-gnome-en-base is already installed and 
configured
InstallationDate: Installed on 2015-02-08 (29 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
PackageArchitecture: all
SourcePackage: language-pack-gnome-en-base
Title: package language-pack-gnome-en-base 1:14.04+20150219 failed to 
install/upgrade: package language-pack-gnome-en-base is already installed and 
configured
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: language-pack-gnome-en-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: already-installed amd64 apport-package trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-gnome-en-
base in Ubuntu.
https://bugs.launchpad.net/bugs/1430103

Title:
  package language-pack-gnome-en-base 1:14.04+20150219 failed to
  install/upgrade: package language-pack-gnome-en-base is already
  installed and configured

Status in language-pack-gnome-en-base package in Ubuntu:
  New

Bug description:
  package language-pack-gnome-en-base 1:14.04+20150219 failed to
  install/upgrade: package language-pack-gnome-en-base is already
  installed and configured

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: language-pack-gnome-en-base 1:14.04+20150219
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  AptdaemonVersion: 1.1.1-1ubuntu5.1
  Architecture: amd64
  Date: Mon Mar  9 21:26:02 2015
  DuplicateSignature: 
package:language-pack-gnome-en-base:1:14.04+20150219:package 
language-pack-gnome-en-base is already installed and configured
  ErrorMessage: package language-pack-gnome-en-base is already installed and 
configured
  InstallationDate: Installed on 2015-02-08 (29 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: language-pack-gnome-en-base
  Title: package language-pack-gnome-en-base 1:14.04+20150219 failed to 
install/upgrade: package language-pack-gnome-en-base is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en-base/+bug/1430103/+subscriptions

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

[Touch-packages] [Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions

[Kelvin]

I experienced it on a fresh Ubuntu 14.04 LTS installation on an HP
Stream 11. Tried the #26 patch but the dmesg errors are still there.
Kernel is 3.13.0-45-generic #74-Ubuntu SMP.


** Attachment added: sudo udevadm test /block/mmcblk0rpmb
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+attachment/4319153/+files/udevadm-mmcblk0rpmb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1333140

Title:
  Fix udev rules to consider mmc rpmb partitions

Status in systemd package in Ubuntu:
  Fix Committed
Status in udisks package in Ubuntu:
  Triaged

Bug description:
  As per JEDEC 4.5 spec for eMMC devices,
  There is a new partitions as part of eMMC storage devices it self. (Further 
details please refer eMMC spec)

  *In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
  with mmcblkXrpmb if device expresses it support of RPMB.

  Issues observed:

  issue 1:
  RPMB (Replay Protected Memory Block), A signed access to a Replay Protected 
Memory Block is provided. This function provides means for the system to store 
data to the specific memory area in an authenticated and replay protected 
manner.
  In that case, any read/write access to this partition device will report 
errors.

  issue 2:
  The by-path, line is wrongly mapping to platform-sdhci-tegra.1  - 
mmcblk2rpmb were as
  it should be platform-sdhci-tegra.1  - mmcblk2

  ls -l /dev/disk/by-path/
  total 0
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.1 - 
../../mmcblk2rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.1-part1 - 
../../mmcblk2p1
  lrwxrwxrwx 1 root root 13 Jan  3  2000 platform-sdhci-tegra.2 - ../../mmcblk1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.2-part1 - 
../../mmcblk1p1
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.3 - 
../../mmcblk0rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part1 - 
../../mmcblk0p1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part2 - 
../../mmcblk0p2

  We have locally resolved in our platform in this file 60-persistent-
  storage.rules

  For issue 1: (with this rule)
  # skip block read for partitions of type rpmb
  KERNEL==mmcblk[0-9]rpmb, SUBSYSTEM==block, GOTO=persistent_storage_end

  For issue 2:
  ENV{DEVTYPE}==disk, ENV{ID_PATH}==?*, KERNEL==mmcblk[0-9]rpmb, 
SYMLINK+=disk/by-path/$env{ID_PATH}-rpmb
  ENV{DEVTYPE}==disk, ENV{ID_PATH}==?*, KERNEL!=mmcblk[0-9]rpmb, 
SYMLINK+=disk/by-path/$env{ID_PATH}

  Please consider this issues fix in next udev release .

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

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