[Kernel-packages] [Bug 1649342] Re: md5sum fails with message "Invalid argument" on 4, 294, 967, 295-byte files in FAT32 - tracked down to Ubuntu incompatible change to kernel's fread and stdio stream

[Jaime Gaspar]

I tested with kernel 4.10.041000-rc5-generic from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc5/ and I cannot
reproduce the 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/1649342

Title:
  md5sum fails with message "Invalid argument" on 4,294,967,295-byte
  files in FAT32 - tracked down to Ubuntu incompatible change to
  kernel's fread and stdio stream

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Triaged

Bug description:
  Bug discovered in the threads at http://lists.gnu.org/archive/html
  /bug-coreutils/2016-12/msg8.html and
  https://bugzilla.kernel.org/show_bug.cgi?id=189981 partially quoted
  below (with the permission of the persons involved).

  
  === Message 1 ===

  --- Bug ---
  In a FAT32 file system, if one runs md5sum on a 4,294,967,294-byte file (one 
byte less than the maximum file size) it succeeds, but if one runs md5sum on a 
4,294,967,295-byte file (the maximum file size) it fails with error message 
"Invalid argument".

  --- How to reproduce the bug ---
  Create a FAT32 file system in a file "tmp.fs":
 truncate -s 9G tmp.fs
 mkfs.vfat -F 32 tmp.fs
  Mount at "/tmp/mounted_tmp/" the file system in file "tmp.fs":
 sudo mkdir /tmp/mounted_tmp/
 sudo mount -o loop,rw,uid=1000,gid=1000 tmp.fs /tmp/mounted_tmp/
  Create two files in "/tmp/mounted_tmp/", file "file_1" with 4,294,967,294 
bytes and file "file_2" with 4,294,967,295 bytes:
 cd /tmp/mounted_tmp/
 truncate -s 4294967294 file_1
 truncate -s 4294967295 file_2
  Run md5sum on the two files "file_1" and "file_2":
 md5sum file_1
 md5sum file_2
  The outputs should be respectively (notice that the second output is an error 
message):
 541249e3205af07b4a03f891185f64a0  file_1
 md5sum: file_2: Invalid argument
  Unmount the file system at "/tmp/mounted_tmp/":
 cd ..
 sudo umount /tmp/mounted_tmp/
 sudo rmdir /tmp/mounted_tmp/
  Remove the file "tmp.fs".

  --- Notes ---
  Tested with md5sum 8.25 running on an updated Ubuntu 16.10 with kernel 
4.8.0-30-generic.
  The same bug affects sha1sum, sha224sum, sha256sum, sha384sum, and sha512sum, 
but not crc32.

  
  === Message 2 ===

  ...
  > --- How to reproduce the bug ---
  ...

  I can't repro this with any md5sum version on 4.2.5-300.fc23.x86_64
  So I'm guessing a kernel regression.
  Can you strace -o /tmp/md5sum.strace md5sum file_2,
  and look towards the end of the strace file to identify the syscall returning 
EINVAL?
  In any case I'd direct the issue towards the kernel folks.
  ...

  
  === Message 3 ===

  > Can you strace -o /tmp/md5sum.strace md5sum file_2,
  > and look towards the end of the strace file to identify the syscall
  > returning EINVAL?

  It is the seventh and eighth lines below:

...
 read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = 
32768
 read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = 
32768
 read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = 
32768
 read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = 
32768
 read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = 
32767
 read(3, 0x25c12b0, 8192)= -1 EINVAL (Invalid argument)
 read(3, 0x25c12b0, 8192)= -1 EINVAL (Invalid argument)
 write(2, "md5sum: ", 8) = 8
 write(2, "file_2", 6)   = 6
 open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 4
 fstat(4, {st_mode=S_IFREG|0644, st_size=2995, ...}) = 0
 read(4, "# Locale name alias data base.\n#"..., 4096) = 2995
 read(4, "", 4096)   = 0
 close(4)= 0
 open("/usr/share/locale/en_GB/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT 
(No such file or directory)
 open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No 
such file or directory)
 open("/usr/share/locale-langpack/en_GB/LC_MESSAGES/libc.mo", O_RDONLY) = 4
 fstat(4, {st_mode=S_IFREG|0644, st_size=3537, ...}) = 0
 mmap(NULL, 3537, PROT_READ, MAP_PRIVATE, 4, 0) = 0x7f53d8d0a000
 close(4)= 0
 open("/usr/share/locale-langpack/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 
ENOENT (No such file or directory)
 write(2, ": Invalid argument", 18)  = 18
 write(2, "\n", 1)   = 1
 lseek(3, 0, SEEK_CUR)   = 4294967295
 close(3)= 0
 close(1)= 0
 close(2)= 0
 exit_group(1)   = ?
 +++ exited with 1 +++

  
  === 

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[ChristianEhrhardt]

Just learned that SRU for that would be more ok than I expected, quoting the 
SRU policy:
"For Long Term Support releases we regularly want to enable new hardware. Such 
changes are appropriate provided that we can ensure not to affect upgrades on 
existing hardware."

That said waiting for verification on the ppa before I continue (also
another SRU has to clear the queue first anyway).

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

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  New
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  New

Bug description:
  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  
  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  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:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
   3: POSIX  ADVISORY  WRITE 1658 00:14:376 0 EOF
   4: FLOCK  ADVISORY  WRITE 3560 00:14:637 0 EOF
   5: POSIX  ADVISORY  WRITE 3571 00:14:640 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri 
Jan 6 17:35:59 UTC 2017
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores 

[Kernel-packages] [Bug 1657112] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 64, failed: 2

[Brad Figg]

tests ran:  64, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/ms10-34-mcdivittB0-kernel__4.8.0-36.38__2017-01-27_03-37-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/1657112

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+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 1659614] Re: [Lenovo M700z] Wifi malfunctions after updating system

[Taihsiang Ho]

The bug is still there if I boot into the previous kernel version
(3.19.0-79.87~14.04.1). However, two weeks ago it did not has this bug
with the previous proposed kernel (3.19.0-79.87~14.04.1).

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

Title:
  [Lenovo M700z] Wifi malfunctions after updating system

Status in linux package in Ubuntu:
  Triaged
Status in linux-lts-vivid package in Ubuntu:
  Triaged

Bug description:
  Lenovo M700z (CID 201601-20436) with its pre-installed image.

  [Steps To Reproduce]
  Enable the proposed pocket, and then update the system by 'sudo apt-get 
dist-upgrade'

  [Expected Result]
  Wifi works

  [Actual Result]
  Wifi malfunctions. The network indicator does not show any wireless AP.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-80-generic 3.19.0-80.88~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Jan 27 01:28:34 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-m700z-trusty-amd64-20160314-0
  InstallationDate: Installed on 2017-01-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Failed to find casper uuid.conf in 
'binary/casper/initrd.img-3.19.0-37-generic.old-dkms' LIVE Binary 20160314-09:31
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659614/+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 1659598] Re: [Dell Computer Corporation Precision 5510] mic malfunctions after updating system

[Taihsiang Ho]

The bug is still there if I boot into the previous kernel version
(3.19.0-79.87~14.04.1). However, two weeks ago it did not has this bug
with the previous proposed kernel (3.19.0-79.87~14.04.1).

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

Title:
  [Dell Computer Corporation Precision 5510] mic malfunctions after
  updating system

Status in linux package in Ubuntu:
  Triaged
Status in linux-lts-vivid package in Ubuntu:
  Triaged

Bug description:
  Dell Computer Corporation Precision 5510 (CID 201612-25281 and
  201612-25287) with pre-installed image.

  [Steps To Reproduce]
  Enable the proposed pocket, and then update the system by 'sudo apt-get 
dist-upgrade'

  [Expected Result]
  The mic works

  [Actual Result]
  The mic malfunctions. The mic didn't even record ambient noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-80-generic 3.19.0-80.88~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Jan 27 00:37:34 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2017-01-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659598/+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 1659614] Re: [Lenovo M700z] Wifi malfunctions after updating system

[Taihsiang Ho]

The bug is still there if I boot into the previous kernel version
(3.19.0-80.88~14.04.1). However, two weeks ago it did not has this bug
with the previous proposed kernel (3.19.0-80.88~14.04.1).

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

Title:
  [Lenovo M700z] Wifi malfunctions after updating system

Status in linux package in Ubuntu:
  Triaged
Status in linux-lts-vivid package in Ubuntu:
  Triaged

Bug description:
  Lenovo M700z (CID 201601-20436) with its pre-installed image.

  [Steps To Reproduce]
  Enable the proposed pocket, and then update the system by 'sudo apt-get 
dist-upgrade'

  [Expected Result]
  Wifi works

  [Actual Result]
  Wifi malfunctions. The network indicator does not show any wireless AP.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-80-generic 3.19.0-80.88~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Jan 27 01:28:34 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-m700z-trusty-amd64-20160314-0
  InstallationDate: Installed on 2017-01-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Failed to find casper uuid.conf in 
'binary/casper/initrd.img-3.19.0-37-generic.old-dkms' LIVE Binary 20160314-09:31
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659614/+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 1657112] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 141, failed: 0

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/ms10-34-mcdivittB0-kernel__4.8.0-36.38__2017-01-27_02-22-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/1657112

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+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 1014992] Re: Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission denied.

[Alejandro Romero Herrera]

Writing a udev rule to ignore device by ModemManager worked for me:

/etc/udev/rules.d/55-bluetooth-drone-NoModem.rules
KERNEL=="rfcomm*", ATTR{address}=="xx:d3:xx:00:xx:xx", 
ENV{ID_MM_DEVICE_IGNORE}="1"

And reloading rules:
sudo udevadm control --reload-rules

So I connect to device as root
sudo rfcomm connect hic0 XX:D3:XX:00:XX:XX

and then I am able to use it as regular user from dialout group

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

Title:
  Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission
  denied.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  After updating from 8.04 to 12.04 I cannot use rfcomm without sudo.

  I've already added the user  to group 'dialout' .

  Temporary I tried to change udev.rules (KERNEL=="rfcomm[0-9]*", 
GROUP="dialout", MODE="666")  but this doesn't
  solve the problem so I removed it again.

  Here the commands I used :

  burki@orion:/$ hcitool scan
  Scanning ...
   00:12:6F:08:98:FFGEO LE-71 1

  burki@orion:/$ rfcomm connect 1 00:12:6F:08:98:FF
  Can't open RFCOMM device: Permission denied

  burki@orion:/$ ls -l /dev/rfcomm1
  ls: cannot access /dev/rfcomm1: No such file or directory

  burki@orion:/$ groups
  burki adm dialout fax cdrom floppy tape sudo audio dip video plugdev fuse 
scanner lpadmin netdev sambashare

  burki@orion:/$ sudo rfcomm connect 1 00:12:6F:08:98:FF
  Connected /dev/rfcomm1 to 00:12:6F:08:98:FF on channel 1
  Press CTRL-C for hangup

  In another terminal while connection is running ...

  burki@orion:/$ ls -l /dev/rfcomm1
  crw-rw 1 root dialout 216, 1 Jun 19 09:01 /dev/rfcomm1

  burki@orion:/$ UDEV_LOG=debug udevadm test $(udevadm info -q path -n rfcomm1)
  (I've stolen this command from another bug report #570692.  Output is very 
long. Please see attachment)

  WORKAROUND: sudo chmod u+s /usr/bin/rfcomm

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-25-generic-pae 3.2.0-25.40
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18
  Uname: Linux 3.2.0-25-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  burki  1730 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 0xfe50 irq 56'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:10ec0887,10438444,00100302 
HDA:80862805,80862805,0010'
     Controls  : 49
     Simple ctrls  : 21
  Date: Tue Jun 19 09:15:54 2012
  HibernationDevice: RESUME=UUID=f3e3a302-4042-4fcd-86c5-756ae88e15b8
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic-pae 
root=UUID=f791f2d4-8966-47d3-a19d-9b0b649e63ea ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-25-generic-pae N/A
   linux-backports-modules-3.2.0-25-generic-pae  N/A
   linux-firmware1.79
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1014992/+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 1657112] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 33, failed: 1

[Brad Figg]

tests ran:  33, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/ms10-34-mcdivittB0-kernel__4.8.0-36.38__2017-01-27_01-08-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/1657112

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+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 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool

[Petr Soukup]

After much consideration I have finally decided to buy Dell 7566 - a
Skylake 6700hq version (a successor of 7559 model).

I am running Debian testing (Stretch) with kernel 4.8.0.2 with nouveau
driver. After testing it for  while I can now confidently say that in
this configuration the 7566 model is not plagued by the fan issue - out
of the box, lm-sensors show CPU operating temperature between 35 and 45
C with 0 RPM for fans on normal "office" workload. Fans only kick in
when CPU temp exceeds 60 C and stop almost immediately once temperature
drops below 50 - 55 C. Originally I suspected CPU fan sensor was not
working correctly as it was constantly showing 0 rpm. I had to actually
run some Android studio application build which taxes CPU fairly, to get
the fans running. They ran for about 1 minute between 1500 - 2500 rpm
and stopped almost immediately after the build had finished. The battery
life is about the same in Win10 and Linux - approximately 6 hours on
normal workload.

I even have the sleep function working out of the box and install works
without any problems (with the safe boot turned off).

I don't know if this helps anyone, but if there are any potential buyers
around here seeking information, I believe it is safe to say that 7566
is a safe bet with Linux.

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

Title:
  Dell Inspiron 7559 fans do not shut off once started, even when cool

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to
  be an issue with the fan control. When I first boot up the machine the
  fans are off. However, after the laptop warms up under normal usage,
  the fans kick on and then never shut off again.  Even when the CPU
  cools down to below 35c, the fans will continue to run.

  If I suspend the the laptop, and then immediately wake it up again
  then fans are once again off, until it warms up again.  So
  essentially, once the fans start they don't seem to ever shut off.

  Fans seem to work normally under Windows 10.  They turn on as needed,
  and then turn off once the laptop cools down.

  I've tried the various BIOS updates that Dell has released, without
  success. I am currently running Dell's latest BIOS for this laptop
  (v1.1.8)

  Below is the output of lm-sensors showing the fans running when the
  CPU is at a cool 35c

  dell_smm-virtual-0
  Adapter: Virtual device
  Processor Fan: 1925 RPM
  Processor Fan: 2143 RPM
  CPU:+35.0°C  
  GPU: +1.0°C  
  SODIMM: +49.0°C

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob1709 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 13 19:18:45 2016
  HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77
  InstallationDate: Installed on 2016-07-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 7559
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.8
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.8
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+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 1657112] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 10, failed: 2

[Brad Figg]

tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/ms10-34-mcdivittB0-kernel__4.8.0-36.38__2017-01-26_23-51-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/1657112

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+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 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 64, failed: 0

[Brad Figg]

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-27_00-27-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/1657112

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+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 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-27_00-26-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/1657112

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+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 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 141, failed: 28

[Brad Figg]

tests ran: 141, failed: 28;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-27_00-02-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/1657112

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+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 1658255] Re: Kernel not enforcing module signatures under SecureBoot

[Steve Beattie]

I have reproduced this and can confirm it only affects 4.8 kernels. I
have a Ubuntu 16.04 system with secure boot enabled, and the 4.4 kernels
were enforcing it. Installing and rebooting into the linux-image-
generic-hwe-edge kernel (4.8.0-34.36~16.04.1-generic) and everything
before the kernel thinks secure boot is enabled, but the kernel does not
and freely loads unsigned modules.

$ cat /proc/version_signature
Ubuntu 4.4.0-59.80-generic 4.4.35
$ mokutil --sb-state
SecureBoot enabled
$ sysctl kernel.secure_boot
kernel.secure_boot = 1

$ cat /proc/version_signature
Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11
$ mokutil --sb-state
SecureBoot enabled
$ sysctl kernel.secure_boot
kernel.secure_boot = 0

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

Title:
  Kernel not enforcing module signatures under SecureBoot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  $ sudo mokutil --sbstate
  SecureBoot enabled
  $ cat /proc/sys/kernel/moksbstate_disabled
  0
  $ sudo insmod ./hello.ko
  $ echo $?
  0
  $ dmesg | grep Hello
  [00112.530866] Hello, world!
  $ strings /lib/modules/$(uname -r)/kernel/lib/test_module.ko | grep signature
  ~Module signature appended~
  $ strings hello.ko | grep signature
  $ uname -r
  4.8.0-34-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658255/+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 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 16, failed: 4

[Brad Figg]

tests ran:  16, failed: 4;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_23-51-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/1657112

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+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 1658255] Re: Kernel not enforcing module signatures under SecureBoot

[Kees Cook]

And it looks like this is specific to the 4.8 kernel. 4.4 thinks secure
boot is enabled.

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

Title:
  Kernel not enforcing module signatures under SecureBoot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  $ sudo mokutil --sbstate
  SecureBoot enabled
  $ cat /proc/sys/kernel/moksbstate_disabled
  0
  $ sudo insmod ./hello.ko
  $ echo $?
  0
  $ dmesg | grep Hello
  [00112.530866] Hello, world!
  $ strings /lib/modules/$(uname -r)/kernel/lib/test_module.ko | grep signature
  ~Module signature appended~
  $ strings hello.ko | grep signature
  $ uname -r
  4.8.0-34-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658255/+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 1658255] Re: Kernel not enforcing module signatures under SecureBoot

[Kees Cook]

And that must be doing something wrong, since:

sudo efivar -p -n $(efivar --list | grep SecureBoot)

shows "1"

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

Title:
  Kernel not enforcing module signatures under SecureBoot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  $ sudo mokutil --sbstate
  SecureBoot enabled
  $ cat /proc/sys/kernel/moksbstate_disabled
  0
  $ sudo insmod ./hello.ko
  $ echo $?
  0
  $ dmesg | grep Hello
  [00112.530866] Hello, world!
  $ strings /lib/modules/$(uname -r)/kernel/lib/test_module.ko | grep signature
  ~Module signature appended~
  $ strings hello.ko | grep signature
  $ uname -r
  4.8.0-34-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658255/+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 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 33, failed: 2

[Brad Figg]

tests ran:  33, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_23-17-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/1657112

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+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 1658255] Re: Kernel not enforcing module signatures under SecureBoot

[Kees Cook]

the proc handler does:
secure_boot_enabled = efi_enabled(EFI_SECURE_BOOT);
this feature flag is set at boot:
#ifdef CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE
if (boot_params.secure_boot == EFI_SECURE_BOOT) {
set_bit(EFI_SECURE_BOOT, );
enforce_signed_modules();
pr_info("Secure boot enabled\n");
}

And since I don't see the pr_info, nor the flag, nor the module
enforcement, the boot_params is probably missing?

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

Title:
  Kernel not enforcing module signatures under SecureBoot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  $ sudo mokutil --sbstate
  SecureBoot enabled
  $ cat /proc/sys/kernel/moksbstate_disabled
  0
  $ sudo insmod ./hello.ko
  $ echo $?
  0
  $ dmesg | grep Hello
  [00112.530866] Hello, world!
  $ strings /lib/modules/$(uname -r)/kernel/lib/test_module.ko | grep signature
  ~Module signature appended~
  $ strings hello.ko | grep signature
  $ uname -r
  4.8.0-34-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658255/+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 1658255] Re: Kernel not enforcing module signatures under SecureBoot

[Kees Cook]

Oh, and that's not set up by the bootloader, it's in
arch/x86/boot/compressed/eboot.c:

boot_params->secure_boot = get_secure_boot();

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

Title:
  Kernel not enforcing module signatures under SecureBoot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  $ sudo mokutil --sbstate
  SecureBoot enabled
  $ cat /proc/sys/kernel/moksbstate_disabled
  0
  $ sudo insmod ./hello.ko
  $ echo $?
  0
  $ dmesg | grep Hello
  [00112.530866] Hello, world!
  $ strings /lib/modules/$(uname -r)/kernel/lib/test_module.ko | grep signature
  ~Module signature appended~
  $ strings hello.ko | grep signature
  $ uname -r
  4.8.0-34-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658255/+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 1657112] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 18, failed: 1

[Brad Figg]

