[Kernel-packages] [Bug 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start

[Brian Burch]

Same messages for me with 16.04 beta2, running with bluez 5.37-0ubuntu5
on 4.4.0-15-generic amd64 kernel. Running on Asus T300 CHI notepad with
bluetooth keyboard/touchpad docking unit. It pairs OK, but connection
comes up briefly and then drops again.

bluetoothctl log extract follows:
[CHG] Device 08:62:66:DB:F3:AA Paired: yes
Pairing successful
[CHG] Device 08:62:66:DB:F3:AA Connected: no
[CHG] Device 08:62:66:DB:F3:AA Class: 0x0005c0
[CHG] Device 08:62:66:DB:F3:AA Connected: yes
[CHG] Device 08:62:66:DB:F3:AA Icon is nil

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

Title:
  15:10: bluetoothd reports "Not enough handles to register service" at
  start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

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

[Kernel-packages] [Bug 1561729] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe A FIFO underrun

[Daniel Basten]

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

i read #1554613 by now and think this bug is a dublicate

** This bug has been marked a duplicate of bug 1554613
   screen flickering on XPS13 9350

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe
  A FIFO underrun

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hey Guys,

  i am encountering some random screen flickering after i launched
  google-chrome. this persists even after closing chrome. it is like the
  screen wents black for a fracture of a second.

  when it happens dmesg reports:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe
  A FIFO underrun

  I am currently on Ubuntu 1604 Daily:

  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  PS: It is a Dell XPS 13 9530 with no external display attached.
  The internal display is an FHD one

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

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

[Kernel-packages] [Bug 1564475] Re: 128M is not enough for kdump on s390 LPARs

[Louis Bouchard]

***WARNING***

KDUMP_CMDLINE_APPEND is used to add parameters to the command used by
kexec to reboot when the system crashes. Adding crashkernel= there is
useless and will most likely be ignored.

The crashkernel= parameter has to be made available on the system when
it first boots so having it in /etc/zipl.conf it the proper way to do
it.

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

Title:
  128M is not enough for kdump on s390 LPARs

Status in makedumpfile package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Michael Holzheu  - 2016-03-31 
10:59:26 ==
  With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs 
crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt").

  On z/VM guests 128M seems to be sufficient.

  One reason on our test LPAR is that a lot of devices are attached (see
  attachment "lscss_lpar.txt") which are not required for kdump but
  consume a lot of memory because the s390 CIO layer allocates data
  structures in the kernel for those devices.

  We can disable the devices by using the "cio_ignore=" kernel parameter
  in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD
  0.0.e934 for /var/crash, we added the following line to disable the
  devices:

  KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1
  cio_ignore=all,!condev,!0.0.e934"

  For more information on the "cio_ignore=" kernel parameter see:
  https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO

  Even with "cio_ignore=" we still get out-of-memory with
  "crashkernel=128M".

  With "crashkernel=196M" and "cio_ignore=" we are able to create a dump
  on our LPAR. We currently do not know why kdump with "cio_ignore=" on
  LPAR consumes more memory than on z/VM guests.

  == Comment: #1 - Michael Holzheu  - 2016-03-31 
11:03:15 ==
  Kernel messages of kdump out-of-memory crash on LPAR with many devices 
without cio_ignore parameter and 128M crashkernel memory.

  == Comment: #2 - Michael Holzheu  - 2016-03-31 
11:04:10 ==
  Output of lscss showing all attached (not online) devices on the LPAR.

  == Comment: #3 - Michael Holzheu  - 2016-03-31 
11:07:35 ==
  To solve this issue our recommendation is:

  1) Increase "crashkernel=" default to 196M on Ubuntu for s390.

  2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used
  to decrease memory consumption for kdump on systems with many devices
  that are not required for kdump.

  The most user friendly solution would be to automatically determine
  the required kdump devices and set the correct "cio_ignore=" kernel
  parameter. But this is not trivial, because it can be difficult to
  find out the required devices for stacked setups like LVM or for
  network dump.

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

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

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Emsi]

Which ubuntu version are you using for tests? 14.04?  How about vss daemon, kvp 
daemon? Have you installed them? Which version and package have you used? Are 
you using crash consistent or application consistent backups (with VSS support 
in the Guest Linux)?
I'd like to independently repeat your tests to confirm the results yet I need 
to replicate your environment.

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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

[Kernel-packages] [Bug 1564759] [NEW] [i915_bpo] Disable RC6 on SKL GT3 & GT4

[Timo Aaltonen]

Public bug reported:

Runtime power management causes GPU hangs on SKL GT3 & GT4 ("Iris" &
"Iris Pro"), so disable it until the bug(s) are fixed.

** Affects: dri
 Importance: Unknown
 Status: Unknown

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Timo Aaltonen (tjaalton)
 Status: Triaged

** Affects: linux (Ubuntu Xenial)
 Importance: High
 Assignee: Timo Aaltonen (tjaalton)
 Status: Triaged

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

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

** Also affects: dri via
   https://bugs.freedesktop.org/show_bug.cgi?id=94161
   Importance: Unknown
   Status: Unknown

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

Title:
  [i915_bpo] Disable RC6 on SKL GT3 & GT4

Status in DRI:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Runtime power management causes GPU hangs on SKL GT3 & GT4 ("Iris" &
  "Iris Pro"), so disable it until the bug(s) are fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1564759/+subscriptions

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

[Kernel-packages] [Bug 1558701] bantam (i386) - tests ran: 167, failed: 12

[Brad Figg]

tests ran: 167, failed: 12;
  
http://kernel.ubuntu.com/testing/3.19.0-58.64/bantam__3.19.0-58.64__2016-04-01_01-44-00/results-index.html

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

Title:
  linux: 3.19.0-58.64 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

Bug description:
  This bug is for tracking the 3.19.0-58.64 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Thursday, 17. March 2016 17:37 UTC
  kernel-stable-Promote-to-proposed-end:Thursday, 17. March 2016 18:02 UTC
  kernel-stable-Prepare-package-end:Friday, 18. March 2016 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 18. March 2016 04:03 UTC
  kernel-stable-Verification-testing-start:Friday, 18. March 2016 13:01 UTC
  kernel-stable-Certification-testing-start:Friday, 18. March 2016 13:01 UTC
  kernel-stable-Security-signoff-start:Friday, 18. March 2016 13:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 18. March 2016 13:01 UTC
  kernel-stable-Security-signoff-end:Saturday, 19. March 2016 14:41 UTC
  kernel-stable-Regression-testing-end:Monday, 28. March 2016 15:02 UTC
  kernel-stable-Verification-testing-end:Tuesday, 29. March 2016 15:01 UTC
  kernel-stable-phase:CopyToUpdates
  kernel-stable-Promote-to-updates-start:Thursday, 31. March 2016 20:56 UTC
  kernel-stable-phase-changed:Thursday, 31. March 2016 20:56 UTC
  kernel-stable-Certification-testing-end:Thursday, 31. March 2016 20:56 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1558701/+subscriptions

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

[Kernel-packages] [Bug 1547838] Re: ADMtek ADM8511 "Pegasus II" USB Ethernet causes oops

[a1291762]

The good news is that I have identified the commit that breaks my
system. It is 313a58e487ab3eb80e7e1f9baddc75968288aad9 (the first of 3
commits to the pegasus driver). I have attached the bisect log in case
it's interesting.

Here's some notes on my process...

The bisecting was entirely in commits that lacked the debian directories
so I used the patches from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.9-saucy/ to restore them. Most of the time, the kernel
asked about configs that were new. I just accepted the defaults.

My build/run process went like this.