tests ran:  18, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/ms10-34-mcdivittB0-kernel__4.8.0-36.38__2017-01-26_22-47-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/1657112

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+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 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 4, failed: 2

[Brad Figg]

tests ran:   4, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_23-03-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/1657112

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+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 1608236] Re: Regression: S-video output does not work

[Jarno Suni]

Why 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/1608236

Title:
  Regression: S-video output does not work

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  Regression. S-video output can not be used. It works by 4.4.0-22-generic.
  xrandr tells on 4.4.0-31-generic:

  TV1 unknown connection (normal left inverted right x axis y axis)
 848x480   50.00 +
 640x480   50.00 +
 1024x768  50.00  
 800x600   50.00

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1573 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jul 31 17:15:16 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (94 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 89224MG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/06
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 63ET13WW
  dmi.board.name: CAPELL VALLEY(NAPA) CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 89224MG
  dmi.product.version: 3000 C200
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1659340] Re: Linux kernel 4.8 hangs at boot up

[lotek]

maybe this delimit the issue:

Lenovo 710S (KabyLake i5-7200):
4.7.5  passed http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.5/
4.7.6  failed http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.6/
4.7.10 failed http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.10/
4.9.6  failed http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.6/

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

Title:
  Linux kernel 4.8 hangs at boot up

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
  Windows 10 and Ubuntu 16.10.

  Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
  When I try to start with any of the 4.8.0 kernels delivered with regular
  Ubuntu updates, they all hang after printing

Läser in Linux 4.8.0-34-generic ...
Läser in initial ramdisk ...

  Sorry for the partly Swedish text. I guess that the lines would start with
  "Loading" instead of "Läser in" on an English version.

  The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34
  and with -generic, -generic (upstart) and -generic (recovery mode).

  After a while the fan runs at full speed, as if the processor is working
  hard, but nothing happens.

  After I've tried in vain to start with Linux 4.8.0-xx, and then starts
  with 4.4.0-45, the following errors are usually printed:

  [  2.511733] usb 4-3: string descriptor 0 read error: -22
  [  3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight 
controller
  /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
  [ 21.335117] usb 4-3: string descriptor 0 read error: -22

  When a successful start has not been immediately preceded by a failed start,
  only the line beginning "/dev/sda7" is printed.

  I have previously commented on bug #1635447. As recommended there, I've
  also tested with the upstream kernel 4.10-rc3. It worked just as bad as
  4.8.0.

  I tried to report this bug with 'ubuntu-bug linux' after I had booted with
  the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45-
  generic is not an official Ubuntu package.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjell  2022 F pulseaudio
   /dev/snd/controlC1:  kjell  2022 F pulseaudio
   /dev/snd/controlC0:  kjell  2022 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb
  InstallationDate: Installed on 2013-09-25 (1218 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V5-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551G
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+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 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

OK, I got the first kernel (v4.4-wily) validated that it works properly.
I IPL'ed back to the 4.4.0-59 to validate the problem had not suddenly
vanished, still there.

So:
4.4.0-59 bad / has the issue
v4.4-wily working / no issue

Do you still need me to install / test / validate the v4.5-rc1-wily
kernel, in this case?

I am thinking to stay booted to the v4.4-wily kernel 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/1656605

Title:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Today I did our first production 14.04 to 16.04 LTS server upgrade. I
  had done so a couple of times successfully on test server machines.
  Upon booting up on the 16.04 system/kernel, after the Grub screen the
  server console screen is completely blank.

  Someone suggested using Ctrl-Alt-F1/8, and indeed pressing those
  hotkeys does toggle through the tty screens.

  There is no boot process logged to the server console screen.

  I did have the last 14.04 kernel yet installed, so selected that one
  from the Grub menu. Booting that 14.04 kernel, then server console
  display behaves normally.

  So I suspected perhaps a bum install of the 16.04 kernel. I used the
  following commands while booted to the 14.04 kernel to reinstall the
  16.04 kernel:

  $ sudo dpkg -P linux-image-4.4.0-59-generic 
linux-image-extra-4.4.0-59-generic linux-image-generic
  $ sudo apt-get install linux-image-generic

  Same results booting the 16.04 kernel after those steps.

  Hardware spec is an Intel Atom D945GCLF2D boxed motherboard with Intel
  Atom 330 Dual-Core processor and 2GB RAM. RAID is 3Ware SATA RAID.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+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 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 10, failed: 1

[Brad Figg]

tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_22-30-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/1657112

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+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 1659087] Re: open(2) returns EOVERFLOW within tmpfs+userns

[Jonathan Calmels]

Thinking more about it, this might be due to the lack of
CAP_DAC_OVERRIDE so I guess I need this too right?

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

Title:
  open(2) returns EOVERFLOW within tmpfs+userns

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  On Ubuntu 4.4.0-59.80-generic 4.4.35, open(2) returns EOVERFLOW when
  creating a file in tmpfs with user namespace enabled.

  This issue wasn't present in 4.4.0-47 and has probably been introduced
  by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634964

  Step to reproduce:

  $ unshare -r -U -m /bin/bash
  # mount -t tmpfs tmpfs /mnt
  # echo $$
  2354

  In another terminal:

  $ sudo nsenter -t 2354 -m  
  # touch /mnt/foo
  touch: cannot touch '/mnt/foo': Value too large for defined data type

  Note that we are not joining the user namespace when creating the file
  but we would expect `touch' to succeed and create the file with an
  inode set to INVALID_UID/GID (i.e. nobody:nogroup) within the mount
  namespace.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659087/+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 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_22-24-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/1657112

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+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 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 18, failed: 2

[Brad Figg]

tests ran:  18, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_22-25-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/1657112

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+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 1659087] Re: open(2) returns EOVERFLOW within tmpfs+userns

[Jonathan Calmels]

Trying the fsuid/fsgid workaround, I came across another oddity:

$ id -u
1000
$ id -g
1000
$ unshare -r -U -m /bin/bash
# mount -t tmpfs tmpfs /mnt
# chmod 555 /mnt
# ls -ldn /mnt
dr-xr-xr-x 2 0 0 40 Jan 26 14:15 /mnt
# echo $$
2354

In another terminal:

$ sudo nsenter -G 1000 -S 1000 -t 2354 -m
$ ls -ldn /mnt
dr-xr-xr-x 2 1000 1000 40 Jan 26 14:10 /mnt
$ touch /mnt/foo
touch: cannot touch '/mnt/foo': Permission denied

Even though I'm supposed to be root in the context of the user namespace, I 
can't create the file because I'm lacking the write permission on the mount 
directory.
In this case, setting the fsuid/fsgid is not sufficient, I have to join the 
user namespace if I want the permissions to be resolved correctly.

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

Title:
  open(2) returns EOVERFLOW within tmpfs+userns

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  On Ubuntu 4.4.0-59.80-generic 4.4.35, open(2) returns EOVERFLOW when
  creating a file in tmpfs with user namespace enabled.

  This issue wasn't present in 4.4.0-47 and has probably been introduced
  by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634964

  Step to reproduce:

  $ unshare -r -U -m /bin/bash
  # mount -t tmpfs tmpfs /mnt
  # echo $$
  2354

  In another terminal:

  $ sudo nsenter -t 2354 -m  
  # touch /mnt/foo
  touch: cannot touch '/mnt/foo': Value too large for defined data type

  Note that we are not joining the user namespace when creating the file
  but we would expect `touch' to succeed and create the file with an
  inode set to INVALID_UID/GID (i.e. nobody:nogroup) within the mount
  namespace.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659087/+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 1659618] Re: Enable ARM64 support in kexec-tools

[Bug Watch Updater]

** Changed in: kexec-tools (Debian)
   Status: Unknown => Fix Released

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

Title:
  Enable ARM64 support in kexec-tools

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Xenial:
  Confirmed
Status in kexec-tools source package in Yakkety:
  Confirmed
Status in kexec-tools package in Debian:
  Fix Released

Bug description:
  [IMPACT]
   * kexec-tools in Xenial (16.04) currently does not support ARM64
     architecture.
   * Backport support for ARM64 arch from upstream
     https://github.com/horms/kexec-tools
   * Majority of the patches are contained in kexec/arch/arm64/ except for
     one patch that impacts purgatory and common device tree routines.

  [TEST CASE]
   * I built kexec-tools for ARM64 and tested it on HW using the following
     testcase:
     $ sudo kexec -l /boot/vmlinuz--generic
   --initrd=/boot/initrd.img--generic
   --command-line="root=UUID= ro vt.handoff=7"
     $ sudo kexec -e
   * I was able to kexec the new kernel successfully.
   * [ 6702.357899] kexec_core: Starting new kernel
     [0.00] Booting Linux on physical CPU 0x200
     [0.00] Linux version -generic (buildd@bos01-arm64-008)
     (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
     [0.00] Boot CPU: AArch64 Processor [510f8000]

  [REGRESSION POTENTIAL]
   * Since patches are confined to arm[64] there is a low overall risk of
     regression.

  [OTHER INFO]
   * You can find a Xenial kexec-tools package built for AMD64, i386 and
     ARM64 in my PPA
     https://launchpad.net/~manjo/+archive/ubuntu/kexec-tools
   * This package is built using the Xenial source package for kexec-tools
     with ARM64 enablement patches applied.
   * Please pull the changes from my PPA package and integrate into Ubuntu
     Xenial kexec-tools after review.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+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 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)

[Joseph Nuzman]

Both kernels behave like any of the kernels from 4.5:  no sound on HDMI.

Recapping:

Ubuntu 4.4.0-59: HDMI audio works properly

Mainline 4.4 (any): i915 drm driver does not seem to support Skylake,
HDMI audio not enumerated

All of the below kernels exhibit the same problem: HDMI produces no sound
Mainline 4.5rc1
Mainline 4.5 final
Mainline 4.6 final
Ubuntu 4.6.0-10
Mainline 4.7 final
Mainline 4.8 final
Ubuntu 4.8.0-11
Ubuntu 4.8.0-34
Mainline 4.9 final
Mainline 4.10rc5

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

Title:
  Regression:  HDMI audio produces no sound (Skylake NUC)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  After upgrade from Xenial 16.04 to Yakkety 16.10, playing audio over HDMI no 
longer produces sound.
  * When booting with old kernel from Xenial (4.4.0-59), HDMI audio works fine
  * Audio from headphone jack works fine
  * Userspace seems to be happily playing to HDMI audio device, but no sound 
produced at HDMI sink (Samsung TV)

  Any of a wide range of pre-built mainline kernels fail to produce HDMI
  audio, but with a different failure mode (HDMI audio does not seem to
  be enumerated in the same way as in the Ubuntu kernels.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  israel 1973 F pulseaudio
   /dev/snd/controlC1:  israel 1973 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jan 20 08:58:35 2017
  HibernationDevice: RESUME=UUID=ca27f739-071f-4c25-974e-0d0f0614b21c
  InstallationDate: Installed on 2016-10-03 (108 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=90c3e094-e890-4c35-a0d2-0a358f5d2430 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-01-13 (6 days ago)
  dmi.bios.date: 06/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-405
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657994/+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 1659654] Re: regression in linux-libc-dev in yakkety: C++ style comments are not allowed in ISO C90

[Andy Whitcroft]

** 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/1659654

Title:
  regression in linux-libc-dev in yakkety: C++ style comments are not
  allowed in ISO C90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  klibc is failing to build on arm64 in yakkety because of a change in
  unistd.h in linux-libc-dev somewhere between 4.4.0-9136.55 and
  4.8.0-36.38:

gcc -Wp,-MD,usr/klibc/syscalls/.SYSCALLS.i.d  -nostdinc -iwithprefix 
include -I/<>/usr/include/arch/arm64 -Iusr/include/arch/arm64  
-I/<>/usr/include/bits64 -Iusr/include/bits64  
-I/<>/usr/klibc/../include -Iusr/klibc/../include  
-I/<>/usr/include -Iusr/include  -I/<>/linux/include 
-Ilinux/include  -I/<>/linux/arch/arm64/include 
-Ilinux/arch/arm64/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-exceptions -mgeneral-regs-only -g -Os 
-march=armv8-a -mtune=generic -W -Wall -Wno-sign-compare -Wno-unused-parameter  
 -I/<>/usr/klibc/syscalls -D__ASSEMBLY__ -ansi -x c -E -o 
usr/klibc/
  syscalls/SYSCALLS.i usr/klibc/SYSCALLS.def
  In file included from /<>/linux/include/asm/unistd.h:19:0,
   from usr/klibc/SYSCALLS.def:13:
  /<>/linux/include/asm-generic/unistd.h:734:1: error: C++ style 
comments are not allowed in ISO C90
   //__SYSCALL(__NR_pkey_get,  sys_pkey_get)
   ^
  /<>/linux/include/asm-generic/unistd.h:734:1: error: (this will 
be reported only once per input file)

  https://launchpad.net/ubuntu/+source/klibc/2.0.4-8ubuntu3.1/+build/11926893

  We should reasonably expect the headers in linux-libc-dev to
  maximally-conformant C headers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659654/+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 1659654] 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 1659654

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

Title:
  regression in linux-libc-dev in yakkety: C++ style comments are not
  allowed in ISO C90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  klibc is failing to build on arm64 in yakkety because of a change in
  unistd.h in linux-libc-dev somewhere between 4.4.0-9136.55 and
  4.8.0-36.38:

gcc -Wp,-MD,usr/klibc/syscalls/.SYSCALLS.i.d  -nostdinc -iwithprefix 
include -I/<>/usr/include/arch/arm64 -Iusr/include/arch/arm64  
-I/<>/usr/include/bits64 -Iusr/include/bits64  
-I/<>/usr/klibc/../include -Iusr/klibc/../include  
-I/<>/usr/include -Iusr/include  -I/<>/linux/include 
-Ilinux/include  -I/<>/linux/arch/arm64/include 
-Ilinux/arch/arm64/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-exceptions -mgeneral-regs-only -g -Os 
-march=armv8-a -mtune=generic -W -Wall -Wno-sign-compare -Wno-unused-parameter  
 -I/<>/usr/klibc/syscalls -D__ASSEMBLY__ -ansi -x c -E -o 
usr/klibc/
  syscalls/SYSCALLS.i usr/klibc/SYSCALLS.def
  In file included from /<>/linux/include/asm/unistd.h:19:0,
   from usr/klibc/SYSCALLS.def:13:
  /<>/linux/include/asm-generic/unistd.h:734:1: error: C++ style 
comments are not allowed in ISO C90
   //__SYSCALL(__NR_pkey_get,  sys_pkey_get)
   ^
  /<>/linux/include/asm-generic/unistd.h:734:1: error: (this will 
be reported only once per input file)

  https://launchpad.net/ubuntu/+source/klibc/2.0.4-8ubuntu3.1/+build/11926893

  We should reasonably expect the headers in linux-libc-dev to
  maximally-conformant C headers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659654/+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 1659654] Re: regression in linux-libc-dev in yakkety: C++ style comments are not allowed in ISO C90

[Joseph Salisbury]

** 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/1659654

Title:
  regression in linux-libc-dev in yakkety: C++ style comments are not
  allowed in ISO C90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  klibc is failing to build on arm64 in yakkety because of a change in
  unistd.h in linux-libc-dev somewhere between 4.4.0-9136.55 and
  4.8.0-36.38:

gcc -Wp,-MD,usr/klibc/syscalls/.SYSCALLS.i.d  -nostdinc -iwithprefix 
include -I/<>/usr/include/arch/arm64 -Iusr/include/arch/arm64  
-I/<>/usr/include/bits64 -Iusr/include/bits64  
-I/<>/usr/klibc/../include -Iusr/klibc/../include  
-I/<>/usr/include -Iusr/include  -I/<>/linux/include 
-Ilinux/include  -I/<>/linux/arch/arm64/include 
-Ilinux/arch/arm64/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-exceptions -mgeneral-regs-only -g -Os 
-march=armv8-a -mtune=generic -W -Wall -Wno-sign-compare -Wno-unused-parameter  
 -I/<>/usr/klibc/syscalls -D__ASSEMBLY__ -ansi -x c -E -o 
usr/klibc/
  syscalls/SYSCALLS.i usr/klibc/SYSCALLS.def
  In file included from /<>/linux/include/asm/unistd.h:19:0,
   from usr/klibc/SYSCALLS.def:13:
  /<>/linux/include/asm-generic/unistd.h:734:1: error: C++ style 
comments are not allowed in ISO C90
   //__SYSCALL(__NR_pkey_get,  sys_pkey_get)
   ^
  /<>/linux/include/asm-generic/unistd.h:734:1: error: (this will 
be reported only once per input file)

  https://launchpad.net/ubuntu/+source/klibc/2.0.4-8ubuntu3.1/+build/11926893

  We should reasonably expect the headers in linux-libc-dev to
  maximally-conformant C headers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659654/+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 1659654] Re: regression in linux-libc-dev in yakkety: C++ style comments are not allowed in ISO C90

[Steve Langasek]

** 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/1659654

Title:
  regression in linux-libc-dev in yakkety: C++ style comments are not
  allowed in ISO C90

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  klibc is failing to build on arm64 in yakkety because of a change in
  unistd.h in linux-libc-dev somewhere between 4.4.0-9136.55 and
  4.8.0-36.38:

gcc -Wp,-MD,usr/klibc/syscalls/.SYSCALLS.i.d  -nostdinc -iwithprefix 
include -I/<>/usr/include/arch/arm64 -Iusr/include/arch/arm64  
-I/<>/usr/include/bits64 -Iusr/include/bits64  
-I/<>/usr/klibc/../include -Iusr/klibc/../include  
-I/<>/usr/include -Iusr/include  -I/<>/linux/include 
-Ilinux/include  -I/<>/linux/arch/arm64/include 
-Ilinux/arch/arm64/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-exceptions -mgeneral-regs-only -g -Os 
-march=armv8-a -mtune=generic -W -Wall -Wno-sign-compare -Wno-unused-parameter  
 -I/<>/usr/klibc/syscalls -D__ASSEMBLY__ -ansi -x c -E -o 
usr/klibc/
  syscalls/SYSCALLS.i usr/klibc/SYSCALLS.def
  In file included from /<>/linux/include/asm/unistd.h:19:0,
   from usr/klibc/SYSCALLS.def:13:
  /<>/linux/include/asm-generic/unistd.h:734:1: error: C++ style 
comments are not allowed in ISO C90
   //__SYSCALL(__NR_pkey_get,  sys_pkey_get)
   ^
  /<>/linux/include/asm-generic/unistd.h:734:1: error: (this will 
be reported only once per input file)

  https://launchpad.net/ubuntu/+source/klibc/2.0.4-8ubuntu3.1/+build/11926893

  We should reasonably expect the headers in linux-libc-dev to
  maximally-conformant C headers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659654/+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 1659654] [NEW] regression in linux-libc-dev in yakkety: C++ style comments are not allowed in ISO C90

[Steve Langasek]

Public bug reported:

klibc is failing to build on arm64 in yakkety because of a change in
unistd.h in linux-libc-dev somewhere between 4.4.0-9136.55 and
4.8.0-36.38:

  gcc -Wp,-MD,usr/klibc/syscalls/.SYSCALLS.i.d  -nostdinc -iwithprefix include 
-I/<>/usr/include/arch/arm64 -Iusr/include/arch/arm64  
-I/<>/usr/include/bits64 -Iusr/include/bits64  
-I/<>/usr/klibc/../include -Iusr/klibc/../include  
-I/<>/usr/include -Iusr/include  -I/<>/linux/include 
-Ilinux/include  -I/<>/linux/arch/arm64/include 
-Ilinux/arch/arm64/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-exceptions -mgeneral-regs-only -g -Os 
-march=armv8-a -mtune=generic -W -Wall -Wno-sign-compare -Wno-unused-parameter  
 -I/<>/usr/klibc/syscalls -D__ASSEMBLY__ -ansi -x c -E -o 
usr/klibc/
syscalls/SYSCALLS.i usr/klibc/SYSCALLS.def
In file included from /<>/linux/include/asm/unistd.h:19:0,
 from usr/klibc/SYSCALLS.def:13:
/<>/linux/include/asm-generic/unistd.h:734:1: error: C++ style 
comments are not allowed in ISO C90
 //__SYSCALL(__NR_pkey_get,  sys_pkey_get)
 ^
/<>/linux/include/asm-generic/unistd.h:734:1: error: (this will be 
reported only once per input file)

https://launchpad.net/ubuntu/+source/klibc/2.0.4-8ubuntu3.1/+build/11926893

We should reasonably expect the headers in linux-libc-dev to maximally-
conformant C headers.

** Affects: linux (Ubuntu)
 Importance: High
 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/1659654

Title:
  regression in linux-libc-dev in yakkety: C++ style comments are not
  allowed in ISO C90

Status in linux package in Ubuntu:
  New

Bug description:
  klibc is failing to build on arm64 in yakkety because of a change in
  unistd.h in linux-libc-dev somewhere between 4.4.0-9136.55 and
  4.8.0-36.38:

gcc -Wp,-MD,usr/klibc/syscalls/.SYSCALLS.i.d  -nostdinc -iwithprefix 
include -I/<>/usr/include/arch/arm64 -Iusr/include/arch/arm64  
-I/<>/usr/include/bits64 -Iusr/include/bits64  
-I/<>/usr/klibc/../include -Iusr/klibc/../include  
-I/<>/usr/include -Iusr/include  -I/<>/linux/include 
-Ilinux/include  -I/<>/linux/arch/arm64/include 
-Ilinux/arch/arm64/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-exceptions -mgeneral-regs-only -g -Os 
-march=armv8-a -mtune=generic -W -Wall -Wno-sign-compare -Wno-unused-parameter  
 -I/<>/usr/klibc/syscalls -D__ASSEMBLY__ -ansi -x c -E -o 
usr/klibc/
  syscalls/SYSCALLS.i usr/klibc/SYSCALLS.def
  In file included from /<>/linux/include/asm/unistd.h:19:0,
   from usr/klibc/SYSCALLS.def:13:
  /<>/linux/include/asm-generic/unistd.h:734:1: error: C++ style 
comments are not allowed in ISO C90
   //__SYSCALL(__NR_pkey_get,  sys_pkey_get)
   ^
  /<>/linux/include/asm-generic/unistd.h:734:1: error: (this will 
be reported only once per input file)

  https://launchpad.net/ubuntu/+source/klibc/2.0.4-8ubuntu3.1/+build/11926893

  We should reasonably expect the headers in linux-libc-dev to
  maximally-conformant C headers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659654/+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 1659618] Re: Enable ARM64 support in kexec-tools

[Ubuntu Foundations Team Bug Bot]

The attachment "updated debdiff - changelog referring to LP# 1659618"
seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to
the bug report so that they can review and hopefully sponsor the
debdiff.  If the attachment isn't a patch, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are member
of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Enable ARM64 support in kexec-tools

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Xenial:
  Confirmed
Status in kexec-tools source package in Yakkety:
  Confirmed
Status in kexec-tools package in Debian:
  Unknown

Bug description:
  [IMPACT]
   * kexec-tools in Xenial (16.04) currently does not support ARM64
     architecture.
   * Backport support for ARM64 arch from upstream
     https://github.com/horms/kexec-tools
   * Majority of the patches are contained in kexec/arch/arm64/ except for
     one patch that impacts purgatory and common device tree routines.

  [TEST CASE]
   * I built kexec-tools for ARM64 and tested it on HW using the following
     testcase:
     $ sudo kexec -l /boot/vmlinuz--generic
   --initrd=/boot/initrd.img--generic
   --command-line="root=UUID= ro vt.handoff=7"
     $ sudo kexec -e
   * I was able to kexec the new kernel successfully.
   * [ 6702.357899] kexec_core: Starting new kernel
     [0.00] Booting Linux on physical CPU 0x200
     [0.00] Linux version -generic (buildd@bos01-arm64-008)
     (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
     [0.00] Boot CPU: AArch64 Processor [510f8000]

  [REGRESSION POTENTIAL]
   * Since patches are confined to arm[64] there is a low overall risk of
     regression.

  [OTHER INFO]
   * You can find a Xenial kexec-tools package built for AMD64, i386 and
     ARM64 in my PPA
     https://launchpad.net/~manjo/+archive/ubuntu/kexec-tools
   * This package is built using the Xenial source package for kexec-tools
     with ARM64 enablement patches applied.
   * Please pull the changes from my PPA package and integrate into Ubuntu
     Xenial kexec-tools after review.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+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 1658999] Re: [Xenial Regression] Kernel panics on HDMI in Xenial

[Timo Aaltonen]

So, those patches do not need to be reverted. The actual panic was
likely something other than i915_bpo related.

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

Title:
  [Xenial Regression] Kernel panics on HDMI in Xenial

Status in linux package in Ubuntu:
  Triaged

Bug description:
  sabdfl is on a Dell XPS 15 and seeing kernel panics on HDMI connect with a
  wide range of displays.  He's running 4.4.0-62.83 and notes this is 
definitely a regression as it was working previously.

  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.995791] [
  cut here ]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.995842] WARNING: CPU: 4
  PID: 2548 at /build/linux-W6HB68/linux-4.4.0/ubuntu/i915/intel_pm.c:3675
  skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]()
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.995846] WARN_ON(!wm_changed)
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.995849] Modules linked
  in: xt_REDIRECT nf_nat_redirect xt_hl xt_conntrack xt_addrtype overlay
  aufs rfcomm xt_CHECKSUM iptable_mangle xt_tcpudp ipt_MASQUERADE
  nf_nat_masquerade_ipv4 xt_comment iptable_nat nf_conntrack_ipv4
  nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc bnep
  binfmt_misc snd_hda_codec_hdmi dell_led snd_hda_codec_realtek
  snd_hda_codec_generic zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO)
  spl(O) zavl(PO) nls_iso8859_1 dell_wmi dell_laptop dcdbas snd_hda_intel
  snd_hda_codec snd_hda_core snd_hwdep snd_pcm brcmfmac snd_seq_midi
  brcmutil snd_seq_midi_event rtsx_pci_ms cfg80211 memstick intel_rapl
  x86_pkg_temp_thermal intel_powerclamp snd_rawmidi coretemp
  crct10dif_pclmul crc32_pclmul snd_seq ghash_clmulni_intel aesni_intel
  uvcvideo aes_x86_64 videobuf2_vmalloc btusb cdc_ether lrw
  videobuf2_memops snd_seq_device gf128mul usbnet videobuf2_v4l2 btrtl
  glue_helper snd_timer ablk_helper videobuf2_core cryptd r8152
  v4l2_common hid_multitouch mii videodev snd media joydev input_leds
  serio_raw soundcore idma64 virt_dma mei_me mei processor_thermal_device
  shpchp intel_lpss_pci intel_soc_dts_iosf intel_lpss_acpi intel_lpss
  hci_uart btbcm btqca btintel int3403_thermal bluetooth dell_smo8800
  intel_hid int3400_thermal mac_hid acpi_thermal_rel sparse_keymap
  int3402_thermal int340x_thermal_zone acpi_pad acpi_als kfifo_buf
  industrialio kvm_intel kvm irqbypass iptable_filter ip_tables
  ip6table_filter ip6_tables x_tables parport_pc ppdev lp parport autofs4
  usbhid rtsx_pci_sdmmc nouveau i915_bpo mxm_wmi intel_ips ttm
  i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt
  fb_sys_fops ahci nvme rtsx_pci drm libahci i2c_hid hid wmi
  pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996021] CPU: 4 PID: 2548
  Comm: Xorg Tainted: P   O4.4.0-62-generic #83-Ubuntu
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996024] Hardware name:
  Dell Inc. XPS 15 9550/0N7TVV, BIOS 01.02.00 04/07/2016
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996027]
  0286 5b61ce69 880880293920 813f7c63
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996033]
  880880293968 c02be9a0 880880293958 810812d2
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996037]
  88089255f000 88089160a148 88089255e000 880892644b78
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996042] Call Trace:
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996051]
  [] dump_stack+0x63/0x90
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996059]
  [] warn_slowpath_common+0x82/0xc0
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996064]
  [] warn_slowpath_fmt+0x5c/0x80
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996101]
  [] skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996136]
  [] skl_update_wm+0x185/0x610 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996190]
  [] ? intel_ddi_enable_transcoder_func+0x17f/0x260
  [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996225]
  [] intel_update_watermarks+0x1e/0x30 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996276]
  [] haswell_crtc_enable+0x761/0x8e0 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996327]
  [] intel_atomic_commit+0x5d6/0x14a0 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996366]
  [] ? drm_atomic_check_only+0x18e/0x590 [drm]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996397]
  [] drm_atomic_commit+0x37/0x60 [drm]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996415]
  [] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996443]
  [] drm_mode_set_config_internal+0x62/0x100 [drm]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996472]
  [] drm_mode_setcrtc+0x3cc/0x4f0 [drm]
  Jan 24 

[Kernel-packages] [Bug 1659623] Re: Shutdown/reboot hang on Dell XPS 15 9550 BIOS 1.2.18+

[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.8 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.8.17/

** 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/1659623

Title:
  Shutdown/reboot hang on Dell XPS 15 9550 BIOS 1.2.18+

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Dell XPS 15 9550 BIOS 1.2.18+, shutdown/reboot job is delayed for
  several seconds in Ubuntu kernel. After shutdown screen appears and
  all shutdown sequence had been done, the power LED turns off; however
  the front LED is flashing in orange for several seconds and the system
  finally turns off. Rebooting is also not working: front LED flashes in
  orange and the system just turns off.

  Switching to mainline kernel 4.9.6, or downgrading to BIOS 1.2.16
  solved the problem. Other Linux distro users didn't observed the
  problem, see also:

  * 
https://www.reddit.com/r/Dell/comments/5przxq/new_dell_xps_15_9550_bios_1219/
  * 
https://www.reddit.com/r/Dell/comments/5l9n3b/xps_15_9550_bios_1218_ubuntu_1610_shutdown_problem/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psj5638 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Jan 26 19:17:24 2017
  HibernationDevice: RESUME=UUID=2cfb78ae-e2b8-4d3a-9ab2-a61ae1a79fd1
  InstallationDate: Installed on 2016-01-21 (371 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=db90ced3-4cfe-4001-b877-d4aa35e7260f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (103 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.asset.tag: ainazi
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: ainazi
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659623/+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 1659621] Re: Random freezes and reboots since last kernel update

[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.45

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

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

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

** 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/1659621

Title:
  Random freezes and reboots since last kernel update

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  I noticed my Laptop () started to freeze and reboot randomly and
  checking the apt logs the date where this started matches a kernel
  update:

  Start-Date: 2017-01-22  18:09:20
  Commandline: apt full-upgrade
  Requested-By: luca (1000)
  Install: linux-image-4.4.0-62-lowlatency:amd64 (4.4.0-62.83, automatic)
  Upgrade: linux-libc-dev:amd64 (4.4.0-59.80, 4.4.0-62.83), 
linux-image-lowlatency:amd64 (4.4.0.59.62, 4.4.0.62.65), libapt-inst2.0:amd64 
(1.2.18, 1.2.19), libsystemd0:amd64 (229-4ubuntu15, 229-4ubuntu16), 
libsystemd0:i386 (229-4ubuntu15, 229-4ubuntu16), apt:amd64 (1.2.18, 1.2.19), 
sudo:amd64 (1.8.16-0ubuntu1.2, 1.8.16-0ubuntu1.3), udev:amd64 (229-4ubuntu15, 
229-4ubuntu16), libapt-pkg5.0:amd64 (1.2.18, 1.2.19), libudev1:amd64 
(229-4ubuntu15, 229-4ubuntu16), libudev1:i386 (229-4ubuntu15, 229-4ubuntu16), 
docker-engine:amd64 (1.12.6-0~ubuntu-xenial, 1.13.0-0~ubuntu-xenial), 
firefox-locale-de:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 
51.0+build2-0ubuntu0.16.04.1), systemd-sysv:amd64 (229-4ubuntu15, 
229-4ubuntu16), firefox-locale-en:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 
51.0+build2-0ubuntu0.16.04.1), libpam-systemd:amd64 (229-4ubuntu15, 
229-4ubuntu16), systemd:amd64 (229-4ubuntu15, 229-4ubuntu16), 
mysql-common:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), 
apt-utils:amd64 (1.2.18, 1.2.19), libmysqlclient20:i386 
(5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), firefox:amd64 
(50.1.0+build2-0ubuntu0.16.04.1, 51.0+build2-0ubuntu0.16.04.1), 
apt-transport-https:amd64 (1.2.18, 1.2.19), linux-tools-common:amd64 
(4.4.0-59.80, 4.4.0-62.83)
  Purge: linux-image-4.4.0-57-lowlatency:amd64 (4.4.0-57.78)
  End-Date: 2017-01-22  18:10:27

  Looking at /var/log/kernel.log (attached fragment) I found a backtrace
  including the i915 module.

  
  Attached is the output from lspci and lshw. Let me know if you need anything 
else.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-lowlatency 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-lowlatency 4.4.40
  Uname: Linux 4.4.0-62-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   luca   2999 F...m pulseaudio
   /dev/snd/controlC1:  luca   2999 F pulseaudio
   /dev/snd/controlC0:  luca   2999 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Jan 26 18:59:53 2017
  HibernationDevice: RESUME=UUID=841aac03-34a5-409e-a845-fdb0c6d7284a
  InstallationDate: Installed on 2015-11-12 (440 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20DT001TGE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-lowlatency 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-lowlatency N/A
   linux-backports-modules-4.4.0-62-lowlatency  N/A
   linux-firmware   1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-12-05 (52 days ago)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET54WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET54WW(1.16):bd08/19/2015:svnLENOVO:pn20DT001TGE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT001TGE
  

[Kernel-packages] [Bug 1659621] Re: Random freezes and reboots since last kernel update

[Joseph Salisbury]

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

** 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/1659621

Title:
  Random freezes and reboots since last kernel update

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  I noticed my Laptop () started to freeze and reboot randomly and
  checking the apt logs the date where this started matches a kernel
  update:

  Start-Date: 2017-01-22  18:09:20
  Commandline: apt full-upgrade
  Requested-By: luca (1000)
  Install: linux-image-4.4.0-62-lowlatency:amd64 (4.4.0-62.83, automatic)
  Upgrade: linux-libc-dev:amd64 (4.4.0-59.80, 4.4.0-62.83), 
linux-image-lowlatency:amd64 (4.4.0.59.62, 4.4.0.62.65), libapt-inst2.0:amd64 
(1.2.18, 1.2.19), libsystemd0:amd64 (229-4ubuntu15, 229-4ubuntu16), 
libsystemd0:i386 (229-4ubuntu15, 229-4ubuntu16), apt:amd64 (1.2.18, 1.2.19), 
sudo:amd64 (1.8.16-0ubuntu1.2, 1.8.16-0ubuntu1.3), udev:amd64 (229-4ubuntu15, 
229-4ubuntu16), libapt-pkg5.0:amd64 (1.2.18, 1.2.19), libudev1:amd64 
(229-4ubuntu15, 229-4ubuntu16), libudev1:i386 (229-4ubuntu15, 229-4ubuntu16), 
docker-engine:amd64 (1.12.6-0~ubuntu-xenial, 1.13.0-0~ubuntu-xenial), 
firefox-locale-de:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 
51.0+build2-0ubuntu0.16.04.1), systemd-sysv:amd64 (229-4ubuntu15, 
229-4ubuntu16), firefox-locale-en:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 
51.0+build2-0ubuntu0.16.04.1), libpam-systemd:amd64 (229-4ubuntu15, 
229-4ubuntu16), systemd:amd64 (229-4ubuntu15, 229-4ubuntu16), 
mysql-common:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), 
apt-utils:amd64 (1.2.18, 1.2.19), libmysqlclient20:i386 
(5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), firefox:amd64 
(50.1.0+build2-0ubuntu0.16.04.1, 51.0+build2-0ubuntu0.16.04.1), 
apt-transport-https:amd64 (1.2.18, 1.2.19), linux-tools-common:amd64 
(4.4.0-59.80, 4.4.0-62.83)
  Purge: linux-image-4.4.0-57-lowlatency:amd64 (4.4.0-57.78)
  End-Date: 2017-01-22  18:10:27

  Looking at /var/log/kernel.log (attached fragment) I found a backtrace
  including the i915 module.

  
  Attached is the output from lspci and lshw. Let me know if you need anything 
else.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-lowlatency 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-lowlatency 4.4.40
  Uname: Linux 4.4.0-62-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   luca   2999 F...m pulseaudio
   /dev/snd/controlC1:  luca   2999 F pulseaudio
   /dev/snd/controlC0:  luca   2999 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Jan 26 18:59:53 2017
  HibernationDevice: RESUME=UUID=841aac03-34a5-409e-a845-fdb0c6d7284a
  InstallationDate: Installed on 2015-11-12 (440 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20DT001TGE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-lowlatency 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-lowlatency N/A
   linux-backports-modules-4.4.0-62-lowlatency  N/A
   linux-firmware   1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-12-05 (52 days ago)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET54WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET54WW(1.16):bd08/19/2015:svnLENOVO:pn20DT001TGE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT001TGE
  dmi.product.version: ThinkPad L450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659621/+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 1659268] Re: Consistent boot time kernel panic

[Joseph Salisbury]

** Changed in: linux (Ubuntu Yakkety)
   Status: Triaged => Fix Committed

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  Consistent boot time kernel panic

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

Bug description:
  I don't know to provide the necessary crash dump and any other things
  that may be required to analyze this.

  The crash occured consistently on every boot with this kernel.

  I'm currently running  4.8.0-32-generic, which I still have installed.
  It does not cause this crash.

  I got this since first reboot after dist-upgrade to 17.04.

  BTW, it is not clear how to properly report a boot time kernel panic, so I 
asked this question:
  
http://askubuntu.com/questions/40792/whats-the-best-way-to-report-a-kernel-panic-bug#

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-12-generic 4.9.0-12.13
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.8.0-32-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/controlC29', 
'/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card29.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card29.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CurrentDesktop: XFCE
  Date: Wed Jan 25 13:35:17 2017
  HibernationDevice: RESUME=/dev/mapper/mightyiam--laptop--vg-swap_1
  MachineType: LENOVO 2007GCG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic 
root=/dev/mapper/username--laptop--vg-root ro splash quiet 
crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.162
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-01-24 (0 days ago)
  dmi.bios.date: 04/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE6WW (2.26 )
  dmi.board.name: 2007GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE6WW(2.26):bd04/01/2010:svnLENOVO:pn2007GCG:pvrThinkPadT60:rvnLENOVO:rn2007GCG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2007GCG
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659268/+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 1658255] Re: Kernel not enforcing module signatures under SecureBoot

[Kees Cook]

(Hm, dmesg WARN on IOMMU seems to think I need
910170442944e1f8674fd5ddbeeb8ccd1877ea98, but that's unrelated...)


** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658255/+attachment/4809482/+files/dmesg.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/1658255

Title:
  Kernel not enforcing module signatures under SecureBoot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  $ sudo mokutil --sbstate
  SecureBoot enabled
  $ cat /proc/sys/kernel/moksbstate_disabled
  0
  $ sudo insmod ./hello.ko
  $ echo $?
  0
  $ dmesg | grep Hello
  [00112.530866] Hello, world!
  $ strings /lib/modules/$(uname -r)/kernel/lib/test_module.ko | grep signature
  ~Module signature appended~
  $ strings hello.ko | grep signature
  $ uname -r
  4.8.0-34-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658255/+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 1659618] Re: Enable ARM64 support in kexec-tools

[Manoj Iyer]

[TESTING ON ARM64 HARDWARE]

$ cat /etc/issue
Ubuntu 16.04.1 LTS \n \l

$ sudo apt-add-repository ppa:manjo/kexec-tools
$ sudo apt update 
$ sudo apt install kexec-tools
$ kexec --version
kexec-tools 2.0.10 released 26 January 2017

$ ls /boot  
abi-4.7.0-2-generic grubSystem.map-4.7.0-2-generic
config-4.7.0-2-generic  initrd.img  vmlinuz
efi initrd.img-4.7.0-2-generic  vmlinuz-4.7.0-2-generic