# remove old kernels
COLUMNS= dpkg -l | awk '/linux-image/{print $2}' | grep -v '3\.19' | grep -v 
lts | xargs sudo apt-get -y remove --purge
# backup old packages
mv ../*.deb ../old
# so the patch works
rm -rf debian*
# depending on the previous test
git bisect good/bad
# so I can build
for file in ../3.9/*.patch; do patch -p1 < $file; done
# set the version to something useful (3.9.0-0+lrx)
vi debian.master/changelog
chmod a+x debian/rules debian/scripts/* debian/scripts/misc/*
fakeroot debian/rules clean
fakeroot debian/rules binary-headers binary-generic
sudo dpkg -i ../linux-image-*
sudo reboot
# test by booting from the kernel, plugging in the USB dongle and pinging the 
gateway


** Attachment added: "bisect.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547838/+attachment/4619231/+files/bisect.log

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

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

Title:
  ADMtek ADM8511 "Pegasus II" USB Ethernet causes oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a rather old USB ethernet adapter. It worked fine for me with
  older distributions (including Ubuntu 10.04). I noticed it causing
  problems after upgrading to 14.04 and stopped using it as a result
  (since I needed reliable USB ethernet for work). I was also not
  completely sure if it was this device causing the issue or interplay
  between this device and a number of other networking USB devices that
  were used at work.

  I'd like to use this ethernet adapter at home but the machine is
  running Ubuntu 14.04 and the issue persists.

  I have collected some information that might help. I'm happy to try
  more things to collect information if that will help.

  I'm running Ubuntu 14.04 server 64-bit. I just rebooted so I'm running
  the latest updates.

  I was told to run ubuntu-bug linux but I'm not sure how much useful
  stuff is included in that. I'm including the kernel log which has some
  bad stuff happening in it. Not sure if it got the system-freezing oops
  or just the errors leading up to that.

  It feels like a bug in the driver that corrupts memory because I see
  issues with network-related things (eg. a ping crashed, but the next
  ping didn't), leading to a full-system freeze.

  This machine has been happily running Ubuntu for a looong time (though
  it was only recently upgraded to Ubuntu 14.04, previously it had been
  running 10.04). I have not had stability issues with the machine but
  plugging in the USB Ethernet reliably makes it freeze within minutes.
  The symptoms also match what I saw on my machine at work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Sat Feb 20 21:23:29 2016
  InstallationDate: Installed on 2015-12-31 (50 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.19.0-49-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0cffa533-89ec-44d8-b5f9-6efe69c1b955
  InstallationDate: Installed on 2015-12-31 (67 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Hewlett-Packard HP EliteBook 8530w
  Package: linux (not installed)
  ProcFB: 0 nouvea

[Kernel-packages] [Bug 1564475] Re: 128M is not enough for kdump on s390 LPARs

[Dimitri John Ledkov]

"Ok, if we go with the 128M default our current assumption is that on
all LPARs kdump for Ubuntu will fail." -> well, that doesn't sound good
either, cause then essentially we take away 128M of RAM away without
actually providing anything to the LPAR installations =(

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

Title:
  128M is not enough for kdump on s390 LPARs

Status in makedumpfile package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Michael Holzheu  - 2016-03-31 
10:59:26 ==
  With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs 
crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt").

  On z/VM guests 128M seems to be sufficient.

  One reason on our test LPAR is that a lot of devices are attached (see
  attachment "lscss_lpar.txt") which are not required for kdump but
  consume a lot of memory because the s390 CIO layer allocates data
  structures in the kernel for those devices.

  We can disable the devices by using the "cio_ignore=" kernel parameter
  in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD
  0.0.e934 for /var/crash, we added the following line to disable the
  devices:

  KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1
  cio_ignore=all,!condev,!0.0.e934"

  For more information on the "cio_ignore=" kernel parameter see:
  https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO

  Even with "cio_ignore=" we still get out-of-memory with
  "crashkernel=128M".

  With "crashkernel=196M" and "cio_ignore=" we are able to create a dump
  on our LPAR. We currently do not know why kdump with "cio_ignore=" on
  LPAR consumes more memory than on z/VM guests.

  == Comment: #1 - Michael Holzheu  - 2016-03-31 
11:03:15 ==
  Kernel messages of kdump out-of-memory crash on LPAR with many devices 
without cio_ignore parameter and 128M crashkernel memory.

  == Comment: #2 - Michael Holzheu  - 2016-03-31 
11:04:10 ==
  Output of lscss showing all attached (not online) devices on the LPAR.

  == Comment: #3 - Michael Holzheu  - 2016-03-31 
11:07:35 ==
  To solve this issue our recommendation is:

  1) Increase "crashkernel=" default to 196M on Ubuntu for s390.

  2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used
  to decrease memory consumption for kdump on systems with many devices
  that are not required for kdump.

  The most user friendly solution would be to automatically determine
  the required kdump devices and set the correct "cio_ignore=" kernel
  parameter. But this is not trivial, because it can be difficult to
  find out the required devices for stacked setups like LVM or for
  network dump.

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

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

[Kernel-packages] [Bug 1564793] [NEW] package linux-image-4.4.0-16-generic 4.4.0-16.32 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Ralf Hildebrandt]

Public bug reported:

During upgrade from trusty to xenial, thing went amiss

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-16-generic 4.4.0-16.32
ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
Uname: Linux 3.19.0-56-generic x86_64
AlsaDevices:
 ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD 
cannot be preloaded (cannot open shared object file): ignored.
 total 0
 crw-rw 1 root audio 116,  1 Apr  1 10:26 seq
 crw-rw 1 root audio 116, 33 Apr  1 10:26 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1: ERROR: ld.so: object 
'/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
Date: Fri Apr  1 10:36:08 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
HibernationDevice: RESUME=UUID=9a552e9f-593f-42f9-8b03-74c062d5fb3b
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD 
cannot be preloaded (cannot open shared object file): ignored.
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: FUJITSU D3401-H1
PciMultimedia:
 
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic 
root=UUID=fd827598-4b67-4b7a-9374-cb789aa7ad8a ro nomodeset intel_pstate=enable 
nomdmonddf nomdmonisw
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
Title: package linux-image-4.4.0-16-generic 4.4.0-16.32 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
UpgradeStatus: Upgraded to xenial on 2016-04-01 (0 days ago)
dmi.bios.date: 11/25/2015
dmi.bios.vendor: FUJITSU // American Megatrends Inc.
dmi.bios.version: V5.0.0.11 R1.7.0.SR.2 for D3401-H1x
dmi.board.name: D3401-H1
dmi.board.vendor: FUJITSU
dmi.board.version: S26361-D3401-H1
dmi.chassis.type: 3
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.11R1.7.0.SR.2forD3401-H1x:bd11/25/2015:svnFUJITSU:pnD3401-H1:pvr:rvnFUJITSU:rnD3401-H1:rvrS26361-D3401-H1:cvnFUJITSU:ct3:cvr:
dmi.product.name: D3401-H1
dmi.sys.vendor: FUJITSU

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-4.4.0-16-generic 4.4.0-16.32 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  New

Bug description:
  During upgrade from trusty to xenial, thing went amiss

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  Uname: Linux 3.19.0-56-generic x86_64
  AlsaDevices:
   ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD 
cannot be preloaded (cannot open shared object file): ignored.
   total 0
   crw-rw 1 root audio 116,  1 Apr  1 10:26 seq
   crw-rw 1 root audio 116, 33 Apr  1 10:26 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1: ERROR: ld.so: object 
'/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
  Date: Fri Apr  1 10:36:08 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=9a552e9f-593f-42f9-8b03-74c062d5fb3b
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD 
cannot be preloaded (cannot open shared object file): ignored.
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU D3401-H1
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic 
root=UUID=fd827598-4b67-4b7a-9374-cb789aa7ad8a ro nomodeset intel_pstate=enable 
nomdmonddf nomdmonisw
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu2
  RfKill: Error: [Errno 2] No such file o

[Kernel-packages] [Bug 1564759] Re: [i915_bpo] Disable RC6 on SKL GT3 & GT4

[Bug Watch Updater]

Launchpad has imported 23 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=94161.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-02-15T16:34:18+00:00 Mikael-w wrote:

Created attachment 121772
GPU crash dump

I have experienced GPU hangs with all kernels after 4.3.

I'm running a MS Surface Pro 4.

Feb 15 17:27:22 hat kernel: [  478.912402] [drm] stuck on render ring
Feb 15 17:27:22 hat kernel: [  478.913345] [drm] GPU HANG: ecode 
9:0:0x85df9fff, in gnome-shell [1956], reason: Ring hung, action: reset
Feb 15 17:27:22 hat kernel: [  478.913357] [drm] GPU hangs can indicate a bug 
anywhere in the entire gfx stack, including userspace.
Feb 15 17:27:22 hat kernel: [  478.913361] [drm] Please file a _new_ bug report 
on bugs.freedesktop.org against DRI -> DRM/Intel
Feb 15 17:27:22 hat kernel: [  478.913364] [drm] drm/i915 developers can then 
reassign to the right component if it's not a kernel issue.
Feb 15 17:27:22 hat kernel: [  478.913367] [drm] The gpu crash dump is required 
to analyze gpu hangs, so please always attach it.
Feb 15 17:27:22 hat kernel: [  478.913371] [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
Feb 15 17:27:22 hat kernel: [  478.915833] drm/i915: Resetting chip after gpu 
hang
Feb 15 17:27:24 hat kernel: [  480.901312] [drm] RC6 on

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/0


On 2016-02-16T11:10:18+00:00 Christophe Prigent wrote:

Hi Mikael,
Which GPU is it: m3 Intel HD graphics 515 / i5 Intel HD graphics 520 / i7 Intel 
Iris graphics?
Which steps are causing the GPU hang?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/1


On 2016-02-16T11:56:42+00:00 Mikael-w wrote:

It's Intel Iris (HD 540).

It's hard to say what exactly is causing it. Once it was caused by a
"tail -f /var/log/syslog" scrolling text in Gnome Terminal. Another time
it was caused by a web page being displayed in Firefox. A third time it
was caused by switching workspace in Gnome Shell.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/2


On 2016-02-16T12:01:27+00:00 Mikael-w wrote:

I should add that these hangs happen every other minute when things
change on the screen.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/3


On 2016-02-20T18:09:12+00:00 Ivan Giuliani wrote:

I seem to be affected by this as well (same GPU, on an XPS 13" (2016)).
Tried any kernel from 4.3 to 4.5 on Ubuntu, including the drm-intel-next
kernel (4.5.0-997-generic).

A workaround is to add i915.enable_rc6=0 to the kernel boot parameters.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/4


On 2016-02-24T21:43:24+00:00 Mikael-w wrote:

I have now tried this with the latest drm-intel kernel and the newest
skl-dcm firmware (1.26).  My libdrm is 2.4.67.

The problem still persists.

A deterministic way to provoke the hang is to run glmark2
(github.com/glmark2).

I can confirm that if I give i915.enable_rc6=0 as a kernel option, the
problem disappears.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/5


On 2016-03-01T20:42:51+00:00 Chris Wilson wrote:

*** Bug 94029 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/6


On 2016-03-02T21:04:46+00:00 Chris Wilson wrote:

To attempt to distinguish another source of bugs, does
intel_pstate=disable make any difference?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/7


On 2016-03-02T21:43:13+00:00 Mikael-w wrote:

(In reply to Chris Wilson from comment #7)
> To attempt to distinguish another source of bugs, does intel_pstate=disable
> make any difference?

Replacing i915.enable_rc6=0 with intel_pstate=disable reintroduces the
GPU crashes.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564759/comments/8


On 2016-03-10T12:50:29+00:00 Chris Wilson wrote:

*** Bug 94462 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.n

[Kernel-packages] [Bug 1564793] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  package linux-image-4.4.0-16-generic 4.4.0-16.32 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During upgrade from trusty to xenial, thing went amiss

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  Uname: Linux 3.19.0-56-generic x86_64
  AlsaDevices:
   ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD 
cannot be preloaded (cannot open shared object file): ignored.
   total 0
   crw-rw 1 root audio 116,  1 Apr  1 10:26 seq
   crw-rw 1 root audio 116, 33 Apr  1 10:26 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1: ERROR: ld.so: object 
'/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
  Date: Fri Apr  1 10:36:08 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=9a552e9f-593f-42f9-8b03-74c062d5fb3b
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD 
cannot be preloaded (cannot open shared object file): ignored.
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU D3401-H1
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic 
root=UUID=fd827598-4b67-4b7a-9374-cb789aa7ad8a ro nomodeset intel_pstate=enable 
nomdmonddf nomdmonisw
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  Title: package linux-image-4.4.0-16-generic 4.4.0-16.32 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-04-01 (0 days ago)
  dmi.bios.date: 11/25/2015
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.11 R1.7.0.SR.2 for D3401-H1x
  dmi.board.name: D3401-H1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3401-H1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.11R1.7.0.SR.2forD3401-H1x:bd11/25/2015:svnFUJITSU:pnD3401-H1:pvr:rvnFUJITSU:rnD3401-H1:rvrS26361-D3401-H1:cvnFUJITSU:ct3:cvr:
  dmi.product.name: D3401-H1
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1564807] [NEW] nfs causes guest system to get stuck

[Rune Philosof]

Public bug reported:

Host OS Ubuntu 15.10
Guest OS Ubuntu 14.10

Using Vagrant with nfs and Virtualbox and static ip on the private
network.

It is working perfectly except that after having suspended the host OS,
the entire guest OS will be unusable. This does not happen when using
the normal virtualbox shared folders.

It's not only the nfs shared folder that is unusable, the entire OS is
hanging. Even syslog does not seem to see much action. This is syslog on
the guest, from waking up until vagrant halt is completed.

Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 1000 
Mbps Full Duplex, Flow Control: RX
Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not 
responding, still trying
Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not 
responding, still trying
Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" 
x-pid="753" x-info="http://www.rsyslog.com";] exiting on signal 15.

When I try to ssh to the guest system I the motd and last login: ..., but 
nothing more, it just hangs.
If I was already logged in the guest system through ssh then that session is 
unresponsive (after pressing enter).

How can this be fixed?
How should I debug it?

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

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

Title:
  nfs causes guest system to get stuck

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Host OS Ubuntu 15.10
  Guest OS Ubuntu 14.10

  Using Vagrant with nfs and Virtualbox and static ip on the private
  network.

  It is working perfectly except that after having suspended the host
  OS, the entire guest OS will be unusable. This does not happen when
  using the normal virtualbox shared folders.

  It's not only the nfs shared folder that is unusable, the entire OS is
  hanging. Even syslog does not seem to see much action. This is syslog
  on the guest, from waking up until vagrant halt is completed.

  Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 
1000 Mbps Full Duplex, Flow Control: RX
  Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not 
responding, still trying
  Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not 
responding, still trying
  Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
  Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on 
signal 15.

  When I try to ssh to the guest system I the motd and last login: ..., but 
nothing more, it just hangs.
  If I was already logged in the guest system through ssh then that session is 
unresponsive (after pressing enter).

  How can this be fixed?
  How should I debug it?

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

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

[Kernel-packages] [Bug 1564807] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1564807

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  nfs causes guest system to get stuck

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Host OS Ubuntu 15.10
  Guest OS Ubuntu 14.10

  Using Vagrant with nfs and Virtualbox and static ip on the private
  network.

  It is working perfectly except that after having suspended the host
  OS, the entire guest OS will be unusable. This does not happen when
  using the normal virtualbox shared folders.

  It's not only the nfs shared folder that is unusable, the entire OS is
  hanging. Even syslog does not seem to see much action. This is syslog
  on the guest, from waking up until vagrant halt is completed.

  Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 
1000 Mbps Full Duplex, Flow Control: RX
  Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not 
responding, still trying
  Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not 
responding, still trying
  Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
  Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on 
signal 15.

  When I try to ssh to the guest system I the motd and last login: ..., but 
nothing more, it just hangs.
  If I was already logged in the guest system through ssh then that session is 
unresponsive (after pressing enter).

  How can this be fixed?
  How should I debug it?

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

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

[Kernel-packages] [Bug 1561830] Re: Hard disk writes fail in 16.04 daily on nForce 430

[Stephen Worthington]

After quite a bit of messing around, I found a way to test kernels on
16.04 beta properly.  I installed my HightPoint Rocket 622A eSATA card
and plugged the Samsung HD103UJ drive into it using a long eSATA to SATA
cable.  That allowed me to boot from my 16.04 daily DVD and do an
install to the HD103UJ without any problems.  I did an apt-get upgrade
and got the latest kernel (4.4.0-16-generic), and also installed the
mainline kernels 4.4.0-040400-generic and 4.5.0-040500-generic.  Then I
checked the other drive installed on the box (Seagate ST31000528AS, used
for testing Windows 10) and found that its 200 Gibyte NTFS data
partition was almost empty, so I resized it and created a tiny EXT2
partition for Grub2, a 50 Gibyte EXT4 partition for intalling to, and a
10 Gibyte swap partition, all at the end of that drive.  Then I rebooted
to the 16.04 beta DVD and installed to the Seagate drive.  Then I
rebooted to the install on the Samsung drive and ran update-grub, to get
the install on the Seagate drive bootable from the Grub on the Samsung
drive.  Then I booted using the Samsung drive and selected the new 16.04
beta install on the Seagate drive to boot.  It did, to my surprise, as
the Seagate drive was on the motherboard nForce 430 SATA controller.  So
I then mounted the Samsung drive from the booted Seagate install, and
tried the test dd commands, and they also all worked with no errors.

So the first conclusion I have come to is that the bug seems to only be
triggered by the Samsung HD103UJ drive when it is on a motherboard
nForce 430 SATA port.  It does not happen when that drive is on the
Rocket 622A's Marvell SATA port.  And the bug also does not happen when
using the Seagate ST31000528AS drive on a motherboard nForce 430 SATA
port.  It seems to require that particular drive on that particular SATA
controller, and using the standard 16.04 beta kernels, for the bug to
occur.

To prevent problems with the swapper using the swap partition on the
Samsung HD103UJ drive, I edited fstab on both 16.04 installs to use the
new swap partition on the Seagate ST31000528AS drive only.

The next test was to shut down and move the Samsung HD103UJ to its
motherboard nForce 430 SATA port, then reboot using the Grub on that
drive to run the install on the Seagate ST31000528AS drive.  Again, the
boot worked, which I expected as there should be little or no writing to
the Samsung drive during that boot process.  I mounted the Samsung drive
16.04 install partition from the Seagate install, and ran the test dd
commands.  I was again surprised that they worked without errors - I
would have expected that a boot of the 16.04 beta standard kernels from
that drive would work the same as a boot of the 16.04 standard kernel
from my install DVD, and would fail when writing to the Samsung HD103UJ
drive when it is on the motherboard nForce 430 SATA port.

The next test was to reboot to the 16.04 beta partition on the Samsung
HD103UJ drive.  As expected, that boot failed badly, and I had to use
the PC's reset button to restart it, after which I rebooted to the 16.04
beta install on the Seagate ST31000528AS drive again and used that
install to run fsck to repair the 16.04 beta install partition on the
Samsung HD103UJ drive.   The fsck check showed two errors that needed
fixing, where the number of blocks and number of inodes were both wrong.
Once fsck had fixed the partition, I mounted it and looked at the
kern.log file from the bad boot.  It looked normal up to a certain
point, after which it was corrupt - I think it had a block full of
zeroes.  So it looks like as soon as the bug hits, no more successful
log writes occur, which makes it difficult to debug.

I do have a serial port on this motherboard, so I looked to see if I
could use that to get debug information during a bad boot, but it turned
out that I do not have the necessary serial cross-over cable to plug the
motherboard's serial port into any of my other PCs' serial ports.  Last
time I needed a cross-over cable, I must have borrowed one from work,
and unfortunately that is no longer possible.

The next test I ran was to boot the Samsung HD103UJ install on the
nForce 430 port, but using Grub to select the mainline
4.4.0-040400-generic kernel.  That also failed badly in exactly the sam
manner, so I rebooted and repaired the partition again, ready for the
final test.

For the last test, I rebooted to the Samsung HD103UJ install on the
nForce 430 port using the mainline 4.5.0-040500-generic kernel, and it
booted without errors.

So it looks like whatever bug is causing this problem has already been
fixed in the upstream 4.5.0 kernels.  However, if 16.04 is going to be
released using 4.4.0 kernels, I hope the fix for this bug can be
backported before 16.04 is released.  Are there any more tests I should
do to help with this?  Is there any more information I can provide?

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

[Kernel-packages] [Bug 1564815] [NEW] Precise update to 3.2.79 stable release

[Luis Henriques]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 3.2.79 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 3.2.79 stable release shall be
applied:

Revert "crypto: algif_skcipher - Do not dereference ctx without socket lock"
crypto: {blk,giv}cipher: Set has_setkey
iommu/vt-d: Fix 64-bit accesses to 32-bit DMAR_GSTS_REG
wext: fix message delay/ordering
cfg80211/wext: fix message ordering
mac80211: fix use of uninitialised values in RX aggregation
nfs: fix nfs_size_to_loff_t
drm/i915: fix error path in intel_setup_gmbus()
cifs: fix erroneous return value
s390/dasd: prevent incorrect length error under z/VM after PAV changes
s390/dasd: fix refcount for PAV reassignment
libata: fix HDIO_GET_32BIT ioctl
xen/pciback: Check PF instead of VF for PCI_COMMAND_MEMORY
xen/pciback: Save the number of MSI-X entries to be copied later.
xen/pcifront: Fix mysterious crashes when NUMA locality information was 
extracted.
ALSA: seq: Fix leak of pool buffer at concurrent writes
tracepoints: Do not trace when cpu is offline
tracing: Fix freak link error caused by branch tracer
ALSA: seq: Fix double port list deletion
af_unix: Don't set err in unix_stream_read_generic unless there was an error
af_unix: Guard against other == sk in unix_dgram_sendmsg
x86, extable: Remove open-coded exception table entries in 
arch/x86/lib/copy_user_nocache_64.S
x86/uaccess/64: Make the __copy_user_nocache() assembly code more readable
x86/uaccess/64: Handle the caching of 4-byte nocache copies properly in 
__copy_user_nocache()
usb: dwc3: Fix assignment of EP transfer resources
net/mlx4_en: Count HW buffer overrun only once
USB: option: add support for SIM7100E
USB: cp210x: add IDs for GE B650V3 and B850V3 boards
USB: option: add "4G LTE usb-modem U901"
Adding Intel Lewisburg device IDs for SATA
ext4: fix bh->b_state corruption
kernel/resource.c: fix muxed resource handling in __request_region()
can: ems_usb: Fix possible tx overflow
mac80211: minstrel_ht: set default tx aggregation timeout to 0
sunrpc/cache: fix off-by-one in qword_get()
KVM: async_pf: do not warn on page allocation failures
Revert "jffs2: Fix lock acquisition order bug in jffs2_write_begin"
jffs2: Fix page lock / f->sem deadlock
Fix directory hardlinks from deleted directories
libata: Align ata_device's id on a cacheline
ipr: Fix out-of-bounds null overwrite
ipr: Fix regression when loading firmware
mm: thp: fix SMP race condition between THP page fault and MADV_DONTNEED
hpfs: don't truncate the file when delete fails
ALSA: timer: Fix broken compat timer user status ioctl
ALSA: hdspm: Fix wrong boolean ctl value accesses
ALSA: hdsp: Fix wrong boolean ctl value accesses
USB: cp210x: Add ID for Parrot NMEA GPS Flight Recorder
ASoC: wm8958: Fix enum ctl accesses in a wrong type
ASoC: wm8994: Fix enum ctl accesses in a wrong type
USB: serial: option: add support for Quectel UC20
ALSA: seq: oss: Don't drain at closing a client
PM / sleep / x86: Fix crash on graph trace through x86 suspend
IB/core: Use GRH when the path hop-limit > 0
mld, igmp: Fix reserved tailroom calculation
MIPS: traps: Fix SIGFPE information leak from `do_ov' and `do_trap_or_bp'
ubi: Fix out of bounds write in volume update code
Revert "drm/radeon: call hpd_irq_event on resume"
s390/mm: four page table levels vs. fork
Input: aiptek - fix crash on detecting device without endpoints
include/linux/poison.h: fix LIST_POISON{1,2} offset
HID: usbhid: fix recursive deadlock
Linux 3.2.79

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

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 3.2.79 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each 

[Kernel-packages] [Bug 1564815] Re: Precise update to 3.2.79 stable release

[Luis Henriques]

** Changed in: linux (Ubuntu Precise)
   Status: New => Fix Committed

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

Title:
  Precise update to 3.2.79 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Precise:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 3.2.79 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 3.2.79 stable release shall be
  applied:

  Revert "crypto: algif_skcipher - Do not dereference ctx without socket lock"
  crypto: {blk,giv}cipher: Set has_setkey
  iommu/vt-d: Fix 64-bit accesses to 32-bit DMAR_GSTS_REG
  wext: fix message delay/ordering
  cfg80211/wext: fix message ordering
  mac80211: fix use of uninitialised values in RX aggregation
  nfs: fix nfs_size_to_loff_t
  drm/i915: fix error path in intel_setup_gmbus()
  cifs: fix erroneous return value
  s390/dasd: prevent incorrect length error under z/VM after PAV changes
  s390/dasd: fix refcount for PAV reassignment
  libata: fix HDIO_GET_32BIT ioctl
  xen/pciback: Check PF instead of VF for PCI_COMMAND_MEMORY
  xen/pciback: Save the number of MSI-X entries to be copied later.
  xen/pcifront: Fix mysterious crashes when NUMA locality information was 
extracted.
  ALSA: seq: Fix leak of pool buffer at concurrent writes
  tracepoints: Do not trace when cpu is offline
  tracing: Fix freak link error caused by branch tracer
  ALSA: seq: Fix double port list deletion
  af_unix: Don't set err in unix_stream_read_generic unless there was an error
  af_unix: Guard against other == sk in unix_dgram_sendmsg
  x86, extable: Remove open-coded exception table entries in 
arch/x86/lib/copy_user_nocache_64.S
  x86/uaccess/64: Make the __copy_user_nocache() assembly code more readable
  x86/uaccess/64: Handle the caching of 4-byte nocache copies properly in 
__copy_user_nocache()
  usb: dwc3: Fix assignment of EP transfer resources
  net/mlx4_en: Count HW buffer overrun only once
  USB: option: add support for SIM7100E
  USB: cp210x: add IDs for GE B650V3 and B850V3 boards
  USB: option: add "4G LTE usb-modem U901"
  Adding Intel Lewisburg device IDs for SATA
  ext4: fix bh->b_state corruption
  kernel/resource.c: fix muxed resource handling in __request_region()
  can: ems_usb: Fix possible tx overflow
  mac80211: minstrel_ht: set default tx aggregation timeout to 0
  sunrpc/cache: fix off-by-one in qword_get()
  KVM: async_pf: do not warn on page allocation failures
  Revert "jffs2: Fix lock acquisition order bug in jffs2_write_begin"
  jffs2: Fix page lock / f->sem deadlock
  Fix directory hardlinks from deleted directories
  libata: Align ata_device's id on a cacheline
  ipr: Fix out-of-bounds null overwrite
  ipr: Fix regression when loading firmware
  mm: thp: fix SMP race condition between THP page fault and MADV_DONTNEED
  hpfs: don't truncate the file when delete fails
  ALSA: timer: Fix broken compat timer user status ioctl
  ALSA: hdspm: Fix wrong boolean ctl value accesses
  ALSA: hdsp: Fix wrong boolean ctl value accesses
  USB: cp210x: Add ID for Parrot NMEA GPS Flight Recorder
  ASoC: wm8958: Fix enum ctl accesses in a wrong type
  ASoC: wm8994: Fix enum ctl accesses in a wrong type
  USB: serial: option: add support for Quectel UC20
  ALSA: seq: oss: Don't drain at closing a client
  PM / sleep / x86: Fix crash on graph trace through x86 suspend
  IB/core: Use GRH when the path hop-limit > 0
  mld, igmp: Fix reserved tailroom calculation
  MIPS: traps: Fix SIGFPE information leak from `do_ov' and `do_trap_or_bp'
  ubi: Fix out of bounds write in volume update code
  Revert "drm/radeon: call hpd_irq_event on resume"
  s390/mm: four page table levels vs. fork
  Input: aiptek - fix crash on detecting device without endpoints
  include/linux/poison.h: fix LIST_POISON{1,2} offset
  HID: usbhid: fix recursive deadlock
  Linux 3.2.79

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

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

[Kernel-packages] [Bug 1555786] Re: [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

[DorinBarboiu]

Tested with upstream kernel 4.0  and 4.0.9 on a 32 bit VM. With both of this 
version VM booted as expected without issues.
Also I tested with upstream kernel 4.1  and VM did not boot. I expect that the 
issue is present for first time in upstream kernel 4.1.

My question is:  Could you please, help me to bisect this issue?

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

Title:
  [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We identified that at least ubuntu (let's take 15.10) does not boot if
  installed in the 32bit architecture, and using the linux-next upstream
  kernel 4.5 on it. This has been seen on other distributions as well.

  We took both the official linux-next branch from kernel.org and the one from 
kernel.ubuntu.com v4.5-rc7.
  For the compilation process we went either with the 4.2 kernel config file 
from the installed running kernel, and also built the config separately. 
  No errors have been encountered during the build or install process of the 
4.5 kernel, however at boot, the VM will just hang.
  There are no call traces or messages at boot to show any pottential issue.

  Have you seen this on your end when testing the 32bit build?
  Attaching the full serial log for reference, however I don't see any errors 
in the kernel boot process.

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

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

[Kernel-packages] [Bug 1546603] Re: Bluetooth mouse connects but doesn't work

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bluez (Ubuntu)
   Status: New => Confirmed

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

Title:
  Bluetooth mouse connects but doesn't work

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth mouse that I can get to connect via the gnome
  bluetooth settings panel, but even after it's connected it doesn't
  move the pointer or register any clicks.

  the following shows up in the journal :

  $ $ journalctl -b 0 |grep bluetooth
  Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth daemon 5.36
  Feb 17 07:18:22 spiny bluetoothd[1009]: Starting SDP server
  Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth management interface 1.10 
initialized
  Feb 17 07:18:22 spiny bluetoothd[1009]: Failed to obtain handles for "Service 
Changed" characteristic
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Error adding Link Loss service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Current Time Service could not be 
registered
  Feb 17 07:18:22 spiny bluetoothd[1009]: gatt-time-server: Input/output error 
(5)
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Sap driver initialization failed.
  Feb 17 07:18:22 spiny bluetoothd[1009]: sap-server: Operation not permitted 
(1)
  Feb 17 07:18:22 spiny NetworkManager[1062]:   Loaded device plugin: 
NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
  Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 
path=/MediaEndpoint/A2DPSource
  Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 
path=/MediaEndpoint/A2DPSink
  Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 
path=/MediaEndpoint/A2DPSource
  Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 
path=/MediaEndpoint/A2DPSink
  Feb 17 07:18:42 spiny bluetoothd[1009]: RFCOMM server failed for Headset 
Voice gateway: rfcomm_bind: Address already in use (98)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher gufw (missing 
desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
language-selector (missing desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)
  Feb 17 07:19:00 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 
'str != NULL' failed
  Feb 17 07:19:01 spiny bluetoothd[1009]: No cache for F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x000c for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x001b for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x003f for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Report Map read failed: Attribute 
requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Protocol Mode characteristic read 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: HID Information read failed: 
Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 

[Kernel-packages] [Bug 1483054] Re: macbook air wakes up immediately after suspend

[Greg Whiteley]

Hope this is of some use to diagnose the issue further.  I have the
following observations from a Macbook pro that wakes immediately after
suspend

```
cat /proc/acpi/wakeup DeviceS-state   Status   Sysfs node
P0P2  S3*disabled  pci::00:01.0
GFX0  S3*disabled  pci::01:00.0
PEG1  S3*disabled  pci::00:01.1
ECS4*disabled  platform:PNP0C09:00
GMUX  S3*disabled  pnp:00:03
HDEF  S3*disabled  pci::00:1b.0
RP03  S3*disabled  pci::00:1c.2
ARPT  S4*disabled  pci::03:00.0
RP04  S3*disabled  pci::00:1c.3
RP05  S3*disabled  pci::00:1c.4
XHC1  S3*enabled   pci::00:14.0
ADP1  S4*disabled  platform:ACPI0003:00
LID0  S4*enabled   platform:PNP0C0D:00
```

Note two ACPI wakeup sources - XHC1 and LID0 (XHC1 is USB - eg for
external keyboards, LID0 is the lid).  Now you can toggle their wakeup
powers as follows

```
$ echo XHC1 | sudo tee /proc/acpi/wakeup
$ echo LID0 | sudo tee /proc/acpi/wakeup
```

(Note with both XHC1 and LID disabled only the power-button will wake
you)

What I see: (Truth table)

  XHC1   |  LID0  |   Result
  disabled   |  disabled  |   Stays asleep until power button hit
  enabled|  enabled   |   Wake after 2.5 seconds sleep
  enabled|  disabled  |   Wake after 2.5 seconds sleep
  disabled   |  enabled   |   Stays asleep if lid left closed
 ||   Wake after 2.5 seconds sleep if lid left open

>From this I infer that something on the USB bus (or the USB driver
itself) is causing a wake - I can't find a culprit device on the bus.

>From this I also infer that the lid state reports regularly - ie its not
the act of opening that causes the wake its the fact of it being open.

So by disabling just XHC1 I lose keyboard wake, but I can close the lid
to sleep and open it to wake which is just about workable for me.

Hope that helps

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

Title:
  macbook air wakes up immediately after suspend

Status in linux package in Ubuntu:
  Confirmed
Status in Debian:
  New

Bug description:
  Whenever I put to suspend my macbook air, ubuntu 15.04 wakes up in a few 
seconds.
  I've found no way to avoid this.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-25-generic 3.19.0-25.26
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lev2001 F pulseaudio
   /dev/snd/controlC1:  lev2001 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Aug  9 23:30:10 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=918f68f1-76f0-4449-b89c-3f9685f8ce63
  InstallationDate: Installed on 2015-07-16 (24 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0291 Apple, Inc. 
   Bus 001 Device 006: ID 05ac:828f Apple, Inc. 
   Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookAir7,2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed 
root=UUID=660bcd07-b8a9-4231-b479-e35018d66612 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-25-generic N/A
   linux-backports-modules-3.19.0-25-generic  N/A
   linux-firmware 1.143.2
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA71.88Z.0166.B06.1506051511
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-937CB26E2E02BB01
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir7,2
  dmi.chassis.asset.tag: Chassis Board Asset Tag#
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-937CB26E2E02BB01
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA71.88Z.0166.B06.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookAir7,2:pvr1.0:rvnAppleInc.:rnMac-937CB26E2E02BB01:rvrMacBookAir7,2:cvnAppleInc.:ct9:cvrMac-937CB26E2E02BB01:
  dmi.product.name: MacBookAir7,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1564475] Re: 128M is not enough for kdump on s390 LPARs

[Louis Bouchard]

If there is a way to determine if we're on a zVM or Lpar, I could adapt
kdump-config to add the appropriate crashkernel=value pair in
/etc/zipl.conf and re-run zipl upon installation of kdump-tools, which
is required in order to capture a dump.

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

Title:
  128M is not enough for kdump on s390 LPARs

Status in makedumpfile package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Michael Holzheu  - 2016-03-31 
10:59:26 ==
  With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs 
crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt").

  On z/VM guests 128M seems to be sufficient.

  One reason on our test LPAR is that a lot of devices are attached (see
  attachment "lscss_lpar.txt") which are not required for kdump but
  consume a lot of memory because the s390 CIO layer allocates data
  structures in the kernel for those devices.

  We can disable the devices by using the "cio_ignore=" kernel parameter
  in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD
  0.0.e934 for /var/crash, we added the following line to disable the
  devices:

  KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1
  cio_ignore=all,!condev,!0.0.e934"

  For more information on the "cio_ignore=" kernel parameter see:
  https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO

  Even with "cio_ignore=" we still get out-of-memory with
  "crashkernel=128M".

  With "crashkernel=196M" and "cio_ignore=" we are able to create a dump
  on our LPAR. We currently do not know why kdump with "cio_ignore=" on
  LPAR consumes more memory than on z/VM guests.

  == Comment: #1 - Michael Holzheu  - 2016-03-31 
11:03:15 ==
  Kernel messages of kdump out-of-memory crash on LPAR with many devices 
without cio_ignore parameter and 128M crashkernel memory.

  == Comment: #2 - Michael Holzheu  - 2016-03-31 
11:04:10 ==
  Output of lscss showing all attached (not online) devices on the LPAR.

  == Comment: #3 - Michael Holzheu  - 2016-03-31 
11:07:35 ==
  To solve this issue our recommendation is:

  1) Increase "crashkernel=" default to 196M on Ubuntu for s390.

  2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used
  to decrease memory consumption for kdump on systems with many devices
  that are not required for kdump.

  The most user friendly solution would be to automatically determine
  the required kdump devices and set the correct "cio_ignore=" kernel
  parameter. But this is not trivial, because it can be difficult to
  find out the required devices for stacked setups like LVM or for
  network dump.

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

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

[Kernel-packages] [Bug 1175465] Re: Alcor AU9520 not recognized by libccid > 1.4.2

[Märt Põder]

As far as I know, there are no differences in libusb between versions
tested, it seems that system doesn't offer automatical updates if I
change version of libccid and I haven't changed anything manually for
sure. I attach CCID parse output.

** Attachment added: "ccid-1.4.22 parse output on Ubuntu 14.04.4"
   
https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465/+attachment/4619343/+files/ccid-parse.txt

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

Title:
  Alcor AU9520 not recognized by libccid > 1.4.2

Status in ccid package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201205-11052 (Pavilion Slimline S5 Pavilion P6)

  With this card reader: 058f:6362 Alcor Micro Corp. Flash Card
  Reader/Writer

  Steps:
  1. Insert a MMC/SD/SDHC card.
  2. (The file browser will pop out.)
  3. Remove the pre-inserted card.

  Expected Results:
  1. The card will be removed from the /media, the icon will disappear from the 
launcher.
  2. Open a file browser, and it's not in the devices section of the left 
column.

  Actual Results:
  1. The card will be removed from the /media, the icon will disappear.
  2. It still listed in the devices section, if you click on it in the file 
browser,
  an error pops, telling you the device was not found, and the disappears from 
the left column of the file browser.

  The reason seems to be the eject event is not being sent through dbus.
  Will try update later to see if it can be solved.
  The eject event is not being sent through dbus

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1547 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d0 irq 50'
     Mixer name : 'IDT 92HD73E1X5'
     Components : 'HDA:111d7676,103c2ada,00100103'
     Controls  : 39
     Simple ctrls  : 21
  Date: Thu May  2 02:11:18 2013
  HibernationDevice: RESUME=UUID=0059822b-2011-4dbc-aea6-3e1aff45462e
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic 
root=UUID=c6420b34-c860-4df2-99fd-9fa1a0b893b7 ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-23-generic N/A
   linux-backports-modules-3.5.0-23-generic  N/A
   linux-firmware1.79.1
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2013
  dmi.bios.vendor: AMI
  dmi.bios.version: 00.05
  dmi.board.name: 2ADA
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: PVT
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr00.05:bd03/29/2013:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn2ADA:rvrPVT:cvnHewlett-Packard:ct3:cvr:
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1564475] Re: 128M is not enough for kdump on s390 LPARs

[Dimitri John Ledkov]

On 1 April 2016 at 12:22, Louis Bouchard  wrote:
> If there is a way to determine if we're on a zVM or Lpar, I could adapt
> kdump-config to add the appropriate crashkernel=value pair in
> /etc/zipl.conf and re-run zipl upon installation of kdump-tools, which
> is required in order to capture a dump.
>

$ systemd-detect-virt
zvm
(aka z/VM)

$ systemd-detect-virt
none
(aka LPAR)

-- 
Regards,

Dimitri.


** Changed in: makedumpfile (Ubuntu)
   Status: Invalid => Confirmed

** Changed in: makedumpfile (Ubuntu)
   Importance: Undecided => High

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

Title:
  128M is not enough for kdump on s390 LPARs

Status in makedumpfile package in Ubuntu:
  Confirmed

Bug description:
  == Comment: #0 - Michael Holzheu  - 2016-03-31 
10:59:26 ==
  With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs 
crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt").

  On z/VM guests 128M seems to be sufficient.

  One reason on our test LPAR is that a lot of devices are attached (see
  attachment "lscss_lpar.txt") which are not required for kdump but
  consume a lot of memory because the s390 CIO layer allocates data
  structures in the kernel for those devices.

  We can disable the devices by using the "cio_ignore=" kernel parameter
  in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD
  0.0.e934 for /var/crash, we added the following line to disable the
  devices:

  KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1
  cio_ignore=all,!condev,!0.0.e934"

  For more information on the "cio_ignore=" kernel parameter see:
  https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO

  Even with "cio_ignore=" we still get out-of-memory with
  "crashkernel=128M".

  With "crashkernel=196M" and "cio_ignore=" we are able to create a dump
  on our LPAR. We currently do not know why kdump with "cio_ignore=" on
  LPAR consumes more memory than on z/VM guests.

  == Comment: #1 - Michael Holzheu  - 2016-03-31 
11:03:15 ==
  Kernel messages of kdump out-of-memory crash on LPAR with many devices 
without cio_ignore parameter and 128M crashkernel memory.

  == Comment: #2 - Michael Holzheu  - 2016-03-31 
11:04:10 ==
  Output of lscss showing all attached (not online) devices on the LPAR.

  == Comment: #3 - Michael Holzheu  - 2016-03-31 
11:07:35 ==
  To solve this issue our recommendation is:

  1) Increase "crashkernel=" default to 196M on Ubuntu for s390.

  2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used
  to decrease memory consumption for kdump on systems with many devices
  that are not required for kdump.

  The most user friendly solution would be to automatically determine
  the required kdump devices and set the correct "cio_ignore=" kernel
  parameter. But this is not trivial, because it can be difficult to
  find out the required devices for stacked setups like LVM or for
  network dump.

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

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

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Joseph Salisbury]

I'm using a Wily 15.10 Gen2 guest has the base OS.  The vss/kvp daemon
are the versions that come in linux-tools and packed for that particular
kernel being tested.

To test a particular kernel, you need to go to the Launchpad download
page for a particular version/arch.  Then download an install four .deb
packages for that kernel.  With dpkg -i from a termina, install the
linux-image, linux-image-extra, linux-tools and linux-tools-generic .deb
packages.

For example to test 3.13.0-17, I went to the URL:
https://launchpad.net/ubuntu/+source/linux/3.13.0-17.37/+build/5800060

Then downloaded these four .deb packages:
1. linux-image-3.13.0-17-generic 3.13.0-17.37
2. linux-image-extra-3.13.0-17-generic 3.13.0-17.37
3. linux-tools-3.13.0-17 3.13.0-17.37
4. linux-tools-3.13.0-17-generic 3.13.0-17.37

All of the Trusty kernels are available for download from:
https://launchpad.net/ubuntu/trusty/+source/linux

You just need to select a particular version, then select the
architecture on the next page, under 'Builds'.

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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

[Kernel-packages] [Bug 1557994] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From utz.bac...@de.ibm.com 2016-04-01 07:45 EDT---
After some measurements, we think the penalty of a ramdisk (where these modules 
would reside on) is acceptable, when in turn we can keep the kernel itself 
small and minimal. So having 9pfs (with virtio and fs_cache) as a module is 
fine!

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

Title:
  s390/kconfig: setting for CONFIG...9P

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Heinz-Werner Seeck  - 
2016-03-16 03:58:51 ==
  Reason:
  To allow using the host file system from within a KVM guest, in order to 
simplify management

  Following settings are required :
  CONFIG_NET_9P=y
  CONFIG_NET_9P_VIRTIO=y
  CONFIG_9P_FS=y
  CONFIG_9P_FS_POSIX_ACL=y
  CONFIG_9P_FS_SECURITY=y

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

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

[Kernel-packages] [Bug 1562155] Re: Touchpad stopped functioning after kernel update for Dell Chromebook "Candy"

[Chan Ju Ping]

I decided to do a full upgrade to the 16.04 Beta for one of these
Chromebooks, since the intention is to eventually run the LTS on these
machines.. The touchpad works for now.

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

Title:
  Touchpad stopped functioning after kernel update for Dell Chromebook
  "Candy"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upon successful installation of Ubuntu 15.10, I ran the usual updates
  and after restarting, the touchpad stopped working.

  I booted into kernel version 4.2.0-16 instead of the updated kernel
  4.2.0-34, and the touchpad that had stopped working functioned as
  usual once more. Changing back into the latest kernel disabled the
  touchpad once more.

  I am installing Ubuntu on the Dell Chromebook 11 "Candy" running Intel
  Celeron(R) CPU N2840 (Baytrail) processor. This deployment is being
  used for several lab machines of the same model.

  Steps to reproduce:

  1. Install Ubuntu 15.10.
  2. Run update.

  Expected:

  1. All hardware to work prior to update.

  Instead:

  1. Touchpad stopped working.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-34-generic 4.2.0-34.39
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  unllife121l980 F pulseaudio
  Date: Fri Mar 25 15:33:10 2016
  HibernationDevice: RESUME=UUID=44e6cef0-6fe7-4afe-a5f9-0a8d60224b28
  InstallationDate: Installed on 2016-03-24 (0 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: GOOGLE Candy
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=a7c1001c-8167-4541-b62e-e2cf805003d8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-34-generic N/A
   linux-backports-modules-4.2.0-34-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/20/2014:svnGOOGLE:pnCandy:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Candy
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1014240] Re: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup

[Egbert van der Wal]

Christopher, thanks for the explanation. However, I was under the
impression that the automatic response was due to the fact that I
changed state of this bug to 'new' (because it was set to 'expired' and
I suffered from the same problem).

I'm currently awaiting the problem but I haven't encountered it since I
installed the latest kernel version in 16.04: 4.4.0-16-generic. If it
occurs again, I will file a new report rather than post here. Thanks
again.

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

Title:
  [Asus eeepc 1225B] Keyboard and Touchpad randomly not working  at
  startup

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Usually, once every 5-6 times when I reboot or awake form hibernate, the 
touchpad and keyboard do not work: no way to input text and login so I need to 
hard reset the laptop. I can ssh in (so the system is not frozen) and  Fn+keys 
to change screen brightness etc always work.
  I collected X and kernel logs when it happens (by logging in remotely via  
SSH) but I'm not able to understand what is going on.

  This issue is reported in multiple forums, and affects Asus 252b as
  well (same laptop model for US market). Another bug is filed for this
  laptop model, related to hibernate/suspend
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/951143) and a
  workaround exists, maybe it helps.

  $ lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04
  $ uname -a
  Linux picolo 3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Joseph Salisbury]

3.13.0-26 is Good, testing 3.13.0-30 next.

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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

[Kernel-packages] [Bug 1529971] bantam (amd64) - tests ran: 11, failed: 3

[Brad Figg]

tests ran:  11, failed: 3;
  
http://kernel.ubuntu.com/testing/4.4.0-17.33/s2lp6g002__4.4.0-17.33__2016-04-01_05-35-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-43.49~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-43.49~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 29. December 2015 22:50 UTC
  kernel-stable-master-bug:1529362
  kernel-stable-Prepare-package-end:Friday, 01. January 2016 21:01 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 01. January 2016 21:01 UTC
  kernel-stable-Certification-testing-end:Monday, 04. January 2016 16:01 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 04. January 2016 18:08 UTC
  kernel-stable-Security-signoff-start:Monday, 04. January 2016 18:30 UTC
  kernel-stable-Regression-testing-start:Monday, 04. January 2016 18:30 UTC
  proposed-announcement-sent:True
  kernel-stable-Verification-testing-start:Monday, 04. January 2016 18:30 UTC
  kernel-stable-Verification-testing-end:Monday, 04. January 2016 20:01 UTC
  kernel-stable-Regression-testing-end:Monday, 04. January 2016 20:01 UTC
  kernel-stable-Security-signoff-end:Tuesday, 05. January 2016 09:00 UTC
  kernel-stable-Promote-to-updates-start:Tuesday, 05. January 2016 10:01 UTC
  kernel-stable-Promote-to-updates-end:Tuesday, 05. January 2016 16:10 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Tuesday, 05. January 2016 18:02 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1529971/+subscriptions

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

[Kernel-packages] [Bug 1511534] Re: [Hyper-V] Fibre Channel multipath error message

[Joseph Salisbury]

** Changed in: linux (Ubuntu Wily)
   Status: Triaged => Fix Released

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => Fix Released

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

Title:
  [Hyper-V] Fibre Channel multipath error message

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Problem statement:
  Wily (and probably other previous releases with the updated kernels) return a 
multipath error for vFC (virtual Fibre Channel).

  Symptoms:
  The following messages are in the dmesg log during booting:
  device-mapper: table: 252:4: multipath: error getting device
  device-mapper: IOCtl: error adding target to table

  After logging in, run the command: multipath -ll

  The multipath command does not return any errors, and no new messages
  are added to the dmesg log or syslog after running the multipath
  command.

  
  Steps to repro
  
  Tested with the released Wily (15.10), kernel 4.2.0-16-generic.

   1. Create a Wily VM.
   2. Boot and install the multipath-tools package.
   3. Shutdown and attach a Virtual Fiber Channel adapter and connect it to a 
virtual SAN.
  Note: The host must have a Fiber Channel adapter. Use Hyper-V managers 
Virtual SAN Manager to create a Virtual Fiber Channel Storage Area Network.
   4. Boot the VM.
   5. Issue the following command to see any errors were reported during the 
boot.
  dmesg | grep -i error
  You should see the following two error:
  device-mapper: table: 252:4: multipath: error getting device
  device-mapper: IOCtl: error adding target to table

  Otherwise, the vFC disks are usable and show no issues at a use test
  case.

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

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

[Kernel-packages] [Bug 1529971] bantam (amd64) - tests ran: 11, failed: 3

[Brad Figg]

tests ran:  11, failed: 3;
  
http://kernel.ubuntu.com/testing/4.4.0-17.33/s2lp3__4.4.0-17.33__2016-04-01_05-49-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-43.49~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-43.49~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 29. December 2015 22:50 UTC
  kernel-stable-master-bug:1529362
  kernel-stable-Prepare-package-end:Friday, 01. January 2016 21:01 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 01. January 2016 21:01 UTC
  kernel-stable-Certification-testing-end:Monday, 04. January 2016 16:01 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 04. January 2016 18:08 UTC
  kernel-stable-Security-signoff-start:Monday, 04. January 2016 18:30 UTC
  kernel-stable-Regression-testing-start:Monday, 04. January 2016 18:30 UTC
  proposed-announcement-sent:True
  kernel-stable-Verification-testing-start:Monday, 04. January 2016 18:30 UTC
  kernel-stable-Verification-testing-end:Monday, 04. January 2016 20:01 UTC
  kernel-stable-Regression-testing-end:Monday, 04. January 2016 20:01 UTC
  kernel-stable-Security-signoff-end:Tuesday, 05. January 2016 09:00 UTC
  kernel-stable-Promote-to-updates-start:Tuesday, 05. January 2016 10:01 UTC
  kernel-stable-Promote-to-updates-end:Tuesday, 05. January 2016 16:10 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Tuesday, 05. January 2016 18:02 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1529971/+subscriptions

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

[Kernel-packages] [Bug 1529971] bantam (amd64) - tests ran: 11, failed: 2

[Brad Figg]

tests ran:  11, failed: 2;
  
http://kernel.ubuntu.com/testing/4.4.0-15.31/kernel01__4.4.0-15.31__2016-04-01_06-04-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-43.49~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-43.49~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 29. December 2015 22:50 UTC
  kernel-stable-master-bug:1529362
  kernel-stable-Prepare-package-end:Friday, 01. January 2016 21:01 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 01. January 2016 21:01 UTC
  kernel-stable-Certification-testing-end:Monday, 04. January 2016 16:01 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 04. January 2016 18:08 UTC
  kernel-stable-Security-signoff-start:Monday, 04. January 2016 18:30 UTC
  kernel-stable-Regression-testing-start:Monday, 04. January 2016 18:30 UTC
  proposed-announcement-sent:True
  kernel-stable-Verification-testing-start:Monday, 04. January 2016 18:30 UTC
  kernel-stable-Verification-testing-end:Monday, 04. January 2016 20:01 UTC
  kernel-stable-Regression-testing-end:Monday, 04. January 2016 20:01 UTC
  kernel-stable-Security-signoff-end:Tuesday, 05. January 2016 09:00 UTC
  kernel-stable-Promote-to-updates-start:Tuesday, 05. January 2016 10:01 UTC
  kernel-stable-Promote-to-updates-end:Tuesday, 05. January 2016 16:10 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Tuesday, 05. January 2016 18:02 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1529971/+subscriptions

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

[Kernel-packages] [Bug 1564901] [NEW] xpad rumble causes full system hang

[Alistair Buxton]

Public bug reported:

To reproduce:

1. Have a wired xbox controller.
2. Modify the SDL2 testrumble.c so it runs forever. (attached)
3. Build and run it.
4. Kill it with sigkill from another terminal.

Expected result: The program should stop running.

Actual result: Entire computer freezes. Soundcard continuously plays the
last second of audio. No response from any input devices or the network.

The bug can also be reproduced by playing the game Borderlands 2 while
having a wired xbox controller connected. The system will randomly
freeze in the exact same way.

The bug has existed since at least 14.04.

The last thing the kernel prints is this:

Apr  1 03:38:29 al-desktop kernel: [94142.404218] usb 7-3: new full-speed USB 
device number 2 using ohci-pci
Apr  1 03:38:29 al-desktop kernel: [94142.565264] usb 7-3: New USB device 
found, idVendor=045e, idProduct=0288
Apr  1 03:38:29 al-desktop kernel: [94142.565268] usb 7-3: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
Apr  1 03:38:29 al-desktop kernel: [94142.567304] hub 7-3:1.0: USB hub found
Apr  1 03:38:29 al-desktop kernel: [94142.569259] hub 7-3:1.0: 3 ports detected
Apr  1 03:38:29 al-desktop kernel: [94142.852248] usb 7-3.1: new full-speed USB 
device number 3 using ohci-pci
Apr  1 03:38:29 al-desktop kernel: [94142.949301] usb 7-3.1: New USB device 
found, idVendor=045e, idProduct=0289
Apr  1 03:38:29 al-desktop kernel: [94142.949308] usb 7-3.1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
Apr  1 03:38:29 al-desktop kernel: [94142.982402] input: Microsoft X-Box pad v2 
(US) as /devices/pci:00/:00:13.0/usb7/7-3/7-3.1/7-3.1:1.0/input/input23
Apr  1 03:38:29 al-desktop kernel: [94142.982503] usbcore: registered new 
interface driver xpad
Apr  1 03:40:09 al-desktop kernel: [94242.318271] [ cut here 
]
Apr  1 03:40:09 al-desktop kernel: [94242.318280] WARNING: CPU: 3 PID: 16529 at 
/build/linux-_Kv5oI/linux-4.2.0/drivers/usb/core/urb.c:339 
usb_submit_urb+0x51/0x70()
Apr  1 03:40:09 al-desktop kernel: [94242.318282] URB 880106cbacc0 
submitted while active
Apr  1 03:40:09 al-desktop kernel: [94242.318283] Modules linked in: joydev 
xpad ff_memless nvidia_uvm(POE) rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) rc_pinnacle_pctv_hd em28xx_rc tda18271 cxd2820r 
em28xx_dvb d
vb_core em28xx binfmt_misc bnep snd_hda_codec_hdmi rc_hauppauge ir_kbd_i2c 
tuner_simple tuner_types input_leds tuner uvcvideo videobuf2_vmalloc kvm_amd 
videobuf2_memops kvm btusb videobuf2_core btrtl snd_seq_midi btbcm 
snd_seq_midi_event 
btintel snd_usb_audio snd_usbmidi_lib snd_hda_codec_via msp3400 
snd_hda_codec_generic snd_rawmidi bluetooth nvidia(POE) snd_seq serio_raw 
snd_hda_intel snd_seq_device snd_hda_codec snd_hda_core snd_hwdep bttv k10temp 
tea575x tveeprom edac
_core videobuf_dma_sg edac_mce_amd rc_core videobuf_core snd_bt87x v4l2_common 
videodev snd_pcm media i2c_algo_bit snd_timer i2c_piix4 snd soundcore drm 
shpchp wmi 8250_fintek asus_atk0110 mac_hid parport_pc ppdev lp parport autofs4 
uas u
sb_storage hid_generic usbhid hid pata_acpi psmouse pata_atiixp ahci libahci 
r8169 mii
Apr  1 03:40:09 al-desktop kernel: [94242.318324] CPU: 3 PID: 16529 Comm: 
testrumble Tainted: P   OE   4.2.0-34-generic #39-Ubuntu
Apr  1 03:40:09 al-desktop kernel: [94242.318326] Hardware name: System 
manufacturer System Product Name/M4A79XTD EVO, BIOS 210206/17/2010
Apr  1 03:40:09 al-desktop kernel: [94242.318328]   
4da02d75 88010a9c3ba8 817ebed3
Apr  1 03:40:09 al-desktop kernel: [94242.318330]   
88010a9c3c00 88010a9c3be8 8107b986
Apr  1 03:40:09 al-desktop kernel: [94242.318331]  88010a9c3bd8 
0010 880103216f08 88010a9c3cd0
Apr  1 03:40:09 al-desktop kernel: [94242.318333] Call Trace:
Apr  1 03:40:09 al-desktop kernel: [94242.318337]  [] 
dump_stack+0x45/0x57
Apr  1 03:40:09 al-desktop kernel: [94242.318340]  [] 
warn_slowpath_common+0x86/0xc0
Apr  1 03:40:09 al-desktop kernel: [94242.318342]  [] 
warn_slowpath_fmt+0x55/0x70
Apr  1 03:40:09 al-desktop kernel: [94242.318345]  [] 
usb_submit_urb+0x51/0x70
Apr  1 03:40:09 al-desktop kernel: [94242.318348]  [] 
xpad_play_effect+0x130/0x240 [xpad]
Apr  1 03:40:09 al-desktop kernel: [94242.318351]  [] 
ml_play_effects+0x104/0x6b0 [ff_memless]
Apr  1 03:40:09 al-desktop kernel: [94242.318353]  [] 
ml_ff_playback+0x85/0x100 [ff_memless]
Apr  1 03:40:09 al-desktop kernel: [94242.318355]  [] 
input_ff_event+0x61/0x90
Apr  1 03:40:09 al-desktop kernel: [94242.318357]  [] 
input_handle_event+0x77/0x4f0
Apr  1 03:40:09 al-desktop kernel: [94242.318359]  [] 
input_inject_event+0x88/0x90
Apr  1 03:40:09 al-desktop kernel: [94242.318360]  [] 
evdev_write+0x1b6/0x230
Apr  1 03:40:09 al-desktop kernel: [94242.318363]  [] 
__vfs_write+0x18/0x40
Apr  1 03:40:09 al-desktop kernel: [94242.318364]  [] 
vfs_write+0xa6/0x1a0
Apr  1 03:40:09 al-desktop kernel: [94242.318

[Kernel-packages] [Bug 1564901] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  xpad rumble causes full system hang

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To reproduce:

  1. Have a wired xbox controller.
  2. Modify the SDL2 testrumble.c so it runs forever. (attached)
  3. Build and run it.
  4. Kill it with sigkill from another terminal.

  Expected result: The program should stop running.

  Actual result: Entire computer freezes. Soundcard continuously plays
  the last second of audio. No response from any input devices or the
  network.

  The bug can also be reproduced by playing the game Borderlands 2 while
  having a wired xbox controller connected. The system will randomly
  freeze in the exact same way.

  The bug has existed since at least 14.04.

  The last thing the kernel prints is this:

  Apr  1 03:38:29 al-desktop kernel: [94142.404218] usb 7-3: new full-speed USB 
device number 2 using ohci-pci
  Apr  1 03:38:29 al-desktop kernel: [94142.565264] usb 7-3: New USB device 
found, idVendor=045e, idProduct=0288
  Apr  1 03:38:29 al-desktop kernel: [94142.565268] usb 7-3: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
  Apr  1 03:38:29 al-desktop kernel: [94142.567304] hub 7-3:1.0: USB hub found
  Apr  1 03:38:29 al-desktop kernel: [94142.569259] hub 7-3:1.0: 3 ports 
detected
  Apr  1 03:38:29 al-desktop kernel: [94142.852248] usb 7-3.1: new full-speed 
USB device number 3 using ohci-pci
  Apr  1 03:38:29 al-desktop kernel: [94142.949301] usb 7-3.1: New USB device 
found, idVendor=045e, idProduct=0289
  Apr  1 03:38:29 al-desktop kernel: [94142.949308] usb 7-3.1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
  Apr  1 03:38:29 al-desktop kernel: [94142.982402] input: Microsoft X-Box pad 
v2 (US) as 
/devices/pci:00/:00:13.0/usb7/7-3/7-3.1/7-3.1:1.0/input/input23
  Apr  1 03:38:29 al-desktop kernel: [94142.982503] usbcore: registered new 
interface driver xpad
  Apr  1 03:40:09 al-desktop kernel: [94242.318271] [ cut here 
]
  Apr  1 03:40:09 al-desktop kernel: [94242.318280] WARNING: CPU: 3 PID: 16529 
at /build/linux-_Kv5oI/linux-4.2.0/drivers/usb/core/urb.c:339 
usb_submit_urb+0x51/0x70()
  Apr  1 03:40:09 al-desktop kernel: [94242.318282] URB 880106cbacc0 
submitted while active
  Apr  1 03:40:09 al-desktop kernel: [94242.318283] Modules linked in: joydev 
xpad ff_memless nvidia_uvm(POE) rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) rc_pinnacle_pctv_hd em28xx_rc tda18271 cxd2820r 
em28xx_dvb d
  vb_core em28xx binfmt_misc bnep snd_hda_codec_hdmi rc_hauppauge ir_kbd_i2c 
tuner_simple tuner_types input_leds tuner uvcvideo videobuf2_vmalloc kvm_amd 
videobuf2_memops kvm btusb videobuf2_core btrtl snd_seq_midi btbcm 
snd_seq_midi_event 
  btintel snd_usb_audio snd_usbmidi_lib snd_hda_codec_via msp3400 
snd_hda_codec_generic snd_rawmidi bluetooth nvidia(POE) snd_seq serio_raw 
snd_hda_intel snd_seq_device snd_hda_codec snd_hda_core snd_hwdep bttv k10temp 
tea575x tveeprom edac
  _core videobuf_dma_sg edac_mce_amd rc_core videobuf_core snd_bt87x 
v4l2_common videodev snd_pcm media i2c_algo_bit snd_timer i2c_piix4 snd 
soundcore drm shpchp wmi 8250_fintek asus_atk0110 mac_hid parport_pc ppdev lp 
parport autofs4 uas u
  sb_storage hid_generic usbhid hid pata_acpi psmouse pata_atiixp ahci libahci 
r8169 mii
  Apr  1 03:40:09 al-desktop kernel: [94242.318324] CPU: 3 PID: 16529 Comm: 
testrumble Tainted: P   OE   4.2.0-34-generic #39-Ubuntu
  Apr  1 03:40:09 al-desktop kernel: [94242.318326] Hardware name: System 
manufacturer System Product Name/M4A79XTD EVO, BIOS 210206/17/2010
  Apr  1 03:40:09 al-desktop kernel: [94242.318328]   
4da02d75 88010a9c3ba8 817ebed3
  Apr  1 03:40:09 al-desktop kernel: [94242.318330]   
88010a9c3c00 88010a9c3be8 8107b986
  Apr  1 03:40:09 al-desktop kernel: [94242.318331]  88010a9c3bd8 
0010 880103216f08 88010a9c3cd0
  Apr  1 03:40:09 al-desktop kernel: [94242.318333] Call Trace:
  Apr  1 03:40:09 al-desktop kernel: [94242.318337]  [] 
dump_stack+0x45/0x57
  Apr  1 03:40:09 al-desktop kernel: [94242.318340]  [] 
warn_slowpath_common+0x86/0xc0
  Apr  1 03:40:09 al-desktop kernel: [94242.318342]  [] 
warn_slowpath_fmt+0x55/0x70
  Apr  1 03:40:09 al-desktop kernel: [94242.318345]  [] 
usb_submit_urb+0x51/0x70
  Apr  1 03:40:09 al-desktop kernel: [94242.318348]  [] 
xpad_play_effect+0x130/0x240 [xpad]
  Apr  1 03:40:09 al-desktop kernel: [94242.318351]  [] 
ml_play_effects+0x104/0x6b0 [ff_memless]
  Apr  1 03:40:09 al-desktop kernel: [94242.318353]  [] 
ml_ff_playback+0x85/0x100 [ff_memless]
  Apr  1 03:40:09 al-desktop kernel: [94242.318355]  [] 
input_ff_event+0x61/0x90
  A

[Kernel-packages] [Bug 1564487] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash (s390x, ppc64)

[Chris J Arges]

** Changed in: crash (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Chris J Arges 
(arges)

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

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash
  (s390x, ppc64)

Status in crash package in Ubuntu:
  Confirmed

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-03-31 02:19:27 ==
  ---Problem Description---
  With the kexec-tools comes from 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=136588#c58 , we have dumpped a 
vmcore for bug 139815 after quiting from xmon. But when trying to analyse with 
crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.4.0-15-generic
  /var/crash/201603310043/dump.201603310043

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  crash: invalid structure member offset: module_num_symtab
 FILE: kernel.c  LINE: 3450  FUNCTION: module_init()

  [/usr/bin/crash] error trace: 1008af0c => 10124250 => 10179bd0 =>
  10083378

10083378: (undetermined)
10179bd0: OFFSET_verify+80
10124250: module_init+1104
1008af0c: main_loop+764

  %

  == Comment: #4 - Hari Krishna Bathini - 2016-03-31 08:20:39 ==
  (In reply to comment #2)
  > Hi, 
  > 
  > Crash failing with 4.4+ kernels is a known issue which is fixed by the
  > upstream patch 
  > 
  > commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
  > Author: Dave Anderson 
  > Date:   Wed Jan 20 09:56:36 2016 -0500
  > 
  > Fix for the changes made to the kernel module structure introduced by
  > this kernel commit for Linux 4.5 and later kernels:
  > 
  >   commit 7523e4dc5057e157212b4741abd6256e03404cf1
  >   module: use a structure to encapsulate layout.
  > 
  > Without the patch, the crash session fails during initialization
  > with the error message: "crash: invalid structure member offset:
  > module_init_text_size".
  > (seb...@linux.vnet.ibm.com)
  > 

  We also need the below upstream patch along with the patch mentioned
  above to fix this issue

  commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
  Author: Dave Anderson 
  Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:
  
commit 8244062ef1e54502ef55f54cced659913f244c3e
modules: fix longstanding /proc/kallsyms vs module insertion race.
  
  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

  Thanks
  Hari

  == Comment: #9 - Hendrik Brueckner - 2016-03-31 11:47:13 ==
  Problem also exists on s390x:

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

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

[Kernel-packages] [Bug 1175465] Re: Alcor AU9520 not recognized by libccid > 1.4.2

[Ludovic Rousseau]

You version is quiet similar to
https://pcsclite.alioth.debian.org/ccid/readers/AU9520.txt

I have no idea what the problem can be.

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

Title:
  Alcor AU9520 not recognized by libccid > 1.4.2

Status in ccid package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201205-11052 (Pavilion Slimline S5 Pavilion P6)

  With this card reader: 058f:6362 Alcor Micro Corp. Flash Card
  Reader/Writer

  Steps:
  1. Insert a MMC/SD/SDHC card.
  2. (The file browser will pop out.)
  3. Remove the pre-inserted card.

  Expected Results:
  1. The card will be removed from the /media, the icon will disappear from the 
launcher.
  2. Open a file browser, and it's not in the devices section of the left 
column.

  Actual Results:
  1. The card will be removed from the /media, the icon will disappear.
  2. It still listed in the devices section, if you click on it in the file 
browser,
  an error pops, telling you the device was not found, and the disappears from 
the left column of the file browser.

  The reason seems to be the eject event is not being sent through dbus.
  Will try update later to see if it can be solved.
  The eject event is not being sent through dbus

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1547 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d0 irq 50'
     Mixer name : 'IDT 92HD73E1X5'
     Components : 'HDA:111d7676,103c2ada,00100103'
     Controls  : 39
     Simple ctrls  : 21
  Date: Thu May  2 02:11:18 2013
  HibernationDevice: RESUME=UUID=0059822b-2011-4dbc-aea6-3e1aff45462e
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic 
root=UUID=c6420b34-c860-4df2-99fd-9fa1a0b893b7 ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-23-generic N/A
   linux-backports-modules-3.5.0-23-generic  N/A
   linux-firmware1.79.1
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2013
  dmi.bios.vendor: AMI
  dmi.bios.version: 00.05
  dmi.board.name: 2ADA
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: PVT
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr00.05:bd03/29/2013:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn2ADA:rvrPVT:cvnHewlett-Packard:ct3:cvr:
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1564901] Re: xpad rumble causes full system hang

[Alistair Buxton]

This is probably fixed by:

https://github.com/torvalds/linux/commit/7fc595f4c02636eadaeeecfe7bbc45b57c173004

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

Title:
  xpad rumble causes full system hang

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To reproduce:

  1. Have a wired xbox controller.
  2. Modify the SDL2 testrumble.c so it runs forever. (attached)
  3. Build and run it.
  4. Kill it with sigkill from another terminal.

  Expected result: The program should stop running.

  Actual result: Entire computer freezes. Soundcard continuously plays
  the last second of audio. No response from any input devices or the
  network.

  The bug can also be reproduced by playing the game Borderlands 2 while
  having a wired xbox controller connected. The system will randomly
  freeze in the exact same way.

  The bug has existed since at least 14.04.

  The last thing the kernel prints is this:

  Apr  1 03:38:29 al-desktop kernel: [94142.404218] usb 7-3: new full-speed USB 
device number 2 using ohci-pci
  Apr  1 03:38:29 al-desktop kernel: [94142.565264] usb 7-3: New USB device 
found, idVendor=045e, idProduct=0288
  Apr  1 03:38:29 al-desktop kernel: [94142.565268] usb 7-3: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
  Apr  1 03:38:29 al-desktop kernel: [94142.567304] hub 7-3:1.0: USB hub found
  Apr  1 03:38:29 al-desktop kernel: [94142.569259] hub 7-3:1.0: 3 ports 
detected
  Apr  1 03:38:29 al-desktop kernel: [94142.852248] usb 7-3.1: new full-speed 
USB device number 3 using ohci-pci
  Apr  1 03:38:29 al-desktop kernel: [94142.949301] usb 7-3.1: New USB device 
found, idVendor=045e, idProduct=0289
  Apr  1 03:38:29 al-desktop kernel: [94142.949308] usb 7-3.1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
  Apr  1 03:38:29 al-desktop kernel: [94142.982402] input: Microsoft X-Box pad 
v2 (US) as 
/devices/pci:00/:00:13.0/usb7/7-3/7-3.1/7-3.1:1.0/input/input23
  Apr  1 03:38:29 al-desktop kernel: [94142.982503] usbcore: registered new 
interface driver xpad
  Apr  1 03:40:09 al-desktop kernel: [94242.318271] [ cut here 
]
  Apr  1 03:40:09 al-desktop kernel: [94242.318280] WARNING: CPU: 3 PID: 16529 
at /build/linux-_Kv5oI/linux-4.2.0/drivers/usb/core/urb.c:339 
usb_submit_urb+0x51/0x70()
  Apr  1 03:40:09 al-desktop kernel: [94242.318282] URB 880106cbacc0 
submitted while active
  Apr  1 03:40:09 al-desktop kernel: [94242.318283] Modules linked in: joydev 
xpad ff_memless nvidia_uvm(POE) rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) rc_pinnacle_pctv_hd em28xx_rc tda18271 cxd2820r 
em28xx_dvb d
  vb_core em28xx binfmt_misc bnep snd_hda_codec_hdmi rc_hauppauge ir_kbd_i2c 
tuner_simple tuner_types input_leds tuner uvcvideo videobuf2_vmalloc kvm_amd 
videobuf2_memops kvm btusb videobuf2_core btrtl snd_seq_midi btbcm 
snd_seq_midi_event 
  btintel snd_usb_audio snd_usbmidi_lib snd_hda_codec_via msp3400 
snd_hda_codec_generic snd_rawmidi bluetooth nvidia(POE) snd_seq serio_raw 
snd_hda_intel snd_seq_device snd_hda_codec snd_hda_core snd_hwdep bttv k10temp 
tea575x tveeprom edac
  _core videobuf_dma_sg edac_mce_amd rc_core videobuf_core snd_bt87x 
v4l2_common videodev snd_pcm media i2c_algo_bit snd_timer i2c_piix4 snd 
soundcore drm shpchp wmi 8250_fintek asus_atk0110 mac_hid parport_pc ppdev lp 
parport autofs4 uas u
  sb_storage hid_generic usbhid hid pata_acpi psmouse pata_atiixp ahci libahci 
r8169 mii
  Apr  1 03:40:09 al-desktop kernel: [94242.318324] CPU: 3 PID: 16529 Comm: 
testrumble Tainted: P   OE   4.2.0-34-generic #39-Ubuntu
  Apr  1 03:40:09 al-desktop kernel: [94242.318326] Hardware name: System 
manufacturer System Product Name/M4A79XTD EVO, BIOS 210206/17/2010
  Apr  1 03:40:09 al-desktop kernel: [94242.318328]   
4da02d75 88010a9c3ba8 817ebed3
  Apr  1 03:40:09 al-desktop kernel: [94242.318330]   
88010a9c3c00 88010a9c3be8 8107b986
  Apr  1 03:40:09 al-desktop kernel: [94242.318331]  88010a9c3bd8 
0010 880103216f08 88010a9c3cd0
  Apr  1 03:40:09 al-desktop kernel: [94242.318333] Call Trace:
  Apr  1 03:40:09 al-desktop kernel: [94242.318337]  [] 
dump_stack+0x45/0x57
  Apr  1 03:40:09 al-desktop kernel: [94242.318340]  [] 
warn_slowpath_common+0x86/0xc0
  Apr  1 03:40:09 al-desktop kernel: [94242.318342]  [] 
warn_slowpath_fmt+0x55/0x70
  Apr  1 03:40:09 al-desktop kernel: [94242.318345]  [] 
usb_submit_urb+0x51/0x70
  Apr  1 03:40:09 al-desktop kernel: [94242.318348]  [] 
xpad_play_effect+0x130/0x240 [xpad]
  Apr  1 03:40:09 al-desktop kernel: [94242.318351]  [] 
ml_play_effects+0x104/0x6b0 [ff_memless]
  Apr  1 03:40:09 al-desktop kernel: [94242.318353]  [] 
ml_ff_playback+0x85/0x100 [ff_memless]
  Apr  1 03:40:09 al-desktop kernel: [94242.318355]  [] 
input_ff_eve

[Kernel-packages] [Bug 1564487] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash (s390x, ppc64)

[Chris J Arges]

Uploaded crash_7.1.4-1ubuntu4 which contains the missing patch.
Hopefully that will be available for testing soon.

** Changed in: crash (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash
  (s390x, ppc64)

Status in crash package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-03-31 02:19:27 ==
  ---Problem Description---
  With the kexec-tools comes from 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=136588#c58 , we have dumpped a 
vmcore for bug 139815 after quiting from xmon. But when trying to analyse with 
crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.4.0-15-generic
  /var/crash/201603310043/dump.201603310043

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  crash: invalid structure member offset: module_num_symtab
 FILE: kernel.c  LINE: 3450  FUNCTION: module_init()

  [/usr/bin/crash] error trace: 1008af0c => 10124250 => 10179bd0 =>
  10083378

10083378: (undetermined)
10179bd0: OFFSET_verify+80
10124250: module_init+1104
1008af0c: main_loop+764

  %

  == Comment: #4 - Hari Krishna Bathini - 2016-03-31 08:20:39 ==
  (In reply to comment #2)
  > Hi, 
  > 
  > Crash failing with 4.4+ kernels is a known issue which is fixed by the
  > upstream patch 
  > 
  > commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
  > Author: Dave Anderson 
  > Date:   Wed Jan 20 09:56:36 2016 -0500
  > 
  > Fix for the changes made to the kernel module structure introduced by
  > this kernel commit for Linux 4.5 and later kernels:
  > 
  >   commit 7523e4dc5057e157212b4741abd6256e03404cf1
  >   module: use a structure to encapsulate layout.
  > 
  > Without the patch, the crash session fails during initialization
  > with the error message: "crash: invalid structure member offset:
  > module_init_text_size".
  > (seb...@linux.vnet.ibm.com)
  > 

  We also need the below upstream patch along with the patch mentioned
  above to fix this issue

  commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
  Author: Dave Anderson 
  Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:
  
commit 8244062ef1e54502ef55f54cced659913f244c3e
modules: fix longstanding /proc/kallsyms vs module insertion race.
  
  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

  Thanks
  Hari

  == Comment: #9 - Hendrik Brueckner - 2016-03-31 11:47:13 ==
  Problem also exists on s390x:

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

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

[Kernel-packages] [Bug 1555786] Re: [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

[Joseph Salisbury]

Sure, I can assist with a bisect.

I can either build kernels and post them for you to test, or I can test
them myself on my Hyper-V setup.  My setup is currently tied up running
test until probably Monday for bug 1470250.  Just let me know if you
want me to start building test kernels for you.  Otherwise, I'll start
testing for this bug next week.

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

Title:
  [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We identified that at least ubuntu (let's take 15.10) does not boot if
  installed in the 32bit architecture, and using the linux-next upstream
  kernel 4.5 on it. This has been seen on other distributions as well.

  We took both the official linux-next branch from kernel.org and the one from 
kernel.ubuntu.com v4.5-rc7.
  For the compilation process we went either with the 4.2 kernel config file 
from the installed running kernel, and also built the config separately. 
  No errors have been encountered during the build or install process of the 
4.5 kernel, however at boot, the VM will just hang.
  There are no call traces or messages at boot to show any pottential issue.

  Have you seen this on your end when testing the 32bit build?
  Attaching the full serial log for reference, however I don't see any errors 
in the kernel boot process.

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

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

[Kernel-packages] [Bug 1564901] Re: xpad rumble causes full system hang

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  xpad rumble causes full system hang

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To reproduce:

  1. Have a wired xbox controller.
  2. Modify the SDL2 testrumble.c so it runs forever. (attached)
  3. Build and run it.
  4. Kill it with sigkill from another terminal.

  Expected result: The program should stop running.

  Actual result: Entire computer freezes. Soundcard continuously plays
  the last second of audio. No response from any input devices or the
  network.

  The bug can also be reproduced by playing the game Borderlands 2 while
  having a wired xbox controller connected. The system will randomly
  freeze in the exact same way.

  The bug has existed since at least 14.04.

  The last thing the kernel prints is this:

  Apr  1 03:38:29 al-desktop kernel: [94142.404218] usb 7-3: new full-speed USB 
device number 2 using ohci-pci
  Apr  1 03:38:29 al-desktop kernel: [94142.565264] usb 7-3: New USB device 
found, idVendor=045e, idProduct=0288
  Apr  1 03:38:29 al-desktop kernel: [94142.565268] usb 7-3: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
  Apr  1 03:38:29 al-desktop kernel: [94142.567304] hub 7-3:1.0: USB hub found
  Apr  1 03:38:29 al-desktop kernel: [94142.569259] hub 7-3:1.0: 3 ports 
detected
  Apr  1 03:38:29 al-desktop kernel: [94142.852248] usb 7-3.1: new full-speed 
USB device number 3 using ohci-pci
  Apr  1 03:38:29 al-desktop kernel: [94142.949301] usb 7-3.1: New USB device 
found, idVendor=045e, idProduct=0289
  Apr  1 03:38:29 al-desktop kernel: [94142.949308] usb 7-3.1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
  Apr  1 03:38:29 al-desktop kernel: [94142.982402] input: Microsoft X-Box pad 
v2 (US) as 
/devices/pci:00/:00:13.0/usb7/7-3/7-3.1/7-3.1:1.0/input/input23
  Apr  1 03:38:29 al-desktop kernel: [94142.982503] usbcore: registered new 
interface driver xpad
  Apr  1 03:40:09 al-desktop kernel: [94242.318271] [ cut here 
]
  Apr  1 03:40:09 al-desktop kernel: [94242.318280] WARNING: CPU: 3 PID: 16529 
at /build/linux-_Kv5oI/linux-4.2.0/drivers/usb/core/urb.c:339 
usb_submit_urb+0x51/0x70()
  Apr  1 03:40:09 al-desktop kernel: [94242.318282] URB 880106cbacc0 
submitted while active
  Apr  1 03:40:09 al-desktop kernel: [94242.318283] Modules linked in: joydev 
xpad ff_memless nvidia_uvm(POE) rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) rc_pinnacle_pctv_hd em28xx_rc tda18271 cxd2820r 
em28xx_dvb d
  vb_core em28xx binfmt_misc bnep snd_hda_codec_hdmi rc_hauppauge ir_kbd_i2c 
tuner_simple tuner_types input_leds tuner uvcvideo videobuf2_vmalloc kvm_amd 
videobuf2_memops kvm btusb videobuf2_core btrtl snd_seq_midi btbcm 
snd_seq_midi_event 
  btintel snd_usb_audio snd_usbmidi_lib snd_hda_codec_via msp3400 
snd_hda_codec_generic snd_rawmidi bluetooth nvidia(POE) snd_seq serio_raw 
snd_hda_intel snd_seq_device snd_hda_codec snd_hda_core snd_hwdep bttv k10temp 
tea575x tveeprom edac
  _core videobuf_dma_sg edac_mce_amd rc_core videobuf_core snd_bt87x 
v4l2_common videodev snd_pcm media i2c_algo_bit snd_timer i2c_piix4 snd 
soundcore drm shpchp wmi 8250_fintek asus_atk0110 mac_hid parport_pc ppdev lp 
parport autofs4 uas u
  sb_storage hid_generic usbhid hid pata_acpi psmouse pata_atiixp ahci libahci 
r8169 mii
  Apr  1 03:40:09 al-desktop kernel: [94242.318324] CPU: 3 PID: 16529 Comm: 
testrumble Tainted: P   OE   4.2.0-34-generic #39-Ubuntu
  Apr  1 03:40:09 al-desktop kernel: [94242.318326] Hardware name: System 
manufacturer System Product Name/M4A79XTD EVO, BIOS 210206/17/2010
  Apr  1 03:40:09 al-desktop kernel: [94242.318328]   
4da02d75 88010a9c3ba8 817ebed3
  Apr  1 03:40:09 al-desktop kernel: [94242.318330]   
88010a9c3c00 88010a9c3be8 8107b986
  Apr  1 03:40:09 al-desktop kernel: [94242.318331]  88010a9c3bd8 
0010 880103216f08 88010a9c3cd0
  Apr  1 03:40:09 al-desktop kernel: [94242.318333] Call Trace:
  Apr  1 03:40:09 al-desktop kernel: [94242.318337]  [] 
dump_stack+0x45/0x57
  Apr  1 03:40:09 al-desktop kernel: [94242.318340]  [] 
warn_slowpath_common+0x86/0xc0
  Apr  1 03:40:09 al-desktop kernel: [94242.318342]  [] 
warn_slowpath_fmt+0x55/0x70
  Apr  1 03:40:09 al-desktop kernel: [94242.318345]  [] 
usb_submit_urb+0x51/0x70
  Apr  1 03:40:09 al-desktop kernel: [94242.318348]  [] 
xpad_play_effect+0x130/0x240 [xpad]
  Apr  1 03:40:09 al-desktop kernel: [94242.318351]  [] 
ml_play_effects+0x104/0x6b0 [ff_memless]
  Apr  1 03:40:09 al-desktop kernel: [94242.318353]  [] 
ml_ff_playback+0x85/0x100 [ff_memless]
  Apr  1 03:40:09 al-desktop kernel: [94242.318355]  [] 
input_ff_event+0x61/0x90
  Apr  1 03:40:09 al-desktop ker

[Kernel-packages] [Bug 1564591] Re: Sync kernel zfs 0.6.5.6 - align with zfsutils-linux and spl packages

[Tim Gardner]

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
 Assignee: Colin Ian King (colin-king)
   Status: In Progress

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  Sync kernel zfs 0.6.5.6 - align with zfsutils-linux and spl packages

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  We need to sync with zfs 0.6.5.6-0ubuntu3 to pick up a couple of minor
  fixes:

  Add support 32 bit FS_IOC32_{GET|SET}FLAGS compat ioctls (for powerpc64 big 
endian mode)
  Fix aarch64 compilation, missing hrtime_t and timestruct_t types

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

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

[Kernel-packages] [Bug 1563229] Re: Touchpad recognised as mouse FTE1000

[Gianmaria Scorza]

** Changed in: xinput (Ubuntu Trusty)
   Status: New => Confirmed

** Changed in: xinput (Ubuntu Wily)
   Status: New => Confirmed

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

Title:
  Touchpad recognised as mouse FTE1000

Status in linux package in Ubuntu:
  Triaged
Status in xinput package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Triaged
Status in xinput source package in Trusty:
  Confirmed
Status in linux source package in Wily:
  Triaged
Status in xinput source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Triaged
Status in xinput source package in Xenial:
  Confirmed

Bug description:
  In my Asus e200ha touchpad is recognized as mouse, only one click, no
  two finger click and scrolling

  Xinput say:
  FTE1000:00 0B05:0101   id=12[slave pointer (2)]

  i've tried:
  - ubuntu 14.04 with stock kernel
  - ubuntu 14.04 with 4.6rc1 kernel
  - Linux mint 17.3 with stock kernel
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: xinput 1.6.1-1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1562778] Re: I2C touchscreen init failed on HP X360

[Kamal Mostafa]

** Changed in: linux (Ubuntu Vivid)
   Status: New => Fix Committed

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

Title:
  I2C touchscreen init failed on HP X360

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  As title, after upgrading to latest Vivid kernel the touchscreen
  failed. After bisecting shows this revert cause the regression:

  commit 95df597989f6f297db63dd8669656d10f5f48eb1
  Author: Andy Shevchenko 
  Date: Fri Dec 4 23:49:18 2015 +0200

  Revert "ACPI / LPSS: allow to use specific PM domain during
  ->probe()"

  [Fix]

  The reverted patch has had a revised version upstreamed:

  commit de16d55206c5ce82ad44590b01718fbe2323853c
  Author: Andy Shevchenko 
  Date:   Fri Dec 4 23:49:19 2015 +0200

  ACPI / LPSS: allow to use specific PM domain during ->probe()

  For Vivid it depends on a patch to device core for adding
  BUS_NOTIFY_DRIVER_NOT_BOUND notification, both are clean cherry-pick.

  For Xenial the touchscreen still works because the original patch is
  not reverted, and with the patch reverted the I2C touchscreen still
  works fine, so I'll skip Xenial for this patch.

  For Wily it also contains the revert patch as Vivid, but the I2C on
  X360 still works.

  [Test]

  3.19.0-56 -> Failed
  3.19.0-56 + patches -> OK (Including suspend)
  4.2.0-34 (with revert patch already) -> OK
  4.4.0-15 -> OK
  4.4.0-15 + revert patch -> OK
  4.4.0-15 + patches -> N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1562778/+subscriptions

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

[Kernel-packages] [Bug 1552788] strace of ip link set enccw0.0.f5f0 up

[bugproxy]

Default Comment by Bridge

** Attachment added: "strace of ip link set enccw0.0.f5f0 up"
   
https://bugs.launchpad.net/bugs/1552788/+attachment/4619462/+files/ip.up.strace.5030

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

Title:
  network lost after large number of reboots

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  network lost after large number of reboots (>500)
   
  Contact Information = pschm...@de.ibm.com 
   
  ---uname output---
  Linux s8330025 4.4.0-2-generic #16-Ubuntu SMP Thu Jan 28 15:44:18 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = s390 z/VM Guest 
   
  ---Steps to Reproduce---
   reboot z/VM guest several times >500. After a large number of reboots the 
network interfaces doesn't come up any more. The z/VM guest boots fine, unless 
the missing network. Impossible to bring up network again manually.

  ==

  Further debug shows that it is the "ip link set enccw0.0.f5f0 up" that
  is failing with "RTNETLINK answers: Operation not permitted".  Looking
  for further debug assistance in determining why the CAP_NET_ADMIN
  check for the root user running ip might be failing.

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

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

[Kernel-packages] [Bug 1564793] Re: package linux-image-4.4.0-16-generic 4.4.0-16.32 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  package linux-image-4.4.0-16-generic 4.4.0-16.32 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During upgrade from trusty to xenial, thing went amiss

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  Uname: Linux 3.19.0-56-generic x86_64
  AlsaDevices:
   ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD 
cannot be preloaded (cannot open shared object file): ignored.
   total 0
   crw-rw 1 root audio 116,  1 Apr  1 10:26 seq
   crw-rw 1 root audio 116, 33 Apr  1 10:26 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1: ERROR: ld.so: object 
'/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
  Date: Fri Apr  1 10:36:08 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=9a552e9f-593f-42f9-8b03-74c062d5fb3b
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD 
cannot be preloaded (cannot open shared object file): ignored.
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU D3401-H1
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic 
root=UUID=fd827598-4b67-4b7a-9374-cb789aa7ad8a ro nomodeset intel_pstate=enable 
nomdmonddf nomdmonisw
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  Title: package linux-image-4.4.0-16-generic 4.4.0-16.32 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-04-01 (0 days ago)
  dmi.bios.date: 11/25/2015
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.11 R1.7.0.SR.2 for D3401-H1x
  dmi.board.name: D3401-H1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3401-H1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.11R1.7.0.SR.2forD3401-H1x:bd11/25/2015:svnFUJITSU:pnD3401-H1:pvr:rvnFUJITSU:rnD3401-H1:rvrS26361-D3401-H1:cvnFUJITSU:ct3:cvr:
  dmi.product.name: D3401-H1
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1564807] Re: nfs causes guest system to get stuck

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/


** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

Title:
  nfs causes guest system to get stuck

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Host OS Ubuntu 15.10
  Guest OS Ubuntu 14.10

  Using Vagrant with nfs and Virtualbox and static ip on the private
  network.

  It is working perfectly except that after having suspended the host
  OS, the entire guest OS will be unusable. This does not happen when
  using the normal virtualbox shared folders.

  It's not only the nfs shared folder that is unusable, the entire OS is
  hanging. Even syslog does not seem to see much action. This is syslog
  on the guest, from waking up until vagrant halt is completed.

  Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 
1000 Mbps Full Duplex, Flow Control: RX
  Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not 
responding, still trying
  Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not 
responding, still trying
  Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
  Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on 
signal 15.

  When I try to ssh to the guest system I the motd and last login: ..., but 
nothing more, it just hangs.
  If I was already logged in the guest system through ssh then that session is 
unresponsive (after pressing enter).

  How can this be fixed?
  How should I debug it?

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

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

[Kernel-packages] [Bug 1564463] Re: Joystick Dragonrise Axes confused in Ubuntu 14.04

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/


** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  Confirmed

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

[Kernel-packages] [Bug 1564423] Re: Touchpad not recognized

[Joseph Salisbury]

Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v3.19 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-ckt17-vivid/

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

Title:
  Touchpad not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi, my Acer E3-111 stopped recognizing the touchpad.  External mouse works; 
the machine seems not to recognize the hardware.  Even the system settings only 
shows me mouse settings.  Attaching dmesg and devices.
  The problem started about a week ago after installing an update and rebooting.
  Thanks!
  Andrea

  $ cat /proc/version_signature
  Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15

  $ cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
  U: Uniq=
  H: Handlers=kbd event0 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
  U: Uniq=
  H: Handlers=event2 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
  U: Uniq=
  H: Handlers=kbd event3 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input4
  U: Uniq=
  H: Handlers=sysrq kbd event4 
  B: PROP=0
  B: EV=120013
  B: KEY=1 c0200 0 0 700f0203 3802078f870f401 febfffdfffef 
fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input5
  U: Uniq=
  H: Handlers=kbd event5 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.0/0003:045E:07B2.0001/input/input6
  U: Uniq=
  H: Handlers=sysrq kbd event6 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff8007ff febeffdff3cf fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.1/0003:045E:07B2.0002/input/input7
  U: Uniq=
  H: Handlers=mouse0 event7 
  B: PROP=0
  B: EV=17
  B: KEY=1f 0 0 0 0
  B: REL=1c3
  B: MSC=10

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input2
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:045E:07B2.0003/input/input8
  U: Uniq=
  H: Handlers=sysrq kbd event8 js0 
  B: PROP=0
  B: EV=10001f
  B: KEY=3f0003007f 0 0 4c317aff32d bf544456 c01 
130f938b17c007 7bfad951dfff febeffdfffef fffe
  B: REL=40
  B: ABS=ff01000701ff
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Acer WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input9
  U: Uniq=
  H: Handlers=rfkill kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1c 0 0 0 0 160080c00 30 0 0
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Acer BMA150 accelerometer"
  P: Phys=wmi/input1
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=event10 js1 
  B: PROP=0
  B: EV=9
  B: ABS=7

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input11
  

[Kernel-packages] [Bug 1564423] Re: Touchpad not recognized

[Joseph Salisbury]

Does this bug go away if you boot back into the prior kernel?

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Touchpad not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi, my Acer E3-111 stopped recognizing the touchpad.  External mouse works; 
the machine seems not to recognize the hardware.  Even the system settings only 
shows me mouse settings.  Attaching dmesg and devices.
  The problem started about a week ago after installing an update and rebooting.
  Thanks!
  Andrea

  $ cat /proc/version_signature
  Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15

  $ cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
  U: Uniq=
  H: Handlers=kbd event0 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
  U: Uniq=
  H: Handlers=event2 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
  U: Uniq=
  H: Handlers=kbd event3 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input4
  U: Uniq=
  H: Handlers=sysrq kbd event4 
  B: PROP=0
  B: EV=120013
  B: KEY=1 c0200 0 0 700f0203 3802078f870f401 febfffdfffef 
fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input5
  U: Uniq=
  H: Handlers=kbd event5 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.0/0003:045E:07B2.0001/input/input6
  U: Uniq=
  H: Handlers=sysrq kbd event6 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff8007ff febeffdff3cf fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.1/0003:045E:07B2.0002/input/input7
  U: Uniq=
  H: Handlers=mouse0 event7 
  B: PROP=0
  B: EV=17
  B: KEY=1f 0 0 0 0
  B: REL=1c3
  B: MSC=10

  I: Bus=0003 Vendor=045e Product=07b2 Version=0111
  N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
  P: Phys=usb-:00:14.0-2.3/input2
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:045E:07B2.0003/input/input8
  U: Uniq=
  H: Handlers=sysrq kbd event8 js0 
  B: PROP=0
  B: EV=10001f
  B: KEY=3f0003007f 0 0 4c317aff32d bf544456 c01 
130f938b17c007 7bfad951dfff febeffdfffef fffe
  B: REL=40
  B: ABS=ff01000701ff
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Acer WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input9
  U: Uniq=
  H: Handlers=rfkill kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1c 0 0 0 0 160080c00 30 0 0
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Acer BMA150 accelerometer"
  P: Phys=wmi/input1
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=event10 js1 
  B: PROP=0
  B: EV=9
  B: ABS=7

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input11
  U: Uniq=
  H: Handlers=event11 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input12
  U: Uniq=
  H: Handlers=event12 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0003 Vendor=04f2 Product=b47f Version=4051
  N: Name="VGA Webcam"
  P: Phys=usb-:00:14.0-4/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input13
  U: Uniq=
  H: Handlers=kbd event13 
  B: PROP=0
  B: EV=3
  B:

[Kernel-packages] [Bug 1564470] Re: Unable to install NI-VISA nikal kernel module because of GPL-only symbol 'pgprot_writecombine'

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  Unable to install NI-VISA nikal kernel module because of GPL-only
  symbol 'pgprot_writecombine'

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Login to National Instruments site
  2. Download NI-VISA 15.0 for linux (NI-VISA-15.0.0.iso).
  3. Launch its installation by "sudo ./INSTALL"
  4. Get errors on nikal kernel modules compilation about "pgprot_writecombine" 
symbol 
  (

  sudo /usr/local/natinst/nikal/bin/updateNIDrivers 
  Configuring NI-KAL for kernel version 4.4.0-16-generic...
  Building module nikal...
  <11>Mar 31 23:04:51 nikal:   CC [M]  
/var/lib/nikal/4.4.0-16-generic/nikal/nikal.o
  <11>Mar 31 23:04:51 nikal:   Building modules, stage 2.
  <11>Mar 31 23:04:51 nikal:   MODPOST 1 modules
  <11>Mar 31 23:04:51 nikal: FATAL: modpost: GPL-incompatible module nikal.ko 
uses GPL-only symbol 'pgprot_writecombine'
  <11>Mar 31 23:04:51 nikal: scripts/Makefile.modpost:91: recipe for target 
'__modpost' failed
  <11>Mar 31 23:04:51 nikal: make[2]: *** [__modpost] Error 1
  <11>Mar 31 23:04:51 nikal: Makefile:1399: recipe for target 'modules' failed
  <11>Mar 31 23:04:51 nikal: make[1]: *** [modules] Error 2
  <11>Mar 31 23:04:51 nikal: Makefile:32: recipe for target 'nikal.ko' failed
  <11>Mar 31 23:04:51 nikal: make: *** [nikal.ko] Error 2
  <11>Mar 31 23:04:51 nikal: ERROR:  failed to build nikal
  <11>Mar 31 23:04:51 nikal: ERROR:  NI-KAL update failed.
  <11>Mar 31 23:04:51 nikal: ERROR:  make of nikal kernel module failed, not 
installing kernel module.
  <11>Mar 31 23:04:51 nikal: ERROR:  updateNIDrivers should be called again 
after fixing the problem.
  <11>Mar 31 23:04:51 nikal: ERROR:  Logging failure...
  find: ‘/lib/modules/4.4.0-15-generic/kernel/natinst’: No such file or 
directory
  <11>Mar 31 23:04:51 nikal: ERROR:  Include the file 
/tmp/niSystemReport.out.gz when contacting
  <11>Mar 31 23:04:51 nikal: ERROR:  National Instruments for support.
  <11>Mar 31 23:04:51 nikal: ERROR: Update of National Instruments drivers 
failed.

  
  )

  Temporary solution:
  1. Edit /usr/src/linux-headers-4.4.0-16-generic/Module.symvers
  and change line
     0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL_GPL
  to
     0xd544e902 pgprot_writecombine vmlinux EXPORT_SYMBOL
  2. Edit /boot/abi-4.4.0-16-generic
  and change line
     EXPORT_SYMBOL_GPL vmlinux 0xd544e902   pgprot_writecombine
  to
     EXPORT_SYMBOL vmlinux 0xd544e902   pgprot_writecombine

  but it does not help - I get "nikal: Unknown symbol
  pgprot_writecombine (err 0)" in syslog.

  Expected results:
  0. The 'pgprot_writecombine' symbol is exported as EXPORT_SYMBOL
  1. Ubuntu can compile and load NI nikal module.

  Actual results:
  Unable to use NI-VISA under Ubuntu.

  Reference (openSUSE):
  
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/GPL-incompatible-module-nikal-ko/td-p/3218730

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  flash  1549 F pulseaudio
   /dev/snd/controlC0:  flash  1549 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 31 18:16:37 2016
  InstallationDate: Installed on 2016-03-26 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic 
root=UUID=eab7b488-5040-499c-afd8-21a7ce9e2383 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A55M-DS2:rvrx.x:cvnG

[Kernel-packages] [Bug 1564487] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From hbath...@in.ibm.com 2016-04-01 10:56 EDT---
(In reply to comment #16)
> Uploaded crash_7.1.4-1ubuntu4 which contains the missing patch. Hopefully
> that will be available for testing soon.

Just so we are clear, you mean "missing patches"? Because there are two of them
as mentioned already by Breno:

098cdab16dfa6a85e9dad2cad604dee14ee15f66
6f1f78e33474d00d5f261d7ed9d835c558b34d61

Thanks
Hari

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

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash
  (s390x, ppc64)

Status in crash package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-03-31 02:19:27 ==
  ---Problem Description---
  With the kexec-tools comes from 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=136588#c58 , we have dumpped a 
vmcore for bug 139815 after quiting from xmon. But when trying to analyse with 
crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.4.0-15-generic
  /var/crash/201603310043/dump.201603310043

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  crash: invalid structure member offset: module_num_symtab
 FILE: kernel.c  LINE: 3450  FUNCTION: module_init()

  [/usr/bin/crash] error trace: 1008af0c => 10124250 => 10179bd0 =>
  10083378

10083378: (undetermined)
10179bd0: OFFSET_verify+80
10124250: module_init+1104
1008af0c: main_loop+764

  %

  == Comment: #4 - Hari Krishna Bathini - 2016-03-31 08:20:39 ==
  (In reply to comment #2)
  > Hi, 
  > 
  > Crash failing with 4.4+ kernels is a known issue which is fixed by the
  > upstream patch 
  > 
  > commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
  > Author: Dave Anderson 
  > Date:   Wed Jan 20 09:56:36 2016 -0500
  > 
  > Fix for the changes made to the kernel module structure introduced by
  > this kernel commit for Linux 4.5 and later kernels:
  > 
  >   commit 7523e4dc5057e157212b4741abd6256e03404cf1
  >   module: use a structure to encapsulate layout.
  > 
  > Without the patch, the crash session fails during initialization
  > with the error message: "crash: invalid structure member offset:
  > module_init_text_size".
  > (seb...@linux.vnet.ibm.com)
  > 

  We also need the below upstream patch along with the patch mentioned
  above to fix this issue

  commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
  Author: Dave Anderson 
  Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:
  
commit 8244062ef1e54502ef55f54cced659913f244c3e
modules: fix longstanding /proc/kallsyms vs module insertion race.
  
  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

  Thanks
  Hari

  == Comment: #9 - Hendrik Brueckner - 2016-03-31 11:47:13 ==
  Problem also exists on s390x:

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

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

[Kernel-packages] [Bug 1564178] Re: [Dell Inc. Precision WorkStation 490] hibernate/resume failure

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  [Dell Inc. Precision WorkStation 490] hibernate/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Unmounts Swap Partion then fails to resume from hibernate

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31 [modified: 
boot/vmlinuz-4.4.0-15-generic]
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luke   1531 F pulseaudio
   /dev/snd/controlC1:  luke   1531 F pulseaudio
  Date: Sun Mar 27 19:28:16 2016
  DuplicateSignature: hibernate/resume:Dell Inc. Precision WorkStation 490:A08
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=8f6ad9fa-5d18-4eb6-94e7-a13e9ccaf888
  InstallationDate: Installed on 2016-03-25 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  InterpreterPath: /usr/bin/python3.5
  MachineType: Dell Inc. Precision WorkStation 490
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=dbf62ba9-e647-41e3-a0a3-0c0c5dcedfec ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  Title: [Dell Inc. Precision WorkStation 490] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/25/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0F9382
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/25/2008:svnDellInc.:pnPrecisionWorkStation490:pvr:rvnDellInc.:rn0F9382:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation 490
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1563998] Re: Ubuntu 16.04 Kernel 4.4.0-16 doesn't boot, cannot open root device

[Joseph Salisbury]

Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.6-wily/

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Tags added: kernel-da-key regression-proposed xenial

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

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

Title:
  Ubuntu 16.04 Kernel 4.4.0-16 doesn't boot, cannot open root device

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  - Thinkpad X230, latest Bios, BIOS Legacy Boot active
  - Ubuntu 16.04
  - Kernel 4.4.0-16
  - dm-crypt / LUKS full disk encryption setup during install with BTRFS as 
filesystems
  - partion layout:

  steven@thinkpad:~$ blkid 
  /dev/mapper/sdb2_crypt: UUID="DiTDe3-wjSv-YCFz-Lful-KBMl-BCWr-t2Jzry" 
TYPE="LVM2_member"
  /dev/mapper/vg_crypt-lv_root: LABEL="ROOT" 
UUID="0760638f-92f7-4bd9-a5b8-638002a1d699" 
UUID_SUB="b8c21ae4-99c7-470f-a2a1-24308c5177e7" TYPE="btrfs"
  /dev/sda1: LABEL="BOOT" UUID="895c6d03-cc2d-4303-b59e-eb8f5b6452f2" 
UUID_SUB="7e9d110f-7a6f-4c21-8438-e746acf53b9a" TYPE="btrfs" 
PARTUUID="83f8d594-01"
  /dev/sda2: UUID="0ce18f8a-9317-40c6-bb1d-cc5608b3b58d" TYPE="crypto_LUKS" 
PARTUUID="83f8d594-02"
  /dev/mapper/vg_crypt-lv_swap: UUID="8010fb1a-fdc0-40d6-a241-1d52d2a89f8f" 
TYPE="swap"

  - since Kernel 4.4.0-16-generic the system doesn't boot, it shows a "VFS: 
Cannot open root device "mapper/vg_crypt-lv_root" or unknown-block(0,0): error 
-6" error
  - see attached screenshots for more detailed error message
  - if i boot Kernel 4.4.0-15-generic then the boot is successfull

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

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

[Kernel-packages] [Bug 1564949] Re: Severe latency/skew on AMD Opetron processor

[Jeff Lane]

Also note, both the Intel and AMD boxes were tested with the same kernel
and the TSC clocksource in use.  I tried HPET on the AMD box as well but
it didn't make any difference.

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  New

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6

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

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

[Kernel-packages] [Bug 1563991] Re: [Dell Inc. Inspiron 5520] hibernate/resume failure [non-free: wl]

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  [Dell Inc. Inspiron 5520] hibernate/resume failure [non-free: wl]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System fails to enter suspend mode on ubuntu 16.04 LTS (beta2) - did
  work on ubuntu 14.04 LTS.

  Events:
  * closing the laptop lid, or
  * calling `sudo pm-hibernate` via terminal

  Effect:
  * Screen goes black
  * System stays on, but no commands are acknowledged (mouse, keyboard, trying 
to switch to tty1 via CTRL+ALT+F1)

  Expectation:
  * System enters standby

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: wl
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarah  2221 F pulseaudio
  Date: Wed Mar 30 19:23:24 2016
  DuplicateSignature: hibernate/resume:Dell Inc. Inspiron 5520:A05
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=61da4468-0d8c-4c4e-8616-32dfc23e0ccd
  InstallationDate: Installed on 2014-08-10 (598 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterpreterPath: /usr/bin/python3.5
  MachineType: Dell Inc. Inspiron 5520
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  Title: [Dell Inc. Inspiron 5520] hibernate/resume failure [non-free: wl]
  UpgradeStatus: Upgraded to xenial on 2016-03-27 (3 days ago)
  UserGroups:
   
  dmi.bios.date: 03/16/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd03/16/2012:svnDellInc.:pnInspiron5520:pvrA05:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvrA05:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A05
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1564949] Re: Severe latency/skew on AMD Opetron processor

[Jeff Lane]

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)"

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  New

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6

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

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

[Kernel-packages] [Bug 1564949] [NEW] Severe latency/skew on AMD Opetron processor

[Jeff Lane]

Public bug reported:

Discovered this while doing pre-release certification testing for 16.04
on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core CPU.

I have some code that essentially does this:  And note, I am NOT a C
programmer, I know enough C to read it and do some minor things, and I
once knew C++ fairly well, about 10 years ago...

gettimeofday(&tval_start, NULL);
sleep(sleeptime);
gettimeofday(&tval_stop, NULL);

where tval_start and tval_stop are timeval structs and sleeptime is 60.

Once it gets the start and stop it finds the delta minus the sleep time.

In a perfect world, for example, start time would be 123456.123 and
end time would be 123516.123 and the delta between them minus the 60
seconds of sleep would be 0.

Of course, that isn't how it works in reality so the delta may be a
few microseconds here and there depending on what else the kernel is
doing at any given moment.  The following, however, are on essentially
idle Xenial systems (only processes running are whatever Ubuntu Server
runs by default, nothing really taxing going on).

On my Skylake i7 with Xenial, the time differences are never more than
a few 10,000ths of a second: (kernel 4.4.0-15.31)
Testing clock direction for 5 minutes...
PASSED: Iteration 0 delta: 0.000109
PASSED: Iteration 1 delta: 0.68
PASSED: Iteration 2 delta: 0.000107
PASSED: Iteration 3 delta: 0.000216
PASSED: Iteration 4 delta: 0.89

On a zVM instance (kernel 4.4.0-16.32) it's even better:
PASSED: Iteration 0 delta: 0.58
PASSED: Iteration 1 delta: 0.58
PASSED: Iteration 2 delta: 0.74
PASSED: Iteration 3 delta: 0.52
PASSED: Iteration 4 delta: 0.62

But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
difference is always in the 10ths of a second, sometimes even several
seconds... in other words, I've seen up to a 7.9 second delta with
this code.  Here's one run that shows 3 seconds in one iteration:
(kernel 4.4.0-15.31)
FAILED: Iteration 0 delta: 3.057980
FAILED: Iteration 1 delta: 0.225712
FAILED: Iteration 2 delta: 0.241468
FAILED: Iteration 3 delta: 0.229084
FAILED: Iteration 4 delta: 0.223933

I ran a second run on the AMD cpu and the latency was all over the place:
FAILED: Iteration 0 delta: 9.302149
FAILED: Iteration 1 delta: 0.624466
FAILED: Iteration 2 delta: 1.644834
FAILED: Iteration 3 delta: 1.011474
FAILED: Iteration 4 delta: 0.923033

After a discussion with cking and apw, deviations of as seen on the
Intel and s390 CPUs are about what we should expect to see depending on
what the system is doing at the moment gettimeofday() is executed.
However, on the AMD CPU, differences of up to 9 seconds or more are NOT
expected and highly irregular.

Colin said he tested this on an AMD C60 CPU and got numbers inline with
the Skylake and s390 chips and could not reproduce the times I am seeing
on the Opteron.

$ cat /proc/version_signature 
Ubuntu 4.4.0-15.31-generic 4.4.6

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

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  New

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But

[Kernel-packages] [Bug 1563900] Re: xts-plain64 encryption method missing in linux-image-3.16.0-67-generic

[Joseph Salisbury]

Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v3.16 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.7-ckt26-trusty/

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  xts-plain64 encryption method missing in linux-image-3.16.0-67-generic

Status in cryptsetup package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running Ubuntu 14.4.0.4

  I have the root disk encrypted with aes-xts-plain64

  After upgrading to linux-image-3.16.0-67-generic I was not able to
  boot getting message cryptsetup: cryptsetup failed, bad password or
  options?

  Trying to decrypt manually the disk shows the xts-plain64 method
  missing.

  After reverting to linux-image-3.16.0-62-generic the password was
  recognized and the boot completed successfully

  Thanks

  Jorge

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

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

[Kernel-packages] [Bug 1563970] Re: Clock issues on AMD Opteron(tm) Processor 6320

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/


** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

** Tags added: kernel-da-key

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

Title:
  Clock issues on AMD Opteron(tm) Processor 6320

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In doing certification testing on an HP DL385p Gen8 server with an AMD
  Opteron(tm) Processor 6320 CPU, we've run into some clock issues, as
  illustrated by the following:

  $ for x in `seq 0 9`; do start=`date +"%s"`; sleep 60; stop=`date +"%s"`; 
echo "$stop - $start"|bc; done
  65
  62
  60
  60
  60
  61
  60
  60
  60
  61

  This should produce a string of "60" values, and does on most systems;
  however, on the DL385p Gen8, the output shown above is quite
  irregular. (The test we use in the certification suite is more
  specialized and is not this exact test; the above is simply an easy-
  to-reproduce bash variant.)

  The system in question is "phelps" in OIL.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Mar 29 14:43 seq
   crw-rw+ 1 root audio 116, 33 Mar 29 14:43 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Wed Mar 30 12:13:22 2016
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: HP ProLiant DL385p Gen8
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=96485ede-c1a8-407d-9960-f4cfa725ea89 ro rootdelay=60
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A28
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrA28:bd02/06/2014:svnHP:pnProLiantDL385pGen8:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL385p Gen8
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1564217] Re: Hot add of a disk attached to LSI Logic SAS is not getting detected

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Tags added: kernel-da-key

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

Title:
  Hot add of a disk attached to LSI Logic SAS is not getting detected

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  when install VM ubuntu 16.04 beta1 image in VMware ESXi,  Hot add of
  a disk attached to LSI Logic SAS is not getting detected

  Steps to reproduce:
  1.Install ubuntu 16.04 beta1 with BUS logic SAS as boot controller in VMware 
ESXi 6.0GA.
  2.Power on the VM
  3.Hot add a hard disk to LSI SAS controller, the ubuntu 16.04 does not detect 
the disk

  the developer from VMware company investigate it and find it's a kernel issue.
  Bug 114611(https://bugzilla.kernel.org/show_bug.cgi?id=114611) is tracking it 
and now have fix for it.

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

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

[Kernel-packages] [Bug 1564950] [NEW] Kernel panic when using CEPHFS (Hammer) /w kernel vivid-lts on Ubuntu 14.04

[Kamal Mostafa]

Public bug reported:

Reported by Dennis Kramer at http://tracker.ceph.com/issues/15302

--

Nowadays i'm getting a kernel panic when i use the vivid-lts (3.19.x)
kernel on ubuntu 14.04 after I try to mount cephfs. Log indicates:

kernel BUG at 
/build/linux-lts-vivid-ZTSmDy/linux-lts-vivid-3.19.0/fs/ceph/mds_client.c:1928[ 
27.305173] kernel BUG at 
/build/linux-lts-vivid-ZTSmDy/linux-lts-vivid-3.19.0/fs/ceph/mds_client.c:1928!
[ 27.307226] invalid opcode:  [#1] SMP 
[ 27.307599] Modules linked in: ceph libceph libcrc32c fscache ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi dm_crypt ppdev parport_pc 8250_fintek pvpanic serio_raw 
joydev parport i2c_piix4 mac_hid hid_generic usbhid hid syscopyarea sysfillrect 
sysimgblt ttm drm_kms_helper psmouse drm pata_acpi floppy
[ 27.307599] CPU: 0 PID: 118 Comm: kworker/0:2 Not tainted 3.19.0-56-generic 
#62~14.04.1-Ubuntu
[ 27.307599] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
1.7.5-20150310_111955-batsu 04/01/2014
[ 27.307599] Workqueue: ceph-msgr con_work [libceph]
[ 27.307599] task: 88007ca0ce80 ti: 88003657c000 task.ti: 
88003657c000
[ 27.307599] RIP: 0010:[] [] 
__prepare_send_request+0x7d0/0x800 [ceph]
[ 27.307599] RSP: 0018:88003657fb48 EFLAGS: 00010283
[ 27.307599] RAX: 880077e1bb02 RBX: 8800364af000 RCX: 
[ 27.307599] RDX: 38a516d3 RSI:  RDI: 880077e1baf2
[ 27.307599] RBP: 88003657fbe8 R08:  R09: 
[ 27.307599] R10: c0275fe6 R11:  R12: 88007873c700
[ 27.307599] R13: 880078458000 R14:  R15: 880077e1ba80
[ 27.307599] FS: () GS:88007fc0() 
knlGS:
[ 27.307599] CS: 0010 DS:  ES:  CR0: 8005003b
[ 27.307599] CR2: 7ff6e2973000 CR3: 36387000 CR4: 06f0
[ 27.307599] Stack:
[ 27.307599] 88003657fb8c c02e1109 0115 0001
[ 27.307599] 8800362e0118 880077e1bafa 88003657fbe8 
[ 27.307599]  8800362e0118  0001
[ 27.307599] Call Trace:
[ 27.307599] [] ? __choose_mds+0x119/0x470 [ceph]
[ 27.307599] [] __do_request+0x230/0x310 [ceph]
[ 27.307599] [] __wake_requests+0x78/0xb0 [ceph]
[ 27.307599] [] dispatch+0x550/0xad0 [ceph]
[ 27.307599] [] try_read+0x4cb/0x10f0 [libceph]
[ 27.307599] [] ? dequeue_task_fair+0x44e/0x660
[ 27.307599] [] ? put_prev_entity+0x31/0x3f0
[ 27.307599] [] ? sched_clock_cpu+0x98/0xc0
[ 27.307599] [] con_work+0xb9/0x620 [libceph]
[ 27.307599] [] process_one_work+0x14f/0x400
[ 27.307599] [] worker_thread+0x118/0x510
[ 27.307599] [] ? rescuer_thread+0x3d0/0x3d0
[ 27.307599] [] kthread+0xd2/0xf0
[ 27.307599] [] ? kthread_create_on_node+0x1c0/0x1c0
[ 27.307599] [] ret_from_fork+0x58/0x90
[ 27.307599] [] ? kthread_create_on_node+0x1c0/0x1c0
[ 27.307599] Code: e9 27 f9 ff ff 44 89 a3 70 02 00 00 48 89 de 4c 89 ef 44 89 
65 88 e8 a0 c3 ff ff 8b 45 88 e9 09 f9 ff ff 4c 63 e0 e9 d9 f9 ff ff <0f> 0b 49 
8b 8f 98 fc ff ff 4d 8b 87 a0 fc ff ff 4c 89 fa 48 c7 
[ 27.307599] RIP [] __prepare_send_request+0x7d0/0x800 [ceph]
[ 27.307599] RSP 
[ 27.379039] ---[ end trace 1928182fad693b4d ]---
[ 27.379983] BUG: unable to handle kernel paging request at ffd8
[ 27.381275] IP: [] kthread_data+0x10/0x20
[ 27.382382] PGD 1c19067 PUD 1c1b067 PMD 0 
[ 27.383004] Oops:  [#2] SMP 
[ 27.383004] Modules linked in: ceph libceph libcrc32c fscache ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi dm_crypt ppdev parport_pc 8250_fintek pvpanic serio_raw 
joydev parport i2c_piix4 mac_hid hid_generic usbhid hid syscopyarea sysfillrect 
sysimgblt ttm drm_kms_helper psmouse drm pata_acpi floppy
[ 27.383004] CPU: 0 PID: 118 Comm: kworker/0:2 Tainted: G D 3.19.0-56-generic 
#62~14.04.1-Ubuntu
[ 27.383004] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
1.7.5-20150310_111955-batsu 04/01/2014
[ 27.383004] task: 88007ca0ce80 ti: 88003657c000 task.ti: 
88003657c000
[ 27.383004] RIP: 0010:[] [] 
kthread_data+0x10/0x20
[ 27.383004] RSP: 0018:88003657f7c8 EFLAGS: 00010096
[ 27.383004] RAX:  RBX:  RCX: 000d
[ 27.383004] RDX:  RSI:  RDI: 88007ca0ce80
[ 27.383004] RBP: 88003657f7c8 R08:  R09: 0246
[ 27.383004] R10: 810721a4 R11: ea0001dfba00 R12: 88007ca0d3a0
[ 27.383004] R13:  R14:  R15: 88007ca0ce80
[ 27.383004] FS: () GS:88007fc0() 
knlGS:
[ 27.383004] CS: 0010 DS:  ES:  CR0: 8005003b
[ 27.383004] CR2: 0028 CR3: 36387000 CR4: 06f0
[ 27.383004] Stack:
[ 27.383004] 88003657f7e8 8108ed05 88003657

[Kernel-packages] [Bug 1564950] Re: Kernel panic when using CEPHFS (Hammer) /w kernel vivid-lts on Ubuntu 14.04

[Kamal Mostafa]

On Thu, Mar 31, 2016 at 12:06:42PM +0800, Yan, Zheng wrote:
> ubuntu-vivid git tree includes commit ebeec2ef4c (ceph: fix message
> length computation), but does not contain backport for upstream commit
> 1f041a89b4 (ceph: fix request time stamp encoding). This breaks cephfs
> kernel driver completely. Please add the later commit to your git
> tree.
>
> Regards
> Yan, Zheng


The patch [[ 1f041a89b4 (ceph: fix request time stamp encoding) ]] is required 
for all trees that carry a backport of 777d738 (ceph: fix message length 
computation):

  3.19.y-ckt (stable)
  3.16.y-ckt (stable)
  ubuntu-vivid
  ubuntu-utopic


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

** Also affects: linux-lts-utopic (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-vivid (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** No longer affects: linux-lts-utopic (Ubuntu Vivid)

** No longer affects: linux-lts-vivid (Ubuntu Vivid)

** No longer affects: linux (Ubuntu Trusty)

** Changed in: linux (Ubuntu Vivid)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux-lts-utopic (Ubuntu)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux-lts-utopic (Ubuntu Trusty)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux-lts-vivid (Ubuntu)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux-lts-vivid (Ubuntu Trusty)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  Kernel panic when using CEPHFS (Hammer) /w kernel vivid-lts on Ubuntu
  14.04

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  New
Status in linux-lts-vivid package in Ubuntu:
  New
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux source package in Vivid:
  New

Bug description:
  Reported by Dennis Kramer at http://tracker.ceph.com/issues/15302

  --

  Nowadays i'm getting a kernel panic when i use the vivid-lts (3.19.x)
  kernel on ubuntu 14.04 after I try to mount cephfs. Log indicates:

  kernel BUG at 
/build/linux-lts-vivid-ZTSmDy/linux-lts-vivid-3.19.0/fs/ceph/mds_client.c:1928[ 
27.305173] kernel BUG at 
/build/linux-lts-vivid-ZTSmDy/linux-lts-vivid-3.19.0/fs/ceph/mds_client.c:1928!
  [ 27.307226] invalid opcode:  [#1] SMP 
  [ 27.307599] Modules linked in: ceph libceph libcrc32c fscache ib_iser 
rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi dm_crypt ppdev parport_pc 8250_fintek pvpanic 
serio_raw joydev parport i2c_piix4 mac_hid hid_generic usbhid hid syscopyarea 
sysfillrect sysimgblt ttm drm_kms_helper psmouse drm pata_acpi floppy
  [ 27.307599] CPU: 0 PID: 118 Comm: kworker/0:2 Not tainted 3.19.0-56-generic 
#62~14.04.1-Ubuntu
  [ 27.307599] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
1.7.5-20150310_111955-batsu 04/01/2014
  [ 27.307599] Workqueue: ceph-msgr con_work [libceph]
  [ 27.307599] task: 88007ca0ce80 ti: 88003657c000 task.ti: 
88003657c000
  [ 27.307599] RIP: 0010:[] [] 
__prepare_send_request+0x7d0/0x800 [ceph]
  [ 27.307599] RSP: 0018:88003657fb48 EFLAGS: 00010283
  [ 27.307599] RAX: 880077e1bb02 RBX: 8800364af000 RCX: 
  [ 27.307599] RDX: 38a516d3 RSI:  RDI: 880077e1baf2
  [ 27.307599] RBP: 88003657fbe8 R08:  R09: 
  [ 27.307599] R10: c0275fe6 R11:  R12: 88007873c700
  [ 27.307599] R13: 880078458000 R14:  R15: 880077e1ba80
  [ 27.307599] FS: () GS:88007fc0() 
knlGS:
  [ 27.307599] CS: 0010 DS:  ES:  CR0: 8005003b
  [ 27.307599] CR2: 7ff6e2973000 CR3: 36387000 CR4: 06f0
  [ 27.307599] Stack:
  [ 27.307599] 88003657fb8c c02e1109 0115 
0001
  [ 27.307599] 8800362e0118 880077e1bafa 88003657fbe8 

  [ 27.307599]  8800362e0118  
0001
  [ 27.307599] Call Trace:
  [ 27.307599] [] ? __choose_mds+0x119/0x470 [ceph]
  [ 27.307599] [] __do_request+0x230/0x310 [ceph]
  [ 27.307599] [] __wake_requests+0x78/0xb0 [ceph]
  [ 27.307599] [] dispatch+0x550/0xad0 [ceph]
  [ 27.307599] [] try_read+0x4cb/0x10f0 [libceph]
  [ 27.307599] [] ? dequeue_task_fair+0x44e/0x660
  [ 27.307599] [] ? put_prev_entity+0x31/0x3f0
  [ 27.307599] [] ? sched_clock_cpu+0x98/0xc0
  [ 27.307599] [] con_work+0xb9/0x620 [libceph]
  [ 27.307599] [] process_one_work+0x14f/0x400
  [ 27.307599] [] worker_thread+0x118/0x510
  [ 27.307599] [] ? rescu

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

[Jeff Lane]

apport information

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

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A28
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrA28:

[Kernel-packages] [Bug 1564949] Lsusb.txt

[Jeff Lane]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1564949/+attachment/4619529/+files/Lsusb.txt

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A28
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrA28:bd02/06/2014:

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

[Jeff Lane]

apport information

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

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A28
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrA28:bd

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

[Jeff Lane]

apport information

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

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A28
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrA28:bd02/06/2014:

[Kernel-packages] [Bug 1564960] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1564960

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  mlx switchdev needs patches to work in 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  mlx switchdev is incomplete in 16.04.  A small set of patches will
  make it functional.  These apply mostly to mlxsw, although there are a
  few patches in net/bridge

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

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

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

[Jeff Lane]

apport information

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

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A28
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrA28:

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

[Jeff Lane]

apport information

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

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A28
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:b

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

[Jeff Lane]

apport information

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

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A28
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrA2

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

[Jeff Lane]

apport information

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

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A28
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvr

[Kernel-packages] [Bug 1564949] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A28
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrA28:bd02/06/2014:svnHP:pnProLiantDL385pGen8:pvr:cvnHP:ct

[Kernel-packages] [Bug 1564949] Re: Severe latency/skew on AMD Opetron processor

[Jeff Lane]

** Tags added: hwcert-server

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A28
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrA28:bd02/06/2014:svnHP:pnProLiantDL385pGen8:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL385p Gen8
  dmi.sys.vendor

[Kernel-packages] [Bug 1563095] Re: Install boots to a frozen screen

[Martin Wimpress]

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

** No longer affects: ubuntu-mate

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

Title:
  Install boots to a frozen screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ubantu-mate 16.04 beta2 powerpc

  Install disk boots to a frozen screen.  I had to add nouveau.noaccel=1
  then it booted to the mate desktop.

  Hardware PowerMac 7,2 with Nvidia GeForce 6800 GT

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

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

[Kernel-packages] [Bug 1564949] Re: Severe latency/skew on AMD Opetron processor

[Jeff Lane]

apport information

** Tags added: apport-collected uec-images xenial

** Description changed:

  Discovered this while doing pre-release certification testing for 16.04
  on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core CPU.
  
  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...
  
  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);
  
  where tval_start and tval_stop are timeval structs and sleeptime is 60.
  
  Once it gets the start and stop it finds the delta minus the sleep time.
  
  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.
  
  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).
  
  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89
  
  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62
  
  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933
  
  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033
  
  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending on
  what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are NOT
  expected and highly irregular.
  
  Colin said he tested this on an AMD C60 CPU and got numbers inline with
  the Skylake and s390 chips and could not reproduce the times I am seeing
  on the Opteron.
  
  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
+  crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20-0ubuntu3
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
+ IwConfig: Error: [Errno 2] No such file or directory
+ MachineType: HP ProLiant DL385p Gen8
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
+ ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-15-generic N/A
+  linux-backports-modules-4.4.0-15-generic  N/A
+  linux-firmware1.157
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  xenial uec-images
+ Uname: Linux 4.4.0-15-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 02/06/2014
+ dmi.bios.vendor: HP
+ dmi.bios.version: A28
+ dmi.chassis.type: 23
+ dmi.chassis.vendor: HP
+ dmi.modalias: 
dmi:bvnHP:bvrA28:bd02/06/2014:svnHP:pnProLiantDL385pGen8:pvr:cvnHP:ct23:cvr:
+ dmi.product.name: ProLiant DL385p Gen8
+ dmi.sys.vendor: HP

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

-- 
You received this bug notification because you are a member of Kernel
Package

[Kernel-packages] [Bug 1563095] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1563095

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Install boots to a frozen screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ubantu-mate 16.04 beta2 powerpc

  Install disk boots to a frozen screen.  I had to add nouveau.noaccel=1
  then it booted to the mate desktop.

  Hardware PowerMac 7,2 with Nvidia GeForce 6800 GT

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

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

[Kernel-packages] [Bug 1564046] Re: New install boot failure

[Martin Wimpress]

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

** No longer affects: ubuntu-mate

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

Title:
  New install boot failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu-Mate 16.04 Beta2

  PowerMac 11,2 2x2.3GHz 6.5GB
  GeForce 6600 Pcie 256MB

  Live session boots and works mostly normally, there was one crash that
  was automatically reported.  After installation was complete I
  rebooted the machine. The reboot failed with the following messages.

  [4.690249] RAMDISK: Incomplete write (13225 !=32768)
  [4.690408] write error
  [4.690744] Kernal panic - not syncing:  VFS: Unable to mount root fs on 
unknown-block(0,0)
  [4.690980] CPU: 1 PID: 1 Comm:  swapper/0 Not tainted 
4.4.0-15-powerpc64-smp #31-Ubuntu
  [4.691205] Call Trace:
  [4.691282] [c00201d67a40] [c0aca774] .dump_stack+0xa8/0xe8

  - seven more lines, I can type them if it is necessary-

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

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

[Kernel-packages] [Bug 1564046] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1564046

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  New install boot failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu-Mate 16.04 Beta2

  PowerMac 11,2 2x2.3GHz 6.5GB
  GeForce 6600 Pcie 256MB

  Live session boots and works mostly normally, there was one crash that
  was automatically reported.  After installation was complete I
  rebooted the machine. The reboot failed with the following messages.

  [4.690249] RAMDISK: Incomplete write (13225 !=32768)
  [4.690408] write error
  [4.690744] Kernal panic - not syncing:  VFS: Unable to mount root fs on 
unknown-block(0,0)
  [4.690980] CPU: 1 PID: 1 Comm:  swapper/0 Not tainted 
4.4.0-15-powerpc64-smp #31-Ubuntu
  [4.691205] Call Trace:
  [4.691282] [c00201d67a40] [c0aca774] .dump_stack+0xa8/0xe8

  - seven more lines, I can type them if it is necessary-

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

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

[Kernel-packages] [Bug 1564960] [NEW] mlx switchdev needs patches to work in 16.04

[Brian Fromme]

Public bug reported:

mlx switchdev is incomplete in 16.04.  A small set of patches will make
it functional.  These apply mostly to mlxsw, although there are a few
patches in net/bridge

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

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

Title:
  mlx switchdev needs patches to work in 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  mlx switchdev is incomplete in 16.04.  A small set of patches will
  make it functional.  These apply mostly to mlxsw, although there are a
  few patches in net/bridge

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

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

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

[Jeff Lane]

apport information

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

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A28
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrA28:bd02/06/201

[Kernel-packages] [Bug 1564949] Re: Severe latency/skew on AMD Opetron processor

[Colin Ian King]

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

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: HP
  dmi.bios.version: A28
  

[Kernel-packages] [Bug 264336] Re: pgsql fails to start due to shared buffer setting greater than kernel allows

[Moi]

can anyone help me I am getting that message on ubuntu I installed Ubuntu on my 
nexus 6 phone 
# service postgresql start
[] Starting PostgreSQL 9.4 database server: main[] The PostgreSQL 
server failed to start. Please check the log output: 2016-04-01 15:06:57 UTC 
[31454-1] FATAL: could not create shared memory segment: Function not 
implemented 2016-04-01 15:06:57 UTC [31454-2] DETAI[FAILiled system call was 
shmget(key=5432001, size=40, 03600). ... failed!
 failed!

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

Title:
  pgsql fails to start due to shared buffer setting greater than kernel
  allows

Status in linux package in Ubuntu:
  Won't Fix
Status in postgresql-8.3 package in Ubuntu:
  Won't Fix
Status in postgresql-9.1 package in Ubuntu:
  Confirmed
Status in postgresql-common package in Ubuntu:
  Invalid
Status in linux source package in Jaunty:
  Won't Fix
Status in postgresql-8.3 source package in Jaunty:
  Won't Fix
Status in postgresql-9.1 source package in Jaunty:
  Invalid
Status in postgresql-common source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: postgresql-8.3

  Freshly installed pgsql 8.3 on hardy got me this error when restarting:
  2008-09-03 09:16:39 EDT DETAIL:  Failed system call was shmget(key=5432001, 
size=38207488, 03600).
  2008-09-03 09:16:39 EDT HINT:  This error usually means that PostgreSQL's 
request for a shared memory segment exceeded your kernel's SHMMAX parameter.  
You can either reduce the request size or reconfigure the kernel with larger 
SHMMAX.  To reduce the request size (currently 38207488 bytes), reduce 
PostgreSQL's shared_buffers parameter (currently 4096) and/or its 
max_connections parameter (currently 103).
  If the request size is already small, it's possible that it is less 
than your kernel's SHMMIN parameter, in which case raising the request size or 
reconfiguring SHMMIN is called for.
  The PostgreSQL documentation contains more information about shared 
memory configuration.

  Checking the kernel settings:
  sudo sysctl -a | grep -i shm
  kernel.shmmax = 33554432
  kernel.shmall = 2097152
  kernel.shmmni = 4096

  The shared_buffers setting defaults to 32MB. I changed this down to
  25MB to test and then the server would start right up.

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

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

[Kernel-packages] [Bug 1546092] Re: computer freezes frequently

[Colin Ian King]

Any MCE log data?  If not, this bug will automatically close in 6 weeks.

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

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

Title:
  computer freezes frequently

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  Running Xenial. Freezes seem to happen every 5 to 45 minutes. I have
  not been able to create any repro steps, it feels quite random.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-4-generic 4.4.0-4.19
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rick   1780 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Feb 16 08:26:12 2016
  HibernationDevice: RESUME=UUID=36268acb-4215-452f-9778-754c015d00d8
  InstallationDate: Installed on 2016-02-02 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: TOSHIBA Satellite L15W-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic.efi.signed 
root=UUID=ed019e52-c90e-48b7-bbe4-ae5d39fea067 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-4-generic N/A
   linux-backports-modules-4.4.0-4-generic  N/A
   linux-firmware   1.155
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.00
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 0670
  dmi.board.vendor: FF40
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.00:bd07/16/2015:svnTOSHIBA:pnSatelliteL15W-B:pvrPSKVUU-00S01U:rvnFF40:rn0670:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Satellite L15W-B
  dmi.product.version: PSKVUU-00S01U
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1506817] Re: left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04)

[Jont Allen]

A lot has happened since I last checked in. Here is a quick Exec
Summary:

I was running kernel 4.5-rc3 and everything was great. Then sometime around Feb 
3, 2016 (I dont know the exact date),
following an standard upgrade from Ubuntu, the old symptoms (left mouse button 
sticking) returned. 
While I have some theories about what happened, I'll just stick to the facts 
(aka, synaptic touch pad (TP) bug).

Long story short, I reinstalled 15.10 from scratch on a new hard drive.
I went the path of 14.04 -> 15.10, for reasons I wont go into.

So I ended up with a brand new install of 15.10. This also, like the
system I abandoned, had the synaptic TP bug.

Next I installed the latest kernel 4.6
(vmlinuz-4.6.0-040600rc1-generic). This also showed the TP bug.

Finally I installed 4.5-rc3 (vmlinuz-4.5.0-040500rc3-generic). Amazing,
it worked, and the TP bug was gone!

Summary:
4.5rc3 started failing on 15.10 around Feb 3, following an upgrade, but once I 
installed it on a fresh system, it started to work.

More very important additional information:

1) It is now very easy to determine if the system will work (no TP bug) or will 
not work (TP bug) follwoing the boot, but before
login. If the synaptic touchpad responds (the mouse can be moved via the touch 
pad) BEFORE login, then the TP bug is present.

2) The presents of the TP bug is perfectly correlated with the post-boot
/pre-login test (i.e., the presents of the TPad being on, or off.)

3) The X250 BIOS (latest version) has an option to turn off the TPad,
and/or the TP mouse.

4) When I turn off the TPad using the BIOS, the non-working kernels ignore this 
BIOS option. Let me restate that:
When I turn off the TPad using the BIOS, every kernel that has the Pad bug, 
ignores the BIOS option. Kernel 4.5rc3, which 
does not show the TPad bug, honors the BIOS options.

5) If I turn ON the Tpad with 4.5rc3, the TPad bug is present.  Note
that this demonstrates that 4.5rc3 listens to the BIOS TP options.

Questions to you:
1) What should I do next, given this new information?
2) Has the problem been isolated to the synaptic modules? Is that how the TPad 
bug returned with the 4.5rc3 kernel? 
Opinion: It seems not to be the kernel, but something else, as I was booting 
4.5-rc3 when it started failing, around Feb 2.

END

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

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

Title:
  left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have reported the details of this problem at
  https://answers.launchpad.net/ubuntu-certification/+question/272142

  As summarized on that question:

  X250 analysis:
   I used the command on the X250
evtest /dev/input/event15 | grep EV_KEY

   I can see the bug, as follows:

  I click on button 1 (left) over and over. When I push the button down,
  I see it register as 1,
  and when I let go of the key, it registers as a 0.

  The bug is that every now and then (once every 20 clicks), when I let go
  of the left mouse button (BIN_LEFT), it does not return to state 0 (it stays 
in state 1).

  This is highly random, but cant be triggered more often, by dragging a
  window, which I do with BIN_LEFT.

  I am using a brand new X250, purchased in late July 2015. The system was 
returned 3 times to IBM repair as I assumed
  this was a hardware error. Now with the above, it seems clear that this is a 
software issue.

  Ubuntu 15.04

  apt-cache policy xserver-xorg-input-synaptics
  xserver-xorg-input-synaptics:
Installed: 1.8.1-1ubuntu1
Candidate: 1.8.1-1ubuntu1
Version table:
   *** 1.8.1-1ubuntu1 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-input-synaptics 1.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 16 04:52:03 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  InstallationDate: Installed on 2015-08-15 (61 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CMCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed 
root=UUID=5718b40f-944e-47a3-acda-04e29336d0bc ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET36W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dm

[Kernel-packages] [Bug 1565029] [NEW] bcache doesn't register/recognize devices on s390x

[Ryan Harper]

Public bug reported:


1. #  cat /proc/version_signature
Ubuntu 4.4.0-16.32-generic 4.4.6

# no pci on s390x, but none-the-less
2. root@ubuntu:~# sudo lspci -vnvn
root@ubuntu:~#

# lsb_release -rd
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04

# apt-cache policy linux-image-generic
linux-image-generic:
  Installed: 4.4.0.16.17
  Candidate: 4.4.0.16.17
  Version table:
 *** 4.4.0.16.17 500
500 http://us.ports.ubuntu.com/ubuntu-ports xenial/main s390x Packages
100 /var/lib/dpkg/status

3. bcache cache and backing devices auto register when created (or can
be registered manually vi /sys/fs/bcache/register

4. what currently happens:

- modprobe bcache
- create a cache device and a backing device

# make-bcache -C /dev/vda1
# make-bcache -B /dev/vda2

on amd64, the cache device is automatically registered, on s390x, there
is a kernel error

[ 4127.805719] bcache: register_bcache() error opening /dev/vda1: Not a
bcache superblock

But bcache-show-super says it's fine:

# bcache-super-show /dev/vda1
sb.magicok
sb.first_sector 8 [match]
sb.csum 70C54F690E440FF5 [match]
sb.version  1 [backing device]

dev.label   (empty)
dev.uuid83e7fe43-66d9-4cf1-8050-8469e869
dev.sectors_per_block   8
dev.sectors_per_bucket  1024
dev.data.first_sector   16
dev.data.cache_mode 0 [writethrough]
dev.data.cache_state0 [detached]

cset.uuid   72f737d7-0dc6-491a-929c-37a4b3e8d058

echo "/dev/vda1" | sudo tee /sys/fs/bcache/register  fails as well,
with:

bash: echo: write error: Invalid argument

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.16.17
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic s390x
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20-0ubuntu3
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Date: Fri Apr  1 11:52:00 2016
IwConfig:
 lono wireless extensions.
 
 docker0   no wireless extensions.
 
 eth0  no wireless extensions.
Lspci:
 
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C
 SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=2a60026a-b696-4b21-88df-e7fc236f4472
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-2-generic N/A
 linux-backports-modules-4.4.0-2-generic  N/A
 linux-firmware   1.157
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug s390x xenial

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

Title:
  bcache doesn't register/recognize devices on s390x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  1. #  cat /proc/version_signature
  Ubuntu 4.4.0-16.32-generic 4.4.6

  # no pci on s390x, but none-the-less
  2. root@ubuntu:~# sudo lspci -vnvn
  root@ubuntu:~#

  # lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  # apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 4.4.0.16.17
Candidate: 4.4.0.16.17
Version table:
   *** 4.4.0.16.17 500
  500 http://us.ports.ubuntu.com/ubuntu-ports xenial/main s390x Packages
  100 /var/lib/dpkg/status

  3. bcache cache and backing devices auto register when created (or can
  be registered manually vi /sys/fs/bcache/register

  4. what currently happens:

  - modprobe bcache
  - create a cache device and a backing device

  # make-bcache -C /dev/vda1
  # make-bcache -B /dev/vda2

  on amd64, the cache device is automatically registered, on s390x,
  there is a kernel error

  [ 4127.805719] bcache: register_bcache() error opening /dev/vda1: Not
  a bcache superblock

  But bcache-show-super says it's fine:

  # bcache-super-show /dev/vda1
  sb.magic  ok
  sb.first_sector   8 [match]
  sb.csum   70C54F690E440FF5 [match]
  sb.version1 [backing device]

  dev.label (empty)
  dev.uuid  83e7fe43-66d9-4cf1-8050-8469e869
  dev.sectors_per_block 8
  dev.sectors_per_bucket1024
  dev.data.first_sector 16
  dev.data.cache_mode   0 [writethrough]
  dev.data.cache_state  0 [detached]

  cset.uuid   72f737d7-0dc6-491a-929c-37a4b3e8d058

  echo 

[Kernel-packages] [Bug 1565029] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1565029

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  bcache doesn't register/recognize devices on s390x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  1. #  cat /proc/version_signature
  Ubuntu 4.4.0-16.32-generic 4.4.6

  # no pci on s390x, but none-the-less
  2. root@ubuntu:~# sudo lspci -vnvn
  root@ubuntu:~#

  # lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  # apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 4.4.0.16.17
Candidate: 4.4.0.16.17
Version table:
   *** 4.4.0.16.17 500
  500 http://us.ports.ubuntu.com/ubuntu-ports xenial/main s390x Packages
  100 /var/lib/dpkg/status

  3. bcache cache and backing devices auto register when created (or can
  be registered manually vi /sys/fs/bcache/register

  4. what currently happens:

  - modprobe bcache
  - create a cache device and a backing device

  # make-bcache -C /dev/vda1
  # make-bcache -B /dev/vda2

  on amd64, the cache device is automatically registered, on s390x,
  there is a kernel error

  [ 4127.805719] bcache: register_bcache() error opening /dev/vda1: Not
  a bcache superblock

  But bcache-show-super says it's fine:

  # bcache-super-show /dev/vda1
  sb.magic  ok
  sb.first_sector   8 [match]
  sb.csum   70C54F690E440FF5 [match]
  sb.version1 [backing device]

  dev.label (empty)
  dev.uuid  83e7fe43-66d9-4cf1-8050-8469e869
  dev.sectors_per_block 8
  dev.sectors_per_bucket1024
  dev.data.first_sector 16
  dev.data.cache_mode   0 [writethrough]
  dev.data.cache_state  0 [detached]

  cset.uuid   72f737d7-0dc6-491a-929c-37a4b3e8d058

  echo "/dev/vda1" | sudo tee /sys/fs/bcache/register  fails as well,
  with:

  bash: echo: write error: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.16.17
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20-0ubuntu3
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Fri Apr  1 11:52:00 2016
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=2a60026a-b696-4b21-88df-e7fc236f4472
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Alex Ng]

Thanks for going through this testing.

Based on your results, I looked at the Hyper-V related commits in
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git between
3.13.0-26.48 (GOOD) and 3.13.0-35.62 (BAD).

>From reviewing these commits, there doesn't seem to be an obvious
culprit. But it's possible that anyone of the following could affect
storage driver behavior. Looking forward to seeing what you uncover in
your bisect.

- a61e9104ea3b183a3b3cfdaa43145e1cd26b21ff Drivers: hv: vmbus: Negotiate 
version 3.0 when running on ws2012r2 hosts
- c8c38b34f5790366d98306c1fc418ddff1b0357b Drivers: hv: vmbus: Fix a bug in the 
channel callback dispatch code

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Joseph Salisbury]

I'll continue to provide updates.  Sorry the bisect is taking a long
time.  It requires at least 8 hours of testing for each test kernel, to
be sure it does not have the bug.

On a positive not, when a kernel is bad, it usually fails within two
hours, which allows me to kick off the next test quicker.  However, I'd
just rather not assume a kernel is good if it runs for longer than two
hours.

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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

[Kernel-packages] [Bug 1565029] Re: bcache doesn't register/recognize devices on s390x

[Joseph Salisbury]

** Tags added: bot-stop-nagging

** Tags added: kernel-da-key

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  bcache doesn't register/recognize devices on s390x

Status in linux package in Ubuntu:
  Triaged

Bug description:
  
  1. #  cat /proc/version_signature
  Ubuntu 4.4.0-16.32-generic 4.4.6

  # no pci on s390x, but none-the-less
  2. root@ubuntu:~# sudo lspci -vnvn
  root@ubuntu:~#

  # lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  # apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 4.4.0.16.17
Candidate: 4.4.0.16.17
Version table:
   *** 4.4.0.16.17 500
  500 http://us.ports.ubuntu.com/ubuntu-ports xenial/main s390x Packages
  100 /var/lib/dpkg/status

  3. bcache cache and backing devices auto register when created (or can
  be registered manually vi /sys/fs/bcache/register

  4. what currently happens:

  - modprobe bcache
  - create a cache device and a backing device

  # make-bcache -C /dev/vda1
  # make-bcache -B /dev/vda2

  on amd64, the cache device is automatically registered, on s390x,
  there is a kernel error

  [ 4127.805719] bcache: register_bcache() error opening /dev/vda1: Not
  a bcache superblock

  But bcache-show-super says it's fine:

  # bcache-super-show /dev/vda1
  sb.magic  ok
  sb.first_sector   8 [match]
  sb.csum   70C54F690E440FF5 [match]
  sb.version1 [backing device]

  dev.label (empty)
  dev.uuid  83e7fe43-66d9-4cf1-8050-8469e869
  dev.sectors_per_block 8
  dev.sectors_per_bucket1024
  dev.data.first_sector 16
  dev.data.cache_mode   0 [writethrough]
  dev.data.cache_state  0 [detached]

  cset.uuid   72f737d7-0dc6-491a-929c-37a4b3e8d058

  echo "/dev/vda1" | sudo tee /sys/fs/bcache/register  fails as well,
  with:

  bash: echo: write error: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.16.17
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20-0ubuntu3
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Fri Apr  1 11:52:00 2016
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=2a60026a-b696-4b21-88df-e7fc236f4472
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1564960] Re: mlx switchdev needs patches to work in 16.04

[Joseph Salisbury]

Hi Brian,

Will the patches be sent to the kernel team mailing list?   They could
also be listed in this bug report.

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

** Tags added: kernel-da-key

** Tags added: xenial

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

Title:
  mlx switchdev needs patches to work in 16.04

Status in linux package in Ubuntu:
  Triaged

Bug description:
  mlx switchdev is incomplete in 16.04.  A small set of patches will
  make it functional.  These apply mostly to mlxsw, although there are a
  few patches in net/bridge

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

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

[Kernel-packages] [Bug 1565016] Re: [2.0a4] Xenial deploy boot-initrd timeout and kernel panic

[Andres Rodriguez]

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

my guess is that a new kernel or a new package has hit xenial, and that
is causing the kernel to panic. THe maas images automatically use newest
stuff on the archives.

** Also affects: maas-images
   Importance: Undecided
   Status: New

** No longer affects: maas

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

** No longer affects: linux (Ubuntu)

** This bug has been marked a duplicate of bug 1563779
   [2.0a4] maas-rackd missing presumed lost

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

Title:
  [2.0a4] Xenial deploy boot-initrd timeout and kernel panic

Status in maas-images:
  New

Bug description:
  1. Installed MAAS 2.0 alpha 4
  2. Enlisted and commissioned 2 HP ProLiant DL360 Gen9 servers.
  3. Used the UI to select Xenial for deployment.
  4. From the server console observed a timeout attempting to TFTP boot-initrd 
followed by a kernel panic.

  ii  maas   2.0.0~alpha4+bzr4843-0ubuntu1   all
  "Metal as a Service" is a physical cloud and IPAM
  ii  maas-cli   2.0.0~alpha4+bzr4843-0ubuntu1   all
  MAAS client and command-line interface
  ii  maas-common2.0.0~alpha4+bzr4843-0ubuntu1   all
  MAAS server common files
  ii  maas-dhcp  2.0.0~alpha4+bzr4843-0ubuntu1   all
  MAAS DHCP server
  ii  maas-dns   2.0.0~alpha4+bzr4843-0ubuntu1   all
  MAAS DNS server
  ii  maas-proxy 2.0.0~alpha4+bzr4843-0ubuntu1   all
  MAAS Caching Proxy
  ii  maas-rack-controller   2.0.0~alpha4+bzr4843-0ubuntu1   all
  Rack Controller for MAAS
  ii  maas-region-api2.0.0~alpha4+bzr4843-0ubuntu1   all
  Region controller API service for MAAS
  ii  maas-region-controller 2.0.0~alpha4+bzr4843-0ubuntu1   all
  Region Controller for MAAS
  ii  python3-django-maas2.0.0~alpha4+bzr4843-0ubuntu1   all
  MAAS server Django web framework (Python 3)
  ii  python3-maas-client2.0.0~alpha4+bzr4843-0ubuntu1   all
  MAAS python API client (Python 3)
  ii  python3-maas-provisioningserver2.0.0~alpha4+bzr4843-0ubuntu1   all
  MAAS server provisioning libraries (Python 3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1565016/+subscriptions

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

[Kernel-packages] [Bug 1564950] Re: Kernel panic when using CEPHFS (Hammer) /w kernel vivid-lts on Ubuntu 14.04

[Kamal Mostafa]

I've constructed a test kernel for Ubuntu Vivid (amd64), comprised of
3.19.0-56.62 plus 1f041a89b4 (ceph: fix request time stamp encoding).
Please confirm that this test kernel fixes the problem (installing just
the linux-image-3.19...deb should be sufficient):

http://kernel.ubuntu.com/~kamal/lp1564950/

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

Title:
  Kernel panic when using CEPHFS (Hammer) /w kernel vivid-lts on Ubuntu
  14.04

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  New
Status in linux-lts-vivid package in Ubuntu:
  New
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux source package in Vivid:
  New

Bug description:
  Reported by Dennis Kramer at http://tracker.ceph.com/issues/15302

  --

  Nowadays i'm getting a kernel panic when i use the vivid-lts (3.19.x)
  kernel on ubuntu 14.04 after I try to mount cephfs. Log indicates:

  kernel BUG at 
/build/linux-lts-vivid-ZTSmDy/linux-lts-vivid-3.19.0/fs/ceph/mds_client.c:1928[ 
27.305173] kernel BUG at 
/build/linux-lts-vivid-ZTSmDy/linux-lts-vivid-3.19.0/fs/ceph/mds_client.c:1928!
  [ 27.307226] invalid opcode:  [#1] SMP 
  [ 27.307599] Modules linked in: ceph libceph libcrc32c fscache ib_iser 
rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi dm_crypt ppdev parport_pc 8250_fintek pvpanic 
serio_raw joydev parport i2c_piix4 mac_hid hid_generic usbhid hid syscopyarea 
sysfillrect sysimgblt ttm drm_kms_helper psmouse drm pata_acpi floppy
  [ 27.307599] CPU: 0 PID: 118 Comm: kworker/0:2 Not tainted 3.19.0-56-generic 
#62~14.04.1-Ubuntu
  [ 27.307599] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
1.7.5-20150310_111955-batsu 04/01/2014
  [ 27.307599] Workqueue: ceph-msgr con_work [libceph]
  [ 27.307599] task: 88007ca0ce80 ti: 88003657c000 task.ti: 
88003657c000
  [ 27.307599] RIP: 0010:[] [] 
__prepare_send_request+0x7d0/0x800 [ceph]
  [ 27.307599] RSP: 0018:88003657fb48 EFLAGS: 00010283
  [ 27.307599] RAX: 880077e1bb02 RBX: 8800364af000 RCX: 
  [ 27.307599] RDX: 38a516d3 RSI:  RDI: 880077e1baf2
  [ 27.307599] RBP: 88003657fbe8 R08:  R09: 
  [ 27.307599] R10: c0275fe6 R11:  R12: 88007873c700
  [ 27.307599] R13: 880078458000 R14:  R15: 880077e1ba80
  [ 27.307599] FS: () GS:88007fc0() 
knlGS:
  [ 27.307599] CS: 0010 DS:  ES:  CR0: 8005003b
  [ 27.307599] CR2: 7ff6e2973000 CR3: 36387000 CR4: 06f0
  [ 27.307599] Stack:
  [ 27.307599] 88003657fb8c c02e1109 0115 
0001
  [ 27.307599] 8800362e0118 880077e1bafa 88003657fbe8 

  [ 27.307599]  8800362e0118  
0001
  [ 27.307599] Call Trace:
  [ 27.307599] [] ? __choose_mds+0x119/0x470 [ceph]
  [ 27.307599] [] __do_request+0x230/0x310 [ceph]
  [ 27.307599] [] __wake_requests+0x78/0xb0 [ceph]
  [ 27.307599] [] dispatch+0x550/0xad0 [ceph]
  [ 27.307599] [] try_read+0x4cb/0x10f0 [libceph]
  [ 27.307599] [] ? dequeue_task_fair+0x44e/0x660
  [ 27.307599] [] ? put_prev_entity+0x31/0x3f0
  [ 27.307599] [] ? sched_clock_cpu+0x98/0xc0
  [ 27.307599] [] con_work+0xb9/0x620 [libceph]
  [ 27.307599] [] process_one_work+0x14f/0x400
  [ 27.307599] [] worker_thread+0x118/0x510
  [ 27.307599] [] ? rescuer_thread+0x3d0/0x3d0
  [ 27.307599] [] kthread+0xd2/0xf0
  [ 27.307599] [] ? kthread_create_on_node+0x1c0/0x1c0
  [ 27.307599] [] ret_from_fork+0x58/0x90
  [ 27.307599] [] ? kthread_create_on_node+0x1c0/0x1c0
  [ 27.307599] Code: e9 27 f9 ff ff 44 89 a3 70 02 00 00 48 89 de 4c 89 ef 44 
89 65 88 e8 a0 c3 ff ff 8b 45 88 e9 09 f9 ff ff 4c 63 e0 e9 d9 f9 ff ff <0f> 0b 
49 8b 8f 98 fc ff ff 4d 8b 87 a0 fc ff ff 4c 89 fa 48 c7 
  [ 27.307599] RIP [] __prepare_send_request+0x7d0/0x800 
[ceph]
  [ 27.307599] RSP 
  [ 27.379039] ---[ end trace 1928182fad693b4d ]---
  [ 27.379983] BUG: unable to handle kernel paging request at ffd8
  [ 27.381275] IP: [] kthread_data+0x10/0x20
  [ 27.382382] PGD 1c19067 PUD 1c1b067 PMD 0 
  [ 27.383004] Oops:  [#2] SMP 
  [ 27.383004] Modules linked in: ceph libceph libcrc32c fscache ib_iser 
rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi dm_crypt ppdev parport_pc 8250_fintek pvpanic 
serio_raw joydev parport i2c_piix4 mac_hid hid_generic usbhid hid syscopyarea 
sysfillrect sysimgblt ttm drm_kms_helper psmouse drm pata_acpi floppy
  [ 27.383004] CPU: 0 PID: 118 Comm: kworker/0:2 Tainted: G D 3.19.0-56-generic 
#62~14.04.1-Ubuntu
  [ 27.383004] Har

[Kernel-packages] [Bug 1564901] Re: xpad rumble causes full system hang

[Joseph Salisbury]

I built a Xenial test kernel with a pick of commit 7fc595f.  This test kernel 
can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1564901/

Can you test this kernel and see if it resolves this bug?

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

Title:
  xpad rumble causes full system hang

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To reproduce:

  1. Have a wired xbox controller.
  2. Modify the SDL2 testrumble.c so it runs forever. (attached)
  3. Build and run it.
  4. Kill it with sigkill from another terminal.

  Expected result: The program should stop running.

  Actual result: Entire computer freezes. Soundcard continuously plays
  the last second of audio. No response from any input devices or the
  network.

  The bug can also be reproduced by playing the game Borderlands 2 while
  having a wired xbox controller connected. The system will randomly
  freeze in the exact same way.

  The bug has existed since at least 14.04.

  The last thing the kernel prints is this:

  Apr  1 03:38:29 al-desktop kernel: [94142.404218] usb 7-3: new full-speed USB 
device number 2 using ohci-pci
  Apr  1 03:38:29 al-desktop kernel: [94142.565264] usb 7-3: New USB device 
found, idVendor=045e, idProduct=0288
  Apr  1 03:38:29 al-desktop kernel: [94142.565268] usb 7-3: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
  Apr  1 03:38:29 al-desktop kernel: [94142.567304] hub 7-3:1.0: USB hub found
  Apr  1 03:38:29 al-desktop kernel: [94142.569259] hub 7-3:1.0: 3 ports 
detected
  Apr  1 03:38:29 al-desktop kernel: [94142.852248] usb 7-3.1: new full-speed 
USB device number 3 using ohci-pci
  Apr  1 03:38:29 al-desktop kernel: [94142.949301] usb 7-3.1: New USB device 
found, idVendor=045e, idProduct=0289
  Apr  1 03:38:29 al-desktop kernel: [94142.949308] usb 7-3.1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
  Apr  1 03:38:29 al-desktop kernel: [94142.982402] input: Microsoft X-Box pad 
v2 (US) as 
/devices/pci:00/:00:13.0/usb7/7-3/7-3.1/7-3.1:1.0/input/input23
  Apr  1 03:38:29 al-desktop kernel: [94142.982503] usbcore: registered new 
interface driver xpad
  Apr  1 03:40:09 al-desktop kernel: [94242.318271] [ cut here 
]
  Apr  1 03:40:09 al-desktop kernel: [94242.318280] WARNING: CPU: 3 PID: 16529 
at /build/linux-_Kv5oI/linux-4.2.0/drivers/usb/core/urb.c:339 
usb_submit_urb+0x51/0x70()
  Apr  1 03:40:09 al-desktop kernel: [94242.318282] URB 880106cbacc0 
submitted while active
  Apr  1 03:40:09 al-desktop kernel: [94242.318283] Modules linked in: joydev 
xpad ff_memless nvidia_uvm(POE) rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) rc_pinnacle_pctv_hd em28xx_rc tda18271 cxd2820r 
em28xx_dvb d
  vb_core em28xx binfmt_misc bnep snd_hda_codec_hdmi rc_hauppauge ir_kbd_i2c 
tuner_simple tuner_types input_leds tuner uvcvideo videobuf2_vmalloc kvm_amd 
videobuf2_memops kvm btusb videobuf2_core btrtl snd_seq_midi btbcm 
snd_seq_midi_event 
  btintel snd_usb_audio snd_usbmidi_lib snd_hda_codec_via msp3400 
snd_hda_codec_generic snd_rawmidi bluetooth nvidia(POE) snd_seq serio_raw 
snd_hda_intel snd_seq_device snd_hda_codec snd_hda_core snd_hwdep bttv k10temp 
tea575x tveeprom edac
  _core videobuf_dma_sg edac_mce_amd rc_core videobuf_core snd_bt87x 
v4l2_common videodev snd_pcm media i2c_algo_bit snd_timer i2c_piix4 snd 
soundcore drm shpchp wmi 8250_fintek asus_atk0110 mac_hid parport_pc ppdev lp 
parport autofs4 uas u
  sb_storage hid_generic usbhid hid pata_acpi psmouse pata_atiixp ahci libahci 
r8169 mii
  Apr  1 03:40:09 al-desktop kernel: [94242.318324] CPU: 3 PID: 16529 Comm: 
testrumble Tainted: P   OE   4.2.0-34-generic #39-Ubuntu
  Apr  1 03:40:09 al-desktop kernel: [94242.318326] Hardware name: System 
manufacturer System Product Name/M4A79XTD EVO, BIOS 210206/17/2010
  Apr  1 03:40:09 al-desktop kernel: [94242.318328]   
4da02d75 88010a9c3ba8 817ebed3
  Apr  1 03:40:09 al-desktop kernel: [94242.318330]   
88010a9c3c00 88010a9c3be8 8107b986
  Apr  1 03:40:09 al-desktop kernel: [94242.318331]  88010a9c3bd8 
0010 880103216f08 88010a9c3cd0
  Apr  1 03:40:09 al-desktop kernel: [94242.318333] Call Trace:
  Apr  1 03:40:09 al-desktop kernel: [94242.318337]  [] 
dump_stack+0x45/0x57
  Apr  1 03:40:09 al-desktop kernel: [94242.318340]  [] 
warn_slowpath_common+0x86/0xc0
  Apr  1 03:40:09 al-desktop kernel: [94242.318342]  [] 
warn_slowpath_fmt+0x55/0x70
  Apr  1 03:40:09 al-desktop kernel: [94242.318345]  [] 
usb_submit_urb+0x51/0x70
  Apr  1 03:40:09 al-desktop kernel: [94242.318348]  [] 
xpad_play_effect+0x130/0x240 [xpad]
  Apr  1 03:40:09 al-desktop kernel: [94242.318351]  [] 
ml_play_effects+0x104/0x6b0 [ff_memless]
  Apr  1 03:40:09 al-desktop kernel: [94242.318353]  [] 
ml_ff_pl

[Kernel-packages] [Bug 1564487] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash (s390x, ppc64)

[Launchpad Bug Tracker]

This bug was fixed in the package crash - 7.1.4-1ubuntu4

---
crash (7.1.4-1ubuntu4) xenial; urgency=medium

  * d/p/0002-Fix-for-the-changes-made-to-the-kernel-module-struct.patch:
Cherry-pick additional crash commit needed to fix issues related to
kernel commit 8244062e. (LP: #1564487)

 -- Chris J Arges   Fri, 01 Apr 2016
08:46:07 -0500

** Changed in: crash (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash
  (s390x, ppc64)

Status in crash package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-03-31 02:19:27 ==
  ---Problem Description---
  With the kexec-tools comes from 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=136588#c58 , we have dumpped a 
vmcore for bug 139815 after quiting from xmon. But when trying to analyse with 
crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.4.0-15-generic
  /var/crash/201603310043/dump.201603310043

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  crash: invalid structure member offset: module_num_symtab
 FILE: kernel.c  LINE: 3450  FUNCTION: module_init()

  [/usr/bin/crash] error trace: 1008af0c => 10124250 => 10179bd0 =>
  10083378

10083378: (undetermined)
10179bd0: OFFSET_verify+80
10124250: module_init+1104
1008af0c: main_loop+764

  %

  == Comment: #4 - Hari Krishna Bathini - 2016-03-31 08:20:39 ==
  (In reply to comment #2)
  > Hi, 
  > 
  > Crash failing with 4.4+ kernels is a known issue which is fixed by the
  > upstream patch 
  > 
  > commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
  > Author: Dave Anderson 
  > Date:   Wed Jan 20 09:56:36 2016 -0500
  > 
  > Fix for the changes made to the kernel module structure introduced by
  > this kernel commit for Linux 4.5 and later kernels:
  > 
  >   commit 7523e4dc5057e157212b4741abd6256e03404cf1
  >   module: use a structure to encapsulate layout.
  > 
  > Without the patch, the crash session fails during initialization
  > with the error message: "crash: invalid structure member offset:
  > module_init_text_size".
  > (seb...@linux.vnet.ibm.com)
  > 

  We also need the below upstream patch along with the patch mentioned
  above to fix this issue

  commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
  Author: Dave Anderson 
  Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:
  
commit 8244062ef1e54502ef55f54cced659913f244c3e
modules: fix longstanding /proc/kallsyms vs module insertion race.
  
  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

  Thanks
  Hari

  == Comment: #9 - Hendrik Brueckner - 2016-03-31 11:47:13 ==
  Problem also exists on s390x:

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

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

[Kernel-packages] [Bug 1564960] Re: mlx switchdev needs patches to work in 16.04

[Brian Fromme]

rtg already integrated the patches and put the results here:
git://kernel.ubuntu.com/rtg/ubuntu-xenial.git mellanox

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

Title:
  mlx switchdev needs patches to work in 16.04

Status in linux package in Ubuntu:
  Triaged

Bug description:
  mlx switchdev is incomplete in 16.04.  A small set of patches will
  make it functional.  These apply mostly to mlxsw, although there are a
  few patches in net/bridge

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

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

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Dominik Franz]

Take your time. I'm incredibly thankful that somebody is taking care of
this. This bug already cost me a substantial amount of time and so far I
found no way of fixing it (except using an old kernel).

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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

[Kernel-packages] [Bug 1564487] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash (s390x, ppc64)

[Breno Leitão]

The package just appeared in the archive and I was able to try it on
ppc64el.

 sudo crash /usr/lib/debug/boot/vmlinux-4.4.0-16-generic
dump.201603291717

crash 7.1.4
Copyright (C) 2002-2015  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.
 
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-16-generic
DUMPFILE: dump.201603291717  [PARTIAL DUMP]
CPUS: 8
DATE: Tue Mar 29 17:17:45 2016
  UPTIME: 01:41:34
LOAD AVERAGE: 0.07, 0.23, 0.22
   TASKS: 873
NODENAME: 1604
 RELEASE: 4.4.0-16-generic
 VERSION: #32-Ubuntu SMP Thu Mar 24 22:31:14 UTC 2016
 MACHINE: ppc64le  (3425 Mhz)
  MEMORY: 8 GB
   PANIC: "sysrq: SysRq : Trigger a crash"
 PID: 8951
 COMMAND: "bash"
TASK: c3debd90  [THREAD_INFO: c001f6c4c000]
 CPU: 7
   STATE: TASK_RUNNING (SYSRQ)


crash> dmesg | tail
[ 6094.597764] [c001f6c4fd90] [c02e1940] vfs_write+0xc0/0x230
[ 6094.597845] [c001f6c4fde0] [c02e297c] SyS_write+0x6c/0x110
[ 6094.597926] [c001f6c4fe30] [c0009204] system_call+0x38/0xb4
[ 6094.598005] Instruction dump:
[ 6094.598047] 3842e9a0 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
39494ee4 
[ 6094.598181] 3921 912a 7c0004ac 3940 <992a> 38210020 e8010010 
7c0803a6 
[ 6094.598336] ---[ end trace 02e18198e9ef49b7 ]---
[ 6094.601009] 
[ 6094.601080] Sending IPI to other CPUs
[ 6094.604482] IPI complete

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

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: cannot analyse vmcore with crash
  (s390x, ppc64)

Status in crash package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-03-31 02:19:27 ==
  ---Problem Description---
  With the kexec-tools comes from 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=136588#c58 , we have dumpped a 
vmcore for bug 139815 after quiting from xmon. But when trying to analyse with 
crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.4.0-15-generic
  /var/crash/201603310043/dump.201603310043

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  crash: invalid structure member offset: module_num_symtab
 FILE: kernel.c  LINE: 3450  FUNCTION: module_init()

  [/usr/bin/crash] error trace: 1008af0c => 10124250 => 10179bd0 =>
  10083378

10083378: (undetermined)
10179bd0: OFFSET_verify+80
10124250: module_init+1104
1008af0c: main_loop+764

  %

  == Comment: #4 - Hari Krishna Bathini - 2016-03-31 08:20:39 ==
  (In reply to comment #2)
  > Hi, 
  > 
  > Crash failing with 4.4+ kernels is a known issue which is fixed by the
  > upstream patch 
  > 
  > commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
  > Author: Dave Anderson 
  > Date:   Wed Jan 20 09:56:36 2016 -0500
 

[Kernel-packages] [Bug 1541361] Re: Unable to load aufs module

[Jonathan Harker]

This has been tracked to a bug in our cloud disk image cloning tool
creating corrupt qcow images.

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

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

Title:
  Unable to load aufs module

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Attempting to load the aufs kernel module results in an error

  $ sudo modprobe aufs
  modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open 
moddep file '/lib/modules/3.13.0-77-generic/modules.dep.bin'

  $ file /lib/modules/3.13.0-77-generic/modules.dep.bin
  /lib/modules/3.13.0-77-generic/modules.dep.bin: empty

  $ uname -a
  Linux template-bare-trusty-1454450408 3.13.0-77-generic #121-Ubuntu SMP Wed 
Jan 20 10:50:42 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo aptitude search aufs
  i   aufs-tools
  - Tools to manage aufs filesystems
 
  p   aufs-tools-dbg
  - Tools to manage aufs filesystems (debug)

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

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

[Kernel-packages] [Bug 1565087] [NEW] Ubuntu no longer can read SD Cards (external reader)

[Tommy_CZ]

Public bug reported:

After upgrade to 16.04, Ubuntu no longer detects SD Cards in my SD Card
reader (external -> USB). Before upgrade (from 15.10) it was OK.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-16-generic 4.4.0-16.32
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  tomas  1881 F pulseaudio
 /dev/snd/controlC2:  tomas  1881 F pulseaudio
 /dev/snd/controlC0:  tomas  1881 F pulseaudio
CurrentDesktop: KDE
Date: Fri Apr  1 22:48:28 2016
HibernationDevice: RESUME=UUID=7b4a2bc3-8fd2-4684-b322-2c990980a5ac
InstallationDate: Installed on 2015-12-13 (110 days ago)
InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: MSI MS-7693
ProcEnviron:
 LANGUAGE=cs
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=520db00b-7805-4f04-8c0c-31acfe536389 ro iommu=soft quiet splash 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-16-generic N/A
 linux-backports-modules-4.4.0-16-generic  N/A
 linux-firmware1.157
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-03-21 (11 days ago)
dmi.bios.date: 12/16/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V22.2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 970 GAMING (MS-7693)
dmi.board.vendor: MSI
dmi.board.version: 4.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 4.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV22.2:bd12/16/2014:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0:
dmi.product.name: MS-7693
dmi.product.version: 4.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug xenial

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

Title:
  Ubuntu no longer can read SD Cards (external reader)

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrade to 16.04, Ubuntu no longer detects SD Cards in my SD
  Card reader (external -> USB). Before upgrade (from 15.10) it was OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tomas  1881 F pulseaudio
   /dev/snd/controlC2:  tomas  1881 F pulseaudio
   /dev/snd/controlC0:  tomas  1881 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Apr  1 22:48:28 2016
  HibernationDevice: RESUME=UUID=7b4a2bc3-8fd2-4684-b322-2c990980a5ac
  InstallationDate: Installed on 2015-12-13 (110 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7693
  ProcEnviron:
   LANGUAGE=cs
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=520db00b-7805-4f04-8c0c-31acfe536389 ro iommu=soft quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-03-21 (11 days ago)
  dmi.bios.date: 12/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V22.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970 GAMING (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV22.2:bd12/16/2014:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0:
  dmi.product.name: MS-7693
  dmi.product.version: 4.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1565087] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  Ubuntu no longer can read SD Cards (external reader)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 16.04, Ubuntu no longer detects SD Cards in my SD
  Card reader (external -> USB). Before upgrade (from 15.10) it was OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tomas  1881 F pulseaudio
   /dev/snd/controlC2:  tomas  1881 F pulseaudio
   /dev/snd/controlC0:  tomas  1881 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Apr  1 22:48:28 2016
  HibernationDevice: RESUME=UUID=7b4a2bc3-8fd2-4684-b322-2c990980a5ac
  InstallationDate: Installed on 2015-12-13 (110 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7693
  ProcEnviron:
   LANGUAGE=cs
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=520db00b-7805-4f04-8c0c-31acfe536389 ro iommu=soft quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-03-21 (11 days ago)
  dmi.bios.date: 12/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V22.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970 GAMING (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV22.2:bd12/16/2014:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0:
  dmi.product.name: MS-7693
  dmi.product.version: 4.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1563991] Re: [Dell Inc. Inspiron 5520] hibernate/resume failure [non-free: wl]

[Lars Kumbier]

Tested with v4.6-rc1-wily
(4.6.0-040600rc1_4.6.0-040600rc1.201603261930_amd64), bug is resolved
there.

** Tags added: kernel-fixed-upstream

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

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

Title:
  [Dell Inc. Inspiron 5520] hibernate/resume failure [non-free: wl]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System fails to enter suspend mode on ubuntu 16.04 LTS (beta2) - did
  work on ubuntu 14.04 LTS.

  Events:
  * closing the laptop lid, or
  * calling `sudo pm-hibernate` via terminal

  Effect:
  * Screen goes black
  * System stays on, but no commands are acknowledged (mouse, keyboard, trying 
to switch to tty1 via CTRL+ALT+F1)

  Expectation:
  * System enters standby

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: wl
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarah  2221 F pulseaudio
  Date: Wed Mar 30 19:23:24 2016
  DuplicateSignature: hibernate/resume:Dell Inc. Inspiron 5520:A05
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=61da4468-0d8c-4c4e-8616-32dfc23e0ccd
  InstallationDate: Installed on 2014-08-10 (598 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterpreterPath: /usr/bin/python3.5
  MachineType: Dell Inc. Inspiron 5520
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  Title: [Dell Inc. Inspiron 5520] hibernate/resume failure [non-free: wl]
  UpgradeStatus: Upgraded to xenial on 2016-03-27 (3 days ago)
  UserGroups:
   
  dmi.bios.date: 03/16/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd03/16/2012:svnDellInc.:pnInspiron5520:pvrA05:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvrA05:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A05
  dmi.sys.vendor: Dell Inc.

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

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