$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.7.0-2-generic 
root=UUID=4f520e6e-6b21-460e-9c2b-332b188e393b ro splash quiet vt.handoff=7

$ sudo kexec -l /boot/vmlinuz-4.7.0-2-generic
--initrd=/boot/initrd.img-4.7.0-2-generic --command-line="root=UUID
=4f520e6e-6b21-460e-9c2b-332b188e393b ro vt.handoff=7"

$ sudo kexec -e 
[  76.658975] kexec_core: Starting new kernel
[0.00] Booting Linux on physical CPU 0x200
[0.00] Linux version 4.7.0-2-generic (buildd@bos01-arm64-008) (gcc 
version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) 
#5~pdaw1.1+.2-Ubuntu SMP Fri Jan 13 18:38:31 UTC 2017 (Ubuntu 
4.7.0-2.5~pdaw1.1+.2-generic 4.7.0)
[0.00] Boot CPU: AArch64 Processor [510f8000]

$ uname -a 
Linux pdaw1 4.7.0-2-generic #5~pdaw1.1+.2-Ubuntu SMP Fri Jan 13 
18:38:31 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux

$ cat /proc/cmdline 
root=UUID=4f520e6e-6b21-460e-9c2b-332b188e393b ro vt.handoff=7

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

Title:
  Enable ARM64 support in kexec-tools

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Xenial:
  Confirmed
Status in kexec-tools source package in Yakkety:
  Confirmed
Status in kexec-tools package in Debian:
  Unknown

Bug description:
  [IMPACT]
   * kexec-tools in Xenial (16.04) currently does not support ARM64
     architecture.
   * Backport support for ARM64 arch from upstream
     https://github.com/horms/kexec-tools
   * Majority of the patches are contained in kexec/arch/arm64/ except for
     one patch that impacts purgatory and common device tree routines.

  [TEST CASE]
   * I built kexec-tools for ARM64 and tested it on HW using the following
     testcase:
     $ sudo kexec -l /boot/vmlinuz--generic
   --initrd=/boot/initrd.img--generic
   --command-line="root=UUID= ro vt.handoff=7"
     $ sudo kexec -e
   * I was able to kexec the new kernel successfully.
   * [ 6702.357899] kexec_core: Starting new kernel
     [0.00] Booting Linux on physical CPU 0x200
     [0.00] Linux version -generic (buildd@bos01-arm64-008)
     (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
     [0.00] Boot CPU: AArch64 Processor [510f8000]

  [REGRESSION POTENTIAL]
   * Since patches are confined to arm[64] there is a low overall risk of
     regression.

  [OTHER INFO]
   * You can find a Xenial kexec-tools package built for AMD64, i386 and
     ARM64 in my PPA
     https://launchpad.net/~manjo/+archive/ubuntu/kexec-tools
   * This package is built using the Xenial source package for kexec-tools
     with ARM64 enablement patches applied.
   * Please pull the changes from my PPA package and integrate into Ubuntu
     Xenial kexec-tools after review.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+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 1659618] Re: Enable ARM64 support in kexec-tools

[Manoj Iyer]

The above test was that of the kexec-tools package that includes review
comments from dannf.

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

Title:
  Enable ARM64 support in kexec-tools

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Xenial:
  Confirmed
Status in kexec-tools source package in Yakkety:
  Confirmed
Status in kexec-tools package in Debian:
  Unknown

Bug description:
  [IMPACT]
   * kexec-tools in Xenial (16.04) currently does not support ARM64
     architecture.
   * Backport support for ARM64 arch from upstream
     https://github.com/horms/kexec-tools
   * Majority of the patches are contained in kexec/arch/arm64/ except for
     one patch that impacts purgatory and common device tree routines.

  [TEST CASE]
   * I built kexec-tools for ARM64 and tested it on HW using the following
     testcase:
     $ sudo kexec -l /boot/vmlinuz--generic
   --initrd=/boot/initrd.img--generic
   --command-line="root=UUID= ro vt.handoff=7"
     $ sudo kexec -e
   * I was able to kexec the new kernel successfully.
   * [ 6702.357899] kexec_core: Starting new kernel
     [0.00] Booting Linux on physical CPU 0x200
     [0.00] Linux version -generic (buildd@bos01-arm64-008)
     (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
     [0.00] Boot CPU: AArch64 Processor [510f8000]

  [REGRESSION POTENTIAL]
   * Since patches are confined to arm[64] there is a low overall risk of
     regression.

  [OTHER INFO]
   * You can find a Xenial kexec-tools package built for AMD64, i386 and
     ARM64 in my PPA
     https://launchpad.net/~manjo/+archive/ubuntu/kexec-tools
   * This package is built using the Xenial source package for kexec-tools
     with ARM64 enablement patches applied.
   * Please pull the changes from my PPA package and integrate into Ubuntu
     Xenial kexec-tools after review.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+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 1659618] Re: Enable ARM64 support in kexec-tools

[Manoj Iyer]

Updated changelog to refer to LP: #1659618

new debdiff attached.

** Patch added: "updated debdiff - changelog referring to LP# 1659618"
   
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+attachment/4809480/+files/updated-debdiff-withLP%23.diff

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

Title:
  Enable ARM64 support in kexec-tools

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Xenial:
  Confirmed
Status in kexec-tools source package in Yakkety:
  Confirmed
Status in kexec-tools package in Debian:
  Unknown

Bug description:
  [IMPACT]
   * kexec-tools in Xenial (16.04) currently does not support ARM64
     architecture.
   * Backport support for ARM64 arch from upstream
     https://github.com/horms/kexec-tools
   * Majority of the patches are contained in kexec/arch/arm64/ except for
     one patch that impacts purgatory and common device tree routines.

  [TEST CASE]
   * I built kexec-tools for ARM64 and tested it on HW using the following
     testcase:
     $ sudo kexec -l /boot/vmlinuz--generic
   --initrd=/boot/initrd.img--generic
   --command-line="root=UUID= ro vt.handoff=7"
     $ sudo kexec -e
   * I was able to kexec the new kernel successfully.
   * [ 6702.357899] kexec_core: Starting new kernel
     [0.00] Booting Linux on physical CPU 0x200
     [0.00] Linux version -generic (buildd@bos01-arm64-008)
     (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
     [0.00] Boot CPU: AArch64 Processor [510f8000]

  [REGRESSION POTENTIAL]
   * Since patches are confined to arm[64] there is a low overall risk of
     regression.

  [OTHER INFO]
   * You can find a Xenial kexec-tools package built for AMD64, i386 and
     ARM64 in my PPA
     https://launchpad.net/~manjo/+archive/ubuntu/kexec-tools
   * This package is built using the Xenial source package for kexec-tools
     with ARM64 enablement patches applied.
   * Please pull the changes from my PPA package and integrate into Ubuntu
     Xenial kexec-tools after review.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+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 1659087] Re: open(2) returns EOVERFLOW within tmpfs+userns

[Jonathan Calmels]

Glad you figured it out, I suspected this had something to do with the
may_create/may_o_create code paths but couldn't wrap my head around it.
Hopefully this will be addressed upstream in the near future.

This change in behavior is surprising though, maybe this should be
documented in user_namespaces(7).

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

Title:
  open(2) returns EOVERFLOW within tmpfs+userns

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  On Ubuntu 4.4.0-59.80-generic 4.4.35, open(2) returns EOVERFLOW when
  creating a file in tmpfs with user namespace enabled.

  This issue wasn't present in 4.4.0-47 and has probably been introduced
  by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634964

  Step to reproduce:

  $ unshare -r -U -m /bin/bash
  # mount -t tmpfs tmpfs /mnt
  # echo $$
  2354

  In another terminal:

  $ sudo nsenter -t 2354 -m  
  # touch /mnt/foo
  touch: cannot touch '/mnt/foo': Value too large for defined data type

  Note that we are not joining the user namespace when creating the file
  but we would expect `touch' to succeed and create the file with an
  inode set to INVALID_UID/GID (i.e. nobody:nogroup) within the mount
  namespace.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659087/+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 1659618] Re: Enable ARM64 support in kexec-tools

[dann frazier]

Thanks Manoj! A few comments on your prepared package.

- We need to fix in zesty and yakkety as well as xenial
- Version for xenial should be 1:2.0.10-1ubuntu2.1
- Is arm64_build.patch needed? I know we had to add it to Debian for compat w/ 
sid's toolchain, but I'm not sure we need it for Ubuntu or xenial (though it 
shouldn't hurt anything).
- There appears to be unncecessary changes to the other debian/patches files - 
like they were all regenerated. Can you avoid that to cleanup the debdiff for 
sru-team?

Other than that - looks good. Backport appears clean/straightforward.

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

Title:
  Enable ARM64 support in kexec-tools

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Xenial:
  Confirmed
Status in kexec-tools source package in Yakkety:
  Confirmed
Status in kexec-tools package in Debian:
  Unknown

Bug description:
  [IMPACT]
   * kexec-tools in Xenial (16.04) currently does not support ARM64
     architecture.
   * Backport support for ARM64 arch from upstream
     https://github.com/horms/kexec-tools
   * Majority of the patches are contained in kexec/arch/arm64/ except for
     one patch that impacts purgatory and common device tree routines.

  [TEST CASE]
   * I built kexec-tools for ARM64 and tested it on HW using the following
     testcase:
     $ sudo kexec -l /boot/vmlinuz--generic
   --initrd=/boot/initrd.img--generic
   --command-line="root=UUID= ro vt.handoff=7"
     $ sudo kexec -e
   * I was able to kexec the new kernel successfully.
   * [ 6702.357899] kexec_core: Starting new kernel
     [0.00] Booting Linux on physical CPU 0x200
     [0.00] Linux version -generic (buildd@bos01-arm64-008)
     (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
     [0.00] Boot CPU: AArch64 Processor [510f8000]

  [REGRESSION POTENTIAL]
   * Since patches are confined to arm[64] there is a low overall risk of
     regression.

  [OTHER INFO]
   * You can find a Xenial kexec-tools package built for AMD64, i386 and
     ARM64 in my PPA
     https://launchpad.net/~manjo/+archive/ubuntu/kexec-tools
   * This package is built using the Xenial source package for kexec-tools
     with ARM64 enablement patches applied.
   * Please pull the changes from my PPA package and integrate into Ubuntu
     Xenial kexec-tools after review.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+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 1659614] Re: [Lenovo M700z] Wifi malfunctions after updating system

[Joseph Salisbury]

Does the bug go away if you boot into the previous kernel version?

** Changed in: linux-lts-vivid (Ubuntu)
   Status: New => Triaged

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

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

** Changed in: linux (Ubuntu)
   Status: New => 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-lts-vivid in Ubuntu.
https://bugs.launchpad.net/bugs/1659614

Title:
  [Lenovo M700z] Wifi malfunctions after updating system

Status in linux package in Ubuntu:
  Triaged
Status in linux-lts-vivid package in Ubuntu:
  Triaged

Bug description:
  Lenovo M700z (CID 201601-20436) with its pre-installed image.

  [Steps To Reproduce]
  Enable the proposed pocket, and then update the system by 'sudo apt-get 
dist-upgrade'

  [Expected Result]
  Wifi works

  [Actual Result]
  Wifi malfunctions. The network indicator does not show any wireless AP.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-80-generic 3.19.0-80.88~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Jan 27 01:28:34 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-m700z-trusty-amd64-20160314-0
  InstallationDate: Installed on 2017-01-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Failed to find casper uuid.conf in 
'binary/casper/initrd.img-3.19.0-37-generic.old-dkms' LIVE Binary 20160314-09:31
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659614/+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 1659598] Re: [Dell Computer Corporation Precision 5510] mic malfunctions after updating system

[Joseph Salisbury]

Does the bug go away if you boot into the previous kernel version?

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

** Changed in: linux-lts-vivid (Ubuntu)
   Status: New => Triaged

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

** Changed in: linux (Ubuntu)
   Status: New => 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-lts-vivid in Ubuntu.
https://bugs.launchpad.net/bugs/1659598

Title:
  [Dell Computer Corporation Precision 5510] mic malfunctions after
  updating system

Status in linux package in Ubuntu:
  Triaged
Status in linux-lts-vivid package in Ubuntu:
  Triaged

Bug description:
  Dell Computer Corporation Precision 5510 (CID 201612-25281 and
  201612-25287) with pre-installed image.

  [Steps To Reproduce]
  Enable the proposed pocket, and then update the system by 'sudo apt-get 
dist-upgrade'

  [Expected Result]
  The mic works

  [Actual Result]
  The mic malfunctions. The mic didn't even record ambient noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-80-generic 3.19.0-80.88~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Jan 27 00:37:34 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2017-01-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659598/+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

Re: [Kernel-packages] [Bug 1658697] Re: package linux-image-3.13.0-107-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[MichaelGeorge]

Sorry made no difference
Mike


Sent from: YOGA TABLET

Joseph Salisbury  wrote:

>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 subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/1658697
>
>Title:
>  package linux-image-3.13.0-107-generic (not installed) failed to
>  install/upgrade: subprocess new pre-installation script returned error
>  exit status 1
>
>Status in linux package in Ubuntu:
>  Incomplete
>
>Bug description:
>  The software updater fails when used therefore I can't update the lubuntu 
> system.
>  Hope this can sorted as ubuntu is a very stable OS.
>  Thanks.
>
>  ProblemType: Package
>  DistroRelease: Ubuntu 14.04
>  Package: linux-image-3.13.0-107-generic (not installed)
>  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
>  Uname: Linux 3.13.0-24-generic i686
>  ApportVersion: 2.14.1-0ubuntu3.21
>  Architecture: i386
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  mike   1385 F lxpanel
>  CRDA: Error: [Errno 2] No such file or directory: 'iw'
>  Date: Mon Jan 23 14:09:24 2017
>  DpkgHistoryLog:
>   Start-Date: 2017-01-23  14:09:18
>   Commandline: apt-get -f install
>   Install: linux-headers-3.13.0-107:i386 (3.13.0-107.154, automatic), 
> linux-image-extra-3.13.0-107-generic:i386 (3.13.0-107.154, automatic), 
> linux-headers-3.13.0-107-generic:i386 (3.13.0-107.154, automatic), 
> linux-image-3.13.0-107-generic:i386 (3.13.0-107.154, automatic), 
> linux-image-3.13.0-105-generic:i386 (3.13.0-105.152, automatic)
>   Upgrade: linux-generic:i386 (3.13.0.105.113, 3.13.0.107.115), 
> linux-image-generic:i386 (3.13.0.105.113, 3.13.0.107.115), 
> linux-headers-generic:i386 (3.13.0.105.113, 3.13.0.107.115)
>  DpkgTerminalLog:
>   Preparing to unpack 
> .../linux-image-3.13.0-107-generic_3.13.0-107.154_i386.deb ...
>   This kernel does not support a non-PAE CPU.
>   dpkg: error processing archive 
> /var/cache/apt/archives/linux-image-3.13.0-107-generic_3.13.0-107.154_i386.deb
>  (--unpack):
>subprocess new pre-installation script returned error exit status 1
>  DuplicateSignature: package:linux-image-3.13.0-107-generic:(not 
> installed):subprocess new pre-installation script returned error exit status 1
>  ErrorMessage: subprocess new pre-installation script returned error exit 
> status 1
>  HibernationDevice: RESUME=UUID=8ea04b59-9c47-4d88-b7c2-9e999ce1435b
>  InstallationDate: Installed on 2016-11-16 (68 days ago)
>  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 
> (20140416.2)
>  Lsusb:
>   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>  MachineType: Samsung Electronics Aquila Slim Platform
>  ProcFB: 0 inteldrmfb
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
> root=UUID=7a8e48cc-a123-4e05-85b6-4187292d7699 ro rootflags=sync quiet splash 
> vt.handoff=7
>  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.12
>  RfKill:
>   0: phy0: Wireless LAN
>   Soft blocked: no
>   Hard blocked: no
>  SourcePackage: linux
>  Title: package linux-image-3.13.0-107-generic (not installed) failed to 
> install/upgrade: subprocess new pre-installation script returned error exit 
> status 1
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  WifiSyslog:
>   
>  dmi.bios.date: 09/17/2003
>  dmi.bios.vendor: Phoenix Technologies LTD
>  dmi.bios.version: 02VE
>  dmi.board.name: Aquila Slim Platform
>  dmi.board.vendor: Samsung Electronics
>  dmi.board.version: Revision 01
>  dmi.chassis.asset.tag: No Asset Tag
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: Samsung Electronics
>  dmi.chassis.version: revision 1.0
>  dmi.modalias: 
> dmi:bvnPhoenixTechnologiesLTD:bvr02VE:bd09/17/2003:svnSamsungElectronics:pnAquilaSlimPlatform:pvrRevision01:rvnSamsungElectronics:rnAquilaSlimPlatform:rvrRevision01:cvnSamsungElectronics:ct10:cvrrevision1.0:
>  dmi.product.name: Aquila Slim Platform
>  dmi.product.version: Revision 01
>  dmi.sys.vendor: Samsung Electronics
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658697/+subscriptions

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

Title:
  package linux-image-3.13.0-107-generic (not installed) failed to
  install/upgrade: subprocess new 

[Kernel-packages] [Bug 1659618] Re: Enable ARM64 support in kexec-tools

[Manoj Iyer]

** Description changed:

  [IMPACT]
   * kexec-tools in Xenial (16.04) currently does not support ARM64
     architecture.
   * Backport support for ARM64 arch from upstream
     https://github.com/horms/kexec-tools
   * Majority of the patches are contained in kexec/arch/arm64/ except for
     one patch that impacts purgatory and common device tree routines.
  
  [TEST CASE]
   * I built kexec-tools for ARM64 and tested it on HW using the following
     testcase:
     $ sudo kexec -l /boot/vmlinuz--generic
   --initrd=/boot/initrd.img--generic
   --command-line="root=UUID= ro vt.handoff=7"
     $ sudo kexec -e
   * I was able to kexec the new kernel successfully.
   * [ 6702.357899] kexec_core: Starting new kernel
     [0.00] Booting Linux on physical CPU 0x200
-    [0.00] Linux version -generic (buildd@bos01-arm64-008)
-(gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
+    [0.00] Linux version -generic (buildd@bos01-arm64-008)
+    (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
     [0.00] Boot CPU: AArch64 Processor [510f8000]
  
  [REGRESSION POTENTIAL]
   * Since patches are confined to arm[64] there is a low overall risk of
     regression.
  
  [OTHER INFO]
   * You can find a Xenial kexec-tools package built for AMD64, i386 and
     ARM64 in my PPA
-    https://launchpad.net/~manjo/+archive/ubuntu/devtools/
+    https://launchpad.net/~manjo/+archive/ubuntu/kexec-tools
   * This package is built using the Xenial source package for kexec-tools
     with ARM64 enablement patches applied.
   * Please pull the changes from my PPA package and integrate into Ubuntu
     Xenial kexec-tools after review.

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

Title:
  Enable ARM64 support in kexec-tools

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Xenial:
  Confirmed
Status in kexec-tools source package in Yakkety:
  Confirmed
Status in kexec-tools package in Debian:
  Unknown

Bug description:
  [IMPACT]
   * kexec-tools in Xenial (16.04) currently does not support ARM64
     architecture.
   * Backport support for ARM64 arch from upstream
     https://github.com/horms/kexec-tools
   * Majority of the patches are contained in kexec/arch/arm64/ except for
     one patch that impacts purgatory and common device tree routines.

  [TEST CASE]
   * I built kexec-tools for ARM64 and tested it on HW using the following
     testcase:
     $ sudo kexec -l /boot/vmlinuz--generic
   --initrd=/boot/initrd.img--generic
   --command-line="root=UUID= ro vt.handoff=7"
     $ sudo kexec -e
   * I was able to kexec the new kernel successfully.
   * [ 6702.357899] kexec_core: Starting new kernel
     [0.00] Booting Linux on physical CPU 0x200
     [0.00] Linux version -generic (buildd@bos01-arm64-008)
     (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
     [0.00] Boot CPU: AArch64 Processor [510f8000]

  [REGRESSION POTENTIAL]
   * Since patches are confined to arm[64] there is a low overall risk of
     regression.

  [OTHER INFO]
   * You can find a Xenial kexec-tools package built for AMD64, i386 and
     ARM64 in my PPA
     https://launchpad.net/~manjo/+archive/ubuntu/kexec-tools
   * This package is built using the Xenial source package for kexec-tools
     with ARM64 enablement patches applied.
   * Please pull the changes from my PPA package and integrate into Ubuntu
     Xenial kexec-tools after review.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+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 1659621] 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/1659621

Title:
  Random freezes and reboots since last kernel update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed my Laptop () started to freeze and reboot randomly and
  checking the apt logs the date where this started matches a kernel
  update:

  Start-Date: 2017-01-22  18:09:20
  Commandline: apt full-upgrade
  Requested-By: luca (1000)
  Install: linux-image-4.4.0-62-lowlatency:amd64 (4.4.0-62.83, automatic)
  Upgrade: linux-libc-dev:amd64 (4.4.0-59.80, 4.4.0-62.83), 
linux-image-lowlatency:amd64 (4.4.0.59.62, 4.4.0.62.65), libapt-inst2.0:amd64 
(1.2.18, 1.2.19), libsystemd0:amd64 (229-4ubuntu15, 229-4ubuntu16), 
libsystemd0:i386 (229-4ubuntu15, 229-4ubuntu16), apt:amd64 (1.2.18, 1.2.19), 
sudo:amd64 (1.8.16-0ubuntu1.2, 1.8.16-0ubuntu1.3), udev:amd64 (229-4ubuntu15, 
229-4ubuntu16), libapt-pkg5.0:amd64 (1.2.18, 1.2.19), libudev1:amd64 
(229-4ubuntu15, 229-4ubuntu16), libudev1:i386 (229-4ubuntu15, 229-4ubuntu16), 
docker-engine:amd64 (1.12.6-0~ubuntu-xenial, 1.13.0-0~ubuntu-xenial), 
firefox-locale-de:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 
51.0+build2-0ubuntu0.16.04.1), systemd-sysv:amd64 (229-4ubuntu15, 
229-4ubuntu16), firefox-locale-en:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 
51.0+build2-0ubuntu0.16.04.1), libpam-systemd:amd64 (229-4ubuntu15, 
229-4ubuntu16), systemd:amd64 (229-4ubuntu15, 229-4ubuntu16), 
mysql-common:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), 
apt-utils:amd64 (1.2.18, 1.2.19), libmysqlclient20:i386 
(5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), firefox:amd64 
(50.1.0+build2-0ubuntu0.16.04.1, 51.0+build2-0ubuntu0.16.04.1), 
apt-transport-https:amd64 (1.2.18, 1.2.19), linux-tools-common:amd64 
(4.4.0-59.80, 4.4.0-62.83)
  Purge: linux-image-4.4.0-57-lowlatency:amd64 (4.4.0-57.78)
  End-Date: 2017-01-22  18:10:27

  Looking at /var/log/kernel.log (attached fragment) I found a backtrace
  including the i915 module.

  
  Attached is the output from lspci and lshw. Let me know if you need anything 
else.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-lowlatency 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-lowlatency 4.4.40
  Uname: Linux 4.4.0-62-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   luca   2999 F...m pulseaudio
   /dev/snd/controlC1:  luca   2999 F pulseaudio
   /dev/snd/controlC0:  luca   2999 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Jan 26 18:59:53 2017
  HibernationDevice: RESUME=UUID=841aac03-34a5-409e-a845-fdb0c6d7284a
  InstallationDate: Installed on 2015-11-12 (440 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20DT001TGE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-lowlatency 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-lowlatency N/A
   linux-backports-modules-4.4.0-62-lowlatency  N/A
   linux-firmware   1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-12-05 (52 days ago)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET54WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET54WW(1.16):bd08/19/2015:svnLENOVO:pn20DT001TGE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT001TGE
  dmi.product.version: ThinkPad L450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659621/+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 1659623] 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/1659623

Title:
  Shutdown/reboot hang on Dell XPS 15 9550 BIOS 1.2.18+

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Dell XPS 15 9550 BIOS 1.2.18+, shutdown/reboot job is delayed for
  several seconds in Ubuntu kernel. After shutdown screen appears and
  all shutdown sequence had been done, the power LED turns off; however
  the front LED is flashing in orange for several seconds and the system
  finally turns off. Rebooting is also not working: front LED flashes in
  orange and the system just turns off.

  Switching to mainline kernel 4.9.6, or downgrading to BIOS 1.2.16
  solved the problem. Other Linux distro users didn't observed the
  problem, see also:

  * 
https://www.reddit.com/r/Dell/comments/5przxq/new_dell_xps_15_9550_bios_1219/
  * 
https://www.reddit.com/r/Dell/comments/5l9n3b/xps_15_9550_bios_1218_ubuntu_1610_shutdown_problem/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psj5638 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Jan 26 19:17:24 2017
  HibernationDevice: RESUME=UUID=2cfb78ae-e2b8-4d3a-9ab2-a61ae1a79fd1
  InstallationDate: Installed on 2016-01-21 (371 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=db90ced3-4cfe-4001-b877-d4aa35e7260f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (103 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.asset.tag: ainazi
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: ainazi
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659623/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

[Bug Watch Updater]

** Changed in: pulseaudio
   Status: Unknown => Confirmed

** Changed in: pulseaudio
   Importance: Unknown => Medium

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1659623] [NEW] Shutdown/reboot hang on Dell XPS 15 9550 BIOS 1.2.18+

[Shinjo Park]

Public bug reported:

On Dell XPS 15 9550 BIOS 1.2.18+, shutdown/reboot job is delayed for
several seconds in Ubuntu kernel. After shutdown screen appears and all
shutdown sequence had been done, the power LED turns off; however the
front LED is flashing in orange for several seconds and the system
finally turns off. Rebooting is also not working: front LED flashes in
orange and the system just turns off.

Switching to mainline kernel 4.9.6, or downgrading to BIOS 1.2.16 solved
the problem. Other Linux distro users didn't observed the problem, see
also:

* https://www.reddit.com/r/Dell/comments/5przxq/new_dell_xps_15_9550_bios_1219/
* 
https://www.reddit.com/r/Dell/comments/5l9n3b/xps_15_9550_bios_1218_ubuntu_1610_shutdown_problem/

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-34-generic 4.8.0-34.36
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  psj5638 F pulseaudio
CurrentDesktop: KDE
Date: Thu Jan 26 19:17:24 2017
HibernationDevice: RESUME=UUID=2cfb78ae-e2b8-4d3a-9ab2-a61ae1a79fd1
InstallationDate: Installed on 2016-01-21 (371 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Dell Inc. XPS 15 9550
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=db90ced3-4cfe-4001-b877-d4aa35e7260f ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-34-generic N/A
 linux-backports-modules-4.8.0-34-generic  N/A
 linux-firmware1.161.1
SourcePackage: linux
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (103 days ago)
dmi.bios.date: 12/22/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.19
dmi.board.asset.tag: ainazi
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: ainazi
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Shutdown/reboot hang on Dell XPS 15 9550 BIOS 1.2.18+

Status in linux package in Ubuntu:
  New

Bug description:
  On Dell XPS 15 9550 BIOS 1.2.18+, shutdown/reboot job is delayed for
  several seconds in Ubuntu kernel. After shutdown screen appears and
  all shutdown sequence had been done, the power LED turns off; however
  the front LED is flashing in orange for several seconds and the system
  finally turns off. Rebooting is also not working: front LED flashes in
  orange and the system just turns off.

  Switching to mainline kernel 4.9.6, or downgrading to BIOS 1.2.16
  solved the problem. Other Linux distro users didn't observed the
  problem, see also:

  * 
https://www.reddit.com/r/Dell/comments/5przxq/new_dell_xps_15_9550_bios_1219/
  * 
https://www.reddit.com/r/Dell/comments/5l9n3b/xps_15_9550_bios_1218_ubuntu_1610_shutdown_problem/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psj5638 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Jan 26 19:17:24 2017
  HibernationDevice: RESUME=UUID=2cfb78ae-e2b8-4d3a-9ab2-a61ae1a79fd1
  InstallationDate: Installed on 2016-01-21 (371 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=db90ced3-4cfe-4001-b877-d4aa35e7260f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (103 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.asset.tag: ainazi
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: ainazi
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1659621] Re: Random freezes and reboots since last kernel update

[luca]

** Attachment added: "lshw"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659621/+attachment/4809443/+files/lshw.txt

** Description changed:

  I noticed my Laptop () started to freeze and reboot randomly and
  checking the apt logs the date where this started matches a kernel
  update:
  
  Start-Date: 2017-01-22  18:09:20
  Commandline: apt full-upgrade
  Requested-By: luca (1000)
  Install: linux-image-4.4.0-62-lowlatency:amd64 (4.4.0-62.83, automatic)
  Upgrade: linux-libc-dev:amd64 (4.4.0-59.80, 4.4.0-62.83), 
linux-image-lowlatency:amd64 (4.4.0.59.62, 4.4.0.62.65), libapt-inst2.0:amd64 
(1.2.18, 1.2.19), libsystemd0:amd64 (229-4ubuntu15, 229-4ubuntu16), 
libsystemd0:i386 (229-4ubuntu15, 229-4ubuntu16), apt:amd64 (1.2.18, 1.2.19), 
sudo:amd64 (1.8.16-0ubuntu1.2, 1.8.16-0ubuntu1.3), udev:amd64 (229-4ubuntu15, 
229-4ubuntu16), libapt-pkg5.0:amd64 (1.2.18, 1.2.19), libudev1:amd64 
(229-4ubuntu15, 229-4ubuntu16), libudev1:i386 (229-4ubuntu15, 229-4ubuntu16), 
docker-engine:amd64 (1.12.6-0~ubuntu-xenial, 1.13.0-0~ubuntu-xenial), 
firefox-locale-de:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 
51.0+build2-0ubuntu0.16.04.1), systemd-sysv:amd64 (229-4ubuntu15, 
229-4ubuntu16), firefox-locale-en:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 
51.0+build2-0ubuntu0.16.04.1), libpam-systemd:amd64 (229-4ubuntu15, 
229-4ubuntu16), systemd:amd64 (229-4ubuntu15, 229-4ubuntu16), 
mysql-common:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), 
apt-utils:amd64 (1.2.18, 1.2.19), libmysqlclient20:i386 
(5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), firefox:amd64 
(50.1.0+build2-0ubuntu0.16.04.1, 51.0+build2-0ubuntu0.16.04.1), 
apt-transport-https:amd64 (1.2.18, 1.2.19), linux-tools-common:amd64 
(4.4.0-59.80, 4.4.0-62.83)
  Purge: linux-image-4.4.0-57-lowlatency:amd64 (4.4.0-57.78)
  End-Date: 2017-01-22  18:10:27
  
+ Looking at /var/log/kernel.log (attached fragment) I found a backtrace
+ including the i915 module.
  
- Looking at /var/log/kernel.log, I found:
  
- Jan 26 18:26:24 labs-064 kernel: [  633.172577] [ cut here 
]
- Jan 26 18:26:24 labs-064 kernel: [  633.172612] WARNING: CPU: 1 PID: 194 at 
/build/linux-W6HB68/linux-4.4.0/drivers/gpu/drm/i915/intel_uncore.c:619 hs
- w_unclaimed_reg_debug+0x69/0x90 [i915]()
- Jan 26 18:26:24 labs-064 kernel: [  633.172615] Unclaimed register detected 
before reading register 0x223a0
- Jan 26 18:26:24 labs-064 kernel: [  633.172616] Modules linked in: 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat 
nf_conntrack_
- ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables 
xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs 
cdc_mb
- im cdc_wdm cdc_ncm usbnet cdc_acm mii rfcomm bnep uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media
-  btusb btrtl btbcm btintel bluetooth intel_rapl snd_hda_codec_realtek 
snd_hda_codec_hdmi snd_hda_codec_generic x86_pkg_temp_thermal arc4 intel_powercl
- amp snd_hda_intel coretemp snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm 
iwlmvm snd_seq_midi snd_seq_midi_event snd_rawmidi irqbypass mac80211 inpu
- t_leds joydev snd_seq mei_me iwlwifi mei serio_raw thinkpad_acpi 
snd_seq_device intel_pch_thermal snd_timer rtsx_pci_ms cfg80211 nvram memstick 
lpc_ic
- h snd shpchp soundcore mac_hid parport_pc ppdev lp parport autofs4 drbg 
ansi_cprng algif_skcipher af_alg hid_cherry hid_generic usbhid hid dm_crypt rt
- sx_pci_sdmmc crct10dif_pclmul crc32_pclmul i915 ghash_clmulni_intel 
aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit 
dr
- m_kms_helper syscopyarea sysfillrect sysimgblt psmouse fb_sys_fops e1000e 
ahci drm libahci rtsx_pci ptp pps_core wmi fjes video
- Jan 26 18:26:24 labs-064 kernel: [  633.172696] CPU: 1 PID: 194 Comm: 
irq/44-i915 Not tainted 4.4.0-62-lowlatency #83-Ubuntu
- Jan 26 18:26:24 labs-064 kernel: [  633.172698] Hardware name: LENOVO 
20DT001TGE/Intel powered classmate PC, BIOS JDET54WW (1.16 ) 08/19/2015
- Jan 26 18:26:24 labs-064 kernel: [  633.172699]  0086 
bdc05e01 880220903c38 81400f01
- Jan 26 18:26:24 labs-064 kernel: [  633.172702]  880220903c80 
c02ad1e0 880220903c70 81081d02
- Jan 26 18:26:24 labs-064 kernel: [  633.172705]  88021fd8 
000223a0 88021fd84568 000223a0
- Jan 26 18:26:24 labs-064 kernel: [  633.172708] Call Trace:
- Jan 26 18:26:24 labs-064 kernel: [  633.172715]  [] 
dump_stack+0x63/0x82
- Jan 26 18:26:24 labs-064 kernel: [  633.172719]  [] 
warn_slowpath_common+0x82/0xc0
- Jan 26 18:26:24 labs-064 kernel: [  633.172721]  [] 
warn_slowpath_fmt+0x5c/0x80
- Jan 26 18:26:24 labs-064 kernel: [  633.172747]  [] 
hsw_unclaimed_reg_debug+0x69/0x90 [i915]
- Jan 26 18:26:24 labs-064 kernel: [  633.172771]  [] 
gen6_read32+0x59/0x1b0 [i915]
- Jan 26 18:26:24 labs-064 kernel: [  633.172775]  [] ? 
irq_finalize_oneshot.part.35+0xd0/0xd0
- Jan 26 18:26:24 

[Kernel-packages] [Bug 1659618] Re: [SRU] [Xenial] Enable ARM64 support in kexec-tools

[dann frazier]

** Changed in: kexec-tools (Ubuntu)
Milestone: xenial-updates => None

** Summary changed:

- [SRU] [Xenial] Enable ARM64 support in kexec-tools
+ Enable ARM64 support in kexec-tools

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

** Also affects: kexec-tools (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791943
   Importance: Unknown
   Status: Unknown

** Also affects: kexec-tools (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: kexec-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: kexec-tools (Ubuntu)
   Status: New => Confirmed

** Changed in: kexec-tools (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: kexec-tools (Ubuntu Yakkety)
   Status: New => Confirmed

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

Title:
  Enable ARM64 support in kexec-tools

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Xenial:
  Confirmed
Status in kexec-tools source package in Yakkety:
  Confirmed
Status in kexec-tools package in Debian:
  Unknown

Bug description:
  [IMPACT]
   * kexec-tools in Xenial (16.04) currently does not support ARM64
     architecture.
   * Backport support for ARM64 arch from upstream
     https://github.com/horms/kexec-tools
   * Majority of the patches are contained in kexec/arch/arm64/ except for
     one patch that impacts purgatory and common device tree routines.

  [TEST CASE]
   * I built kexec-tools for ARM64 and tested it on HW using the following
     testcase:
     $ sudo kexec -l /boot/vmlinuz--generic
   --initrd=/boot/initrd.img--generic
   --command-line="root=UUID= ro vt.handoff=7"
     $ sudo kexec -e
   * I was able to kexec the new kernel successfully.
   * [ 6702.357899] kexec_core: Starting new kernel
     [0.00] Booting Linux on physical CPU 0x200
     [0.00] Linux version -generic (buildd@bos01-arm64-008)
 (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
     [0.00] Boot CPU: AArch64 Processor [510f8000]

  [REGRESSION POTENTIAL]
   * Since patches are confined to arm[64] there is a low overall risk of
     regression.

  [OTHER INFO]
   * You can find a Xenial kexec-tools package built for AMD64, i386 and
     ARM64 in my PPA
     https://launchpad.net/~manjo/+archive/ubuntu/devtools/
   * This package is built using the Xenial source package for kexec-tools
     with ARM64 enablement patches applied.
   * Please pull the changes from my PPA package and integrate into Ubuntu
     Xenial kexec-tools after review.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+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 1659621] Re: Random freezes and reboots since last kernel update

[luca]

** Attachment added: "kernel.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659621/+attachment/4809444/+files/kernel.log

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

Title:
  Random freezes and reboots since last kernel update

Status in linux package in Ubuntu:
  New

Bug description:
  I noticed my Laptop () started to freeze and reboot randomly and
  checking the apt logs the date where this started matches a kernel
  update:

  Start-Date: 2017-01-22  18:09:20
  Commandline: apt full-upgrade
  Requested-By: luca (1000)
  Install: linux-image-4.4.0-62-lowlatency:amd64 (4.4.0-62.83, automatic)
  Upgrade: linux-libc-dev:amd64 (4.4.0-59.80, 4.4.0-62.83), 
linux-image-lowlatency:amd64 (4.4.0.59.62, 4.4.0.62.65), libapt-inst2.0:amd64 
(1.2.18, 1.2.19), libsystemd0:amd64 (229-4ubuntu15, 229-4ubuntu16), 
libsystemd0:i386 (229-4ubuntu15, 229-4ubuntu16), apt:amd64 (1.2.18, 1.2.19), 
sudo:amd64 (1.8.16-0ubuntu1.2, 1.8.16-0ubuntu1.3), udev:amd64 (229-4ubuntu15, 
229-4ubuntu16), libapt-pkg5.0:amd64 (1.2.18, 1.2.19), libudev1:amd64 
(229-4ubuntu15, 229-4ubuntu16), libudev1:i386 (229-4ubuntu15, 229-4ubuntu16), 
docker-engine:amd64 (1.12.6-0~ubuntu-xenial, 1.13.0-0~ubuntu-xenial), 
firefox-locale-de:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 
51.0+build2-0ubuntu0.16.04.1), systemd-sysv:amd64 (229-4ubuntu15, 
229-4ubuntu16), firefox-locale-en:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 
51.0+build2-0ubuntu0.16.04.1), libpam-systemd:amd64 (229-4ubuntu15, 
229-4ubuntu16), systemd:amd64 (229-4ubuntu15, 229-4ubuntu16), 
mysql-common:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), 
apt-utils:amd64 (1.2.18, 1.2.19), libmysqlclient20:i386 
(5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), firefox:amd64 
(50.1.0+build2-0ubuntu0.16.04.1, 51.0+build2-0ubuntu0.16.04.1), 
apt-transport-https:amd64 (1.2.18, 1.2.19), linux-tools-common:amd64 
(4.4.0-59.80, 4.4.0-62.83)
  Purge: linux-image-4.4.0-57-lowlatency:amd64 (4.4.0-57.78)
  End-Date: 2017-01-22  18:10:27

  Looking at /var/log/kernel.log (attached fragment) I found a backtrace
  including the i915 module.

  
  Attached is the output from lspci and lshw. Let me know if you need anything 
else.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-lowlatency 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-lowlatency 4.4.40
  Uname: Linux 4.4.0-62-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   luca   2999 F...m pulseaudio
   /dev/snd/controlC1:  luca   2999 F pulseaudio
   /dev/snd/controlC0:  luca   2999 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Jan 26 18:59:53 2017
  HibernationDevice: RESUME=UUID=841aac03-34a5-409e-a845-fdb0c6d7284a
  InstallationDate: Installed on 2015-11-12 (440 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20DT001TGE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-lowlatency 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-lowlatency N/A
   linux-backports-modules-4.4.0-62-lowlatency  N/A
   linux-firmware   1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-12-05 (52 days ago)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET54WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET54WW(1.16):bd08/19/2015:svnLENOVO:pn20DT001TGE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT001TGE
  dmi.product.version: ThinkPad L450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659621/+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 1655748] Re: linux-lts-vivid: 3.19.0-80.88~14.04.1 -proposed tracker

[Taihsiang Ho]

Certification test found two potential regressions:
LP: #1659598
LP: #1659614

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

Title:
  linux-lts-vivid: 3.19.0-80.88~14.04.1 -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:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-80.88~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
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655745
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655748/+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 1659621] [NEW] Random freezes and reboots since last kernel update

[luca]

Public bug reported:

I noticed my Laptop () started to freeze and reboot randomly and
checking the apt logs the date where this started matches a kernel
update:

Start-Date: 2017-01-22  18:09:20
Commandline: apt full-upgrade
Requested-By: luca (1000)
Install: linux-image-4.4.0-62-lowlatency:amd64 (4.4.0-62.83, automatic)
Upgrade: linux-libc-dev:amd64 (4.4.0-59.80, 4.4.0-62.83), 
linux-image-lowlatency:amd64 (4.4.0.59.62, 4.4.0.62.65), libapt-inst2.0:amd64 
(1.2.18, 1.2.19), libsystemd0:amd64 (229-4ubuntu15, 229-4ubuntu16), 
libsystemd0:i386 (229-4ubuntu15, 229-4ubuntu16), apt:amd64 (1.2.18, 1.2.19), 
sudo:amd64 (1.8.16-0ubuntu1.2, 1.8.16-0ubuntu1.3), udev:amd64 (229-4ubuntu15, 
229-4ubuntu16), libapt-pkg5.0:amd64 (1.2.18, 1.2.19), libudev1:amd64 
(229-4ubuntu15, 229-4ubuntu16), libudev1:i386 (229-4ubuntu15, 229-4ubuntu16), 
docker-engine:amd64 (1.12.6-0~ubuntu-xenial, 1.13.0-0~ubuntu-xenial), 
firefox-locale-de:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 
51.0+build2-0ubuntu0.16.04.1), systemd-sysv:amd64 (229-4ubuntu15, 
229-4ubuntu16), firefox-locale-en:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 
51.0+build2-0ubuntu0.16.04.1), libpam-systemd:amd64 (229-4ubuntu15, 
229-4ubuntu16), systemd:amd64 (229-4ubuntu15, 229-4ubuntu16), 
mysql-common:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), 
apt-utils:amd64 (1.2.18, 1.2.19), libmysqlclient20:i386 
(5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), firefox:amd64 
(50.1.0+build2-0ubuntu0.16.04.1, 51.0+build2-0ubuntu0.16.04.1), 
apt-transport-https:amd64 (1.2.18, 1.2.19), linux-tools-common:amd64 
(4.4.0-59.80, 4.4.0-62.83)
Purge: linux-image-4.4.0-57-lowlatency:amd64 (4.4.0-57.78)
End-Date: 2017-01-22  18:10:27

Looking at /var/log/kernel.log (attached fragment) I found a backtrace
including the i915 module.


Attached is the output from lspci and lshw. Let me know if you need anything 
else.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-62-lowlatency 4.4.0-62.83
ProcVersionSignature: Ubuntu 4.4.0-62.83-lowlatency 4.4.40
Uname: Linux 4.4.0-62-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0p:   luca   2999 F...m pulseaudio
 /dev/snd/controlC1:  luca   2999 F pulseaudio
 /dev/snd/controlC0:  luca   2999 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
Date: Thu Jan 26 18:59:53 2017
HibernationDevice: RESUME=UUID=841aac03-34a5-409e-a845-fdb0c6d7284a
InstallationDate: Installed on 2015-11-12 (440 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 20DT001TGE
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-lowlatency 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-62-lowlatency N/A
 linux-backports-modules-4.4.0-62-lowlatency  N/A
 linux-firmware   1.157.8
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-12-05 (52 days ago)
dmi.bios.date: 08/19/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: JDET54WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: Intel powered classmate PC
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrJDET54WW(1.16):bd08/19/2015:svnLENOVO:pn20DT001TGE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20DT001TGE
dmi.product.version: ThinkPad L450
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug package-from-proposed xenial

** Attachment added: "lspci"
   https://bugs.launchpad.net/bugs/1659621/+attachment/4809426/+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/1659621

Title:
  Random freezes and reboots since last kernel update

Status in linux package in Ubuntu:
  New

Bug description:
  I noticed my Laptop () started to freeze and reboot randomly and
  checking the apt logs the date where this started matches a kernel
  update:

  Start-Date: 2017-01-22  18:09:20
  Commandline: apt full-upgrade
  Requested-By: luca (1000)
  Install: linux-image-4.4.0-62-lowlatency:amd64 (4.4.0-62.83, automatic)
  Upgrade: linux-libc-dev:amd64 (4.4.0-59.80, 4.4.0-62.83), 
linux-image-lowlatency:amd64 (4.4.0.59.62, 4.4.0.62.65), libapt-inst2.0:amd64 
(1.2.18, 1.2.19), libsystemd0:amd64 (229-4ubuntu15, 229-4ubuntu16), 
libsystemd0:i386 (229-4ubuntu15, 229-4ubuntu16), apt:amd64 (1.2.18, 1.2.19), 
sudo:amd64 (1.8.16-0ubuntu1.2, 1.8.16-0ubuntu1.3), udev:amd64 (229-4ubuntu15, 
229-4ubuntu16), libapt-pkg5.0:amd64 (1.2.18, 1.2.19), libudev1:amd64 
(229-4ubuntu15, 229-4ubuntu16), libudev1:i386 (229-4ubuntu15, 

[Kernel-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Alberto Salvia Novella]

** 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/1597415

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597415/+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 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3

[Alberto Salvia Novella]

** Changed in: flash-kernel (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/1652504

Title:
  Recent updates broke Ubuntu on Raspberry Pi 3

Status in flash-kernel package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I've been running Raspberry Pi 3 with Ubuntu as described here 
https://wiki.ubuntu.com/ARM/RaspberryPi

  I've installed Ubuntu 16.04 and then upgraded to 16.10 and have been
  using this setup successfully since October up until last week.
  Unfortunately one of the latest kernel updates broke the installation
  and I found out the same happened for Ubuntu 16.04 LTS - and therefore
  I can no longer run up-to-date Ubuntu installation (with updated
  kernel) on my RPI.

  I am getting this error:
  Error image is not a fdt - must reset the board to recover

  I also tried this but it didn't help me:
  https://www.raspberrypi.org/forums/viewtopic.php?f=28=168838

  Now I know running Ubuntu on RPI3 this way is not officially
  supported, but since Ubuntu Snappy is supported I thought someone here
  could know what is going on.

  Thank you very much.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1652504/+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 1659618] [NEW] [SRU] [Xenial] Enable ARM64 support in kexec-tools

[Manoj Iyer]

Public bug reported:

[IMPACT]
 * kexec-tools in Xenial (16.04) currently does not support ARM64
   architecture.
 * Backport support for ARM64 arch from upstream
   https://github.com/horms/kexec-tools
 * Majority of the patches are contained in kexec/arch/arm64/ except for
   one patch that impacts purgatory and common device tree routines.

[TEST CASE]
 * I built kexec-tools for ARM64 and tested it on HW using the following
   testcase:
   $ sudo kexec -l /boot/vmlinuz--generic
 --initrd=/boot/initrd.img--generic
 --command-line="root=UUID= ro vt.handoff=7"
   $ sudo kexec -e
 * I was able to kexec the new kernel successfully.
 * [ 6702.357899] kexec_core: Starting new kernel
   [0.00] Booting Linux on physical CPU 0x200
   [0.00] Linux version -generic (buildd@bos01-arm64-008)
   (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
   [0.00] Boot CPU: AArch64 Processor [510f8000]

[REGRESSION POTENTIAL]
 * Since patches are confined to arm[64] there is a low overall risk of
   regression.

[OTHER INFO]
 * You can find a Xenial kexec-tools package built for AMD64, i386 and
   ARM64 in my PPA
   https://launchpad.net/~manjo/+archive/ubuntu/devtools/
 * This package is built using the Xenial source package for kexec-tools
   with ARM64 enablement patches applied.
 * Please pull the changes from my PPA package and integrate into Ubuntu
   Xenial kexec-tools after review.

** Affects: kexec-tools (Ubuntu)
 Importance: High
 Assignee: Louis Bouchard (louis-bouchard)
 Status: New

** Package changed: ubuntu => kexec-tools (Ubuntu)

** Changed in: kexec-tools (Ubuntu)
   Importance: Undecided => High

** Description changed:

  [IMPACT]
-  * kexec-tools in Xenial (16.04) currently does not support ARM64 
architecture.
-  * Backport support for ARM64 arch from upstream 
https://github.com/horms/kexec-tools
-  * Majority of the patches are contained in kexec/arch/arm64/ except for one 
patch that impacts
-purgatory and common device tree routines. 
+  * kexec-tools in Xenial (16.04) currently does not support ARM64 
architecture.
+  * Backport support for ARM64 arch from upstream
+https://github.com/horms/kexec-tools
+  * Majority of the patches are contained in kexec/arch/arm64/ except for  
+one patch that impacts purgatory and common device tree routines.
  
  [TEST CASE]
-  * I built kexec-tools for ARM64 and tested it on HW using the following 
testcase:
-$ sudo kexec -l /boot/vmlinuz--generic 
--initrd=/boot/initrd.img--generic
-  --command-line="root=UUID= ro vt.handoff=7"
-$ sudo kexec -e
-  * I was able to kexec the new kernel successfully. 
-  * [ 6702.357899] kexec_core: Starting new kernel
-[0.00] Booting Linux on physical CPU 0x200
-[0.00] Linux version -generic (buildd@bos01-arm64-008) 
(gcc version 5.4.0   
-20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
-[0.00] Boot CPU: AArch64 Processor [510f8000]
-
+  * I built kexec-tools for ARM64 and tested it on HW using the following 
+testcase:
+    $ sudo kexec -l /boot/vmlinuz--generic 
+  --initrd=/boot/initrd.img--generic
+  --command-line="root=UUID= ro vt.handoff=7"
+    $ sudo kexec -e
+  * I was able to kexec the new kernel successfully.
+  * [ 6702.357899] kexec_core: Starting new kernel
+    [0.00] Booting Linux on physical CPU 0x200
+    [0.00] Linux version -generic (buildd@bos01-arm64-008) 
(gcc version 5.4.0
+    20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
+    [0.00] Boot CPU: AArch64 Processor [510f8000]
+ 
  [REGRESSION POTENTIAL]
-  * Since patches are confined to arm[64] there is a low overall risk of 
regression.
+  * Since patches are confined to arm[64] there is a low overall risk of  
+regression.
  
  [OTHER INFO]
-  * You can find a Xenial kexec-tools package built for AMD64, i386 and ARM64 
in my PPA
- https://launchpad.net/~manjo/+archive/ubuntu/devtools/
-  * This package is built using the Xenial source package for kexec-tools with 
ARM64 enablement 
-patches applied.
-  * Please pull the changes from my PPA package and integrate into Ubuntu 
Xenial kexec-tools after
-review.
+  * You can find a Xenial kexec-tools package built for AMD64, i386 and 
+ARM64 in my PPA
+    https://launchpad.net/~manjo/+archive/ubuntu/devtools/
+  * This package is built using the Xenial source package for kexec-tools 
+with ARM64 enablement patches applied.
+  * Please pull the changes from my PPA package and integrate into Ubuntu 
+Xenial kexec-tools after review.

** Description changed:

  [IMPACT]
-  * kexec-tools in Xenial (16.04) currently does not support ARM64 
architecture.
-  * Backport support for ARM64 arch from upstream
-https://github.com/horms/kexec-tools
-  * Majority of the patches are contained in kexec/arch/arm64/ except for  
-one patch that impacts purgatory and common device tree routines.
+  * 

[Kernel-packages] [Bug 1659618] [NEW] [SRU] [Xenial] Enable ARM64 support in kexec-tools

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[IMPACT]
 * kexec-tools in Xenial (16.04) currently does not support ARM64 architecture.
 * Backport support for ARM64 arch from upstream 
https://github.com/horms/kexec-tools
 * Majority of the patches are contained in kexec/arch/arm64/ except for one 
patch that impacts
   purgatory and common device tree routines. 

[TEST CASE]
 * I built kexec-tools for ARM64 and tested it on HW using the following 
testcase:
   $ sudo kexec -l /boot/vmlinuz--generic 
--initrd=/boot/initrd.img--generic
 --command-line="root=UUID= ro vt.handoff=7"
   $ sudo kexec -e
 * I was able to kexec the new kernel successfully. 
 * [ 6702.357899] kexec_core: Starting new kernel
   [0.00] Booting Linux on physical CPU 0x200
   [0.00] Linux version -generic (buildd@bos01-arm64-008) (gcc 
version 5.4.0   
   20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
   [0.00] Boot CPU: AArch64 Processor [510f8000]
   
[REGRESSION POTENTIAL]
 * Since patches are confined to arm[64] there is a low overall risk of 
regression.

[OTHER INFO]
 * You can find a Xenial kexec-tools package built for AMD64, i386 and ARM64 in 
my PPA
https://launchpad.net/~manjo/+archive/ubuntu/devtools/
 * This package is built using the Xenial source package for kexec-tools with 
ARM64 enablement 
   patches applied.
 * Please pull the changes from my PPA package and integrate into Ubuntu Xenial 
kexec-tools after
   review.

** Affects: kexec-tools (Ubuntu)
 Importance: High
 Assignee: Louis Bouchard (louis-bouchard)
 Status: New

-- 
[SRU] [Xenial] Enable ARM64 support in kexec-tools
https://bugs.launchpad.net/bugs/1659618
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to kexec-tools in Ubuntu.

-- 
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 1648867] aws--aio-dio-bugs--xenial (amd64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/ip-172-31-8-139__4.4.0-62.83__2017-01-23_02-36-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/1648867

Title:
  linux: 4.4.0-57.78 -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:
  Fix Released
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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-57.78 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648867/+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 1659598] Re: [Dell Computer Corporation Precision 5510] mic malfunctions after updating system

[Taihsiang Ho]

** Tags added: 201612-25281 201612-25287 taipei-lab

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

Title:
  [Dell Computer Corporation Precision 5510] mic malfunctions after
  updating system

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  Dell Computer Corporation Precision 5510 (CID 201612-25281 and
  201612-25287) with pre-installed image.

  [Steps To Reproduce]
  Enable the proposed pocket, and then update the system by 'sudo apt-get 
dist-upgrade'

  [Expected Result]
  The mic works

  [Actual Result]
  The mic malfunctions. The mic didn't even record ambient noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-80-generic 3.19.0-80.88~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Jan 27 00:37:34 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2017-01-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1659598/+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 1659614] [NEW] [Lenovo M700z] Wifi malfunctions after updating system

[Taihsiang Ho]

Public bug reported:

Lenovo M700z (CID 201601-20436) with its pre-installed image.

[Steps To Reproduce]
Enable the proposed pocket, and then update the system by 'sudo apt-get 
dist-upgrade'

[Expected Result]
Wifi works

[Actual Result]
Wifi malfunctions. The network indicator does not show any wireless AP.



ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-80-generic 3.19.0-80.88~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-80-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Fri Jan 27 01:28:34 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-sutton-m700z-trusty-amd64-20160314-0
InstallationDate: Installed on 2017-01-25 (1 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Failed to find casper uuid.conf in 
'binary/casper/initrd.img-3.19.0-37-generic.old-dkms' LIVE Binary 20160314-09:31
SourcePackage: linux-lts-vivid
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: 201612-25281 201612-25287 amd64 apport-bug package-from-proposed 
taipei-lab trusty

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

Title:
  [Lenovo M700z] Wifi malfunctions after updating system

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  Lenovo M700z (CID 201601-20436) with its pre-installed image.

  [Steps To Reproduce]
  Enable the proposed pocket, and then update the system by 'sudo apt-get 
dist-upgrade'

  [Expected Result]
  Wifi works

  [Actual Result]
  Wifi malfunctions. The network indicator does not show any wireless AP.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-80-generic 3.19.0-80.88~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Jan 27 01:28:34 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-m700z-trusty-amd64-20160314-0
  InstallationDate: Installed on 2017-01-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Failed to find casper uuid.conf in 
'binary/casper/initrd.img-3.19.0-37-generic.old-dkms' LIVE Binary 20160314-09:31
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1659614/+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 1658101] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 64, failed: 2

[Brad Figg]

tests ran:  64, failed: 2;
  
http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_16-40-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/1658101

Title:
  linux: 4.9.0-15.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-15.16 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1658101/+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 1659268] Re: Consistent boot time kernel panic

[Shahar Or]

The following package from zesty-proposed does not have this crash:

Package: linux-image-4.9.0-15-generic
Priority: optional
Section: kernel
Installed-Size: 67599
Maintainer: Ubuntu Kernel Team 
Architecture: amd64
Source: linux
Version: 4.9.0-15.16
Provides: fuse-module, ivtv-modules, kvm-api-4, linux-image, 
redhat-cluster-modules, spl-dkms, virtualbox-guest-modules, zfs-dkms
Depends: initramfs-tools | linux-initramfs-tool, kmod
Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo
Suggests: fdutils, linux-doc-4.9.0 | linux-source-4.9.0, linux-tools, 
linux-headers-4.9.0-15-generic
Filename: pool/main/l/linux/linux-image-4.9.0-15-generic_4.9.0-15.16_amd64.deb
Size: 22942540
MD5sum: 18e0a5ef0cb3ee2f17af575e4f7a6f78
SHA1: d3c740859ed36a440a29217ca36e8716c8953b88
SHA256: 3af0399fcc3038f5286c37936d12cb9a26bec7e5fae5d0e3622e117c93096591
Description: Linux kernel image for version 4.9.0 on 64 bit x86 SMP
Description-md5: b760ff9cdd3fd1409e7e9503f48bea3b
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu

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

Title:
  Consistent boot time kernel panic

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Triaged

Bug description:
  I don't know to provide the necessary crash dump and any other things
  that may be required to analyze this.

  The crash occured consistently on every boot with this kernel.

  I'm currently running  4.8.0-32-generic, which I still have installed.
  It does not cause this crash.

  I got this since first reboot after dist-upgrade to 17.04.

  BTW, it is not clear how to properly report a boot time kernel panic, so I 
asked this question:
  
http://askubuntu.com/questions/40792/whats-the-best-way-to-report-a-kernel-panic-bug#

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-12-generic 4.9.0-12.13
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.8.0-32-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/controlC29', 
'/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card29.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card29.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CurrentDesktop: XFCE
  Date: Wed Jan 25 13:35:17 2017
  HibernationDevice: RESUME=/dev/mapper/mightyiam--laptop--vg-swap_1
  MachineType: LENOVO 2007GCG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic 
root=/dev/mapper/username--laptop--vg-root ro splash quiet 
crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.162
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-01-24 (0 days ago)
  dmi.bios.date: 04/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE6WW (2.26 )
  dmi.board.name: 2007GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE6WW(2.26):bd04/01/2010:svnLENOVO:pn2007GCG:pvrThinkPadT60:rvnLENOVO:rn2007GCG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2007GCG
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659268/+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 1646068] Re: bonding: don't use stale speed and duplex information

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu Trusty)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Vivid)
   Status: Incomplete => In Progress

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

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

Title:
  bonding: don't use stale speed and duplex information

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 Xenial:
  In Progress

Bug description:
  This upstream patch is missing (needed for all kernel between 3.9 and
  4.4 (both included)):

  266b495f11d6 bonding: don't use stale speed and duplex information
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=266b495f11d6

  Without this patch, reported speeds can be wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646068/+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

Re: [Kernel-packages] [Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40

[Andrew McDermott]

I haven't tried recently as I disabled IPv6 on my machine.

On 26 January 2017 at 16:31, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Does this bug still happen with the latest Xenial updates?
>
> ** Changed in: linux (Ubuntu)
>Status: In Progress => Incomplete
>
> ** Changed in: linux (Ubuntu Xenial)
>Status: In Progress => Incomplete
>
> ** Changed in: linux (Ubuntu Yakkety)
>Status: In Progress => Incomplete
>
> ** Changed in: linux (Ubuntu)
>  Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
>
> ** Changed in: linux (Ubuntu Xenial)
>  Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
>
> ** Changed in: linux (Ubuntu Yakkety)
>  Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1614953
>
> Title:
>   hw csum failure when IPv6 interfaces configured in
>   netdev_rx_csum_fault+0x38/0x40
>
> Status in linux package in Ubuntu:
>   Incomplete
> Status in linux source package in Xenial:
>   Incomplete
> Status in linux source package in Yakkety:
>   Incomplete
>
> Bug description:
>   Since I started using IPv6 I noticed the following kernel error:
>
>   Thu Aug 18 15:05:01 2016] : hw csum failure
>   [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread
> Tainted: P   OE   4.4.0-34-generic #53-Ubuntu
>   [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd.
> To be filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013
>   [Thu Aug 18 15:05:01 2016]  0286 c05989f2
> 8807573dfcd0 813f11b3
>   [Thu Aug 18 15:05:01 2016]   0008
> 8807573dfce8 8171f6e8
>   [Thu Aug 18 15:05:01 2016]  0074 8807573dfd30
> 8171639b fe091360
>   [Thu Aug 18 15:05:01 2016] Call Trace:
>   [Thu Aug 18 15:05:01 2016]  [] dump_stack+0x63/0x90
>   [Thu Aug 18 15:05:01 2016]  []
> netdev_rx_csum_fault+0x38/0x40
>   [Thu Aug 18 15:05:01 2016]  []
> skb_copy_and_csum_datagram_msg+0xeb/0x100
>   [Thu Aug 18 15:05:01 2016]  []
> udpv6_recvmsg+0x233/0x670
>   [Thu Aug 18 15:05:01 2016]  [] inet_recvmsg+0x7e/0xb0
>   [Thu Aug 18 15:05:01 2016]  [] sock_recvmsg+0x3b/0x50
>   [Thu Aug 18 15:05:01 2016]  [] SYSC_recvfrom+0xe1/0x160
>   [Thu Aug 18 15:05:01 2016]  [] ? wake_up_q+0x70/0x70
>   [Thu Aug 18 15:05:01 2016]  [] SyS_recvfrom+0xe/0x10
>   [Thu Aug 18 15:05:01 2016]  []
> entry_SYSCALL_64_fastpath+0x16/0x71
>
>   It repeats periodically:
>
>   $ dmesg -T | grep 'hw csum failure' | wc -l
>   201
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: linux-image-4.4.0-34-generic 4.4.0-34.53
>   ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
>   Uname: Linux 4.4.0-34-generic x86_64
>   NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm
> nvidia_modeset nvidia
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Fri Aug 19 13:47:54 2016
>   HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2
>   InstallationDate: Installed on 2016-04-24 (116 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
>   ProcFB: 0 EFI VGA
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed
> root=/dev/mapper/rootpool-rootvol ro intel_iommu=on
>   RelatedPackageVersions:
>linux-restricted-modules-4.4.0-34-generic N/A
>linux-backports-modules-4.4.0-34-generic  N/A
>linux-firmware1.157.3
>   RfKill:
>
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 11/14/2013
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: F22
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: Z77-D3H
>   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.:bvrF22:bd11/14/2013:
> svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:
> rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:
> cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
>   dmi.product.name: To be filled by O.E.M.
>   dmi.product.version: To be filled by O.E.M.
>   dmi.sys.vendor: Gigabyte Technology Co., Ltd.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1614953/+subscriptions
>


-- 
Andrew McDermott 
Juju Core Sapphire team 

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

[Kernel-packages] [Bug 1659340] Re: Linux kernel 4.8 hangs at boot up

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu Trusty)
   Status: New => In Progress

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

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  Linux kernel 4.8 hangs at boot up

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
  Windows 10 and Ubuntu 16.10.

  Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
  When I try to start with any of the 4.8.0 kernels delivered with regular
  Ubuntu updates, they all hang after printing

Läser in Linux 4.8.0-34-generic ...
Läser in initial ramdisk ...

  Sorry for the partly Swedish text. I guess that the lines would start with
  "Loading" instead of "Läser in" on an English version.

  The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34
  and with -generic, -generic (upstart) and -generic (recovery mode).

  After a while the fan runs at full speed, as if the processor is working
  hard, but nothing happens.

  After I've tried in vain to start with Linux 4.8.0-xx, and then starts
  with 4.4.0-45, the following errors are usually printed:

  [  2.511733] usb 4-3: string descriptor 0 read error: -22
  [  3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight 
controller
  /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
  [ 21.335117] usb 4-3: string descriptor 0 read error: -22

  When a successful start has not been immediately preceded by a failed start,
  only the line beginning "/dev/sda7" is printed.

  I have previously commented on bug #1635447. As recommended there, I've
  also tested with the upstream kernel 4.10-rc3. It worked just as bad as
  4.8.0.

  I tried to report this bug with 'ubuntu-bug linux' after I had booted with
  the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45-
  generic is not an official Ubuntu package.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjell  2022 F pulseaudio
   /dev/snd/controlC1:  kjell  2022 F pulseaudio
   /dev/snd/controlC0:  kjell  2022 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb
  InstallationDate: Installed on 2013-09-25 (1218 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V5-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551G
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+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 1483343] Re: NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr tests

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu Vivid)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux-lts-xenial (Ubuntu)
   Status: Triaged => 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/1483343

Title:
  NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr
  tests

Status in linux package in Ubuntu:
  Incomplete
Status in linux-lts-xenial package in Ubuntu:
  Incomplete
Status in linux source package in Vivid:
  Incomplete

Bug description:
  ---Problem Description---
  NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr tests

  ---uname output---
  Linux alp15 3.19.0-18-generic #18~14.04.1-Ubuntu SMP Wed May 20 09:40:36 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 

  ---Steps to Reproduce---
  Install a P8 Power VM LPAR with Ubuntu 14.04.2 ISO.
  Then install the Ubuntu 14.04.3 kernel on the same and reboot.
  Then compile and build the LTP latest test suites on the same.

  root@alp15:~# tar -xvf ltp-full-20150420.tar.bz2
  root@alp15:~# cd ltp-full-20150420/
  root@alp15:~/ltp-full-20150420# ls
  aclocal.m4  configure execltp.in  install-sh  Makefile  
READMErunltplite.shtestcasesutils
  autom4te.cache  configure.ac  IDcheck.sh  lib Makefile.release  
README.kernel_config  runtest  testscripts  ver_linux
  config.guessCOPYING   include ltpmenu missing   
runalltests.shscenario_groups  TODO VERSION
  config.sub  doc   INSTALL m4  pan   
runltpscripts  tools
  root@alp15:~/ltp-full-20150420# ./configure
  root@alp15:~/ltp-full-20150420# make
  root@alp15:~/ltp-full-20150420# make install

  root@alp15:/opt/ltp/testcases/bin# ./lock_torture.sh
  lock_torture 1 TINFO : estimate time 6.00 min
  lock_torture 1 TINFO : spin_lock: running 60 sec...

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034386] NMI watchdog: BUG: soft lockup - CPU#10 stuck 
for 21s! [lock_torture_wr:2337]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034389] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 
22s! [lock_torture_wr:2331]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034394] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 
22s! [lock_torture_wr:2339]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034396] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 
22s! [lock_torture_wr:2346]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034398] NMI watchdog: BUG: soft lockup - CPU#7 stuck for 
21s! [lock_torture_wr:2334]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034410] NMI watchdog: BUG: soft lockup - CPU#11 stuck 
for 22s! [lock_torture_wr:2321]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034412] NMI watchdog: BUG: soft lockup - CPU#9 stuck for 
22s! [lock_torture_wr:2333]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.038386] NMI watchdog: BUG: soft lockup - CPU#14 stuck 
for 22s! [lock_torture_wr:2327]

   
  Stack trace output:
   root@alp15:~# dmesg | more
  [ 1717.146881] lock_torture_wr R  running task
  [ 1717.146881]
  [ 1717.146885] 0  2555  2 0x0804
  [ 1717.146887] Call Trace:
  [ 1717.146894] [c00c7551b820] [c00c7551b860] 0xc00c7551b860 
(unreliable)
  [ 1717.146899] [c00c7551b860] [c00b4fb0] __do_softirq+0x220/0x3b0
  [ 1717.146904] [c00c7551b960] [c00b5478] irq_exit+0x98/0x100
  [ 1717.146909] [c00c7551b980] [c001fa54] timer_interrupt+0xa4/0xe0
  [ 1717.146913] [c00c7551b9b0] [c0002758] 
decrementer_common+0x158/0x180
  [ 1717.146922] --- interrupt: 901 at _raw_write_lock+0x68/0xc0
  [ 1717.146922] LR = torture_rwlock_write_lock+0x28/0x40 [locktorture]
  [ 1717.146927] [c00c7551bca0] [c00c7551bcd0] 0xc00c7551bcd0 
(unreliable)
  [ 1717.146934] [c00c7551bcd0] [dd4810b8] 
torture_rwlock_write_lock+0x28/0x40 [locktorture]
  [ 1717.146939] [c00c7551bcf0] [dd480578] 
lock_torture_writer+0x98/0x210 [locktorture]
  [ 1717.146944] [c00c7551bd80] [c00da4d4] kthread+0x114/0x140
  [ 1717.146948] [c00c7551be30] [c000956c] 
ret_from_kernel_thread+0x5c/0x70
  [ 1717.146951] Task dump for CPU 10:
  [ 1717.146953] lock_torture_wr R  running task0  2537  2 
0x0804
  [ 1717.146957] Call Trace:
  [ 1717.146961] [c00c7557b820] [c00c7557b860] 0xc00c7557b860 
(unreliable)
  [ 1717.146966] [c00c7557b860] [c00b4fb0] 

[Kernel-packages] [Bug 1659598] [NEW] [Dell Computer Corporation Precision 5510] mic malfunctions after updating system

[Taihsiang Ho]

Public bug reported:

Dell Computer Corporation Precision 5510 (CID 201612-25281 and
201612-25287) with pre-installed image.

[Steps To Reproduce]
Enable the proposed pocket, and then update the system by 'sudo apt-get 
dist-upgrade'

[Expected Result]
The mic works

[Actual Result]
The mic malfunctions. The mic didn't even record ambient noise.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-80-generic 3.19.0-80.88~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-80-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Fri Jan 27 00:37:34 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150721-1
InstallationDate: Installed on 2017-01-26 (0 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
SourcePackage: linux-lts-vivid
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug package-from-proposed trusty

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

Title:
  [Dell Computer Corporation Precision 5510] mic malfunctions after
  updating system

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  Dell Computer Corporation Precision 5510 (CID 201612-25281 and
  201612-25287) with pre-installed image.

  [Steps To Reproduce]
  Enable the proposed pocket, and then update the system by 'sudo apt-get 
dist-upgrade'

  [Expected Result]
  The mic works

  [Actual Result]
  The mic malfunctions. The mic didn't even record ambient noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-80-generic 3.19.0-80.88~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Jan 27 00:37:34 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2017-01-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1659598/+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 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40

[Joseph Salisbury]

Does this bug still happen with the latest Xenial updates?

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

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

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Incomplete

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Yakkety)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  hw csum failure when IPv6 interfaces configured in
  netdev_rx_csum_fault+0x38/0x40

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  Since I started using IPv6 I noticed the following kernel error:

  Thu Aug 18 15:05:01 2016] : hw csum failure
  [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P 
  OE   4.4.0-34-generic #53-Ubuntu
  [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be 
filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013
  [Thu Aug 18 15:05:01 2016]  0286 c05989f2 
8807573dfcd0 813f11b3
  [Thu Aug 18 15:05:01 2016]   0008 
8807573dfce8 8171f6e8
  [Thu Aug 18 15:05:01 2016]  0074 8807573dfd30 
8171639b fe091360
  [Thu Aug 18 15:05:01 2016] Call Trace:
  [Thu Aug 18 15:05:01 2016]  [] dump_stack+0x63/0x90
  [Thu Aug 18 15:05:01 2016]  [] 
netdev_rx_csum_fault+0x38/0x40
  [Thu Aug 18 15:05:01 2016]  [] 
skb_copy_and_csum_datagram_msg+0xeb/0x100
  [Thu Aug 18 15:05:01 2016]  [] udpv6_recvmsg+0x233/0x670
  [Thu Aug 18 15:05:01 2016]  [] inet_recvmsg+0x7e/0xb0
  [Thu Aug 18 15:05:01 2016]  [] sock_recvmsg+0x3b/0x50
  [Thu Aug 18 15:05:01 2016]  [] SYSC_recvfrom+0xe1/0x160
  [Thu Aug 18 15:05:01 2016]  [] ? wake_up_q+0x70/0x70
  [Thu Aug 18 15:05:01 2016]  [] SyS_recvfrom+0xe/0x10
  [Thu Aug 18 15:05:01 2016]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

  It repeats periodically:

  $ dmesg -T | grep 'hw csum failure' | wc -l
  201

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 19 13:47:54 2016
  HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2
  InstallationDate: Installed on 2016-04-24 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/rootpool-rootvol ro intel_iommu=on
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-D3H
  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.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614953/+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 1611901] Re: Backport Surface 3 touchscreen driver

[Joseph Salisbury]

Does this bug still exists after applying the latest updates?

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

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

** Changed in: linux (Ubuntu Yakkety)
   Status: Triaged => 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/1611901

Title:
  Backport Surface 3 touchscreen driver

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  The surface3_spi touchscreen driver finally hit Linus' kernel tree in
  v4.8rc1. It would be great if this could be backported to the kernels
  that Ubuntu ships.

  The relevant upstream commits should be:
  e399037e06beec6d190a302ff5e4fee4aae77c50 ACPI / scan: set status to 0 if _STA 
failed
  30f3a6ab44d8d06bb3d94f6320e4aa76df59d025 spi: pxa2xx: Add support for both 
chip selects on Intel Braswell
  4feacbc24eea0c5f36728017575cc0ad28d8758b Input: add new driver for the 
Surface 3
  427ee20610a7c252e99d08e08e70a4203c6059d0 Input: surface3_spi - Prepare to add 
support for Surface Pen
  72fb4765ac9eea56a94282f29cdc70706f21494e Input: surface3_spi - add surface 
pen support for Surface 3

  These should hopefully be enough to get the touchscreen working. 4.4
  is a really old kernel, so there might be some additional ACPI fixes
  needed. I'm not 100% certain. This is all that was needed on top of
  4.6.

  Config options needed on i386 and amd64:
  CONFIG_SPI_PXA2XX=m
  CONFIG_PINCTRL_CHERRYVIEW=m
  CONFIG_TOUCHSCREEN_SURFACE3_SPI=m

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.376
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1286:204c Marvell Semiconductor, Inc.
   Bus 001 Device 003: ID 045e:07de Microsoft Corp.
   Bus 001 Device 002: ID 03f0:b107 Hewlett-Packard v255w/c310w Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface 3
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash 
systemd.unit=rescue.target ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.51116.178
  dmi.board.asset.tag: 0
  dmi.board.name: Surface 3
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.51116.178:bd03/09/2015:svnMicrosoftCorporation:pnSurface3:pvrB16D1SW1C4G1X1:rvnMicrosoftCorporation:rnSurface3:rvr00:cvnMicrosoftCorporation:ct9:cvr1:
  dmi.product.name: Surface 3
  dmi.product.version: B16D1SW1C4G1X1
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611901/+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 1616949] Re: guest on bridge becomes inaccessible

[Joseph Salisbury]

** 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/1616949

Title:
  guest on bridge becomes inaccessible

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have a "virtual maas" setup where we have a maas node on a linux
  bridge (created by libvirt) and some other number of nodes on that
  same bridge.

  the maas node then controls the other nodes turning them on and off
  and generally working maas-like magic.

  In this scenario on 16.04 with when deploying 3 or so nodes at a time,
  the maas node becomes inaccessible, and as it is the root device for
  iscsi storage of the installs, the nodes fail also.

  This occurred with xenial kernel (4.4).
  Reverting the kernel to 3.19 (linux-lts-vivid) kernel fixes the problem.
  https://launchpad.net/ubuntu/+source/linux-lts-vivid
  Specifically, the fixed kernel is
  $ dpkg-query --show | grep linux-.*3.19
  linux-image-3.19.0-66-generic   3.19.0-66.74~14.04.1
  linux-image-extra-3.19.0-66-generic 3.19.0-66.74~14.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-66-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 25 12:10 seq
   crw-rw 1 root audio 116, 33 Aug 25 12:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: ppc64el
  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:
  Date: Thu Aug 25 14:37:07 2016
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   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
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0
  ProcLoadAvg: 0.40 0.28 0.46 1/1337 140794
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 3.19.0-66-generic (buildd@bos01-ppc64el-021) (gcc 
version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #74~14.04.1-Ubuntu SMP Tue Jul 
19 19:54:47 UTC 2016
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-66-generic N/A
   linux-backports-modules-3.19.0-66-generic  N/A
   linux-firmware 1.157.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.667 GHz (cpu 120)
   max: 3.691 GHz (cpu 0)
   avg: 3.689 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT is off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616949/+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 1603810] Re: Ubuntu turns monitor permanently off during boot

[Joseph Salisbury]

** 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/1603810

Title:
  Ubuntu turns monitor permanently off during boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a regression, at least trusty (and prior) worked fine on this
  hardware.

  Booting the Xenial installer image off USB also worked fine.

  The system boots fine, however the monitor is in DPMS power-off and
  does not ever turn back on. Switching VTs doesn't help, I have found
  no way to get it switch on.

  Removing '$vt_handoff' from grub resolves the problem and the system
  seems to work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jgg2224 F pulseaudio
   /dev/snd/controlC0:  jgg2224 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jul 17 14:04:30 2016
  HibernationDevice: RESUME=UUID=b254872c-e84b-427c-bebe-343c031cbdcd
  InstallationDate: Installed on 2016-04-22 (86 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/main2-xenial64 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/25/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MEVO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603810/+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 1619446] Re: mismatching headers between powerpc/ppc64el and other archs

[Joseph Salisbury]

Does this bug still exists with Xenial?

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/1619446

Title:
  mismatching headers between powerpc/ppc64el and other archs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  the header files from linux-libc-dev are causing repsnapper on
  -proposed to FTBFS on powerpc/ppc64el

  I tracked it to 2 include clauses:

  #include 
  #include 

  causing the following error on powerpc/ppc64el builds:

  following errors:

src/printer/custom_baud.cpp: In function 'bool set_custom_baudrate(int, 
int)':
src/printer/custom_baud.cpp:15:19: error: aggregate 
'set_custom_baudrate(int, int)::termios2 options' has incomplete type and 
cannot be defined
   struct termios2 options;
 ^
src/printer/custom_baud.cpp:17:26: error: 'TCGETS2' was not declared in 
this scope
   if ( ioctl( device_fd, TCGETS2,  ) < 0 ) {
^
src/printer/custom_baud.cpp:27:26: error: 'TCSETS2' was not declared in 
this scope
   if ( ioctl( device_fd, TCSETS2,  ) < 0 ) {

  Please see bug #1619100 for more info.

  Comparing the powerpc/ppc64el headers to amd64 I found that they seem
  to be missing includes to other headers under asm-generic/

  If I try to add the missing asm-generic headers:

  #include 
  #include 
  #include 
  #include 

  Then the build again fails on both powerpc/ppc64el and succeeds on all
  other archs, this time the error is:

  In file included from src/printer/custom_baud.cpp:11:0:
  /usr/include/asm-generic/termbits.h:11:8: error: redefinition of ‘struct 
termios’
   struct termios {
  ^~~
  In file included from src/printer/custom_baud.cpp:9:0:
  /usr/include/powerpc-linux-gnu/asm/termbits.h:22:8: error: previous 
definition of ‘struct termios’
   struct termios {
  ^~~
  In file included from src/printer/custom_baud.cpp:11:0:
  /usr/include/asm-generic/termbits.h:31:8: error: redefinition of ‘struct 
ktermios’
   struct ktermios {
  ^~~~
  In file included from src/printer/custom_baud.cpp:9:0:
  /usr/include/powerpc-linux-gnu/asm/termbits.h:35:8: error: previous 
definition of ‘struct ktermios’
   struct ktermios {
  ^~~~

  Finally, modifying the original includes to remove the asm/termbits.h:

  #include 
  #include 
  #include 

  Allows for the repsnapper build to succeed on all arches, including
  powerpc/ppc64el. Question is: why is this even needed?

  
  linux-libc-dev packages:
  Get:10 http://ftpmaster.internal/ubuntu yakkety/main powerpc linux-libc-dev 
powerpc 4.4.0-9136.55 [818 kB]
  Get:10 http://ftpmaster.internal/ubuntu yakkety/main ppc64el linux-libc-dev 
ppc64el 4.4.0-9136.55 [818 kB]
  Get:10 http://ftpmaster.internal/ubuntu yakkety/main amd64 linux-libc-dev 
amd64 4.4.0-9136.55 [828 kB]

  Checking the headers is seems that powerpc/ppc64el are missing
  includes for asm-generics:

  $ grep -r TCGETS2 linux-libc-dev_4.4.0-9136.55_*/
  linux-libc-dev_4.4.0-9136.55_amd64/usr/include/asm-generic/ioctls.h:#define 
TCGETS2   _IOR('T', 0x2A, struct termios2)
  linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/asm-generic/ioctls.h:#define 
TCGETS2 _IOR('T', 0x2A, struct termios2)

  $ grep -r ioctls.h linux-libc-dev_4.4.0-9136.55_*/
  
linux-libc-dev_4.4.0-9136.55_amd64/usr/include/x86_64-linux-gnu/asm/ioctls.h:#include
 
  linux-libc-dev_4.4.0-9136.55_amd64/usr/include/asm-generic/termios.h:#include 

  
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/asm-generic/termios.h:#include 

  
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/powerpc64le-linux-gnu/asm/termios.h:#include
 

  $ grep -r "termios2 {" linux-libc-dev_4.4.0-9136.55_*/ 
  linux-libc-dev_4.4.0-9136.55_amd64/usr/include/asm-generic/termbits.h:struct 
termios2 {
  
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/asm-generic/termbits.h:struct 
termios2 {

  $ grep -r termbits.h linux-libc-dev_4.4.0-9136.55_*/  
  
linux-libc-dev_4.4.0-9136.55_amd64/usr/include/x86_64-linux-gnu/asm/termbits.h:#include
 
  linux-libc-dev_4.4.0-9136.55_amd64/usr/include/asm-generic/termios.h:#include 

  
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/asm-generic/termios.h:#include 

  
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/powerpc64le-linux-gnu/asm/termios.h:#include
 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619446/+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 1622763] Re: Sennheiser Officerunner - cannot get freq at ep 0x83

[Joseph Salisbury]

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu)
   Status: Fix Committed => 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/1622763

Title:
  Sennheiser Officerunner - cannot get freq at ep 0x83

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

Bug description:
  This USB headset doesn't seem to support sample rate polling, similar
  to this issue:

  https://bugzilla.kernel.org/show_bug.cgi?id=95961

  == The problem ==

  Every time something goes to interact with the device (playing a sound
  file, opening the sound panel, opening web audio/video), a 10 second
  pause is encountered, where dmesg prints out two messages:

usb 2-1.2: 2:1: cannot get freq at ep 0x83
usb 2-1.2: 2:1: cannot get freq at ep 0x83

  Once the sound is playing, everything is fine.  These sample rate
  polls don't seem to keep happening.  After waiting for maybe 30
  seconds after sound is playing, future interactions will again trigger
  the pause.

  This 10 second pause can introduce other subtle problems.  For
  instance, google hangouts will sometimes timeout waiting for the sound
  device to respond, and the browser tab will crash or not fully load as
  a result.  The sound panel often also will not display the device in
  the list of choices, and you will have to close it out.  Sometimes
  restart pulse audio to get it to recognize the headset again.

  == The solution ==

  It is simple, add this USB ID to the
  sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function.

  case USB_ID(0x1395, 0x740a): /* Sennheiser Officerunner */

  version signature: Ubuntu 4.4.0-36.55-generic 4.4.16

  # lsusb |grep Senn
  Bus 002 Device 004: ID 1395:740a Sennheiser Communications

  # zcat  /var/log/kern.log.2.gz | grep 'cannot get' | tail -4
  Sep  2 11:26:56 helo kernel: [908040.937098] usb 2-1.2: 2:1: cannot get freq 
at ep 0x4
  Sep  2 11:27:01 helo kernel: [908045.941168] usb 2-1.2: 2:1: cannot get freq 
at ep 0x4
  Sep  2 12:18:44 helo kernel: [911149.006318] usb 2-1.2: 3:1: cannot get freq 
at ep 0x83
  Sep  2 12:18:49 helo kernel: [911154.010268] usb 2-1.2: 3:1: cannot get freq 
at ep 0x83
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  dpb   12893 F pulseaudio
   /dev/snd/controlC2:  dpb   12893 F pulseaudio
   /dev/snd/controlC1:  dpb   12893 F pulseaudio
   /dev/snd/controlC0:  dpb   12893 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a9a39ff3-c97d-471e-a0b3-518b4db8685c
  InstallationDate: Installed on 2015-03-18 (544 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
  MachineType: Hewlett-Packard HP Z620 Workstation
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia zfs zunicode zcommon 
znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=/dev/mapper/vgroot-lvroot ro console=tty0 console=ttyS4,115200 nosplash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-02-16 (210 days ago)
  UserGroups: adm cdrom dip docker libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/27/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.88
  dmi.board.asset.tag: 2UA41528ZC
  dmi.board.name: 158A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.asset.tag: 2UA41528ZC
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z620 Workstation
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/+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 1620089] Re: REGRESSION: Laptop hangs during second time it suspends

[Joseph Salisbury]

Does this bug still happen after applying the latest Xenial updates?

** 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/1620089

Title:
  REGRESSION: Laptop hangs during second time it suspends

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Kubuntu 15.10 I had a problem with the suspend functionality on my
  laptop. The second time it suspends it would hang, and a hard reset
  was necessary to resolve the problem. After the update to 16.04, the
  problem was resolved (see
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552216)

  I updated my laptop using the xenial-updates repository. After the
  upgrade to linux 4.4.0-31, the suspend issue returned. I have also
  tried later updates (4.4.0-34 and 4.4.0-36), but the issue is also
  present in those versions. I therefore still use 4.4.0-28.

  I tried bisecting, but after a few iterations it messed up my boot
  partition, and after repairing that, I no longer took the time to
  finish the bisection. (see
  https://launchpad.net/ubuntu/+source/linux/4.4.0-31.50 for changelog)

  I have a short bit (but not complete work) of the git bisect log:

  $ git bisect log
  # bad: [2a1e175b928aefed1fd3c90c98e845f764fa8684] UBUNTU: Ubuntu-4.4.0-31.50
  # good: [a6409cad137621e2b43d9f49c757fbc996539e85] UBUNTU: Ubuntu-4.4.0-28.47
  git bisect start 'Ubuntu-4.4.0-31.50' 'Ubuntu-4.4.0-28.47'
  # bad: [44d66d94ed3e6e2434b06af7180a441cbf2b9f83] UBUNTU: Ubuntu-4.4.0-29.48
  git bisect bad 44d66d94ed3e6e2434b06af7180a441cbf2b9f83


  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jan9230 F pulseaudio
  Date: Sun Sep  4 19:42:54 2016
  HibernationDevice: RESUME=UUID=321acbbf-9a6a-4825-8f47-a89d56536272
  InstallationDate: Installed on 2016-02-03 (214 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:57eb Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=43cbb8c2-c0ce-40e2-a795-3a506e63d450 ro nogpumanager quiet splash 
pci=noaer
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.160
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.77
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A4
  dmi.board.vendor: HP
  dmi.board.version: 91.1C
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.77:bd12/18/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A4:rvr91.1C:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620089/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse

[Joseph Salisbury]

Does this bug still occur after applying the latest updates?

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

** 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/1630245

Title:
  after starting ubuntu 16.10 -- no keyboard, no mouse

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  After starting Ubuntu 16.10 keyboard and mouse are dead. Since it
  works with an older kernel but not with the latest one, I'd assume the
  newer kernel does not initialize the devices the right way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  4 15:27:52 2016
  InstallationDate: Installed on 2012-12-12 (1391 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1613472] Re: Ubuntu doesn't read SD cards

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** 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/1613472

Title:
  Ubuntu doesn't read SD cards

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  Ubuntu doesn't read SD cards, I use internal card reader in my PC.

  I tried latest mainline kernel and it did not help.

  Before upgrade to this kernel, it worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tomas  3985 F pulseaudio
   /dev/snd/controlC2:  tomas  3985 F pulseaudio
   /dev/snd/controlC0:  tomas  3985 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Aug 16 00:58:27 2016
  HibernationDevice: RESUME=UUID=7b4a2bc3-8fd2-4684-b322-2c990980a5ac
  InstallationDate: Installed on 2016-07-26 (20 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  MachineType: MSI MS-7693
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=2aaf2167-aca2-41be-b11e-930925090f92 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V22.4
  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.4:bd12/21/2015: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/1613472/+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 1622894] Re: sg devices are not being created for SCSI storage controller devices starting from v4.4.0-30

[Joseph Salisbury]

Does Xenial still exhibit this bug with the latest updates?

** 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/1622894

Title:
  sg devices are not being created for SCSI storage controller devices
  starting from v4.4.0-30

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Most storage array expose a store controller device to logical unit 0.
  Following LP #1567602, when this happens and the alua driver is loaded, 
Ubuntu doesn't create the sg device for it, and linux fails to discover the 
disks that are attached to higher logical unit numbers.

  With kernel version 4.4.0-31, we tried a number of things:
  - With a disk mapped to LUN0, everything is working.
  - Without a disk mapped to LUN0, nothing works - linux doesn't see disks 
mapped to higher LUNs, calling rescan_scsi_bus throws a stack trace to syslog: 
https://gist.github.com/grzn/20c05ce3fc96062ec9572fd5b8093b55
  - When turning on SCSI logging to the maximum 
(https://access.redhat.com/articles/337903 - 0xfff), we see that after ALUA 
driver rejected the SCSI controller nothing happens (look for 18:0:0:0 which is 
a controller here 
(https://gist.github.com/grzn/f8b65dd07b2df5f3f72ca8121d8c93ad) vs 19:0:00 
which is a disk here 
(https://gist.github.com/grzn/48da86b7f7390dab2983927862cda949).
  - When removing the scsi_dh_alua driver and then reloading the lpfc driver, 
everything is working as expected when no disk is mapped to LUN0.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 18:00 seq
   crw-rw 1 root audio 116, 33 Sep 12 18:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1b089ce2-057f-44d6-9e53-5ee1b7fb5be9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6738fbd7-7243-4860-949f-717dfd084c43 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.3
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 09/17/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622894/+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 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

[Joseph Salisbury]

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

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

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  When I install Ubuntu 16.04 on my computer the screen goes blank at
  login. I can blindly login and it boots but I cannot use the display
  (external monitor through HDMI).

  I've looked online for an answer to this issue but could not find a
  solution.  However, many people report this issue in forums with the
  4.4x kernel.

  On my main computer, I upgraded from 14.04 to 16.04.1. On this
  computer I was able to switch back to the 3.13 kernel which *does
  work*.

  On the same computer, if I use a 16.04 live CD, it does the same
  thing.  The screen goes blank.

  UEFI may be part of the issue as well.  I have it disabled in bios
  (set to legacy mode) but when I first boot, it seems to go into UEFI
  mode first and then, after rebooting with  it shows
  me the list of kernels. I can select the kernel from there but if I
  use a 4.4x kernel, it blanks out at encryption passphrase screen.

  There are also people with similar issues on AskUbuntu.

  Here's some basic HW info.  If you require more, please ask.

  sudo lshw | head
  zbox
  description: Notebook
  product: ZBOX-ID18 (NA)
  vendor: ZOTAC
  version: XX
  serial: G211X
  width: 64 bits
  capabilities: smbios-2.7 dmi-2.7 vsyscall32
  configuration: boot=normal chassis=notebook family=NA sku=NA 
uuid=00020003-0004-0005-0006-000700080009
    *-core

  sudo lshw -C display
    *-display
     description: VGA compatible controller
     product: 3rd Gen Core processor Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 09
     width: 64 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:45 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user5536 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38
  InstallationDate: Installed on 2014-07-23 (743 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  MachineType: ZOTAC ZBOX-ID18
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-92-generic N/A
   linux-backports-modules-3.13.0-92-generic  N/A
   linux-firmware 1.157.2
  RfKill:

  StagingDrivers: rts5139
  Tags:  xenial staging
  Uname: Linux 3.13.0-92-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B211P011
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID18
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 10
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB211P011:bd03/13/2014:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA:
  dmi.product.name: ZBOX-ID18
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609242/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => 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/1602577

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

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

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Yakkety)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Incomplete

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

** Changed in: linux (Ubuntu)
   Status: In Progress => 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/1573062

Title:
  memory_stress_ng failing for Power architecture for 16.04

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+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 1646068] Re: bonding: don't use stale speed and duplex information

[Vincent JARDIN]

They build their own kernel, they cannot test your
http://kernel.ubuntu.com/~jsalisbury/lp1646068/trusty

>From the code review, this fix is needed.

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

Title:
  bonding: don't use stale speed and duplex information

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Trusty:
  Incomplete
Status in linux source package in Vivid:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  This upstream patch is missing (needed for all kernel between 3.9 and
  4.4 (both included)):

  266b495f11d6 bonding: don't use stale speed and duplex information
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=266b495f11d6

  Without this patch, reported speeds can be wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646068/+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 1641127] Re: Network interface is not coming up

[Joseph Salisbury]

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

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

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Network interface is not coming up

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  Fresh installation of Ubuntu 16.04 and even after executing ifconfig
   up, the network interface is not coming up. Below are the
  kernel and driver details:

  lsb_release -rd
  Description:Ubuntu 16.04
  Release:16.04

  cat /proc/version_signature
  Ubuntu 4.4.0-47.68-generic 4.4.24

  sudo lspci -vnvn > lspci-vnvn.log
  Attached the .log file

  Basically bnxt_en driver needs to be updated with latest HWRM spec.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641127/+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 1658101] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 141, failed: 0

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_15-25-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/1658101

Title:
  linux: 4.9.0-15.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.9.0-15.16 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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1658101/+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 1629784] Re: Ubuntu16.04 installation failed on IBM LE server

[Joseph Salisbury]

** 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/1629784

Title:
  Ubuntu16.04 installation failed on IBM LE server

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu OS installation is getting failed on IBM LE server. Please let
  us know whether this is System/OS specific issue.,

  Also please include "christy.rajku...@broadcom.com" in bug_list for
  any further information regarding bug.

  We tried installation with the image("ubuntu-16.04-server-ppc64el") that is 
available 
  under link: http://cdimage.ubuntu.com/releases/16.04.1/release/

  
  Please find the error message below.
   
   
   
   GNU GRUB  version 2.02~beta2-36ubuntu3
   
   
++
   |*Install
|
   | Rescue mode
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   
++
   
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, `e' to edit the commands
before booting or `c' for a command-line.
  '
   
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) 
(gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon 
Apr 18 18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/install/vmlinux tasks=standard 
pkgsel/language-pack-patterns= pkgsel/install-language-support=false --- quiet
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0ad4
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0eb8... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0ad5 -> 0x0ad5197e
  Device tree struct  0x0ad6 -> 0x0adb
   -> smp_release_cpus()
  spinning_secondaries = 191
   <- smp_release_cpus()
   <- setup_system()
  [1.277480] pci 0005:50:00.0: of_irq_parse_pci() failed with rc=-22
  [1.490146] pci 0007:80:00.0: of_irq_parse_pci() failed with rc=-22
  [3.611923] genirq: Flags mismatch irq 16.  (hvc_console) vs. 
 (hvsi)
  [3.611954] hvc_open: request_irq failed with rc -16.
  [3.611981] Warning: unable to open an initial console.
  Starting system log daemon: syslogd, klogd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629784/+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 1633391] Re: Ubuntu doesn't boot anymore {REGRESSION}

[Joseph Salisbury]

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

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

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Ubuntu doesn't boot anymore {REGRESSION}

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  After I upgraded to latest kernel, Ubuntu does not boot without messing with 
grub (I had to delete quiet splash options). 
  Before upgrade it was OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-42-generic 4.4.0-42.62
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tomas  2090 F pulseaudio
   /dev/snd/controlC1:  tomas  2090 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 14 11:32:56 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ff267c2-ec30-4f81-975c-46640f436942
  InstallationDate: Installed on 2016-09-13 (30 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 10104
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-42-generic 
root=UUID=fd50bb86-da1a-45bb-957b-ea19b330d7ff ro rootflags=subvol=@ 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ELKT31AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10104
  dmi.product.version: Lenovo C440
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633391/+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 1641593] Re: unable to enable iommu on HPE Proliant Gen9 server

[Joseph Salisbury]

** 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/1641593

Title:
  unable to enable iommu on HPE Proliant Gen9 server

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using MAAS to enable the following kernel flags on install/boot:

    iommu=pt intel_iommu=on

  in order to be able to passthrough SR-IOV VF functions to KVM guess;
  however when these options are enabled, the servers fail to install
  (see attached screenshot).

  The install eventually fails - it looks like the writes back to one of
  the disks starts to fail for some reason.

  Servers are targeted with Xenial and the release 4.4 kernel (no HWE).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641593/+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 1608236] Re: Regression: S-video output does not work

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => 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/1608236

Title:
  Regression: S-video output does not work

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  Regression. S-video output can not be used. It works by 4.4.0-22-generic.
  xrandr tells on 4.4.0-31-generic:

  TV1 unknown connection (normal left inverted right x axis y axis)
 848x480   50.00 +
 640x480   50.00 +
 1024x768  50.00  
 800x600   50.00

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1573 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jul 31 17:15:16 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (94 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 89224MG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/06
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 63ET13WW
  dmi.board.name: CAPELL VALLEY(NAPA) CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 89224MG
  dmi.product.version: 3000 C200
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1626436] Re: [4.8 regression] boot has become very slow

[Joseph Salisbury]

The patches we testing have now landed in mainline.  Does this bug still
happen on Yakkety with the latest updates?

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436/+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 1632902] Re: kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  This occurred after rebooting after running Kubuntu's Update Manager
  5.6.2 on 2016-10-12. Unfortunately, I hadn't rebooted after the last
  update that required me to do so, and thus I don't know if the problem
  was from that update or this one.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacob  1494 F pulseaudio
   /dev/snd/controlC0:  jacob  1494 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Oct 12 19:54:03 2016
  HibernationDevice: RESUME=UUID=c5fdca37-edfe-4f31-928b-970bd6696164
  InstallationDate: Installed on 2016-05-25 (140 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=c70ba36b-21e9-48ae-bf12-79060d17dcfc ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-DS3H
  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.:bvrF3:bd04/02/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632902/+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 1643622] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

[Joseph Salisbury]

Does this bug still happen on Yakkety with the latest updates?

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

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/1643622

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

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  Lenova x260 i7 laptop - screen blanks for < 1 second when this happens

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 21 16:49:37 2016
  HibernationDevice: RESUME=UUID=2a2aa818-8baa-4c43-9dad-51997def38f8
  InstallationDate: Installed on 2016-11-06 (15 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20F6CTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=a1b30635-761b-43ba-af92-7e41dcb3968c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R02ET48W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F6CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR02ET48W(1.21):bd06/01/2016:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20F6CTO1WW
  dmi.product.version: ThinkPad X260
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643622/+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